Difference between revisions of "Overview of the Systems Approach"

From SEBoK
Jump to navigation Jump to search
Line 1: Line 1:
Jackson and colleagues (2010, 41-43) define the [[Systems Approach]] as a set of top-level principles that provide the foundation of Systems Engineering. The Systems Approach implies taking a [[holistic (glossary)]] view of a system that includes the full life cycle as well as specific knowledge of systems engineering technical and management methods.  
+
According to Ryan (2008) the Systems Approach and Systems Engineering formed and grew somewhat independently, but the two of them are highly related and compatible.  Both are based on the concepts of Systems Thinking that produces a broader understanding of the challenges being faced, the environment, and all of the related parts of the solution.  Good Systems Engineering process and lifecycle descriptions are based upon the Systems Approach.  The best Systems Engineers must be good systems thinkers and should understand and apply a Systems Approach to all challenges and problems that they face in the conduct of Systems Engineering.
 +
 
 +
The Systems Approach is essential when reductionist assumptions that the whole system has properties derived directly from the properties of their components, no longer applies to the system of interest.  Emergent properties at the system level, which cannot be derived from a summation of the subsystem properties, necessitate a holistic Systems Approach.  The Systems Approach is often invoked in applications beyond product systems. For example, the Systems Approach may be used in the educational domain. According to Biggs (1993), the system of interest includes “the student, the classroom, the institution, and the community.”  In fact as the founder of Systems Thinking and Systems Science Ludvig von Bertalanffy (1968) point out: “Systems are Everywhere.”
 +
 +
The goal of the Systems Approach is to understand the organization of ideas and to view problems and solutions holistically. It views the organization of ideas as a compound concept that incorporates structure, dynamics and behavior of related systems associated with a problem and its possible solutions. It has resulted in a loosely connected set of techniques, where each technique contributes some insight on systemic aspects of problem or solution systems and helps us deal with different aspects of [Complexity (glossary)].  Because no single technique provides a complete understanding, knowledge of the limits of applicability of individual techniques is central to any systems approach.  The application of the Systems Approach must consider whether what kind of approach is applicable to the system of interest and select appropriate techniques accordingly.    Within the Systems Approach we might employ [[Hard System (glossary)]] and [[Soft System (glossary)]] tools and techniques suggested by Checkland (1999), Boardman and Sauser (2008), Senge (1990), and others.
  
 
Lawson (2010) describes the relationship among the [[Systems Approach]], [[Systems Thinking]], and Systems Engineering as a mind-set to “think” and “act” in terms of systems.  Developing this mind-set is promoted by several paradigms including the [[System Coupling Diagram (glossary)]], which includes the elements Situation System, Respondent System, and System Assets (Figure 1).
 
Lawson (2010) describes the relationship among the [[Systems Approach]], [[Systems Thinking]], and Systems Engineering as a mind-set to “think” and “act” in terms of systems.  Developing this mind-set is promoted by several paradigms including the [[System Coupling Diagram (glossary)]], which includes the elements Situation System, Respondent System, and System Assets (Figure 1).
Line 15: Line 19:
 
Since the premise is that the Systems Approach is a mind-set prerequisite to Systems Engineering, it can be said that projects and programs executed with this mind-set are more likely to solve the problem or achieve the opportunity identified in the beginning (ADD CITATION TO SUPPORT THIS ASSERTION).
 
Since the premise is that the Systems Approach is a mind-set prerequisite to Systems Engineering, it can be said that projects and programs executed with this mind-set are more likely to solve the problem or achieve the opportunity identified in the beginning (ADD CITATION TO SUPPORT THIS ASSERTION).
  
