Difference between revisions of "Implementing and Proving a Solution"

From SEBoK
Jump to navigation Jump to search
m (moved Proving the System to Proving a System: CM - Minor change request for Part 2, approved at Workshop VII)
 
Line 28: Line 28:
  
 
WASSON, C. S. 2006. System Analysis, Design, and Development, Hoboken, NJ, John Wiley & Sons.
 
WASSON, C. S. 2006. System Analysis, Design, and Development, Hoboken, NJ, John Wiley & Sons.
 +
 +
==References==
 +
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information.
 +
 +
===Citations===
 +
List all references cited in the article.  Note:  SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information.
 +
 +
===Primary References===
 +
All primary references should be listed in alphabetical order.  Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ ([[title]]).  Please do not include version numbers in the links.
 +
 +
===Additional References===
 +
All additional references should be listed in alphabetical order.
 +
  
  

Revision as of 16:59, 24 June 2011

Introduction

The Systems Approach also requires that the system be proved. In Systems Engineering this is called verification and validation. All of the system principles come into play in proving the system.

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 (see principle of grouping and System Analysis).

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 a Systems Engineering context, (Wasson, 2006, pp. 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.

Primary References

JACKSON, S., HITCHINS, D. & EISNER, H. 2010. What is the Systems Approach? INCOSE Insight. International Council on Systems Engineering.

Additional References

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

References

Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Citations

List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Primary References

All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.

Additional References

All additional references should be listed in alphabetical order.


Article Discussion

[Go to discussion page]