1/24
Looks like no tags are added yet.
flowdown
how something in a larger context applies to a smaller part, way of creating new requirements
derivation
new knowledge/requirements found during the design process implemented as a requirement, way of creating new requirements
allocation
assigning requirements to parts
ov-1
High-Level Operational Concept Graphic puts an operational situation or scenario into context and is a tool for discussion and presentation
OV-2
shows flow of information, resources, and material between some origin and the location where it is required
OV-3
represents the resource flow discussed in OV-2 + more information in a table
OV-4
Organizational Relationships Chart
OV-5a
development of OV-4, shows operation being decomposed as opposed to organization
OV-5b
chronological version of decomposed operation
OV-6a
details rules and restrictions a system operates under
OV-6b
shows completeness, changes, and state changes similar to OV-5b
OV-6c
acts like OV-6b but multiple states concurrently
SV-1
shows what reources and through what interface the resources are passed through for individual systems
SV-2
adds technical detail to SV-1
SV-3
table version of SV-1
SV-4
basically OV-5b aad shows what is stored in each system
SV-5a
connects operational aspects to physical systems. needs OV-5b and SV-4
SV-5b
maps operational aspects to systems themselves
SV-6
log showing what resource is being exchanged, to/from where, and what interface is being used
SV-7
gives further context to characteristics of systems and what resources are being used (needs SV-6)
SV-8
shows how main systems and external systems change and interact over time
SV-9
shows the technological impacts on an SoS' operations. Can be categorized as benign or destructive.
SV-10a
sets rules for systems in terms of resource flows and interfaces
SV-10b
does same as OV-6 but for systems view with order of system state changes due to internal or external input
SV-10c
systems version of OV-6c, shows concurrent or chronological events for all systems