(1) A hierarchy is an arrangement of items (objects, names, values, categories, etc.) in which the items are represented as being "above," "below," or "at the same level as" one another. Levels in a hierarchy may also represent authority, control or ownership of lower levels (command structure). (Oxford English Dictionary 2012)
(2) Organisation of system elements into groups of (sub-)system wholes, based on relative strenght of element cohesion. (Simon 1962)
(3) The hierarchy principle of systems, is the consequential concept of simultaneous multiple containment of one system by many containing systems. (Checkland 1999)
(4) An abstract view of a defined system that is developed to meet some need. The system results from an analysis that decomposes a system into constituent elements at two or more levels. Often based around a defined taxonomy of levels covering System, element, Subsystem, assembly, components and parts. (INCOSE 2011)
(1) Oxford English Dictionary, s.v. "Hierarchy."
(2) Simon, H.A. 1962. "The Architecture of Complexity." Proceedings of the American Philosophical Society. 106(6) (December 12, 1962): 467-482.
(3) Checkland, P. 1999. Systems Thinking, Systems Practice. New York: John Wiley & Sons.
(4) INCOSE. 2012. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2.
(1) is a general dictionary definition.
(2) is a system science definition, relates to the tendency of natural systems to form hierarchies and os the stability of hierarchical structures for man made systems.
(3) Soft systems definition, allowing for a system to be associated with several hierarchical structure, one of the factors leading to multiple stakeholder viewpoints. This is the definition which should be used for problem systems.
(4) defines the man-made hierarchy created within a system. The use of a standard taxonomy defined against the types of technology and use of system elements can be useful as a common language for defining production of support processes. Care must be taken to avoid this leading to a reductionist approach. This is the definition which should be used for hard solution systems.
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.blog comments powered by Disqus