Difference between revisions of "SEBoK Users and Uses"
m (→Primary Users) |
(Robot improving glossary links) |
||
(48 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
− | + | The users and uses described in this article were identified based on the six SEBoK purposes described in the [[SEBoK Introduction]]. | |
− | |||
− | The users and uses described in this article were identified based on the six SEBoK purposes described in the [[SEBoK | ||
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. | 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. | ||
− | + | ==New to SEBoK or Systems Engineering?== | |
− | + | The list of users and use cases below allow someone who has come to the SEBoK with a particular focus to identify quickly where to focus their reading. If you are completely new to systems engineering or have no clear view of how it is covered in the SEBoK you should use Use Case 0 below to orient yourself and learn the basics before looking at the other use cases: | |
− | + | *[[Use Case 0: Systems Engineering Novices]] | |
− | *[[Use Case | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Primary Users== | ==Primary Users== | ||
− | Primary users are those who use the SEBoK directly, as shown in Table 1. | + | 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 [http://sebokwiki.org/draft/Case_Studies here.] |
{| | {| | ||
Line 27: | Line 17: | ||
|- | |- | ||
| 1 | | 1 | ||
− | |[[Use Case 1: Practicing Systems Engineers|Practicing | + | |[[Use Case 1: Practicing Systems Engineers|Practicing Systems Engineers]] ranging from novice through expert |
| | | | ||
*Taking on a new SE role in a project; preparing by finding references for study | *Taking on a new SE role in a project; preparing by finding references for study | ||
Line 44: | Line 34: | ||
|- | |- | ||
| 3 | | 3 | ||
− | |[[Use Case 4: | + | |[[Use Case 4: Educators and Researchers|Faculty Members]] |
| | | | ||
− | *Developing a new graduate program in SE, and deciding what core knowledge all its students must master; in conjunction with the SEBoK | + | *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 | *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 | *Incorporate SE concepts in courses or curricula focused on engineering disciplines other than SE | ||
|- | |- | ||
| 4 | | 4 | ||
− | + | |GRCSE authors | |
| | | | ||
− | *As members of the GRCSE author team, deciding what knowledge to expect from all SE graduate students | + | *As members of the GRCSE author team, deciding what knowledge to expect from all SE graduate students |
+ | *See ''[[Graduate Reference Curriculum for Systems Engineering (GRCSE™)]]'' (Pyster et al. 2015) | ||
|- | |- | ||
| 5 | | 5 | ||
Line 64: | Line 55: | ||
|[[Use Case 5: General Managers|General Managers]], [[Use Case 2: Other Engineers|Other Engineers]], developers, testers, researchers | |[[Use Case 5: General Managers|General Managers]], [[Use Case 2: Other Engineers|Other Engineers]], developers, testers, researchers | ||
| | | | ||
− | *Mastering basic vocabulary, boundaries, and structure of SE; seeking a few primary references | + | *Mastering basic [[Glossary of Terms|vocabulary]], boundaries, and structure of SE; seeking a few [[Primary References|primary references]] |
*Learning what the scope of SE is, relative to the General Manager role | *Learning what the scope of SE is, relative to the General Manager role | ||
− | *Learning what | + | *Learning what the role of the {{Term|Systems Engineering (glossary)|systems engineer}} consists of, relative to others on a project or in an organization |
− | *Learning to effectively perform a | + | *Learning to effectively perform a general manager role on an SE integrated product team |
|- | |- | ||
| 7 | | 7 | ||
|[[Use Case 3: Customers of Systems Engineering|Customers of Systems Engineering]] | |[[Use Case 3: Customers of Systems Engineering|Customers of Systems Engineering]] | ||
| | | | ||
− | *Providing resources to and receiving artifacts from systems engineers | + | *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 | ||
|- | |- | ||
| 8 | | 8 | ||
Line 100: | Line 92: | ||
|Human resource development professionals | |Human resource development professionals | ||
| | | | ||
− | * | + | *Supporting the hiring and professional development of systems engineers |
|- | |- | ||
| 2 | | 2 | ||
|Non-technical managers | |Non-technical managers | ||
| | | | ||
− | * | + | *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 |
|- | |- | ||
| 3 | | 3 | ||
− | |Attorneys, policy | + | |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 this time not every class of user has a use case developed. To illustrate the major uses, the following use cases are included: | ||
+ | |||
+ | *[[Use Case 1: Practicing Systems Engineers|Use Case 1: Practicing Systems Engineers]]. This covers the first set of users from Table 1. | ||
+ | *[[Use Case 2: Other Engineers|Use Case 2: Other Engineers]]. This covers the second and sixth sets of users from Table 1. | ||
+ | *[[Use Case 3: Customers of Systems Engineering|Use Case 3: Customers of Systems Engineering]]. This covers the seventh set of users from Table 1. | ||
+ | *[[Use Case 4: Educators and Researchers|Use Case 4: Educators and Researchers]]. This covers the third, fourth, and ninth sets of users from Table 1. | ||
+ | *[[Use Case 5: General Managers|Use Case 5: General Managers]]. This covers the sixth and eighth sets of users from Table 1. | ||
+ | |||
+ | While not exhaustive, the use cases show the utility of the SEBoK in various applications and contexts. | ||
==References== | ==References== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
None. | None. | ||
---- | ---- | ||
− | <center>[[Systems Engineering | + | <center>[[Systems Engineering Core Concepts|< Previous Article]] | [[SEBoK Introduction|Parent Article]] | [[Use Case 0: Systems Engineering Novices|Next Article >]]</center> |
− | + | <center>'''SEBoK v. 2.0, released 1 June 2019'''</center> | |
[[Category:Part 1]] | [[Category:Part 1]] | ||
[[Category:SEBoK Users and Uses]] | [[Category:SEBoK Users and Uses]] |
Revision as of 21:20, 21 August 2019
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.
New to SEBoK or Systems Engineering?
The list of users and use cases below allow someone who has come to the SEBoK with a particular focus to identify quickly where to focus their reading. If you are completely new to systems engineering or have no clear view of how it is covered in the SEBoK you should use Use Case 0 below to orient yourself and learn the basics before looking at the other use cases:
Primary Users
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.
# | Users | Uses |
---|---|---|
1 | Practicing Systems Engineers ranging from novice through expert |
|
2 | Process engineers responsible for defining or implementing SE processes |
|
3 | Faculty Members |
|
4 | GRCSE authors |
|
5 | Certifiers |
|
6 | General Managers, Other Engineers, developers, testers, researchers |
|
7 | Customers of Systems Engineering |
|
8 | SE managers |
|
9 | SE researchers |
|
Secondary Users
Secondary users are those who use the SEBoK with assistance from a systems engineer, as shown in Table 2.
# | Users | Uses |
---|---|---|
1 | Human resource development professionals |
|
2 | Non-technical managers |
|
3 | Attorneys, policy makers |
|
List of Use Cases
At this time not every class of user has a use case developed. To illustrate the major uses, the following use cases are included:
- Use Case 1: Practicing Systems Engineers. This covers the first set of users from Table 1.
- Use Case 2: Other Engineers. This covers the second and sixth sets of users from Table 1.
- Use Case 3: Customers of Systems Engineering. This covers the seventh set of users from Table 1.
- Use Case 4: Educators and Researchers. This covers the third, fourth, and ninth sets of users from Table 1.
- Use Case 5: General Managers. This covers the sixth and eighth sets of users from Table 1.
While not exhaustive, the use cases show the utility of the SEBoK in various applications and contexts.
References
None.