UNCLASSIFIED - NO CUI
This project is archived. Its data is
read-only
.
Changes
Page history
Updated Change Management Workflow
authored
Aug 07, 2020
by
Ezra J Holmes
Show whitespace changes
Inline
Side-by-side
Home.md
View page @
667a4b93
...
...
@@ -61,16 +61,21 @@ MTTL Repo
-
**SPECIALIZATIONS.json**
: file to designate specialization progression and repository links to material on training/evaluations
## Change Management Workflow
The change management workflow is depicted below.
```
mermaid
graph TD;
START-->ISSUE([Request Change via Issue])
ISSUE-->CHANGE([Make change on dedicated branch])
CHANGE-->IF_PASS{CI/CD}
IF_PASS-- Failed -->CHANGE
IF_PASS-- Passed -->IF_APPROVE{Approved}
IF_APPROVE-- No -->CHANGE
IF_APPROVE-- Yes -->FINISH[Merged to Master]
NEW_REQUEST[NEW CUSTOMER REQUEST]-->|ASSIGN POC| REVIEW(REVIEW REQUEST);
REVIEW-->CLARIFY(CLARIFY REQUEST);
CLARIFY-->RESPONSE{CUSTOMER RESPONSE};
RESPONSE-- Revise -->CLARIFY;
RESPONSE-- Accept -->CREATE(CREATE MERGE REQUEST);
CREATE-->UPDATE(MAKE UPDATES);
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
...
...
...
...