SEBoK Users and Uses: Difference between revisions

From SEBoK Draft
Jump to navigation Jump to search
mNo edit summary
Line 29: Line 29:
|[[Use Case 1: Practicing Systems Engineers|Practicing systems Engineers]] ranging from novice up through expert
|[[Use Case 1: Practicing Systems Engineers|Practicing systems Engineers]] 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
*Taking on a new SE role in a project; preparing by finding references for study
*Users want to expand their areas of SE expertise and specialization and need the best references to read
*Expanding SE expertise and specialization; preparing by finding references for study 
*Users want to understand the principles of SE and find the best references to elaborate on those principles  
*Seeking to understand the principles of SE; seeking the best references to elaborate on those principles  
*Users want to understand what best SE practices to look for in a project they are reviewing, or for mentoring a new SE performer  
*Reviewing a project they or mentoring a new SE performer; seeking to understand what best practices to look for 
*Users want to continue to develop professionally through study of SE topics, including new developments in SE.
*Pursuing professional development through study of SE topics, including new developments in SE  
|-
|-
|  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 models and standards  
*Maintaining a library of SE process assets; seeking to understand which SE process models and standards are most relevant 
*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  
*Tailoring a process for a specific project; seeking to learn how others have tailored processes, or how a specific application domain affects 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  
*Measuring the effectiveness of an organization’s SE processes; seeking to learn how others have done such measurement  
*Users are defining standards for a professional society or standards organization.
*Defining standards for a professional society or standards organization  
|-
|-
|  3   
|  3   
|[[Use Case 4: Faculty Members|Faculty Members]]
|[[Use Case 4: 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
*Developing a new graduate program in SE, and deciding what core knowledge all its students must master; in conjunction with the SEBoK, this user should consult the GRCSE  
*Users are developing a new SE course and need to identify course objectives, topics, and reading assignments  
*Developing a new SE course; seeking to identify course objectives, topics, and reading assignments  
*Users in other engineering disciplines want to incorporate SE concepts in their courses or curricula  
*Incorporate SE concepts in courses or curricula focused on engineering disciplines other than SE 
|-
|-
|  4   
|  4   
|[[Acronyms|GRCSE]] authors
|[[Acronyms|GRCSE]] authors
|
|
*Users are members of the GRCSE author team and need to decide 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  
|-
|-
|  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  
*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  
*Users are defining certification criteria for a professional society or licensure program.
*Defining certification criteria for a professional society or licensure program
|-
|-
|  6   
|  6   
|[[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
|
|
*Users want to understand the scope of SE relative to their roles
*Mastering basic vocabulary, boundaries, and structure of SE; seeking a few primary references
*Users want to understand basic vocabulary, boundaries, and structure of SE and are looking for a few primary references  
*Learning what the scope of SE is, relative to the General Manager role 
*Users want to understand the role of the systems engineer versus others on a project or in an organization  
*Learning what the the role of the systems engineer consists of, relative to others on a project or in an organization  
*Users want to effectively perform their roles on a SE integrated product team  
*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]]
|
|
*Users provide resources to and receive artifacts from systems engineers and want 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  
*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   
|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
*Evaluating possible changes in team processes and tools proposed by systems engineers on various teams; seeking independent information with which to evaluate the proposals
*Users need to hire systems engineers and want to develop competency-based job descriptions  
*Hiring systems engineers, and developing 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
*Looking for gaps are in SE knowledge to help guide a research agenda
*Users want to familiarize themselves with research topics and want to know the best articles to read
*Getting familiarize with a research topic; seeking the most important articles about the topic
|}
|}


Revision as of 12:11, 18 August 2012

<html><a style="float:right;padding:2px 4px 0 0" href="javascript:void(0)" onclick="$('#light').hide();$('#fade').hide()">[X]</a></html>
This navigational tool is a prototype under development SEBoK 1.0. Comments are welcome for improvement.
Use [+] to expand and [-] to collapse. Clicking on a title will open that article.
{{#star: }}

<html><a style="float:right" href="javascript:void(0)" onclick="$('#light').show();$('#fade').show()"><img src="/dev/extensions/SEBoK/staricon.png" alt="Star menu" /></a>
</html>

The users and uses described in this article were identified based on the six SEBoK purposes described in the SEBoK 1.0 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.

For five common classes of SEBoK users, detailed use cases follow. Each provides guidance for using the SEBoK that is appropriate for a particular class of user. The use cases are:


To download a PDF of all of Part 1 (including all of the use cases), please click here.

Primary Users

Primary users are those who use the SEBoK directly, as shown in Table 1.

Table 1. Primary SEBoK Users and Common Uses. (SEBoK Original)
# Users Uses
1 Practicing systems Engineers ranging from novice up through expert
  • Taking on a new SE role in a project; preparing by finding references for study
  • Expanding SE expertise and specialization; preparing by finding references for study
  • Seeking to understand the principles of SE; seeking the best references to elaborate on those principles
  • Reviewing a project they or mentoring a new SE performer; seeking to understand what best practices to look for
  • Pursuing professional development through study of SE topics, including new developments in SE
2 Process engineers responsible for defining or implementing SE processes
  • 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
  • Measuring the effectiveness of an organization’s SE processes; seeking to learn how others have done such measurement
  • Defining standards for a professional society or standards organization
3 Faculty Members
  • Developing a new graduate program in SE, and deciding what core knowledge all its students must master; in conjunction with the SEBoK, this user should consult the GRCSE
  • 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
4 GRCSE authors
  • As members of the GRCSE author team, deciding what knowledge to expect from all SE graduate students
5 Certifiers
  • 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
6 General Managers, Other Engineers, developers, testers, researchers
  • Mastering basic vocabulary, boundaries, and structure of SE; seeking a few primary references
  • 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 to effectively perform a General Manager role on an SE integrated product team
7 Customers of Systems Engineering
  • 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 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
  • Hiring systems engineers, and developing competency-based job descriptions
9 SE researchers
  • 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

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)
# Users Uses
1 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
2 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
3 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

References

Works Cited

None.

Primary References

None.

Additional References

None.

< Previous Article | Parent Article | Next Article >


SEBoK v. 1.9.1 released 30 September 2018

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

Retrieved from "https://sebokwiki.org/draft/w/index.php?title=SEBoK_Users_and_Uses&oldid=39635"