Advertisement

Diary of a domain analyst: a domain analysis case-study from avionics

  • Tim P. Kelly
  • Wing Lam
  • Ben R. Whittle
  • Andy Mowles
  • Rob Rimmer
Chapter
Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT)

Abstract

Domain analysis has been suggested by some in the reuse research community as an important process for achieving successful reuse. In this paper, we describe a domain analysis case-study in the domain of aero-engine systems. The principle objective of the case-study was to evaluate the use of a domain analysis technique on a complex domain in an industrial setting.

As a result of the case-study we have learnt a number of lessons about successful domain analysis practice and experienced at first hand some of the widely accepted difficulties. For example, we now know that it is important to uncover the ‘real’ issues in the domain, recognise the value of different information sources, organise and structure domain knowledge, and to recognise emerging architectures. The case-study has also helped us to identify the significance of those areas we feel are less well understood in domain analysis, such as domain structuring, modelling complex forms of commonality and optionality, rationale capture and multiple-perspectives. Adopting an analysis method provided some lessons and an introduction to more complex issues. However, we feel that our experience points to a number of areas which are not adequately supported by the domain analysis method and which therefore provide a suitable target for future research.

Keywords

Domain analysis reuse domain knowledge domain model requirements 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Arango G. and Prieto-Diaz R. (1991) Domain Analysis and Software Systems Modelling. IEEE Computer Society Press.Google Scholar
  2. Batory D., Coglianese L., Goodwin M. and Shafer S. (1995) Creating Reference Architectures: An Example from Avionics, in Proceedings of the ACM SIGSOFT Symposium on Software Reusability Seattle, Washington, April 28–30, 1995.Google Scholar
  3. France R.B. and Horton T.B. (1995) Applying Domain Analysis and Modelling: An Industrial Experience, in Proceedings of the ACM SIGSOFT Symposium on Software Reusability Seattle, Washington, April 28–30, 1995.Google Scholar
  4. Gomaa H. (1995) Reusable Software Requirements and Architectures for Families of Systems. Journal of Systems and Software, 28: 189–202.CrossRefGoogle Scholar
  5. Kang K., Cohen S., Hess J., Novak W. and Peterson S. (1990) Feature-Oriented Domain Analysis Feasibility Study. Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie-Mellon University.Google Scholar
  6. Prieto-Diaz R. (1990) Domain Analysis: an Introduction. Software Engineering Notes, 15: 47–54.CrossRefGoogle Scholar
  7. Rumbaugh J., Blaha M., Premerlani W., Eddy F. and Lorensen W. (1991) Object–Oriented Modelling and Design. Prentice–Hall ISBN 0–13–630054–5.Google Scholar
  8. Stars (1995) ‘Organisation Domain Modelling Guidebook’. STARS-VCA023/011/00, March 1995.Google Scholar
  9. Tracz W., Coglianese L. and Young P. (1993) A Domain-Specific Software Architecture Engineering Process Outline. Software Engineering Notes, 18(2):40–49.CrossRefGoogle Scholar
  10. Wartik S. and Prieto-Diaz P. (1992) Criteria for Comparing Reuse-Oriented Domain Analysis Approaches. International Journal of Software Engineering and Knowledge Engineering, 2 (3): 403–431.CrossRefGoogle Scholar

Copyright information

© IFIP International Federation for Information Processing 1996

Authors and Affiliations

  • Tim P. Kelly
    • 1
  • Wing Lam
    • 1
  • Ben R. Whittle
    • 1
  • Andy Mowles
    • 2
  • Rob Rimmer
    • 2
  1. 1.Rolls-Royce University Technology CentreUniversity of YorkUK
  2. 2.Rolls Smiths Engine Controls LimitedRolls-RoyceDerbyUK

Personalised recommendations