Towards a method for rigorous development of generic requirements patterns

Authors:
Colin Snook;Michael Poppleton;Ian Johnson
Affiliations:
School of Electronics and Computer Science, University of Southampton, Highfield, Southampton, UK;School of Electronics and Computer Science, University of Southampton, Highfield, Southampton, UK;AT Engine Controls, Portsmouth
Venue:
Rigorous Development of Complex Fault-Tolerant Systems
Year:
2006

Citing 10
Cited 0

DSSA (Domain-Specific Software Architecture): pedagogical example

ACM SIGSOFT Software Engineering Notes
The B-book: assigning programs to meanings

The B-book: assigning programs to meanings
Achieving requirements reuse: a domain-specific approach from avionics

Journal of Systems and Software
Object-oriented application frameworks

Communications of the ACM
Managing Domain-Specific, Product-Line Development

IEEE Software
Model-Driven Product Line Architectures

SPLC 2 Proceedings of the Second International Conference on Software Product Lines
Product-Line Requirements Specification (PRS): An Approach and Case Study

RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Scaling Step-Wise Refinement

IEEE Transactions on Software Engineering
Fault Tolerance in a Layered Architecture: A General Specification Pattern in B

SEFM '04 Proceedings of the Software Engineering and Formal Methods, Second International Conference
On the Design and Development of Program Families

IEEE Transactions on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

We present work in progress on a method for the engineering, validation and verification of generic requirements using domain engineering and formal methods. The need to develop a generic requirement set for subsequent system instantiation is complicated by the addition of the high levels of verification demanded by safety-critical domains such as avionics. Our chosen application domain is the failure detection and management function for engine control systems: here generic requirements drive a software product line of target systems. A pilot formal specification and design exercise is undertaken on a small (two-sensor) system element. This exercise has a number of aims: to support the domain analysis, to gain a view of appropriate design abstractions, for a B novice to gain experience in the B method and tools, and to evaluate the usability and utility of that method. We also present a prototype method for the production and verification of a generic requirement set in our UML-based formal notation, UML-B, and tooling developed in support. The formal verification both of the structural generic requirement set, and of a particular application, is achieved via translation to the formal specification language, B, using our U2B and ProB tools.