Use Case 0: Systems Engineering Novices

From SEBoK
Jump to navigation Jump to search

Some users of the Systems Engineering Body of Knowledge (SEBoK) may be new to the field. This article provides recommended readings for such a user.

Learn the Basic Terms

As discussed in the Introduction to the SEBoK, there are four key terms that you should first understand when learning about systems engineering (SE):

  • A system is “a collection of elements and a collection of inter-relationships amongst the elements such that they can be viewed as a bounded whole relative to the elements around them. Open Systems exists in an environment described by related systems with which they may interact and conditions to which they may respond. While there are many definitions of the word “system,” the SEBoK authors believe that this definition encompasses most of those which are relevant to SE.
  • An engineered system is an open system of technical or sociotechnical elements that exhibits emergent properties not exhibited by its individual elements. It is created by and for people; has a purpose, with multiple views; satisfies key stakeholders’ value propositions; has a life cycle and evolution dynamics; has a boundary and an external environment; and is part of a system-of-interest hierarchy.
  • Systems engineering is “an interdisciplinary approach and means to enable the realization of successful (engineered) systems” (INCOSE 2012). It focuses on holistically and concurrently understanding stakeholder needs; exploring opportunities; documenting requirements; and synthesizing, verifying, validating, and evolving solutions while considering the complete problem, from system concept exploration through system disposal.
  • A systems engineer is “a person who practices systems engineering” as defined above, and whose systems engineering capabilities and experience include sustained practice, specialization, leadership, or authority over SE activities. These activities may be conducted by any competent person regardless of job title or professional affiliation.

Get an Overview

The next step for someone new to SE is get an overview of the discipline. Part 1: SEBoK Introduction contains four articles particularly helpful to one new to SE.

Learn about Systems

Engineering is often described as the application of science to develop new products or systems. Part 2: Systems describes some of the underlying systems principles that form the foundation for systems engineering.

Learn how the Systems Approach is Applied to Engineered Systems

The Knowledge Area Systems Approach Applied to Engineered Systems describes how systems science and systems thinking lead to the practice of systems engineering. All eight articles are recommended.

Explore the Methods of Systems Engineering

The SEBoK uses a life-cycle framework to describe the processes that comprise systems engineering. Part 3:SE and Management contains the plurality of the content of the SEBoK in eight knowledge areas. A new user should be familiar with the introductions to each of these Knowledge Areas, and should read further in those KAs of interest.

Explore the Applications of Systems Engineering

The SEBoK partitions the body of knowledge between methods and areas of application. Areas of application are classified as:

A new user should read the introduction to Part 4: Applications of Systems Engineering and to the four knowledge areas listed above. The reader’s interests can then suggest which further reading should be done.

Read Case Studies

Finally, the new user should scan the case studies and vignettes in Part7: SE Implementation Examples and read a few of those in areas that appeal to the reader. This will help reinforce the fundamentals as well as illustrate the practice of SE.

The case studies and vignettes are:

For Later Reading

Part 6: Related Disciplines contains a broad selection of Knowledge Areas and Topics that describe how systems engineers work with other disciplines. The Knowledge area on SE and Software Engineering is particularly important, as modern systems get much of their functionality from software.

Part 5: Enabling Systems Engineering has KAs describing how individuals,teams, and organizations can develop to practice effective systems engineering.

A person new to SE should become familiar with several references that are beyond that SEBoK. They include the INCOSE Handbook, several standards (listed in Relevant Standards), and the main journals of systems engineering (including but not limited to Systems Engineering, the Journal of Enterprise Transformation, and Systems, Man, and Cybernetics).


Works Cited


Primary References


Additional References


Previous Article | Parent Article | Next Article >

SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

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.

Error in widget DISQUS: unable to write file /var/www/sebokwiki/mediawiki/extensions/Widgets/compiled_templates/wrt638e136a797292_53758118