A Family-Oriented Software Development Process for Engine Controllers
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.
KeywordsSoftware Engineer Software Architecture Software Development Process Architectural Style Family Analysis
Unable to display preview. Download preview PDF.
- [Barnes97]John Barnes. High Integrity Ada The SPARK Approach. Addison-Wesley Longman Ltd, 1997.Google Scholar
- [Berzin99]Sergey Berezin. The SMV web site. http://www.cs.cmu.edu/~modelcheck/smv.html, 1999. The latest version of SMV and its documentation may be downloaded from this site.
- [Burns-et-al95]A. Burns and A.J. Wellings. HRT-HOOD: A Structured Design Method for Hard Real Time Ada Systems. Elsevier, 1995.Google Scholar
- [Burton-et-al00]Simon Burton, John Clark, and John McDermid. Testing, proof and automation, an integrated approach. In Proceedings of the 1st International Workshop on Automated Program Analysis, Testing and Verification, June 2000.Google Scholar
- [Clark-et-al97]John Clark and Nigel Tracey. Solving constraints in LAW. LAW/D5.1.1(E), European Commission-DG III Industry, 1997. Legacy Assessment Worbench Feasibility Assessment.Google Scholar
- [Coplien-et-al98]James Coplien, Daniel Hoffmann, and David Weiss. Commonality and variability in software engineering. IEEE Software, pages 37–45, November/December 1998.Google Scholar
- [DeMillo-et-al78]R. DeMillo, R. Lipton, and F. Sayward. Hints on test data selection: Help for the practicing programmer. IEEE Computer, 11:34–41, 1978.Google Scholar
- [Galloway-et-al-98]Andy Galloway, Trevor Cockram, and John McDermid. Experiences with the application of discrete formal methods to the development of engine control software. Proceedings of DCCS’ 98. IFAC, 1998.Google Scholar
- [Hill-et-al94]J.V. Hill, J.A. McDermid, R. Rimmer, and B.R. Whittle. Re-use of engine control technology. 1994 Avionics Conference and Exhibition, ERA Technology, 1994.Google Scholar
- [Mannion-et-al99]Mike Mannion, Barry Keepence, Hermann Kaindl, et. al. Reusing Single System Requirements from Application Family Requirements. In Proceedings of the 21st International Conference of Software Engineering, pages 453–463, May 1999.Google Scholar
- [McDermid-et-al98]John McDermid, Andy Galloway, Simon Burton, John Clark, Ian Toyn, Nigel Tracey and Samuel Valentine. Towards industrially applicable formal methods: Three small steps, one giant leap. Proceedings of the International Conference on Formal Engineering Methods, October 1998.Google Scholar
- [Ould95]M.A. Ould. Business Processes: Modelling and analysis for re-engineering and improvement. Wiley, 1995.Google Scholar
- [Prieto-Díaz90]R Prieto-Díaz. Domain Analysis: an Introduction. Software Engineering Notes, 15(2):47–54, April 1990.Google Scholar
- [simpson96]H.R. Simpson. Layered architecture(s): Principles and practice in concurrent distributed systems. In IEEE Symposium on Parallel and Distributed Processing, 1996.Google Scholar
- [SEI97]Software Engineering Institute. Model-Based Software Engineering. http://www.sei.cmu.edu/mbse/, 1997.
- [Spivey92]J.M. Spivey. The Z Notation-A Reference Manual. Prentice-Hall, Second edition, 1992.Google Scholar
- [Toyn96]Ian Toyn. Formal reasoning in the Z notation using CADiZ. 2nd International Workshop on User Interface Design for Theorem Proving Systems, July 1996.Google Scholar
- [Toyn99]Ian Toyn. The CADiZ web site. http://www.cs.york.ac.uk/~ian/cadiz/, 1999. The latest version of CADiZ and its documentation may be downloaded from this site.
- [Vickers-et-al96a]A. Vickers, P. Tongue and J. Smith. Complexity and its Management in Requirements Engineering. INCOSE UK Annual Symposium-Getting to Grips with Complexity, Coventry, UK, 1996.Google Scholar
- [Vickers-et-al96b]A.J. Vickers, J.E. Smith, P.J. Tongue and W. Lam. The ConCERT Approach to Requirements Specification-Version 2.0. Technical Report YUTC/TR/96.1 Rolls-Royce University Technology Centre, University of York, York, UK, YO10 5DD, November 1996.Google Scholar