| ... | ... | @@ -12,20 +12,19 @@ This repository design is for the automation of training and evaluation requirem |
|
|
|
|
|
|
|
1. Must contain all necessary Knowledge, Skills, Abilities, and Tasks (KSA&Ts) for the organization's work roles
|
|
|
|
2. We must be able to link every KSA&T to "one or many" work roles
|
|
|
|
3. The proficiency of each KSA&T as they relate to their respective work role/specialization.
|
|
|
|
3. The proficiency of each KSA&T as they relate to their respective work role.
|
|
|
|
4. Should be able to trace the training required to accomplish a specific KSA&T at a specific proficiency level
|
|
|
|
5. Should be able to trace the evaluation material to accomplish a specific KSA&T at a specific proficiency level
|
|
|
|
6. Individuals should be able to submit a change management request to add/remove/modify a work role/specialization KSA&T.
|
|
|
|
6. Individuals should be able to submit a change management request to add/remove/modify a work role KSA&T.
|
|
|
|
|
|
|
|
We have chosen not to use a traditional database for a few reasons: One, traditional databases do not provide the foundational tools necessary to operate in the "[Agile](https://www.guru99.com/agile-scrum-extreme-testing.html)" paradigm. Git (gitlab) provides the infrastructure for change management, distribution of work, and more. Two, gaining access to a Relational/Non-Relational database on our organization's enterprise network takes too much time. Limiting the necessary requirements to operate the tool also allows for potentially fast exportation of the code base to other networks/organizations. Three, the data relationships we are making are simplistic and a traditional database is not necessary to maintain the data as our requirements grow. We will only have a finite number of requirements ever. Gitlab comes with many different tools that we use and we will discuss these further in this document.
|
|
|
|
We have chosen not to use a traditional database for a few reasons: One, traditional databases do not provide the foundational tools necessary to operate in the "[Agile](https://www.guru99.com/agile-scrum-extreme-testing.html)" paradigm. Git (gitlab) provides the infrastructure for change management, distribution of work, and more. Two, gaining access to a Relational/Non-Relational database on our organization's enterprise network takes too much time. Limiting the necessary requirements to operate the tool also allows for potentially fast exportation of the code base to other networks/organizations.
|
|
|
|
|
|
|
|
In short, we are using [Git](https://git-scm.com/) and [Gitlab](https://gitlab.com/) for change and project management, [Gitlab continuous integration (CI) pipelines](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/) to join the data and build the presentation layer, and [Gitlab Pages](https://about.gitlab.com/stages-devops-lifecycle/pages/) to host the presentation layer to view the information. To do this we must first organize the data in a logical manner to promote scalability/sustainability. The items below will be necessary to maintain this concept.
|
|
|
|
In short, we are using [Git](https://git-scm.com/) and [Gitlab](https://gitlab.com/) for change and project management, [Gitlab continuous integration (CI) pipelines](https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/) and a disposable [MongoDB](https://www.mongodb.com/) service in the pipeline to join the data and build the presentation layer, and [Gitlab Pages](https://about.gitlab.com/stages-devops-lifecycle/pages/) to host the presentation layer to view the information. To do this we must first organize the data in a logical manner to promote scalability/sustainability. The items below will be necessary to maintain this concept.
|
|
|
|
|
|
|
|
1. The MTTL repo will not contain an MTTL file. Instead, the MTTL file will be an artifact that is produced in the repo's CI/CD pipeline.
|
|
|
|
1. The MTTL repo will not contain a single MTTL file. Instead, the MTTL file will be an artifact that is produced in the repo's CI/CD pipeline.
|
|
|
|
2. The meat of what makes the MTTL repo is the [knowledge, skill, ability, and task files](#knowledge-skill-ability-and-task-json-files), and the [WORK-ROLES.json and SPECIALIZATIONS.json files](#work-roles-and-specializations-json-files) that contain a list of all work-roles and specializations.
|
|
|
|
- The [knowledge, skill, ability, and task files](#knowledge-skill-ability-and-task-json-files) will be dictionaries of all of the knowledge, skills, abilities, tasks that are required for the organization. These items will only have the KSA&T to KSA&T relationship information, topic information, requirement source information, and available training and evaluation information. Proficiency is work role/specialization specific and will be located inside the TTL files respectively.
|
|
|
|
- The [WORK-ROLES.json and SPECIALIZATIONS.json files](#work-roles-and-specializations-json-files) will be dictionaries of work role/specialization specific information which will contain work role/specialization repository URLs that will contain rel-link information to populate training and evaluation coverage of the KSAs
|
|
|
|
- The [PROF.json file](#prof-json-file) (or proficiency JSON file) is a dictionary of proficiency standards from different organizations. This file will be used as a "Rosetta Stone" to easily compile an MTTL with different proficiency standards if an organization requires it.
|
|
|
|
- The [knowledge, skill, ability, and task files](#knowledge-skill-ability-and-task-json-files) will be datasets of all of the knowledge, skills, abilities, tasks that are required for the organization. These items will only have the KSA&T to KSA&T relationship information, topic information, requirement source information, and available training and evaluation information. Proficiency of work roles/specializations will be located inside the TTL files in the 'work-roles' folder respectively.
|
|
|
|
- The [WORK-ROLES.json and SPECIALIZATIONS.json files](#work-roles-and-specializations-json-files) will be dictionaries of work role/specialization specific information which will contain work role/specialization repository URLs that will contain progression information for the [MTTL Training Roadmap](https://90cos.gitlab.io/mttl/#/roadmap)
|
|
|
|
|
|
|
|
## Data file Directory Structure
|
|
|
|
|
| ... | ... | |
