Software Engineering

1. 
Each structural component must be independently testable against its compo-
nent integration specification.
2. 
Structural components should provide a significantly more capable element in 
the structural integration hierarchy. Therefore, each structural component should 
be able to be traced to a significant task within the operational or business pro-
cess, or should satisfy one or more of the software requirements.
3. 
Structural components should be able to be tested as a “black box” with an 
emphasis on ensuring the internal interfaces among integrated subcompo-
nents and/or units, and the measurement of component performance. Black 
box testing does not evaluate the internal logic, behaviors, or algorithms of 
integrated elements. It should focus on exercising the integrated functionality 
and performance of the structural component that results from the integration 
effort.
4. 
The number of integration tasks involved with the software integration 
strategy should be condensed as much as possible. Excessive integration tasks 
will increase software development costs and extend the software develop-
ment schedule. The burden associated with software integration and testing 
will occur many times throughout the software product life cycle with each 
update or new release of the product. Therefore, each integration task should be 
scrutinized to ensure that it represents a necessary and cost-effective integration 
activity.

---