4. Determining the boundaries of object A
a. Physical
b. Functional
c. Behavioral
5. Determining the boundaries of object B
a. Physical
b. Functional
c. Behavioral
6. Specifying the interactions that characterize the relation(s) between
object A and object B
a. Boundary conditions
b. EMMI
7. Describing the interaction(s) between object A and object B
a. Inputs
b. Outputs
i. Performance(s)
ii. Loss(es)
8. Describing the characteristics of the interaction(s) that serve as a
function for the user (verification)
a. Conditions for the function (test planning)
b. Boundaries to enable the function (test planning)
c. Limits of the function (test planning)
9. Attempting to demonstrate the function
a. Test setup
b. Measurement approach and meaning
10. Evaluating the conditions for the functions* of
a. Reliability
b. Availability
c. Vulnerability
d. Susceptibility
11. Analyzing the boundaries that enable the function
* For the purposes of this book, we define requirements only in terms of functional require
ments. In other words, there is no accommodation for “nonfunctional requirements.” As
such, reliability, availability, vulnerability, susceptibility (and the like genre of “ilities”) are
deemed as functional requirements with target performance(s) and quality requirements
representing deviations from those requirements.
122
Engineering Systems Integration
­