System Concept Definition: Difference between revisions
| Line 31: | Line 31: | ||
---- | ---- | ||
<center>[[Integration of Process and Product Models|< Previous Article]] | [[Systems Engineering and Management|Parent Article]] | [[Mission Analysis|Next Article ->]]</center> | <center>[[Integration of Process and Product Models|< Previous Article]] | [[Systems Engineering and Management|Parent Article]] | [[Mission Analysis|Next Article ->]]</center> | ||
==Comments from SEBoK 0.5 Wiki== | |||
Please note that in version 0.5, this article was titled “Mission Analysis and Stakeholder Requirements”. The comments below are shared with the [[Stakeholder Needs and Requirements]] article. | |||
<html> | |||
<iframe src="http://bkcasewiki.org/index.php?title=Talk:Mission_Analysis&printable=yes" width=825 height=200 frameborder=1 scrolling=auto> | |||
</iframe> | |||
</html> | |||
{{DISQUS}} | |||
[[Category:Part 3]][[Category:Knowledge Area]] | [[Category:Part 3]][[Category:Knowledge Area]] | ||
Revision as of 00:46, 7 March 2012
Concept definition is the set of systems engineering activities in which the problem space and the needs of the stakeholders are closely examined; this occurs before any formal definition of the system of interest (soi) is developed. Mission Analysis focuses on defining the problem or opportunity that exists (often called the problem space), as well as understanding the constraints on and boundaries of the solution space. Stakeholder Needs and Requirements explores and defines the operational aspects of a potential solution for the stakeholders from their pointof view, independent of any specific solution.
Mission analysis examines why a solution is desired; what problem or opportunity it will address. Stakeholder needs and requirements describe what a solution should accomplish. Both why and what need to be answered before any consideration of how the problem will be addressed (i.e., what type of solution) and how the solution will be defined and developed. If the chosen solution is a new or modified system, then System Definition activities are performed to define the system.
Various authors use different terms to describe these phases. For example, Kossiakoff and Sweet (2005) call them needs analysis and concept exploration.
Topics
The topics contained within this knowledge area include:
Concept Definition Activities
There are two primary activities discussed under concept definition: mission analysis and the definition of stakeholder needs and requirements:
- Mission Analysis initiates the life cycle of a potential system of interest (SoI) that could solve a problem or realize an opportunity for developing a new product, service or enterprise. These activities define the problem space, identify the stakeholders, develop preliminary operational concepts, and identify environmental conditions and constraints that bound the solution space.
- Stakeholder Needs and Requirements works with the stakeholders across the life cycle to elicit and capture a set of needs, expectations, goals, or objectives of a desired solution to the problem or opportunity, called Stakeholder Needs. The stakeholder needs are used to produce a clear, concise, and verifiable set of stakeholder requirements.
The products and artifacts produced during concept definition are then used in System Definition.
References
Works Cited
Kossiakoff, A, and W. Sweet. 2009. Systems Engineering: Principles and Practice. Hoboken, NJ, USA: John Wiley and Sons.
Primary References
No primary references have been identified for version 0.75. Please provide any recommendations on primary references in your review.
Additional References
No additional references have been identified for version 0.75. Please provide any recommendations on additional references in your review.
Comments from SEBoK 0.5 Wiki
Please note that in version 0.5, this article was titled “Mission Analysis and Stakeholder Requirements”. The comments below are shared with the Stakeholder Needs and Requirements article.
<html> <iframe src="http://bkcasewiki.org/index.php?title=Talk:Mission_Analysis&printable=yes" width=825 height=200 frameborder=1 scrolling=auto> </iframe> </html>
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