Difference between revisions of "SEBoK Users and Uses"
Line 1: | Line 1: | ||
− | The users and uses described in this article were identified based on the six SEBoK purposes described in the [[SEBoK 1.0 Introduction|SEBoK 1.0 Introduction]]. | + | The users and uses described in this article were identified based on the six SEBoK purposes described in the [[SEBoK v. 1.0.1 Introduction|SEBoK v. 1.0.1 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. | 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== | ==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. | + | 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://www.sebokwiki.org/1.0/index.php/Category:Use_Case here.] |
{| | {| | ||
Line 14: | Line 14: | ||
|- | |- | ||
| 1 | | 1 | ||
− | |[[Use Case 1: Practicing Systems Engineers|Practicing systems Engineers]] ranging from novice | + | |[[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 31: | Line 31: | ||
|- | |- | ||
| 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; the user should consult the | + | *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 40: | Line 40: | ||
|[[Acronyms|GRCSE]] authors | |[[Acronyms|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™)]]'' | ||
|- | |- | ||
| 5 | | 5 | ||
Line 51: | Line 52: | ||
|[[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 the the role of the systems engineer consists of, relative to others on a project or in an organization | + | *Learning what the the role of the [[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 101: | Line 103: | ||
==List of Use Cases== | ==List of Use Cases== | ||
− | At the time of version 1.0, not every class of user has a use case developed. To illustrate the major uses, the following use cases are included: | + | 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: |
*[[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. |
Revision as of 01:07, 28 November 2012
The users and uses described in this article were identified based on the six SEBoK purposes described in the SEBoK v. 1.0.1 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
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 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:
- 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.
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.
blog comments powered by Disqus