The Systems Approach is often invoked in applications beyond product systems. For example, the Systems Approach may be used in the educational domain. According to Biggs (1993), the system of interest includes “the student, the classroom, the institution, and the community.”
 
 
The [[Systems Approach]] must be viewed in the context of [[Systems Thinking ]] as discussed by Checkland (1999) and by Edson (2008). According to Checkland (1999, 318), [[Systems Thinking (glossary)]] is “''an epistemology which, when applied to human activity is based on basic ideas of systems''.”
 
 
Senge (1990) provides an expanded definition as follows:  “''Systems thinking is a discipline for seeing wholes. It is a framework for seeing interrelationships rather than things, for seeing patterns of change rather than static "snapshots." It is a set of general principles -- distilled over the course of the twentieth century, spanning fields as diverse as the physical and social sciences, engineering, and management. During the last thirty years, these tools have been applied to understand a wide range of corporate, urban, regional, economic, political, ecological, and even psychological systems. And systems thinking is a sensibility for the subtle interconnectedness that gives living systems their unique character.''”
 
  
[[Systems Thinking]] has two parts. The first part is a set of [[System Concepts|principles and concepts]] to assist in learning how to think in terms of systems. 
 
  
The second part is the Systems Approach. It is a "how-to" approach -- an abstract set of principles applied to problem situations and potential solutions. [[Systems Approach (glossary)]] relates Systems Thinking to:  
+
The Systems Approach described in the SEBoK uses the following general problem solving steps:
 
#The exploration of potential [[problem (glossary)]] or [[opportunity (glossary)]] situations;  
 
#The exploration of potential [[problem (glossary)]] or [[opportunity (glossary)]] situations;  
 
#The application of [[System Analysis (glossary)|analysis (glossary)]], [[synthesis (glossary)]], and [[proving (glossary)]] to system solutions;
 
#The application of [[System Analysis (glossary)|analysis (glossary)]], [[synthesis (glossary)]], and [[proving (glossary)]] to system solutions;

Revision as of 15:58, 7 February 2012

According to Ryan (2008) the Systems Approach and Systems Engineering formed and grew somewhat independently, but the two of them are highly related and compatible. Both are based on the concepts of Systems Thinking that produces a broader understanding of the challenges being faced, the environment, and all of the related parts of the solution. Good Systems Engineering process and lifecycle descriptions are based upon the Systems Approach. The best Systems Engineers must be good systems thinkers and should understand and apply a Systems Approach to all challenges and problems that they face in the conduct of Systems Engineering.

The Systems Approach is essential when reductionist assumptions that the whole system has properties derived directly from the properties of their components, no longer applies to the system of interest. Emergent properties at the system level, which cannot be derived from a summation of the subsystem properties, necessitate a holistic Systems Approach. The Systems Approach is often invoked in applications beyond product systems. For example, the Systems Approach may be used in the educational domain. According to Biggs (1993), the system of interest includes “the student, the classroom, the institution, and the community.” In fact as the founder of Systems Thinking and Systems Science Ludvig von Bertalanffy (1968) point out: “Systems are Everywhere.”

The goal of the Systems Approach is to understand the organization of ideas and to view problems and solutions holistically. It views the organization of ideas as a compound concept that incorporates structure, dynamics and behavior of related systems associated with a problem and its possible solutions. It has resulted in a loosely connected set of techniques, where each technique contributes some insight on systemic aspects of problem or solution systems and helps us deal with different aspects of [Complexity (glossary)]. Because no single technique provides a complete understanding, knowledge of the limits of applicability of individual techniques is central to any systems approach. The application of the Systems Approach must consider whether what kind of approach is applicable to the system of interest and select appropriate techniques accordingly. Within the Systems Approach we might employ hard system and soft system tools and techniques suggested by Checkland (1999), Boardman and Sauser (2008), Senge (1990), and others.

Lawson (2010) describes the relationship among the Systems Approach, Systems Thinking, and Systems Engineering as a mind-set to “think” and “act” in terms of systems. Developing this mind-set is promoted by several paradigms including the system coupling diagram , which includes the elements Situation System, Respondent System, and System Assets (Figure 1).

Figure 1. System Coupling Diagram (Lawson 2010) Reprinted with permission of Harold "Bud" Lawson.
  • Situation System – The problem or opportunity situation, either unplanned or planned. The situation may be the work of nature, man-made, a combination of both natural and man-made, or a postulated situation that is to be used as a basis for deeper understanding and training (for example, business games or military exercises).
  • Respondent System – The system created to respond to the situation. The parallel bars indicate that this system interacts with the situation and transforms the situation to a new situation. Based on the situation that is being treated, a Respondent System can have several names such as Project, Program, Mission, Task Force, or in a scientific context, Experiment. One of the system elements of this system is a control element that directs the operation of the Respondent System in its interaction with the situation. This element is based on an instantiation of a Control System asset, for example a Command and Control System, or a control process of some form.
  • System Assets – The sustained assets of one or more enterprises to be used in responding to situations. System assets must be adequately managed throughout the life cycle so they will perform their function when instantiated in a Respondent System. These assets are the primary objects for Systems Engineers. Examples of assets include value-added products or services, facilities, instruments and tools, and abstract systems such as theories, knowledge, processes, and methods.

