Difference between revisions of "SEBoK Users and Uses"
Jump to navigation
Jump to search
Line 77: | Line 77: | ||
|*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 | ||
|} | |} | ||
+ | |||
+ | ====Article Discussion==== | ||
+ | |||
+ | [[{{TALKPAGENAME}}|[Go to discussion page]]] | ||
[[Category:Part 1]] | [[Category:Part 1]] |
Revision as of 02:48, 24 June 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 | *Users are taking on a new SE role in a project and need the best references to help prepare
|
2 | 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
|
3 | 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
|
4 | GRCSE authors | *Users are members of the GRCSE author team and need to decide what knowledge to expect from all SE graduate students |
5 | 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 |
6 | Managers, other engineers, developers, testers, researchers | *Users want to understand the scope of SE relative to their roles
|
7 | 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 |
8 | 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
|
9 | SE researchers | *Users want to understand where the gaps are in SE knowledge to help guide their research agendas
|
# | 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 |