UNCLASSIFIED - NO CUI

Updated Change Management Workflow authored by Ezra J Holmes's avatar Ezra J Holmes
...@@ -61,16 +61,21 @@ MTTL Repo ...@@ -61,16 +61,21 @@ MTTL Repo
- **SPECIALIZATIONS.json**: file to designate specialization progression and repository links to material on training/evaluations - **SPECIALIZATIONS.json**: file to designate specialization progression and repository links to material on training/evaluations
## Change Management Workflow ## Change Management Workflow
The change management workflow is depicted below.
```mermaid ```mermaid
graph TD; graph TD;
START-->ISSUE([Request Change via Issue]) NEW_REQUEST[NEW CUSTOMER REQUEST]-->|ASSIGN POC| REVIEW(REVIEW REQUEST);
ISSUE-->CHANGE([Make change on dedicated branch]) REVIEW-->CLARIFY(CLARIFY REQUEST);
CHANGE-->IF_PASS{CI/CD} CLARIFY-->RESPONSE{CUSTOMER RESPONSE};
IF_PASS-- Failed -->CHANGE RESPONSE-- Revise -->CLARIFY;
IF_PASS-- Passed -->IF_APPROVE{Approved} RESPONSE-- Accept -->CREATE(CREATE MERGE REQUEST);
IF_APPROVE-- No -->CHANGE CREATE-->UPDATE(MAKE UPDATES);
IF_APPROVE-- Yes -->FINISH[Merged to Master] UPDATE-->GOVREVIEW(GOV/CUSTOMER REVIEW);
GOVREVIEW-->APPROVED{CHANGES APPROVED};
APPROVED-- No -->UPDATE;
APPROVED-- Yes -->DONE[MERGED TO MASTER]
APPROVED-- Rejected -->DEAD[CLOSED WITHOUT MERGE]
``` ```
## WORK-ROLES and SPECIALIZATIONS JSON Files ## WORK-ROLES and SPECIALIZATIONS JSON Files
... ...
......