This model portrays the essence of a Systems Approach and is applicable to Product Systems Engineering, Service Systems Engineering, and Enterprise Systems Engineering. Furthermore, it forms the basis for Systems of Systems in which System Assets from multiple actors combine to form a Respondent System to address a given situation.

Since the premise is that the Systems Approach is a mind-set prerequisite to Systems Engineering, it can be said that projects and programs executed with this mind-set are more likely to solve the problem or achieve the opportunity identified in the beginning (ADD CITATION TO SUPPORT THIS ASSERTION).


The Systems Approach described in the SEBoK uses the following general problem solving steps:

  1. The exploration of potential problem or opportunity situations;
  2. The application of analysis , synthesis , and proving to system solutions;
  3. Ownership and use of systems within an enterprise .

All of the above are considered within a concurrent , recursive , and iterative life cycle approach. Items 1 and 3 are part of the business cycles of providing stakeholder value (Ring 2004) within an enterprise, whereas item 2 can be mapped directly to product system , service system , and enterprise system Engineering. A distinction is made here between the normal business of an enterprise and the longer term strategic activities of Enterprise Systems Engineering.

The Systems Approach employs hard system and soft system tools and techniques suggested by Checkland (1999), Boardman and Sauser (2008), Senge (1990), and others.

When parts of the approach are executed in the real world of an engineered system , a number of engineering and management disciplines emerge, including systems engineering . SEBoK Parts 3 and 4 contain a detailed guide to Systems Engineering. Part 5 provides a guide to the relationships between Systems Engineering and the organizations, and Part 6 a guide to the relationship between Systems Engineering and other disciplines. More detailed discussion of how the System Approach relates to these engineering and management disciplines is included in the Applying the Systems Approach topic in this knowledge area.


References

Citations

Biggs, J.B. 1993. "From Theory to Practice: A Cognitive Systems Approach". Journal of Higher Education & Development. Available from http://www.informaworld.com/smpp/content~db=all~content=a758503083.

Boardman, J. and B. Sauser 2008. Systems Thinking - Coping with 21st Century Problems. Boca Raton, FL, USA: CRC Press.

Checkland, P. 1999. Systems Thinking, Systems Practice. New York, NY, USA: John Wiley & Sons.

Edson, R. 2008. Systems Thinking. Applied. A Primer. Arlington, VA, USA: Applied Systems Thinking (ASysT) Institute, Analytic Services Inc.

Lawson, H. 2010. A Journey Through the Systems Landscape. London, UK: College Publications, Kings College.

Senge, P.M. 1990. The Fifth Discipline: The Art and Practice of the Learning Organization. New York, NY, USA: Doubleday/Currency.

Ring J. 2004. "Seeing an Enterprise as a System". INCOSE Insight. 6(2) (January 2004): 7-8.

Primary References

Boardman, J. and B. Sauser 2008. Systems Thinking: Coping with 21st Century Problems. Boca Raton, FL, USA: CRC Press.

Checkland, P. 1999. Systems Thinking, Systems Practice. New York, NY, USA: John Wiley & Sons.

Senge, Peter. M. 1990. The Fifth Discipline: The Art and Practice of the Learning Organization. New York: Doubleday/Currency.

Additional References

Biggs, J.B. 1993. "From Theory to Practice: A Cognitive Systems Approach". Journal of Higher Education & Development.. Available from http://www.informaworld.com/smpp/content~db=all~content=a758503083.

Edson, R. 2008. Systems Thinking. Applied. A Primer. Arlington, VA, USA: Applied Systems Thinking (ASysT) Institute, Analytic Services Inc.

Lawson, H. 2010. A Journey Through the Systems Landscape. London, UK: College Publications, Kings College.


<- Previous Article | Parent Article | Next Article ->