Difference between revisions of "SEBoK Users and Uses"
m (Text replacement - "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>" to "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>") |
|||
(23 intermediate revisions by 5 users not shown) | |||
Line 4: | Line 4: | ||
==New to SEBoK or Systems Engineering?== | ==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: | + | 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 0: Systems Engineering Novices]] | ||
==Primary Users== | ==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 [http:// | + | 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 30: | Line 30: | ||
*Maintaining a library of SE process assets; seeking to understand which SE process models and standards are most relevant | *Maintaining a library of SE process assets; seeking to understand which SE process models and standards are most relevant | ||
*Tailoring a process for a specific project; seeking to learn how others have tailored processes, or how a specific application domain affects tailoring | *Tailoring a process for a specific project; seeking to learn how others have tailored processes, or how a specific application domain affects tailoring | ||
− | *Measuring the effectiveness of an organization’s SE processes; seeking to learn how others have | + | *Measuring the effectiveness of an organization’s SE processes; seeking to learn how others have implemented processes |
*Defining standards for a professional society or standards organization | *Defining standards for a professional society or standards organization | ||
|- | |- | ||
Line 36: | Line 36: | ||
|[[Use Case 4: Educators and Researchers|Faculty Members]] | |[[Use Case 4: Educators and Researchers|Faculty Members]] | ||
| | | | ||
− | *Developing a new graduate program in SE | + | *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 | ||
Line 43: | Line 43: | ||
|GRCSE authors | |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 53: | Line 52: | ||
|- | |- | ||
| 6 | | 6 | ||
− | |[[Use Case 5: General Managers|General Managers]], [[Use Case 2: Other Engineers|Other Engineers]], | + | |[[Use Case 5: General Managers|General Managers]], [[Use Case 2: Other Engineers|Other Engineers]], Developers, Testers, Researchers |
| | | | ||
*Mastering basic [[Glossary of Terms|vocabulary]], boundaries, and structure of SE; seeking a few [[Primary References|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 of what the role of the {{Term|Systems Engineering (glossary)|systems engineer}} consists, relative to others on a project or in an organization |
*Learning to effectively perform a general manager role on an SE integrated product team | *Learning to effectively perform a general manager role on an SE integrated product team | ||
|- | |- | ||
Line 67: | Line 66: | ||
|- | |- | ||
| 8 | | 8 | ||
− | |SE | + | |SE Managers |
| | | | ||
*Evaluating possible changes in team processes and tools proposed by systems engineers on various teams; seeking independent information with which to evaluate the proposals | *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 | + | *Hiring systems engineers and developing competency-based job descriptions |
|- | |- | ||
| 9 | | 9 | ||
− | |SE | + | |SE Researchers |
| | | | ||
*Looking for gaps are in SE knowledge to help guide a research agenda | *Looking for gaps are in SE knowledge to help guide a research agenda | ||
− | * | + | *Familiarizing themselves with a research topic; seeking the most important articles about the topic |
|} | |} | ||
Line 90: | Line 89: | ||
|- | |- | ||
| 1 | | 1 | ||
− | |Human | + | |Human Resource Development Professionals |
| | | | ||
*Supporting the hiring and professional development of systems engineers | *Supporting the hiring and professional development of systems engineers | ||
|- | |- | ||
| 2 | | 2 | ||
− | |Non- | + | |Non-Technical Managers |
| | | | ||
− | *Augmenting understanding of central concerns with information about relevant SE topics | + | *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, | + | |Attorneys, Policy Makers |
| | | | ||
− | *Defining the impact of SE performance on central concerns | + | *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== | ==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: | + | 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 1: Practicing Systems Engineers|Use Case 1: Practicing Systems Engineers]]. This covers the first set of users from Table 1. | ||
Line 118: | Line 117: | ||
==References== | ==References== | ||
+ | ===Works Cited=== | ||
+ | None. | ||
+ | |||
+ | ===Primary References=== | ||
+ | None. | ||
+ | |||
+ | ===Additional References=== | ||
None. | None. | ||
---- | ---- | ||
− | <center>[[ | + | <center>[[Fundamentals for Future Systems Engineering|< Previous Article]] | [[SEBoK Introduction|Parent Article]] | [[Use Case 0: Systems Engineering Novices|Next Article >]]</center> |
− | + | <center>'''SEBoK v. 2.6, released 20 May 2022'''</center> | |
[[Category:Part 1]] | [[Category:Part 1]] | ||
[[Category:SEBoK Users and Uses]] | [[Category:SEBoK Users and Uses]] |
Revision as of 19:31, 19 May 2022
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
Works Cited
None.
Primary References
None.
Additional References
None.