Validation obligations a novel approach to check compliance between requirements and their formal specification

Traditionally, practitioners use formal methods predominately for one half of the quality-assurance process: verification (do we build the software right?). The other half - validation (do we build the right software?) - has been given comparatively little attention. While verification is the core o...

Full description

Saved in:
Bibliographic Details
Published in:2021 IEEE/ACM 43rd International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER) pp. 1 - 5
Main Authors: Mashkoor, Atif, Leuschel, Michael, Egyed, Alexander
Format: Conference Proceeding
Language:English
Published: Piscataway, NJ, USA IEEE Press 25.05.2021
IEEE
Series:ACM Conferences
Subjects:
Adaptation models
formal methods
Formal specifications
General and reference
General and reference > Cross-computing tools and techniques
Prototypes
refinement
Software
Software and its engineering
Software and its engineering > Software creation and management
Software and its engineering > Software creation and management > Software development process management
Software and its engineering > Software creation and management > Software verification and validation
Software and its engineering > Software creation and management > Software verification and validation > Formal software verification
Software and its engineering > Software organization and properties
Software and its engineering > Software organization and properties > Software functional properties
Software and its engineering > Software organization and properties > Software functional properties > Formal methods
Software engineering
specification
Theory of computation
Theory of computation > Semantics and reasoning
validation obligations
Velocity control
specification
refinement
validation obligations
formal methods
ISBN:9780738133249, 0738133248, 1665401400, 9781665401401
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Traditionally, practitioners use formal methods predominately for one half of the quality-assurance process: verification (do we build the software right?). The other half - validation (do we build the right software?) - has been given comparatively little attention. While verification is the core of refinement-based formal methods, where each new refinement step must preserve all properties of its abstract model, validation is usually postponed until the latest stages of the development, when models can be automatically executed. Thus mistakes in requirements or in their interpretation are caught too late: usually at the end of the development process. In this paper, we present a novel approach to check compliance between requirements and their formal refinement-based specification during the earlier stages of development. Our proposed approach - "validation obligations" - is based on the simple idea that both verification and validation are an integral part of all refinement steps of a system.
ISBN:9780738133249
0738133248
1665401400
9781665401401
DOI:10.1109/ICSE-NIER52604.2021.00009