04:61

Continued from A1...

 

Environment and boundaries
Systems theory views the world as a complex system of interconnected parts. One scopes a system by defining its boundary; this means choosing which entities are inside the system and which are outside—part of the environment. One can make simplified representations (models) of the system in order to understand it and to predict or impact its future behavior. These models may define the structure and behavior of the system.
Natural and human-made systems
There are natural and human-made (designed) systems. Natural systems may not have an apparent objective but their behavior can be interpreted as purposeful by an observer. Human-made systems are made with variable purposes that are achieved by some action performed by or with the system. The parts of a system must be related; they must be "designed to work as a coherent entity" — otherwise they would be two or more distinct systems.
Theoretical framework
Most systems are open systems, exchanging matter and energy with its surroundings; like a car, a coffeemaker, or Earth. A closed system exchanges energy, but not matter, with its environment; like a computer or the project Biosphere 2. An isolated system exchanges neither matter nor energy with its environment. A theoretical example of such system is the Universe.
Process and transformation process
An open system can also be viewed as a bounded transformation process, that is, a black box that is a process or collection of processes that transforms inputs into outputs. Inputs are consumed; outputs are produced. The concept of input and output here is very broad. For example, an output of a passenger ship is the movement of people from departure to destination.
System model
A system comprises multiple views. Man-made systems may have such views as concept, analysis, design, implementation, deployment, structure, behavior, input data, and output data views. A system model is required to describe and represent all these views.
Systems architecture
A systems architecture, using one single integrated model for the description of multiple views, is a kind of system model.

subsystem

A subsystem is a set of elements, which is a system itself, and a component of a larger system. The IBM Mainframe Job Entry Subsystem family (JES1, JES2, JES3, and their HASP/ASP predecessors) are examples. The main elements they have in common are the components that handle input, scheduling, spooling and output; they also have the ability to interact with local and remote operators.

A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. The Data tests are performed to verify the correctness of the individual subsystem configuration data (e.g. MA Length, Static Speed Profile, …) and they are related to a single subsystem in order to test its Specific Application (SA).