View: System Structure (Pattern of Organization)

The system structure or pattern of organization represents a logical model of the system-of-interest. This logical model is independent of any specific concrete realization of any of the systems. This logical model may also be called a conceptual model of the system-of-interest. These concepts establish the terminology used throughout the resulting system description. This conceptual model is closely associated with the identity of the system-of-interest. Changing the conceptual model may actually create a new type of system-of-interest resulting in a new name or capability (e.g. a new type of system-of-interest). This is very similar to the identification of species and the evolution of species.

Concept: Identification and Relationships

The conceptual model for an abstract system is shown below.

Abstract System Conceptual Model used as the basis for the System Architecture Description Framework

The following logic statements describe the definition of a "System" based upon the model above:

  • System Name and Class:

    • A System has one or more names

    • A System is a type of one or more System Classes.

    • A System exhibits one or more architectures.

  • System Purpose:

    • A System has one or more purposes.

    • may be supported by principles, objectives, goals.

  • System Properties:

    • A System has one or more system properties. (e.g. a set of system properties).

    • A systemic property is a type of system property.

    • Systemic Properties are properties of the whole system not found in any of the parts and emerge through interactions.

    • A quantity system property is a type of system property.

    • The quantity system property may be the sum of the property found in one or more system elements.

  • Environment:

    • A System is situated in an Environment or Context.

    • A System has a Boundary separating the inside from the outside as agreed by stakeholders.

  • System Structure (Pattern of Organization):

    • A System contains two or more System Elements. (e.g. a set of system elements)

    • A System Element has one or more relationships with another System Element or itself.

    • A system element may be both a system element and a system (e.g. a Holon).

    • A system element may be a part of another system element (Constraint: as a part of a holon).

  • Behavior (Structural Changes):

    • A System responds to external or internal triggers or events through interactions.

    • One or more interactions are needed to generate a systemic property.

    • Interactions can be from:

      • a system interacting with another system

      • a system element interacting with an element in the environment

      • a system element interacting with one or more system elements (a network)

    • To characterise the behaviour of a system, an interaction can be described as a process:

      • Cyclical / repeating Process (an operational type of process)

      • Developmental process (a life cycle change process)

    • A System is transformed by one or more life cycles (a development process)..

NOTE: Russell Ackoff has a definition of System that shows how additional constraints and attributes can be added to this list of statements. Russell Ackoff also created a "system" of system concepts. The Abstract System conceptual model can also be viewed as an "Abstract System of System Concepts".

Definition of System based upon the System Conceptual Model:

Abstract System: A set of 2 or more related system elements that interact with system elements, the environment or other systems to create one or more emergent system properties.

The boundary is a key concept of a system as the boundary provides a way to determine what is inside or outside of the system. The boundary may take the form of a system element or a systemic property depending upon characteristics of the system-of-interest.

The following system-of-interest conceptual model allows any-thing to be identified as a system-of-interest. The System-of-Interest inherits the full definition of an abstract system to enable the system-of-interest apply the definition to the identified thing.

System-of-Interest Conceptual Model with relationship to System Description, Thing and Stakeholder with Notes

The System-of-Interest model is described below:

  • The System-of-Interest

    • is a type of Abstract System. This allows the System-of-Interest to inherit all of the abstract system concepts.

    • has an identified name of a Thing

    • has associated system concerns

  • A set of stakeholders:

    • has interests in a system-of-interest.

    • has concerns about the system-of-interest

    • gain a shared understanding of the system-of-interest by using a System Description.

  • The System Description:

    • is created using a System Description ADF

    • describes a system-of-interest using the abstract system definition

    • describes a named thing as a system.

Once a set of stakeholders can be identified that have concerns or interests in the system-of-interest, these stakeholders make the system-of-interest a concrete system by identifying the thing by name that can be described in a System Description as a system. The System-of-Interest is a type of System and inherits all of the properties of the system class.

Once a named system-of-interest has been identified, the system-of-interest is then shown using a System Breakdown Structure conceptual model. The following diagram is an example system breakdown structure (using ISO 15288:2023 figure 2) and the repeating system pattern (using ISO 15288:2023 Figure 1).

System Breakdown Structure based for a Named System-of-Interest based upon Figure 2 from ISO 15288:2015

Each system element that is a holon (both system element and a system) in the system breakdown structure can be selected as a system-of-interest in their own right. Each of the holons inherit the definition of a system. The architecting process is then recursive with a new System-of-Interest. The System Breakdown Structure contains the hierarchical relationships of system elements and holons and may also identify the relationships between the various system elements and holons.

System Patterns

System patterns extend the abstract system model that is suitable for systems in general with patterns that may be useful for specific types of systems. For example, the concept of feedback and control is included in the control system pattern. The adaptive control system pattern builds on the control system pattern with a model based adaptive mechanism.

Only selected parts of the Structure for the system patterns have been included here.

The following PDF contains all of the System Descriptions for the System Patterns.

Link to the System Patterns PDF

Link to the Top System Classifications PDF