Independent verification & validation: a life cycle engineering process for quality software
Independent verification & validation: a life cycle engineering process for quality software
First international workshop on architectures for software systems workshop summary
ACM SIGSOFT Software Engineering Notes
Test and analysis of software architectures
ISSTA '96 Proceedings of the 1996 ACM SIGSOFT international symposium on Software testing and analysis
WISR8: 8th annual workshop on software reuse: summary and working group reports
ACM SIGSOFT Software Engineering Notes
Software Verification and Validation: An Overview
IEEE Software
V&V of Flight and Mission-Critical Software
IEEE Software
Scenario-Based Analysis of Software Architecture
IEEE Software
Parameterized programming and software architecture
ICSR '96 Proceedings of the 4th International Conference on Software Reuse
Certification of Reusable Software Parts
Certification of Reusable Software Parts
Toward safe reuse of product family specifications
SSR '99 Proceedings of the 1999 symposium on Software reusability
Utilizing domain models for application design and validation
Information and Software Technology
The domain analysis concept revisited: a practical approach
ICSR'06 Proceedings of the 9th international conference on Reuse of Off-the-Shelf Components
| Hi-index | 0.00 |
Verification and Validation (V&V) is currently performed during application development for many systems, especially safety‐critical and mission‐critical systems. The V&V process is intended to discover errors, especially errors related to critical processing, as early as possible during the development process. The system application provides the context under which the software artifacts are validated. This paper describes a framework that extends V&V; from an individual application system to a product line of systems that are developed within an architecture‐based software engineering environment. This framework includes the activities of traditional application‐level V&V, and extends these activities into domain engineering and into the transition between domain engineering and application engineering. The framework includes descriptions of the types of activities to be performed during each of the life‐cycle phases, and provides motivation for the activities.