JSEA  Vol.5 No.10 , October 2012
Lessons Learned from Practical Independent Verification and Validation Based on IEEE 1012
Author(s) Joon Ku Lee*, Yang Mo Kim*
ABSTRACT
IEEE 1012 [1] describes the SDLC phase activities for software independent verification and validation (IV & V) for nuclear power plant in truly general and conceptual manner, which requires the upward and/or downward tailoring on its interpretation for practical IV & V. It contains crucial and encompassing check points and guidelines to analyze the design integrity, without addressing the formalized and the specific criteria for IV & V activities confirming the technical integrity. It is necessary to list up the inspection viewpoint via interpretation of the standard that is practical review points checking design consistency. For fruitful IV & V of Control Element Driving Mechanism Control System (CEDMCS) software for Yonggwang Nuclear Power Plant unit 3 & 4, the specific viewpoints and approach are necessary based on the guidelines of IEEE 1012 to enhance the system quality by considering the level of implementation of the theoretical and the practical IV & V. Additionally IV & V guideline of IEEE 1012 does not specifically provide the concrete measure considering the system characteristics of CEDMCS. This paper provides the seven (7) characteristic criteria for CEDMCS IV & V, and by applying these viewpoints, the design analysis such as function, performance, interface and exception, backward and forward requirement traceability analysis has been conducted. The requirement, design, implementation, and test phase were only considered for IV & V in this project. This article also provides the translation of code to map theoretical verification and validation into practical verification and validation. This paper emphasizes the necessity of the intensive design inspection and walkthrough for requirement phase to resolve the design faults because the IV & V of early phase of SDLC obviously contributes to find out most of critical design inconsistency. Especially for test phase IV & V, it is strongly recommended to prepare the test plan document which is going to be the basis for the test coverage selection and test strategy. This test plan document should be based on the critical characteristics of function and performance of CEDMCS. Also to guarantee the independency of V & V organization participating in this project, and to acquire the full package of design details for IV & V, the systematic approach and efforts with an aspect of management is highlighted among the participants.

Cite this paper
J. Ku Lee and Y. Mo Kim, "Lessons Learned from Practical Independent Verification and Validation Based on IEEE 1012," Journal of Software Engineering and Applications, Vol. 5 No. 10, 2012, pp. 810-815. doi: 10.4236/jsea.2012.510093.
References
[1]   IEEE Standard 1012TM+“IEEE Standard for Software Verification and Validation,” 2004.http://standards.ieee.org/findstds/standard/1012-2004.html

[2]   R. S. Pressman, “Software Engineering, a Practitioner’s Approach,” 5th Edition, McGraw-Hill Higher Education, New York, 2004.

[3]   K. H. Cha, K. C. Kwon and C. S. Woo, “The Software Verification and Validation Tasks for a Safety Critical System in Nuclear Power Plants,” International Journal of Safety, Vol. 3, No. 1, 2004, pp. 38-46.

[4]   C. Ponsard, P. Massonet, J. F. Molderez, A. Rifaut, A. van Lamsweerde and H. Tran Van, “Early Verification and Validation of Mission Critical Systems,” Formal Methods in system Design, Vol. 30, No. 3, 2004, pp. 233-247.

[5]   IEEE Standard 829, “IEEE Standard for Software and System Test Documentation,” 2008. http://standards.ieee.org/findstds/standard/829-2008.html

[6]   IEEE Standard 1008, “IEEE Standard for Software Unit Testing,” 1987.http://standards.ieee.org/findstds/standard/1008-1987.html

[7]   NUREG/CR-6430, “Software Safety Hazard Analysis,” 1995.

 
 
Top