Difference between revisions of "Implementing and Proving a Solution"

From SEBoK
Jump to: navigation, search
(Additional References)
Line 35: Line 35:
 
<center>[[Analysis and Selection between Alternative Solutions|< Previous Article]] | [[Systems Approach|Parent Article]] | [[Deploying, Using, and Sustaining Systems to Solve Problems|Next Article >]]</center>
 
<center>[[Analysis and Selection between Alternative Solutions|< Previous Article]] | [[Systems Approach|Parent Article]] | [[Deploying, Using, and Sustaining Systems to Solve Problems|Next Article >]]</center>
  
{{5comments}}
+
==Comments from SEBoK 0.5 Wiki==
 +
Please note that in version 0.5, this article was titled “Proving a System”.
 +
 
 +
<html>
 +
<iframe src="http://bkcasewiki.org/index.php?title=Talk:Proving_a_System&printable=yes" width=825 height=200 frameborder=1 scrolling=auto>
 +
</iframe>
 +
</html>
 +
 
 +
{{DISQUS}}
  
 
[[Category:Part 2]][[Category:Topic]]
 
[[Category:Part 2]][[Category:Topic]]
 
[[Category:Systems Approach]]
 
[[Category:Systems Approach]]

Revision as of 23:45, 6 March 2012

This article considers the activities of the systems approach related to the implementation and proving of a prefered solution in detail. Any of the activities described below may need to be considered concurrently with activites the other activities of in the Systems Approach article. The final article in this knowledge area, Applying the Systems Approach, considers the dynamic aspects of how these activities are used as part of the Systems Approach and how this relates in detail to elements of Systems Engineering.


Proving the System Overview

This topic covers both the sub-topics of verification and validation.

Verification

Verification is the determination that each element of the system meets the requirements of a documented specification (see principle of elements). Verification is performed at each level of the system hierarchy. In the systems approach this topic pertains to the more abstract level of providing evidence that the system will accomplish what it was meant to do. In systems engineering this topic pertains to providing quantitative evidence from tests and other methods for verifying the performance of the system.

Validation

Validation is the determination that the entire system meets the needs of the stakeholders. Validation only occurs at the top level of the system hierarchy. In the systems approach this topic pertains to the more abstract level of making sure the system meets the needs of the stakeholders. In systems engineering, this topic pertains to the detailed demonstrations and other methods to satisfy the stakeholders.

In a systems engineering context, Wasson (2006, 691-709) provides a comprehensive guide to the methods of both system verification and system validation.

Linkages to other topics

The systems approach topic is linked to the systems engineering topics of verification and validation.

References

Works Cited

Jackson, S., D. Hitchins and H. Eisner. 2010. "What is the Systems Approach?" INCOSE Insight. 13(1) (April 2010): 41-43.

Wasson, C. S. 2006. System Analysis, Design, and Development. Hoboken, NJ, USA: John Wiley & Sons.

Primary References

Jackson, S., D. Hitchins and H. Eisner. 2010. "What is the Systems Approach?" INCOSE Insight. 13(1) (April 2010): 41-43.

Additional References

Wasson, C. S. 2006. System Analysis, Design, and Development. Hoboken, NJ, USA: John Wiley & Sons.


< Previous Article | Parent Article | Next Article >

Comments from SEBoK 0.5 Wiki

Please note that in version 0.5, this article was titled “Proving a System”.

<html> <iframe src="http://bkcasewiki.org/index.php?title=Talk:Proving_a_System&printable=yes" width=825 height=200 frameborder=1 scrolling=auto> </iframe> </html>


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