Software Engineering

318
CHAPTER 18 
Software Architecture Definition
4. 
Update risk mitigation plans.
 Risk assessment records should be prepared 
for those physical unit risks that could not be eliminated or avoided and still 
threaten the achievement of program objectives. Risk mitigation plans should 
be identified for each identified risk. Risk assessment records should capture the 
results of the risk assessment, including the probability of occurrence and the 
consequences should the risk be realized. Risk mitigation plans should identify 
the course of action being taken to monitor and prevent the risk from occurring, 
the criteria that would make the risk unacceptable to proceed as planned, and the 
contingency plans that would be executed.
5. 
Revise the WBS
. Once the physical architecture is complete and the software 
implementation plan finalized, the program WBS should be adjusted to reflect 
the improved understanding of the scope of the software implementation and 
test and evaluation work effort. The software engineering–related work pack-
ages, associated tasks, and resource allocations must be assigned to the tasks 
identified in the software implementation plan.
6. 
Refine technical plans.
 The technical plans must be revisited for the remaining 
stages of the software development program to have them reflect the remain-
ing scope of the work effort. The technical plans must be living documents and 
reflect the design decisions that are made and their impact on the scope of work 
to be performed. The software engineering–related work packages, associated 
task descriptions, and resource allocations must be aligned with the tasks iden-
tified in the plan. The resulting software engineering plan should identify the 
tasks to be performed throughout the remaining stages of the software develop-
ment effort. The SWE-IPT must synthesize organizational plans and refine the 
integrated technical plan and schedule (ITP/ITS).
7. 
Update the software nomenclature register.
 The software architecture dictionary 
should be updated and expanded to reflect the physical architecture. The names of all 
physical units and components must be added to the software architecture dictionary.
8. 
Prepare for the CDR.
 The SWE-IPT must prepare for the architecture CDR. The 
purpose of the CDR is to present the consistent requirements baseline and func-
tional and physical architectures to program management, customers, or other 
stakeholders. The design decisions that drove the major changes to the program 
structure and plans should be identified and traced to the impact on the WBS and 
program plans. The software test planning, including quality assurance inspec-
tion and audits conducted during the detailed architecture definition, should be 
addressed. The risks identified and their risk abatement plans should be reviewed.