Name: System of Systems
Based on: System (Abstract)
Abstract System: This system has been identified as an abstract system that cannot be implemented directly. The abstract system establishes a shared pattern of characteristics that any system can use to describe its unique characteristics when referenced in the 'based on' list above. These references are described using a generalization association in UML.
The System of Systems is very similar to the basic system structure. There are a number of conditions that the system elements of the System of Systems must meet.
See Wikipedia System of Systems
For example, an industry can be considered a System of Systems. This would include a number of independent enterprises to participate in this SoS.
There are other areas that may be considered a System of Systems:
- smart cities
- Information Systems (The Internet or IoT).
The remainder of this system description is the same as a system. This description will evolve as more work is done highlighting some of the variations in approach.
Appendix G of ISO 15288:2015 also provides a good description of a System of Systems.
The primary purpose or reason for being for the system-of-interest is included in this section. There may be a number of purpose statements that may be based upon the estakeholders identified below.
The purpose statement is for the whole System-of-Interest situated in its environment.
Systemic Measurable Variables
The measurable variables for the system-of-interest provide the means of determining performance, quality, response times, and effectiveness of change. The variable description included in this specification provides the key and top level variables for this system-of-interest. These variables provide meaning for stakeholders externally and internally. A full definition of these system variables contains the following:
- Units and definition of the scale.
- How and when the variable is measured
- Key markers on the scale: Minimum acceptable, Objective (goal), Target, Stretch, etc.
Systemic Capabilities or Functions
The capabilities of the system-of-interest or the individual functions that transform inputs to desired results are identified in this section. There may be a number of capabilities or functions this system-of-interest provides. Some of these are desired and expected and some may be undesired and unexpected.
System States
There may be a number of types of states that may be defined in this section. The various defined states that the system-of-interest can be in.
- Architectural states: These are states that align to a specific version of the Architecture Description for a system. For example, there may be:
- a Current Architecture Description,
- a number of intermediate Architecture Descriptions (representing key operational points)
- and the Target Architecture Description for a revision.
- Transformational States: These transformational states tend to align to key stages in the development process. These are typically
- Designed
- Built
- Integrated
- Released
- Operational
- Operational States: Operational States relate to the type of outcomes that are expected. Some may relate to the delivery of products and services while others relate to specific operational states and objectives. These states are identified in the capabilities and processes used during operation. These operational states are designed and implemented into the way the operational system performs.
Identify the key stakeholders and their concerns for this system-of-interest. Each stakeholder is identified and their concerns and interests are identified. The list below is an example. Each system-of-interest will have a specific set of stakeholders and concerns.
- Owner / manager: Is this a sustainable / stable system? will our customers be satisfied?
- System Architect: Are the system concepts understood? Are the system properties sufficient to deliver the objectives?
- People in the environment Will the people confirm or use the benefits of the system?
- Change Agents Do we have the ability to change the system in a planned way?
- People who are part of the system Will I understand my contribution to the system?
The system-of-interest interacts with the environment as an open system. This section describes some of the key interactions and the relationship to the various properties of the system.
The environment and the potential impacts on the system-of-interest.
this section includes
- Transactional: This typically relates to an exchange of goods or services with a customer or user. Typically the system-of-interest may have influence without control.
- Contextual: This type of environment cannot be influenced or controlled but may have an impact on the system. This includes natural disasters, wars, etc.
- Regulatory: Regulatory requirements constrain the actions of the system-of-interest and may require specific types of interaction with external regulators.
The system-of-interest is situated in its environment as an open system. The environment that can influence the purpose and properties as a whole of the system-of-interest are identified here. These can be:
- the physical environment (weather, earthquakes, rivers, etc.)
- local communities
- transportation
- the government
- competition
- education.
- etc.
For systems that can be described in a similar way to Figure 2 Page 12 of ISO 15288:2015, each of the systems identified in the hierarchy will participate as a system element and have the containing system serve as an environment. This provides a fractal model for systems within an overall system-of-interest.
The following diagram shows the relationship of a System of Systems to the System Conceptual Model.
This model of a System of Systems that the main elements of this type of system are constituent systems. These constituent systems form a network of interacting systems. These systems are generally autonomous and independently managed and aligned to create a result that is more than any one of the constituent systems. These constituent systems are both a system element of a system and a system in their own right.
Note: These constituent systems may become a separate system-of-interest and may be described using a Link to the System Description Template.
The relationships are defined in this section. The System Behavior section describes the interactions and processes that create the emergent properties of the System of Systems.
Configuration / Scenario:
Describes any configuration / scenario attributes for a specific system-of-interest. This may not be appropriate for all system descriptions (e.g. patterns or abstract systems).
Cyclical (Repeating / Regular) Processes
Some of the systems involved in the creation, of the system-of-interest, may need to create, change or transform system elements within the system-of-interest. These life cycles relate to the system elements that make up the system-of-interest. This also provides a structure for the various state transitions for the system-of-interest (e.g. architectural, transformational and operational).
Development Life Cycle Processes
These life cycle elements describe the overall approach to create, use and release / retire a system-of-interest. This is the normal life cycle of the system-of-interest. This section identifies the systems involved in the elements of this life cycle. These may be external systems or internal systems that create this system-of-interest
The following references support this type of system-of-interest.
Click here to provide feedback on this topic