A Family-Oriented Software Development Process for Engine Controllers

Authors:
Karen Allenby;Simon Burton;Darren Buttle;John A. McDermid;John Murdoch;Alan Stephenson;Mike Bardill;Stuart Hutchesson
Affiliations:
-;-;-;-;-;-;-;-
Venue:
PROFES '01 Proceedings of the Third International Conference on Product Focused Software Process Improvement
Year:
2001

Citing 12
Cited 0

Information-flow and data-flow analysis of while-programs

ACM Transactions on Programming Languages and Systems (TOPLAS)
The Mascot method

Software Engineering Journal - Special issue on Mascot 3
STATEMATE: A Working Environment for the Development of Complex Reactive Systems

IEEE Transactions on Software Engineering
The Z notation: a reference manual

The Z notation: a reference manual
HRT-HOOD: a structured design method for hard real-time systems

Real-Time Systems
Reusing single system requirements from application family requirements

Proceedings of the 21st international conference on Software engineering
Domain analysis: an introduction

ACM SIGSOFT Software Engineering Notes
Commonality and Variability in Software Engineering

IEEE Software
Priority Inheritance Protocols: An Approach to Real-Time Synchronization

IEEE Transactions on Computers
Towards Industrially Applicable Formal Methods: Three Small Steps, and One Giant Leap

ICFEM '98 Proceedings of the Second IEEE International Conference on Formal Engineering Methods
Hints on Test Data Selection: Help for the Practicing Programmer

Computer
On the Design and Development of Program Families

IEEE Transactions on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper presents a software engineering process that includes family-based aspects for aero-engine control software. The process uses a "family capability" derived from family analysis of the embedding system. This analysis allows reuse capability to be designed into the process by exploiting prior knowledge of the differences between members of an engine family. The process described follows the traditional software lifecycle. However, the nature of the stages is modified to incorporate the use of the family capability, essentially to allow systematic application of both compositional and generational reuse throughout the development process. The process described was evaluated on a trial project to develop, and subsequently modify, a thrust reverser system for a small aero-engine. Initial results show that this process can reduce effort for both initial and subsequent developments through the use of the family capability.