Academia.eduAcademia.edu

Outline

ISVV Process and Facility Project

Abstract

Independent Software Verification and Validation (ISVV) is an established practice in European space projects. An organisation independent of the software supplier and the prime performs verification and validation of software requirements, design, and code. The purpose is to identify faults as early as possible and to create confidence in the software scrutinised. This paper presents a consolidated, coherent, and cost effective ISVV process and a prototype ISVV facility developed in the context of an ESA project, for use across the space industry in Europe. It discusses the motivation for ISVV (including the importance of independence), as well as the purpose and contents of the various ISVV activities. The activities of the defined process are: Management, Criticality Analysis, Technical Specification Analysis, Design Analysis, Code Analysis, and Validation. The process itself is being validated by applying it to elements of the on board software of the European Robotic Arm.

Key takeaways
sparkles

AI

  1. The ISVV process aims to improve software quality and reliability in European space projects.
  2. ISVV activities include Management, Criticality Analysis, Technical Specification Analysis, Design Analysis, Code Analysis, and Validation.
  3. The ISVV Level classification determines the rigor of tasks based on software criticality and risk factors.
  4. The Independent Software Validation Facility (ISVVF) prototypes methods and tools for effective ISVV implementation.
  5. Independence in ISVV enhances fault detection and overall software confidence, crucial for mission-critical applications.

References (4)

  1. J. D. Arthur, M. K. Gröner, K. J. Hayhurst, and C. M. Holloway, "Evaluating the Effectiveness of Independent Verification and Validation," IEEE Computer, October 1999. [Arthur:2000]
  2. J. D. Arthur and R.E. Nance, "Verification and Validation without Independence: A Recipe for Failure". In Proceedings of the 2000 Winter Simulation Conference. Eds. J. A. Joines, R. R. Barton, K. Kang, and P. A. Fishwick. 2000. [ECSS-Q80-03:2004] ECSS-Q80-03 Draft 1, "Space Product Assurance, Methods and techniques to support the assessment of software dependability and Safety", ESA-ESTEC, April 8 th 2004. [Fagan:1976]
  3. M. E. Fagan, "Design and Code Inspections to Reduce Errors in Program Development", IBM Systems Journal, Volume 15, Number 3, 1976. [Formal:2005] http://vl.fmnet.info/,"Formal Methods", The World Wide Web Virtual Library, visited in May 19 th , 2005. [Maegaard:1998]
  4. C. Maegaard and P. Beerthuizen, "Development of a Safety Critical Hard Real-Time System in a World of Changes", Proceedings of the Data Systems in Aerospace Conference, DASIA '98, Athens, Greece, May, 1998. [Roe:2003] D. Roe, K. Broda, and A. Russo, "Mapping UML Models incorporating OCL Constraints into Object-Z", Department of Computer Science, Imperial College London, September 30 th , 2003.