Software Engineering

17.2 
Software engineering integrated product team 

---

298
CHAPTER 17 
Software Requirements Definition
 
models, drawings, or other forms of documentation necessary to manage the 
development of each configuration item.
10. 
Refine project and technical plans
. The plans for the remaining stages of 
the software development project should be revisited to reflect the enriched 
understanding of the scope of the development effort. The project and techni-
cal plans have to be dynamic documents that are continually updated to reflect 
architectural decisions and authorized change proposals. Project plans must 
illuminate the scope of work remaining to be performed and amplify the prob-
ability of successful execution.
11. 
Prepare the software nomenclature register
. The SWE-IPT should prepare 
the software nomenclature register
 to designate unique identifiers, names, 
and definitions for the elements of the software architecture. Registry entries 
should include the elements identified by the operational model, and the initial 
functional and physical architectures. Data items should be defined in terms of 
their purpose, type (e.g., constant, variable, string, integer, Boolean, or date), 
security classification (if applicable), units of measurement, and acceptable 
range of values. The nomenclature register is intended to ensure that the entire 
software development team has knowledge of the authorized architectural ele-
ment names, identifiers, and definitions. This is to ensure that architectural 
elements are properly exploited and that duplicate names or identifiers are not 
assigned.
12. 
Prepare for the software requirements review (SRR)
. The SWE-IPT should pre-
pare for the SRR, which is a formal project-level review performed to exhibit 
the status of the software architecture to project management personnel, cus-
tomers, and other stakeholders. The identified risks and their abatement plans 
must be reviewed. Finally, the modifications to the WBS, specification tree, 
and project plans should be promoted. The architectural decisions that drove 
the major changes to the project plans should be identified and traced to the 
impact on the WBS, specification tree, and project plans. The software updated 
technical plans and outcome of software quality inspections and audits should 
be reported.