Difference between revisions of "SEBoK Users and Uses"
Line 10: | Line 10: | ||
| 1 | | 1 | ||
|Practicing SEs ranging from novice up through expert | |Practicing SEs ranging from novice up through expert | ||
− | |*Users are taking on a new SE role in a project and need the best references to help prepare | + | | |
+ | *Users are taking on a new SE role in a project and need the best references to help prepare | ||
*Users want to expand their areas of SE expertise and specialization and need the best references to read | *Users want to expand their areas of SE expertise and specialization and need the best references to read | ||
*Users want to understand the principles of SE and find the best references to elaborate on those principles | *Users want to understand the principles of SE and find the best references to elaborate on those principles | ||
Line 17: | Line 18: | ||
| 2 | | 2 | ||
|Process engineers responsible for defining or implementing SE processes | |Process engineers responsible for defining or implementing SE processes | ||
− | |*Users are maintaining a library of SE process assets and want to understand which are the most relevant SE process standards | + | | |
+ | *Users are maintaining a library of SE process assets and want to understand which are the most relevant SE process standards | ||
*Users are tailoring a process for a specific project and want to find examples in the literature of how others have tailored processes in the past or to find how a specific application domain should affect tailoring | *Users are tailoring a process for a specific project and want to find examples in the literature of how others have tailored processes in the past or to find how a specific application domain should affect tailoring | ||
*Users wish to measure the effectiveness of their organization’s SE processes and want to find examples in the literature of how others have done such measurement | *Users wish to measure the effectiveness of their organization’s SE processes and want to find examples in the literature of how others have done such measurement | ||
Line 23: | Line 25: | ||
| 3 | | 3 | ||
|Faculty members | |Faculty members | ||
− | |*Users are developing a new graduate program in SE and need to decide the core knowledge that all students in the program should master; users would simultaneously reference GRCSE, which makes extensive reference to the SEBoK | + | | |
+ | *Users are developing a new graduate program in SE and need to decide the core knowledge that all students in the program should master; users would simultaneously reference GRCSE, which makes extensive reference to the SEBoK | ||
*Users are developing a new SE course and need to identify course objectives, topics, and reading assignments | *Users are developing a new SE course and need to identify course objectives, topics, and reading assignments | ||
*Users in other engineering disciplines want to incorporate SE concepts in their courses or curricula | *Users in other engineering disciplines want to incorporate SE concepts in their courses or curricula | ||
Line 29: | Line 32: | ||
| 4 | | 4 | ||
|GRCSE authors | |GRCSE authors | ||
− | |*Users are members of the GRCSE author team and need to decide what knowledge to expect from all SE graduate students | + | | |
+ | *Users are members of the GRCSE author team and need to decide what knowledge to expect from all SE graduate students | ||
|- | |- | ||
| 5 | | 5 | ||
|Certifiers | |Certifiers | ||
− | |*Users are defining a company’s in-house SE certification program and want 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 | + | | |
+ | *Users are defining a company’s in-house SE certification program and want 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 | ||
|- | |- | ||
| 6 | | 6 | ||
|Managers, other engineers, developers, testers, researchers | |Managers, other engineers, developers, testers, researchers | ||
− | |*Users want to understand the scope of SE relative to their roles | + | | |
+ | *Users want to understand the scope of SE relative to their roles | ||
*Users want to understand basic vocabulary, boundaries, and structure of SE and are looking for a few primary references | *Users want to understand basic vocabulary, boundaries, and structure of SE and are looking for a few primary references | ||
*Users want to understand the role of the systems engineer versus others on a project or in an organization | *Users want to understand the role of the systems engineer versus others on a project or in an organization | ||
Line 44: | Line 50: | ||
| 7 | | 7 | ||
|Customers of systems engineers | |Customers of systems engineers | ||
− | |*Users receive artifacts from systems engineers and want to better understand what to ask for, how to request it, and how to judge the quality of what is received | + | | |
+ | *Users receive artifacts from systems engineers and want to better understand what to ask for, how to request it, and how to judge the quality of what is received | ||
|- | |- | ||
| 8 | | 8 | ||
|SE managers | |SE managers | ||
− | |*Users’ teams of systems engineers are proposing changes in the teams’ processes and tools, and the users want to read independent information to evaluate the proposal | + | | |
+ | *Users’ teams of systems engineers are proposing changes in the teams’ processes and tools, and the users want to read independent information to evaluate the proposal | ||
*Users need to hire systems engineers and want to develop competency-based job descriptions | *Users need to hire systems engineers and want to develop competency-based job descriptions | ||
|- | |- | ||
| 9 | | 9 | ||
|SE researchers | |SE researchers | ||
− | |*Users want to understand where the gaps are in SE knowledge to help guide their research agendas | + | | |
+ | *Users want to understand where the gaps are in SE knowledge to help guide their research agendas | ||
*Users want to familiarize themselves with research topics and want to know the best articles to read | *Users want to familiarize themselves with research topics and want to know the best articles to read | ||
|} | |} | ||
Line 67: | Line 76: | ||
| 1 | | 1 | ||
|Human resource development professionals | |Human resource development professionals | ||
− | |*Users will access SEBoK with the assistance of a direct user in order to support the hiring and professional development of systems engineers | + | | |
+ | *Users will access SEBoK with the assistance of a direct user in order to support the hiring and professional development of systems engineers | ||
|- | |- | ||
| 2 | | 2 | ||
|Non-technical managers | |Non-technical managers | ||
− | |*Users will access SEBoK with the assistance of a direct user in order to find specific information of interest about SE topics central to the managers’ concerns; e.g., a contracting manager might want to better understand SE deliverables being called out in a contract | + | | |
+ | *Users will access SEBoK with the assistance of a direct user in order to find specific information of interest about SE topics central to the managers’ concerns; e.g., a contracting manager might want to better understand SE deliverables being called out in a contract | ||
|- | |- | ||
| 3 | | 3 | ||
|Attorneys, policy makers | |Attorneys, policy makers | ||
− | |*Users will access SEBoK with the assistance of a direct user in order to understand such legal issues as the liability of a systems engineer for errors in judgment on a project, or to understand the limitations of SE in guaranteeing the success of a project vs. the actions of sponsors, managers, or developers | + | | |
+ | *Users will access SEBoK with the assistance of a direct user in order to understand such legal issues as the liability of a systems engineer for errors in judgment on a project, or to understand the limitations of SE in guaranteeing the success of a project vs. the actions of sponsors, managers, or developers | ||
|} | |} | ||
Revision as of 20:01, 25 July 2011
Based on the six purposes described in Table 1, there are nine primary types of SEBoK users, that are shown in Table 2 along with example uses of the SEBoK. These users have the technical skills necessary to access and understand the SEBoK. Table 3 shows another three types of secondary users who lack those technical skills and would likely rely on someone who is a primary user type, such as a practicing systems engineer, to help them access and understand the SEBoK. The example uses shown in Tables 2 and 3 are intended to be indicative, but not exhaustive.
# | Users | Uses |
---|---|---|
1 | Practicing SEs ranging from novice up through expert |
|
2 | Process engineers responsible for defining or implementing SE processes |
|
3 | Faculty members |
|
4 | GRCSE authors |
|
5 | Certifiers |
|
6 | Managers, other engineers, developers, testers, researchers |
|
7 | Customers of systems engineers |
|
8 | SE managers |
|
9 | SE researchers |
|
# | Users | Uses |
---|---|---|
1 | Human resource development professionals |
|
2 | Non-technical managers |
|
3 | Attorneys, policy makers |
|
References
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Citations
List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Primary References
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.
Additional References
All additional references should be listed in alphabetical order.