Requirements‐related fault prevention during the transformation from formal specifications to programs

Software faults are costly to find and remove from programs. It is better to avoid inserting the faults in the first place. The authors identify requirements‐related faults that can arise during the transformation of formal specifications into programs, analyse each to discover its causes, and propo...

Full description

Saved in:
Bibliographic Details
Published in:IET software Vol. 17; no. 3; pp. 316 - 332
Main Authors: Li, Jiandong, Liu, Shaoying
Format: Journal Article
Language:English
Published: John Wiley & Sons, Inc 01.06.2023
Wiley
Subjects:
formal specification
object‐oriented programming
software development management
software quality
software reliability
ISSN:1751-8806, 1751-8814
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Software faults are costly to find and remove from programs. It is better to avoid inserting the faults in the first place. The authors identify requirements‐related faults that can arise during the transformation of formal specifications into programs, analyse each to discover its causes, and propose corresponding fault prevention methods. The approach works by analysing a specification, decomposing it into specification fragments with different levels like components, determining the correct implementation order among the components, and enabling automated code generation for the components and other low‐level specification fragments. The approach seeks to reduce the faults in programs significantly by guiding programmers to work effectively and productively. The authors evaluate the approach's performance experimentally and compare it to the performance of a fault‐prevention method with industry applications. In this paper, we identify requirements‐related faults that can arise during the transformation of formal specifications into programs, analyse each to discover its causes, and propose corresponding fault prevention methods. The approach works by analysing a specification, decomposing it into specification fragments with different levels like components, determining the correct implementation order among the components, and enabling automated code generation for the components and other low‐level specification fragments. The approach seeks to reduce the faults in programs significantly by guiding programmers to work effectively and productively.
ISSN:1751-8806
1751-8814
DOI:10.1049/sfw2.12126