Thorough system design definitions concentrate on
requirements and interface control documents,
among others – static system definitions. It
isn’t possible, however, to build a competent
system if its behavior isn’t defined and if there
isn’t a dynamic system definition. This
presentation proposes hierarchical sets of
correlated/linked execution threads from the
Concept of Operations (CONOPS) for the system all
the way down to the programmer’s use cases.
The approach begins with a set of system threads indicating how the design responds to and covers the requirements of the CONOPS. It continues with lower-level execution threads for the segments of the system, then for the components of the segments, then for the configuration items within the components, and finally for the software. Each thread is linked to the higher-level thread(s) to which it contributes and to the lower-level thread(s) contributing to it.
Advantages of the approach throughout the system life-cycle are discussed.
Track 3Salon I
Wednesday June 20, 2007
3:10 PM - 3:55 PM