The users and uses described in this article were identified based on the six SEBoK purposes described in the SEBoK Introduction.
Users can either be primary (those who use the SEBoK directly) or secondary (those who use the SEBoK with assistance from a systems engineer). Indicative, but not exhaustive, sets of example uses are shown in Tables 1 and 2 below.
Primary users are those who use the SEBoK directly, as shown in Table 1. Hyperlinks in the second column link to the associated use case, where one has been written. The use cases are listed at the end of the topic, and may also be seen here.
Table 1. Primary SEBoK Users and Common Uses. (SEBoK Original)
Developing a new graduate program in SE, and deciding what core knowledge all its students must master; the user should consult the Graduate Reference Curriculum for Systems Engineering (GRCSE™) in conjunction with the SEBoK
Developing a new SE course; seeking to identify course objectives, topics, and reading assignments
Incorporate SE concepts in courses or curricula focused on engineering disciplines other than SE
As members of the GRCSE author team, deciding what knowledge to expect from all SE graduate students
Defining a company’s in-house SE certification program; seeking to understand what others have done, how such programs are typically structured, and how to select the knowledge that each person seeking certification should master
Defining certification criteria for a professional society or licensure program
Providing resources to and receiving artifacts from systems engineers
Seeking to better understand what to ask for, how to request it, how much to pay for it, and how to judge the quality of what is received
Evaluating possible changes in team processes and tools proposed by systems engineers on various teams; seeking independent information with which to evaluate the proposals
Hiring systems engineers, and developing competency-based job descriptions
Looking for gaps are in SE knowledge to help guide a research agenda
Getting familiarize with a research topic; seeking the most important articles about the topic
Secondary users are those who use the SEBoK with assistance from a systems engineer, as shown in Table 2.
Table 2. Secondary SEBoK Users and Common Usages. (SEBoK Original)
Human resource development professionals
Supporting the hiring and professional development of systems engineers
Augmenting understanding of central concerns with information about relevant SE topics; e.g., a contracting manager might want to better understand SE deliverables being called out in a contract
Attorneys, policy makers
Defining the impact of SE performance on central concerns; e.g., understanding the liability of a systems engineer for errors in judgment on a project, or the limitations of SE in guaranteeing the success of a project against actions of sponsors, managers, or developers
List of Use Cases
At the time of version 1.0.1, not every class of user has a use case developed. To illustrate the major uses, the following use cases are included:
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 Editors' Note.
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.