Designed Abstract Systems

View: System Name and Class

Name:  Designed Abstract System

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.

Designed Abstract Systems are those that can represent the following types of systems:

  • Symbol System (Abstract) (Language, Music, Mathematics, etc)

  • System (Abstract)

  • Money

Note: Designed Abstract Systems may be part of the development life cycle of a designed physical system. Such as a process or architecture. These would be used to help develop the designed physical system.

View: System Purpose

The purpose of a Designed Abstract System is to provide an opportunity for humans to describe a system that may not exist (architecture) or a set of concepts in the mind (conceptual model) that can be described as a system. Some of these types are:

  • Enjoyment (art, music, poetry, stories, sports, etc.)
  • Understanding the world (mathematics, science, research, etc.)
  • Understanding Systems (abstract systems)
  • Symbol Systems (Language, Mathematics, Music, etc)
View: System Properties

Systemic Measurable Variables

The emergent properties created or used through the interaction of the elements. This includes both desired and undesired.

Systemic Capabilities or Functions

  • Shared understanding or meaning
  • Communication
  • Beauty
  • Accuracy
  • Factual

System States

The various defined states that the system-of-interest can be in.

  • Architectural states
  • Transformational States
  • Operational States
View: System Stakeholders and Concerns

The stakeholders of the designed abstract system are:

  • The designers / creator s of the System (Abstract)

  • The users of the System (Abstract)

  • Those who benefit from the System (Abstract)

View: System Environment (Context)

The environment depends upon the type of Designed Abstract System. Some examples are:

  • Human activity systems (creation, maintenance, improvement, etc)
  • Designed Physical System
  • Natural System (reflection of our natural world).
View: System Structure (Pattern of Organization)

The pattern of organization depends upon the specific Designed Abstract System. Some examples are:

  • Mental images written down
  • Conceptual Models (abstract design) based upon a network of connected concepts
  • Skills development
  • Documented information about the system.
View: System Behavior (Structural Changes)

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

  • Trigger: event starting a process; Process: a response to the trigger relative to the Designed Abstract System.

Development Life Cycle Processes

  • Life cycles of development of abstract things (art, music, poetry, stories, etc).
References

The following references support this type of system-of-interest.