Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

An Implementers’ View of Systems Engineering for Systems of Systems1

[document] Submitted on 18 July, 2019 - 09:38
Keywords An Implementers’ View of Systems Engineering for Systems of Systems1 system of systems system of systems engineering systems engineering artifacts
Standards groups

Develop and Evolve SoS Architecture develops and evolves the persistent technical framework for addressing SoS evolution and a migration plan identifying risks and mitigations. The SoS architecture is the key artifact created
and used in this element. The architecture is created in the first execution of this element. Subsequently, the SoS architecture is evolved, as depicted in figure 4. The architecture provides a shared representation of the SoS technical framework and is used to inform and document decisions and guide SoS
evolution. The SoS architecture includes systems, key SoS functions, relationships and dependencies, as well as end-toend functionality, data flow and communications protocols. It is used to address possible changes in functionality, performance or interfaces. It defines the way in which the
contributing, constituent systems work together. Implementation of the architecture will add to the requirements space with changes needed in systems both in interfaces and in functionality when key to cross-cutting SoS issues.

Metadata
Date published
UNKNOWN
Document type
technical white paper
Pages
6
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
ImplementerViewSE-SoS-Final.pdf application/pdf   214.96 KB English DOWNLOAD!
File attachments
Abstract

This paper builds on and extends U.S. Department of
Defense published guidance on systems engineering (SE) of
systems of systems (SoS) by developing and presenting a view of
SoS SE that translates the SoS SE core elements, their
interrelationships, and SoS decision-making artifacts and
information from a “trapeze” model to a more familiar and
intuitive time-sequenced “wave” model representation. The
information is thus rendered in a form more readily usable by
SoS SE practitioners in the field and one that corresponds with
incremental development approaches that are the norm for SoS
capability evolution. The paper describes and motivates the
development of the wave model, discusses its key characteristics,
and provides examples of SoS efforts that reflect this view of SoS
SE. Finally, the paper describes how the information critical to
successful SoS SE is created, where it fits into the wave model,
how it evolves over time, and in which artifacts the information is
normally contained.

Defines standard
Visit also