|
Tag: visualeditor-switched |
| Line 1: |
Line 1: |
| | ---- | | ---- |
| − | '''''Lead Author:''''' ''Rick Adcock'', '''''Contributing Authors:''''' ''Hillary Sillitto, Sarah Sheard'' | + | '''''Lead Author:''''' ''Rick Adcock'', '''''Contributing Authors:''''' ''Janet Singer, Duane Hybertson'' |
| | ---- | | ---- |
| − | This article is part of the [[Systems Fundamentals]] knowledge area (KA). It gives the background of and an indication of current thinking on {{Term|Complexity (glossary)|complexity}} and how it influences {{Term|Systems Engineering (glossary)|systems engineering}} (SE) practice. | + | This knowledge area (KA) provides a guide for applying the {{Term|Systems Approach (glossary)|systems approach}} as a means of identifying and understanding complex problems and opportunities, synthesizing possible alternatives, analyzing and selecting the best alternative, implementing and approving a solution, as well as deploying, using and sustaining {{Term|Engineered System (glossary)|engineered system}} solutions. The active participation of stakeholders during all the activities of the systems approach is the key to the success of the systems approach. |
| | | | |
| − | Complexity is one of the most important and difficult to define {{Term|System (glossary)|system}} {{Term|Concept (glossary)|concepts}}. Is a system's complexity in the eye of the beholder, or is there inherent complexity in how systems are organized? Is there a single definitive definition of complexity and, if so, how can it be assessed and {{Term|Measure (glossary)|measured}}? This topic will discuss how these ideas relate to the general definitions of a system given in [[What is a System?]], and in particular to the different {{Term|Engineered System (glossary)|engineered system}} {{Term|Context (glossary)|contexts}}. This article is closely related to the [[Emergence|emergence]] topic that follows it.
| + | In an engineered system context, a systems approach is a holistic approach that spans the entire life of the system; however, it is usually applied in the development and operational/support life cycle stages. This knowledge area defines a systems approach using a common language and intellectual foundation to ensure that practical systems concepts, principles, patterns and tools are accessible to perform {{Term|Systems Engineering (glossary)|systems engineering}} (SE), as is discussed in the introduction to [[Foundations of Systems Engineering|Part 2: Foundations of Systems Engineering]]. |
| | | | |
| − | ==Defining System Complexity== | + | ==Topics== |
| − | Complexity has been considered by a number of authors from various perspectives; some of the discussions of complexity relevant to systems are described in the final section of this article. Sheard and Mostashari (Sheard and Mostashari 2011) synthesize many of these ideas to categorize complexity as follows:
| + | Each part of the Guide to the SE Body of Knowledge (SEBoK) is divided into KAs, which are groupings of information with a related theme. The KAs, in turn, are divided into topics. This KA contains the following topics: |
| − | #'''Structural Complexity''' looks at the system elements and relationships. In particular, structural complexity looks at how many different ways system elements can be combined. Thus, it is related to the potential for the system to adapt to external needs.
| + | *[[Overview of the Systems Approach]] |
| − | #'''Dynamic Complexity''' considers the complexity which can be observed when systems are used to perform particular tasks in an environment. There is a time element to dynamic complexity. The ways in which systems interact in the short term is directly related to system behavior; the longer-term effects of using systems in an environment is related to system evolution.
| + | *[[Engineered System Context]] |
| − | #'''Socio-Political Complexity''' considers the effect of individuals or groups of people on complexity. People-related complexity has two aspects. One is related to the perception of a situation as complex or not complex, due to multiple stakeholder {{Term|Viewpoint (glossary)|viewpoints}} within a system context and social or cultural biases which add to the wider influences on a system context. The other involves either the “irrational” behavior of an individual or the swarm behavior of many people behaving individually in ways that make sense; however, the {{Term|Emergence (glossary)|emergent}} behavior is unpredicted and perhaps counterproductive. This latter type is based on the interactions of the people according to their various interrelationships and is often graphed using systems dynamics formalisms.
| + | *[[Identifying and Understanding Problems and Opportunities]] |
| | + | *[[Synthesizing Possible Solutions]] |
| | + | *[[Analysis and Selection between Alternative Solutions]] |
| | + | *[[Implementing and Proving a Solution]] |
| | + | *[[Deploying, Using, and Sustaining Systems to Solve Problems]] |
| | + | *[[Applying the Systems Approach]] |
| | | | |
| − | Thus, complexity is a measure of how difficult it is to understand how a system will behave or to predict the consequences of changing it. It occurs when there is no simple relationship between what an individual element does and what the system as a whole will do, and when the system includes some element of adaptation or problem solving to achieve its goals in different situations. It can be affected by objective attributes of a system such as by the number, types of and diversity of system elements and relationships, or by the subjective perceptions of system observers due to their experience, knowledge, training, or other sociopolitical considerations.
| + | ==Systems Approach== |
| | + | This KA describes a high-level framework of activities and principles synthesized from the elements of the systems approach, as described earlier in Part 2 of the SEBoK, and is mapped to the articles [[Concepts of Systems Thinking]], [[Principles of Systems Thinking]], and [[Patterns of Systems Thinking]]. The concept map in Figure 1 describes how the knowledge is arranged in this KA and the linkage to the KA in Part 3. |
| | | | |
| − | This view of complex systems provides insight into the kind of system for which systems thinking and a {{Term|Systems Approach (glossary)|systems approach}} is essential.
| + | [[File:Fig_1_Systems_Engineering_and_the_Systems_Approach_RA.png|thumb|650px|center|'''Figure 1. Systems Engineering and the Systems Approach.''' (SEBoK Original)]] |
| | | | |
| − | ==Complexity and Engineered Systems==
| + | According to Jackson et al. (2010, 41-43), the systems approach to engineered systems is a problem-solving paradigm. It is a comprehensive problem identification and resolution approach based upon the principles, concepts, and tools of {{Term|Systems Thinking (glossary)|systems thinking}} and {{Term|Systems Science (glossary)|systems science}}, along with the concepts inherent in engineering problem-solving. It incorporates a holistic systems view that covers the larger context of the system, including engineering and operational environments, stakeholders, and the entire life cycle. |
| | + | |
| | | | |
| − | The different perspectives on complexity are not independent when considered across a {{Term|System Context (glossary)|systems context}}. The structural complexity of a {{Term|System-of-Interest (glossary)|system-of-interest}} (SoI) may be related to dynamic complexity when the SoI also functions as part of a wider system in different problem scenarios. People are involved in most system contexts, as part of the problem situation, as system elements and part of the operating environment. The human activity systems which we create to identify, design, build and support an {{Term|Engineered System (glossary)|engineered system}} and the wider social and business systems in which they sit are also likely to be complex and affect the complexity of the systems they produce and use.
| + | Successful systems practice should not only apply systems thinking to the system being created but should also utilize systems thinking in consideration of the way in which work is planned and conducted. See [[Enabling Systems Engineering|Part 5: Enabling Systems Engineering]] for further discussions on how individuals, teams, businesses and enterprises may be enabled to perform systems engineering. |
| | | | |
| − | Sheard and Mostashari (2011) show the ways different views of complexity map onto {{Term|Product System (glossary)|product system}}, {{Term|Service System (glossary)|service system}} and {{Term|Enterprise System (glossary)|enterprise system}} contexts, as well as to associated development and sustainment systems and project {{Term|Organization (glossary)|organizations}}. Ordered systems occur as system {{Term|Component (glossary)|components}} and are the subject of traditional {{Term|Engineering (glossary)|engineering}}. It is important to understand the behaviors of such systems when using them in a complex system. One might also need to consider both truly random or chaotic natural or social systems as part of the context of an engineered system. The main focus for systems approaches is '''organized complexity '''(see below). This kind of complexity cannot be dealt with by traditional analysis techniques, nor can it be totally removed by the way we design or use solutions. A systems approach must be able to recognize and deal with such complexity across the life of the systems with which it interacts.
| + | ==References== |
| | | | |
| − | Sillitto (2014) considers the link between the types of system complexity and system {{Term|Architecture (glossary)|architecture}}. The ability to understand, manage and respond to both objective and subjective complexity in the problem situation, the systems we develop or the systems we use to develop and sustain them is a key component of the [[Systems Approach Applied to Engineered Systems]] and hence to the practice of systems engineering.
| |
| − |
| |
| − | ==Origins and Characteristics of Complexity==
| |
| − |
| |
| − | This section describes some of the prevailing ideas on complexity. Various authors have used different language to express these ideas. While a number of common threads can be seen, some of the ideas take different {{Term|Viewpoint (glossary)|viewpoints}} and may be contradictory in nature.
| |
| − |
| |
| − | One of the most widely used definitions of complexity is the degree of difficulty in predicting the properties of a system if the properties of the system's parts are given (generally attributed to Weaver). This, in turn, is related to the number of {{Term|Element (glossary)|elements}} and connections between them. Weaver (Weaver 1948) relates complexity to types of elements and how they interact. He describes simplicity as {{Term|Problem (glossary)|problems}} with a finite number of variables and interaction, and identifies two kinds of complexity:
| |
| − | #'''Disorganized Complexity''' is found in a system with many loosely coupled, disorganized and equal elements, which possesses certain average properties such as temperature or pressure. Such a system can be described by “19th Century” statistical analysis techniques.
| |
| − | #'''Organized Complexity''' can be found in a system with many strongly coupled, organized and different elements which possess certain {{Term|Emergence (glossary)|emergent}} properties and phenomena such as those exhibited by economic, political or social systems. Such a system cannot be described well by traditional analysis techniques.
| |
| − |
| |
| − | Weaver's ideas about this new kind of {{Term|Complex (glossary)|complex}} problem are some of the foundational ideas of {{Term|Systems Thinking (glossary)|systems thinking}}. (See also [[Systems Thinking]].)
| |
| − |
| |
| − | Later authors, such as Flood and Carson (1993) and Lawson (2010), expand organized complexity to systems which have been organized into a {{Term|Structure (glossary)|structure}} intended to be understood and thus amenable to {{Term|Engineering (glossary)|engineering}} and {{Term|Life Cycle Management (glossary)|life cycle management}} (Braha et al. 2006). They also suggest that disorganized complexity could result from a heterogeneous {{Term|Complex (glossary)|complex}} system evolving without explicit architectural {{Term|Control (glossary)|control}} during its life (complexity creep). This is a different use of the terms “organized” and “disorganized” to that used by Weaver. Care should be taken in mixing these ideas
| |
| − |
| |
| − | Complexity should not be confused with "complicated". Many authors make a distinction between ordered and disordered collections of elements.
| |
| − |
| |
| − | Ordered systems have fixed relationships between elements and are not adaptable. Page (2009) cites a watch as an example of something which can be considered an ordered system. Such a system is complicated, with many elements working together. Its {{Term|Component (glossary)|components}} are based on similar technologies, with clear mapping between form and function. If the operating {{Term|Environment (glossary)|environment}} changes beyond prescribed limits, or one key component is removed, the watch will cease to perform its {{Term|Function (glossary)|function}}.
| |
| − |
| |
| − | In common usage, {{Term|Chaos (glossary)|chaos}} is a state of disorder or unpredictability characterized by elements which are not interconnected and behave randomly with no adaptation or control. Chaos Theory (Kellert 1993) is applied to certain dynamic systems (e.g., the weather) which, although they have structure and relationships, exhibit unpredictable {{Term|Behavior (glossary)|behavior}}. These systems may include aspects of randomness but can be described using deterministic models from which their behavior can be described given a set of initial conditions. However, their structure is such that (un-measurably) small perturbations in inputs or environmental conditions may result in unpredictable changes in behavior. Such systems are referred to as deterministically chaotic or, simply, chaotic systems. {{Term|Simulation (glossary)|Simulations}} of chaotic systems can be created and, with increases in computing power, reasonable predictions of behavior are possible at least some of the time.
| |
| − |
| |
| − | On a spectrum of order to complete disorder, complexity is somewhere in the middle, with more flexibility and change than complete order and more stability than complete disorder (Sheard and Mostashari 2009).
| |
| − |
| |
| − | Complex systems may evolve “to the edge of chaos,” resulting in systems which can appear deterministic but which exhibit counter intuitive behavior compared to that of more ordered systems. The statistics of chance events in a complex system are often characterized by a power-law distribution, the “signature of complexity” (Sheard 2005). The power-law distribution is found in a very wide variety of natural and man-made phenomena, and it means that the probability of a low probability—large impact event is much higher than a Gaussian distribution would suggest. Such a system may react in a non-linear way to exhibit abrupt phase changes. These phase changes can be either reversible or irreversible. This has a major impact on engineered systems in terms of the occurrence, impact and public acceptance of {{Term|Risk (glossary)|risk}} and failure.
| |
| − |
| |
| − | '''Objective''' complexity is an attribute of complex systems and is a measure of where a system sits on this spectrum. It is defined as the extent to which future {{Term|State (glossary)|states}} of the system cannot be predicted with certainty and precision, regardless of our knowledge of current state and history. Subjective complexity is a measure of how easy it is for an observer to understand a system or predict what it will do next. As such, it is a function of the perspective and comprehension of each individual. It is important to be prepared to mitigate subjective complexity with consistent, clear communication and strong {{Term|Stakeholder (glossary)|stakeholder}} engagement (Sillitto 2009).
| |
| − |
| |
| − | The literature has evolved to a fairly consistent definition of the characteristics of system elements and relationships for objective systems complexity. The following summary is given by Page (2009):
| |
| − | #'''Independence''': Autonomous system elements which are able to make their own decisions, influenced by information from other elements and the adaptability algorithms the autonomous elements carry with themselves (Sheard and Mostashari 2009).
| |
| − | #'''Interconnectedness''': System elements connect via a physical connection, shared data or simply a visual awareness of where the other elements are and what they are doing, as in the case of the flock of geese or the squadron of aircraft.
| |
| − | #'''Diversity''': System elements which are either technologically or functionally different in some way. For example, elements may be carrying different {{Term|Adaptability (glossary)|adaptability}} algorithms.
| |
| − | #'''Adaptability''': Self-organizing system elements which can do what they want to do to support themselves or the entire system in response to their environment (Sheard and Mostashari 2009). Adaptability is often achieved by human elements but can be achieved with software. Pollock and Hodgson (2004) describe how this can be done in a variety of complex system types, including power grids and {{Term|Enterprise (glossary)|enterprise}} systems.
| |
| − |
| |
| − | Due to the variability of human behavior as part of a system and the perceptions of people outside the system, the inclusion of people in a system is often a factor in their complexity. People may be viewed as observing systems or as system elements which contribute to the other types of complexity (Axelrod and Cohen 1999). The rational or irrational behavior of individuals in particular situations is a vital factor in respect to complexity (Kline 1995). Some of this complexity can be reduced through education, training and familiarity with a system. Some is irreducible and must be managed as part of a problem or solution. Checkland (1999) argues that a group of stakeholders will have its own world views which lead them to form different, but equally valid, understandings of a system context. These differences cannot be explained away or analyzed out, and must be understood and considered in the formulation of problems and the creation of potential solutions.
| |
| − |
| |
| − | Warfield (2006) developed a powerful methodology for addressing complex issues, particularly in the socio-economic field, based on a relevant group of people developing an understanding of the issue in the form of a set of interacting problems - what he called the “problematique”. The complexity is then characterized via several {{Term|Measure (glossary)|measures}}, such as the number of significant problems, their interactions and the degree of consensus about the nature of the problems. What becomes clear is that how, why, where and by whom a system is used may all contribute to its perceived complexity.
| |
| − |
| |
| − | Sheard and Mostashari (2011) sort the attributes of complexity into causes and effects. Attributes that cause complexity include being non-linear; emergent; chaotic; adaptive; tightly coupled; self-organized; decentralized; open; political (as opposed to scientific); and multi-scale; as well as having many pieces. The effects of those attributes which make a system be perceived as complex include being uncertain; difficult to understand; unpredictable; uncontrollable; unstable; unrepairable; unmaintainable and costly; having unclear cause and effect; and taking too long to build.
| |
| − |
| |
| − | ==References==
| |
| − |
| |
| | ===Works Cited=== | | ===Works Cited=== |
| − | | + | Jackson, S., D. Hitchins, and H. Eisner. 2010. "[[What is the Systems Approach?]]." INCOSE ''Insight,'' vol. 13, no. 1, pp. 41-43. |
| − | Axelrod, R. and M. Cohen. 1999. ''Harnessing Complexity: Organizational Implications of a Scientific Frontier''. New York, NY, USA: Simon and Schuster.
| |
| − | | |
| − | Braha, D., A. Minai, and Y. Bar-Yam (eds.). 2006. ''Complex Engineered Systems: Science Meets Technology''. New York, NY, USA: Springer.
| |
| − | | |
| − | Checkland, P. 1999. ''Systems Thinking, Systems Practice''. New York, NY, USA: John Wiley & Sons.
| |
| − | | |
| − | Flood, R. L., and E.R. Carson. 1993. ''Dealing with Complexity: An Introduction to The Theory and Application of Systems Science'', 2nd ed. New York, NY, USA: Plenum Press.
| |
| − | | |
| − | Lawson, H. W. 2010. ''A Journey Through the Systems Landscape''. Kings College, UK: College Publications.
| |
| − | | |
| − | Kellert, S. 1993. ''In the Wake of Chaos: Unpredictable Order in Dynamical Systems'', Chicago, IL, USA: University of Chicago Press.
| |
| − | | |
| − | Kline, S. 1995. ''Foundations of Multidisciplinary Thinking''. Stanford, CA, USA: Stanford University Press.
| |
| − | | |
| − | Page, Scott E. 2009. ''Understanding Complexity''. Chantilly, VA, USA: The Teaching Company.
| |
| − | | |
| − | Pollock, J.T. and R. Hodgson. 2004. ''Adaptive Information''. Hoboken, NJ, USA: John Wiley & Sons.
| |
| − | | |
| − | Senge, P.M. 1990. ''The Fifth Discipline: The Art & Practice of The Learning Organization''. New York, NY, USA: Doubleday/Currency.
| |
| − | | |
| − | Sheard, S.A. 2005. "Practical applications of complexity theory for systems engineers". ''Proceedings of the Fifteenth Annual International Council on Systems Engineering,'' vol. 15, no. 1.
| |
| − | | |
| − | Sheard, S.A. and A. Mostashari. 2009. "Principles of complex systems for systems engineering." ''Systems Engineering'', vol. 12, no. 4, pp. 295-311.
| |
| − | | |
| − | Sheard, SA. and A. Mostashari. 2011. "Complexity types: From science to systems engineering." Proceedings of the 21st Annual of the International Council on Systems Engineering (INCOSE) International Symposium, Denver, Colorado, USA, 20-23 June 2011.
| |
| − | | |
| − | Sillitto, H. 2014. "Architecting Systems - Concepts, Principles and Practice", London, UK: College Publications.
| |
| − | | |
| − | Warfield, J.N. 2006. ''An Introduction to Systems Science''. London, UK: World Scientific Publishing.
| |
| − | | |
| − | Weaver, W. 1948. "Science and complexity." ''American Science,'' vol. 36, pp. 536-544.
| |
| | | | |
| | ===Primary References=== | | ===Primary References=== |
| − | Flood, R. L., & E.R. Carson. 1993. ''[[Dealing with Complexity]]: An Introduction to The Theory and Application of Systems Science'', 2nd ed. New York, NY, USA: Plenum Press.
| + | Checkland, P. 1999. ''[[Systems Thinking, Systems Practice]]''. New York, NY, USA: John Wiley & Sons. |
| − | | |
| − | Page, Scott E. 2009. ''[[Understanding Complexity]]''. Chantilly, VA, USA: The Teaching Company.
| |
| − | | |
| − | Sheard, S.A. and A. Mostashari. 2009. "[[Principles of Complex Systems for Systems Engineering|Principles of complex systems for systems engineering]]". ''Systems Engineering'', vol. 12, no. 4, pp. 295-311.
| |
| − | | |
| − | ===Additional References===
| |
| − | | |
| − | Ashby, W.R. 1956. ''An Introduction to Cybernetics''. London, UK: Chapman and Hall.
| |
| − | | |
| − | Aslaksen, E.W. 2004. "System thermodynamics: A model illustrating complexity emerging from simplicity". ''Systems Engineering'', vol. 7, no. 3. Hoboken, NJ, USA: Wiley.
| |
| − | | |
| − | Aslaksen, E.W. 2009. ''Engineering Complex Systems: Foundations of Design in the Functional Domain''. Boca Raton, FL, USA: CRC Press.
| |
| − | | |
| − | Aslaksen, E.W. 2011. "Elements of a systems engineering ontology". Proceedings of SETE 2011, Canberra, Australia.
| |
| | | | |
| − | Eisner, H. 2005. ''Managing Complex Systems: Thinking Outside the Box''. Hoboken, NJ, USA: John Wiley & Sons.
| + | Hitchins, D. 2009. "What are the General Principles Applicable to Systems?" INCOSE ''Insight,'' vol. 12, no. 4. |
| | | | |
| − | Jackson, S., D. Hitchins, and H. Eisner. 2010. “What is the Systems Approach?” INCOSE ''Insight,'' vol. 13, no. 1, April, pp. 41-43, 2010. | + | Jackson, S., D. Hitchins, and H. Eisner. 2010. "[[What is the Systems Approach?]]" INCOSE ''Insight,'' vol. 13, no. 1, pp. 41-43. |
| | | | |
| − | MITRE. 2011. "Systems engineering strategies for uncertainty and complexity." ''Systems Engineering Guide.'' Accessed 9 March 2011. Available at: http://www.mitre.org/work/systems_engineering/guide/enterprise_engineering/comprehensive_viewpoint/sys_engineering_strategies_uncertainty_complexity.html.
| + | ===Additional References=== |
| | + | Hitchins, D. 2007. ''Systems Engineering: A 21st Century Systems Methodology''. Hoboken, NJ, USA: John Wiley & Sons. |
| | | | |
| − | Ryan, A. 2007. "Emergence is coupled to scope, not Level, complexity". A condensed version appeared in INCOSE ''Insight'', vol. 11, no. 1, January, pp. 23-24, 2008.
| + | Lawson, H. 2010. ''A Journey Through the Systems Landscape''. London, UK: College Publications, Kings College. |
| | | | |
| − | Sillitto H.G. 2009. "On systems architects and systems architecting: Some thoughts on explaining the art and science of system architecting." Proceedings of the 19th Annual International Council on Systems Engineering (INCOSE) International Symposium, Singapore, 20-23 July 2009.
| + | Senge, P. M. 1990. ''The Fifth Discipline: The Art and Practice of the Learning Organization''. New York, NY, USA: Doubleday/Currency. |
| | | | |
| | ---- | | ---- |
| − | <center>[[Types of Systems|< Previous Article]] | [[Systems Fundamentals|Parent Article]] | [[Emergence|Next Article >]]</center> | + | <center>[[Fundamentals for Future Systems Engineering|< Previous Article]] | [[Foundations of Systems Engineering|Parent Article]] | [[Overview of Systems Approaches|Next Article >]]</center> |
| | | | |
| − | <center>'''SEBoK v. 2.0, released 2 June 2019'''</center> | + | <center>'''SEBoK v. 2.1, released 31 October 2019'''</center> |
| | | | |
| − | [[Category:Part 2]][[Category:Topic]] | + | [[Category:Part 2]][[Category:Knowledge Area]] |
| − | [[Category:Systems Science]]
| |
Lead Author: Rick Adcock, Contributing Authors: Janet Singer, Duane Hybertson
This knowledge area (KA) provides a guide for applying the systems approachsystems approach as a means of identifying and understanding complex problems and opportunities, synthesizing possible alternatives, analyzing and selecting the best alternative, implementing and approving a solution, as well as deploying, using and sustaining engineered systemengineered system solutions. The active participation of stakeholders during all the activities of the systems approach is the key to the success of the systems approach.
In an engineered system context, a systems approach is a holistic approach that spans the entire life of the system; however, it is usually applied in the development and operational/support life cycle stages. This knowledge area defines a systems approach using a common language and intellectual foundation to ensure that practical systems concepts, principles, patterns and tools are accessible to perform systems engineeringsystems engineering (SE), as is discussed in the introduction to Part 2: Foundations of Systems Engineering.
Topics
Each part of the Guide to the SE Body of Knowledge (SEBoK) is divided into KAs, which are groupings of information with a related theme. The KAs, in turn, are divided into topics. This KA contains the following topics:
Systems Approach
This KA describes a high-level framework of activities and principles synthesized from the elements of the systems approach, as described earlier in Part 2 of the SEBoK, and is mapped to the articles Concepts of Systems Thinking, Principles of Systems Thinking, and Patterns of Systems Thinking. The concept map in Figure 1 describes how the knowledge is arranged in this KA and the linkage to the KA in Part 3.
Figure 1. Systems Engineering and the Systems Approach. (SEBoK Original)
According to Jackson et al. (2010, 41-43), the systems approach to engineered systems is a problem-solving paradigm. It is a comprehensive problem identification and resolution approach based upon the principles, concepts, and tools of systems thinkingsystems thinking and systems sciencesystems science, along with the concepts inherent in engineering problem-solving. It incorporates a holistic systems view that covers the larger context of the system, including engineering and operational environments, stakeholders, and the entire life cycle.
Successful systems practice should not only apply systems thinking to the system being created but should also utilize systems thinking in consideration of the way in which work is planned and conducted. See Part 5: Enabling Systems Engineering for further discussions on how individuals, teams, businesses and enterprises may be enabled to perform systems engineering.
References
Works Cited
Jackson, S., D. Hitchins, and H. Eisner. 2010. "What is the Systems Approach?." INCOSE Insight, vol. 13, no. 1, pp. 41-43.
Primary References
Checkland, P. 1999. Systems Thinking, Systems Practice. New York, NY, USA: John Wiley & Sons.
Hitchins, D. 2009. "What are the General Principles Applicable to Systems?" INCOSE Insight, vol. 12, no. 4.
Jackson, S., D. Hitchins, and H. Eisner. 2010. "What is the Systems Approach?" INCOSE Insight, vol. 13, no. 1, pp. 41-43.
Additional References
Hitchins, D. 2007. Systems Engineering: A 21st Century Systems Methodology. Hoboken, NJ, USA: John Wiley & Sons.
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.
< Previous Article | Parent Article | Next Article >
SEBoK v. 2.1, released 31 October 2019
