Software Engineering

19.1 
Products of software implementation
The products identified in this section do not represent the complete set of products 
generated during software implementation. The following artifacts identify the soft-
ware implementation artifacts that concern the software engineering effort:
1. 
Software unit programmatic design diagrams.
 The programmatic design dia-
grams provide a representation of the computational logic for each software 
unit. They should address control, data, and procedural flows necessary to trans-
form inputs into desired outputs. Emphasis should be placed on the algorithmic 
computation of data items that result in accurate data values, fault handling 
mechanisms, and procedural calls or interfaces to other software elements. Each 
software unit must be evaluated to ensure that it satisfies its specification that 
involves performance and other nonfunctional requirements (e.g., size, resource 
utilization).
2. 
Programmatic design descriptions.
 Programmatic design descriptions provide 
a narrative, procedural explanation of how the software unit design achieves it 
data processing responsibilities.
3. 
Software unit test scenarios.
 Unit test scenarios should identify the data sets, 
procedures, and expected outcomes for each unit test case. Unit test scenarios 
describe how a software unit will be verified to confirm that it satisfies its struc-
tural unit specification. Unit test scenarios should be developed and documented 
in the software development folders (SDFs).
4. 
Software unit source code files.
 Source code files represent the computing lan-
guage-specific data declarations and instructions that constitute a software mod-
ule, routine, procedure, or class. A source code file is intended to be compiled 
into an executable binary file that can be run on the target computing system.