Introduction to Systems Engineering Fundamentals
System Science View
How can we take the many uses of the word system in everyday use and turn them into a theoretical framwork capable of supporting the application of systems thinking in such a way that it can be usefully applied across all potential appliction domains and disciplines?
The basic ideas of a system whole can be traced back to the thinking of Aristotle, and culminates in the philosopher Hegel (M’Pherson, 1974). Hegel’s view of holism states that an individual as part of an organic whole, is fully realised only through his relationship to the whole. Humans have used this idea to help explain the relationship between abstract ideas by describing them as a system of related concepts, rules or ideas, for example the natural number system or political system. We also identify systems as combinations of elements with some relationship(s) which can be best understood by considering them as a whole.
General Systems Theory (GST) (von Bertalanffy, 1968) considers the similarities between systems from different domain as a set of common system Principles and Concepts. The generally agreed System Science (glossary) definition is that:
- a closed system has no relationships with the environment.
- an open system shares input and output with its environment across the boundary.
System elements may be conceptual organizations of ideals in symbolic form or real objects, e.g. people, data, physical artifacts, etc.
- Abstract system contains only conceptual elements.
- Concrete system contains at least two elements which are objects.
This simple idea is then further elaborated through a set of principles and concepts. The following System Principles, derived from GST, relate directly to the definition of system.
- Wholeness: all systems are formed from groups of related elements into a whole with an observable shared identity in an environment.
- Behavior: all systems exhibit behaviors resulting from the interaction between elements.
- Survival Behavior: all systems have one or more stable state, and will act to sustain those states against environmental pressures of disturbances.
- Goal Seeking Behavior: some systems will exhibit more complex combinations of behavior to create the functions needed to complete specific goals or broader objectives.
- Control: all systems have regulation and control mechanism to guide their behaviors.
- Effectiveness: some systems are able to assess their effectiveness against a desired objective and to adaption and learn to sustain and improve that effectiveness
- Hierarchy: all systems form hierarchical structures, additional behaviors will emerge within the hierarchy due to interactions between system elements.
- Complexity: at some levels of a hierarchy systems are sufficiently complex that they can only be understood, used or changed through a Systems Approach.
Thus, a collection of elements which tend to group together will form themselves into coherent wholes. Once formed they will tend to stay in those structures and to combine and evolve further into more complex stable states. Systems exploit this cohesion to sustain themselves in the face of threats or environmental pressures. Some systems are created by people for specific reasons, and will need to not only exist and survie but also achieve necessary outcomes.
These system principles, and associated concepts, relate to all kinds of systems, are described in more detail in the System Concepts Knowledge Area.
Scope of System
The world we live in has numerous kinds of systems that influence our daily life. Some examples of the use of the word system in everyday usage are education system, transport system, solar system, telephone system, Dewey decimal system, weapons system, ecological system, space system, and so on; there is almost no end to the uses of the word “system” that come to mind
Using the basic System Science definition of system we can related this to the real world through three related system domains, as follows.
natural systems are real world phenomena to which we apply system thinking to help us better understand what they do and how they do it. A truly natural system would be a system we can observe and reason about, but over which we cannot exercise control, such as the solar system. As shown above, there are some managed natural systems which fall under the scope of one or both of the other domains. For engineered systems (ES) and social systems (SS), the best way to define the domain scope is to identify the types of systems for which we have authority to commit and manage resources for system creation and sustainment, and responsibility for the results. Purely technical systems such as bridges, electric autos, and power generation and distribution systems are exclusively in the ES domain, while purely human systems such as legislatures, conservation foundations, and the United Nations (UN) Security Council are exclusively in the SS domain. These systems are purely human artefacts, created to help us gain some kind of control over or protection from the real world. In System Science terms they are Concrete, Open System.
Systems common to both the SS and ES domains such as water and power management and safety governance systems, and water and power safety assurance systems, are often called sociotechnical systems . The systems common to the ES and NS domains such as dams and flood control systems might equally be termed as environ-technical systems, although the term socio-technical is often extended to cover both. The behavior of such systems is determined both by the nature of the engineered elements and by their ability to integrate with or deal with the variability of the natural and social systems in which they sit. The ultimate success of any engineered system is thus measured in its ability to contribute to the success of relevant socio (or enviro) technical systems.
System Definitions – a discussion
How is system defined in the Systems Engineering literature? Systems Engineers generally refer to their system of interest as “the system,” and their definitions of “system” tend to characterize Engineered Systems.
Two examples are:
- “A system is an array of components designed to accomplish a particular objective according to plan.” (Johnson, Kast, and Rosenzweig, 1963).
- “A system is defined as a set of concepts and/or elements used to satisfy a need or requirement.” (Miles, 1973).
The INCOSE Handbook generalizes this idea of an engineered system as: “An interacting combination of elements to accomplish a defined objective. These include hardware, software, firmware, people, information, techniques, facilities, services, and other support elements.” (INCOSE 2011).
However, engineered systems often find that their environment includes Natural Systems that don’t follow the definitions of “system” above, in that they have not been defined to satisfy a requirement or come into being to satisfy a defined objective. These include such systems as the solar system, if one’s engineered system is an interplanetary spacecraft. This has led to more general definitions of system, following the system science approach, such as the following (Aslaksen 2004):
A system consists of three related sets:
- a set of elements;
- a set of internal interactions between the elements; and
- a set of external interactions between one or more elements and the external world; i.e. interactions that can be observed from outside the system.
This definition of system enables people to reason about numerous classes of dynamical systems that involve Engineered, Social and Natural Systems.
Fundamental properties of a system described in the Systems Engineering literature include togetherness, structure, behavior and emergence. These properties provide one perspective on what a system is: “We believe that the essence of a system is togetherness, the drawing together of various parts and the relationships they form in order to produce a new whole….” (Boardman and Sauser 2008). Hitchins (2009, 59-63) refers to this systems property as cohesion.
The joining together of various parts (elements) can be related either to the structure of a system or to the behavior of a system. The structure is the static existence of the system; namely its elements and their relationships, whereas the behavior refers to the effect produced when an instance of the system is in operation. The actual behavior produced in operation leads to the fundamental property of emergence as indicated in the following quotation: “Whole entities exhibit properties which are meaningful only when attributed to the whole, not to its parts ….” (Checkland 1999)
Natural Systems and Social Systems often form part of the environment in which Engineered Systems need to exist. For a Natural or Social System simply continuing to exist, and if appropriate to adapt and grow, are sufficient. Man made Engineered and Sociotechnical systems are created with a defined purpose (Hitchins, 2009). Thus, they must not only be able to exist within their environment, but also to do the thing necessary to achieve that purpose.
As can be seen from the discussion above, most attempts to define the term system either include in them assumptions about the system domain being considered, or are are attempts to take an a system science view. We need to make a clear distinction between defining "the system" to which we wish to apply a stsrems approach; and defining "systems" as an absract idea which we can use to help understand complex situations.
The reason we use the concept of a system is to help make sense of the complexity of the real world. This is done either by creating an abstract system to help explain complex situations, such as the real number system; by creating a standardized approach to common problems, such as the Dewey system; or by agreeing on a model of a new situation to allow it to be further explored, such as a scientific theory or conceptual system design. People use systems to make sense of complexity in an individual way, and when they work together to solve problems.
In the systems approach we may consider a number pf relevant systems to fully explore problems and solutions, and a given element may be included in several system views. Thus, it is less important that we can define “the system” than it is that we can use combinations of systems to help achieve engineeering or management tasks.
We use the idea of a system context to define an Engineered system of interest (soi) , and to capture and agree the important relationships between it, the systems it works directly with and the systems which influence it in some way. This Engineered System context relates to the system science ideas of an Open, Concrete System; although such a system may include Abstract system elements. There are a number of more detailed System Concepts such as Static/Dynamic, Deterministic/Non-Determicistic/Chaotic, Homeostatic, Complexity and Adaptation, Feedback and Control, etc. which the Systems Approach must also consider.
All application of a Systems Approach (and hence of Systems Engineering) are applied to an Engineered System Context, and not to an individual system.
Alaksen,E. 2004. "A Critical Examination of the Foundations of Systems Engineering Tutorial". Paper presented at 14th Annual International Council on Systems Engineering (INCOSE) International Symposium, 20-24 June 2004, Toulouse, France.
Boardman, J. and Sauser, B. 2008. Systems Thinking: Coping with 21st Century Problems. Boca Raton, FL, USA: Taylor & Francis Inc.
Checkland, P. 1999. Systems Thinking, Systems Practice. New York, NY, USA: John Wiley & Sons.
Hitchins, Derek. 2009. "What are the General Principles Applicable to Systems?", Insight, VOL & ISSUE 59-63.
INCOSE. 2011. INCOSE Systems Engineering Handbook. Version 3.2.1. International Council on Systems Engineering. INCOSE-TP-2003-002-03.2.1
Johnson, R.A. 1963. F.W. Kast, and J.E. Rosenzweig, The Theory and Management of Systems, McGraw-Hill. NEED TO COMPLETE
Miles, R.F. (ed.)1973. System Concepts, Wiley. NEED TO COMPLETE
M’Pherson, P, K. 1974. "A perspective on systems science and systems philosophy". Futures 6(3), June 1974, p. 219-239.
von Bertalanffy, L. 1968. General system theory: Foundations, Development, Applications. Revised ed. New York, NY, USA: Braziller.
INCOSE 2011, INCOSE Systems Engineering Handbook Issue 3.2.1 INCOSE-TP-2003-002-03.2.1
von Bertalanffy, L. 1968. General System Theory: Foundations, Development, Applications. Revised ed. New York, NY: Braziller.
No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review.
--Radcock 15:55, 15 August 2011 (UTC)
--Lee 11:59, 21 August 2011 (UTC)