Software Engineering

316
CHAPTER 18 
Software Architecture Definition
 6. 
Database query specification.
 The database query specification should be 
developed to provide general query instructions for prevalent database trans-
actions. The data persistence functions identified during functional analysis 
should be the basis for database query specifications. Each data persistence 
function involves preservation of data in a repository or database manage-
ment system (DBMS). Structured query language (SQL) instructions provide 
a standard set of instructions or commands for adding, deleting, updating, 
and sorting information in a DBMS. The database query specification should 
establish the set of privileged database queries that provide access to restricted 
database information.
 7. 
Structural unit specifications.
 Each structural unit must be specified to permit it 
to be designed with leveraging the selected programming language expressions or 
constructs. A software development folder (SDF) should be established for each 
structural unit to provide a repository for all subsequent implementation artifacts. 
The requirements specification associated with each physical unit should be 
retained in the appropriate SDF. Structural unit specifications should express the 
coalesced functional requirements, interfaces, and programmatic design charac-
teristics (e.g., budgeted line of code) to which each unit must conform.
 8. 
Updated requirements traceability matrix.
 The requirements traceability matrix 
should be updated to reflect the structural unit linkages to the functional archi-
tecture, as well as the extended reach of software integration strategy.
 9. 
Updated software nomenclature register.
 The software nomenclature register 
should be updated to reflect the physical architecture and ensure that each 
structural unit, component, assembly, and data element name and definition is 
unique throughout the software architecture.
10. 
Finalize the software implementation plan.
 The software implementation plan 
should be finalized to identify the level of effort and resources necessary to 
accomplish the implementation stage of the software development effort. The 
implementation plan must refine the work packages to reflect the evolving 
structural configuration and software integration strategy.
11. 
Finalize the computing environment implementation plan.
 The computing envi-
ronment implementation plan should be finalized to identify the level of effort 
and resources necessary to establish and qualify the computing environment 
that will be utilized during software acceptance testing. The computing environ-
ment implementation plan must refine the work packages to reflect the resource 
requirements for the computing environment implementation organization.
12. 
Software test plan.
 The software test and evaluation organization must expand 
the software test plan to establish test scenarios and procedures. The software 
test plan must refine work packages to reflect the effort associated with prepar-
ing for and conducting software acceptance testing.
13. 
Post-development process implementation plan.
 The post-development 
implementation organization must expand the post-development process 
implementation plan to reflect the effort associated with implementing the 
post-development processes. The post-development process implementation 

---