Software Engineering

327
19.3 
Software implementation tasks
19.2 
 Software engineering tasks (software 
implementation stage)
1. 
Monitor software implementation progress.
 The SWE-IPT monitors the soft-
ware implementation effort to ensure that the implementation is being accom-
plished as specified by the physical units. When software engineering proposals 
are submitted, the SWE-IPT must execute the software engineering process to 
determine the appropriate corrective action. It is acceptable for the SWE-IPT to 
reject an ECP and not deviate from the established requirements baseline and 
functional and physical architectures.
2. 
Refine the software architecture.
 The SWE-IPT should modify the software 
architecture to resolve engineering change requests that are necessary for the 
software implementation effort to be successfully accomplished. The functional 
and physical architectures may need to be modified and updated to reflect 
changes required to resolve a requested architectural deficiency. The supporting 
artifacts, models, and formal documentation should be updated, as necessary, to 
reflect the change in the software architecture.
3. 
Evaluate ECRs
. The SWE-IPT should evaluate each ECR to determine if the 
desired change can be satisfied within project cost and schedule constraints. The 
impact of the change on the software architecture must be determined and the 
level of effort required to implement the change determined. If the functional or 
allocated baselines need to be changed, the SWE-IPT should prepare an engi-
neering change proposal (ECP) to identify the extent of the change, its impact 
on the achievement of program objectives and customer satisfaction, and the 
resources necessary to implement the change proposal.