System Concept Definition: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Concept definition is the phase of systems engineering in which the problem space and the needs of the stakeholders are closely examined; this occurs before any formal definition of the | Concept definition is the phase of systems engineering 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 (glossary)]] is developed. [[Mission Analysis]] focuses on the identification of the primary purpose(s) of the system, while [[Stakeholder Needs and Requirements]] definition explores what capabilities stakeholders desire and may include some detail on certain aspects that the system must perform. | ||
Mission analysis examines ''why'' | Mission analysis examines ''why'' a system is desired. Stakeholder needs and requirements describe ''what'' a system should accomplish. Both ''why'' and ''what'' need to be answered before any consideration of ''how'' the system will be architected and designed. | ||
Various authors use different terms to describe these phases. For example, Kossiakoff and Sweet (2005) call them ''needs analysis'' and ''concept exploration.'' | Various authors use different terms to describe these phases. For example, Kossiakoff and Sweet (2005) call them ''needs analysis'' and ''concept exploration.'' | ||
Revision as of 20:06, 29 February 2012
Concept definition is the phase of systems engineering 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 (glossary) is developed. Mission Analysis focuses on the identification of the primary purpose(s) of the system, while Stakeholder Needs and Requirements definition explores what capabilities stakeholders desire and may include some detail on certain aspects that the system must perform.
Mission analysis examines why a system is desired. Stakeholder needs and requirements describe what a system should accomplish. Both why and what need to be answered before any consideration of how the system will be architected and designed.
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:
References
Works Cited
Kossiakoff, A, and W. Sweet. 2009. Systems Engineering: Principles and Practice. Hoboken, NJ, USA: John Wiley and Sons.
Primary References
Reviewers are invited to suggest references for this article.
Additional References
Reviewers are invited to suggest references for this article.