Using domain knowledge for requirements engineering: a process view

  • Georges Grosz
  • Colette Rolland
  • Neil A. M. Maiden
Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT)


In this paper, we present a process model which describes the use of the domain theory* developed at the City University of London by Sutcliffe and Maiden. The domain theory proposes a means for modelling domain knowledge. We propose to view the process of modelling domain knowledge as a decision based process, as suggested by the process theory* developed at the University of Paris Sorbonne. Detailing out the process of modelling domain knowledge following the process theory contributes to (1) clarifying how one models domain knowledge as well as the decisional aspects of this process (2) putting forward heuristic knowledge implicitly used by requirements engineers in modelling domain knowledge and (3) proposals for a tool environment which offers effective guidance to requirements engineers based on the process representation.


Requirements Engineering Domain Knowledge Process Model CASE tool Domain theory Process theory 


  1. Chandrasekaran B., Keuneke A. and Tanner M. (1986) Explanation in Knowledge Systems, The Roles of the Task Structures and Domain Functional Models, Proc. of the Workshop on Task based Explanation, Samos, Greece.Google Scholar
  2. Dardenne A., Fickas S. and van Lamsweerde A. (1991) Goal-directed Concept Acquisition in Requirements Elicitation, in Proc. of the 6th Workshop on Software Specification and Design, Como, Italy, pp 14–21.CrossRefGoogle Scholar
  3. Falkenhainer B., Forbus K.D. and Gentner D. (1989) The Structure-Mapping Engine: Algorithm and Examples, Artificial Intelligence, 41, pp 1–63.zbMATHCrossRefGoogle Scholar
  4. A. Finkelstein, J. Kramer and B. Nuseibeh (eds) (1994) Software Process Modelling and Technology, John Wiley (pub).Google Scholar
  5. Fischer G., Girensohn A., Nakakoji K. and Redmiles D. (1992) Supporting Software Designers with Integrated Domain Oriented Design Environments, IEEE Transactions on Software Engineering, 18 (6), pp 511–522.CrossRefGoogle Scholar
  6. Jackson M and Zave P. (1993) Domain Description, Proc. of RE’93, 1st Intl. IEEE Symp. on Requirements Engineering, pp 56–64.Google Scholar
  7. Jarke M., Rolland R. and Sutcliffe A. (1995) The NATURE of Requirements Engineering, to be published.Google Scholar
  8. Maiden N.A.M and Sutcliffe A.G. (1991) Analogical Matching for Specification Retrieval, Proc of the 6th Knowledge-Based Software Engineering Conference, IEEE Computer Society Press, pp 108–116.CrossRefGoogle Scholar
  9. Maiden N.A.M and Sutcliffe A.G. (1993) Requirements Engineering by Example: an Empirical Study, Proc. of IEEE Symposium on Requirements Engineering, IEEE Computer Press, pp 104–112.Google Scholar
  10. Maiden N.A.M and Sutcliffe A.G. (1994) Requirements Critiquing Using Domain Abstractions, Proc. of the 1st Int. Symposium on Requirements Engineering, IEEE Computer Society press, pp 104–112.Google Scholar
  11. O2 (1993) The O2 User Manual.Google Scholar
  12. Plihon V. (1996): Un environnement pour l’ingénierie des méthodes, PhD dissertation, University of Paris 1, January 1996.Google Scholar
  13. Puncello P.P., Torrigiani P., Peitri F., Burion R., Cardile B. and Conti M. (1988) ASPII: A Knowledge-Based CASE Environment, IEEE Transactions on Software Engineering, 18 (6), pp 498–510.Google Scholar
  14. Prieto-Diaz R. (1987) Domain analysis for Reusability, in proceedings of COMPSAC’87, Tokyo, Japan.Google Scholar
  15. Reubenstein H.B. and Waters R.C. (1991) The Requirements Apprentice: Automated Assistance for Requirements Acquisition, IEEE Transactions on Software Engineering 17 (3), pp 226–240.CrossRefGoogle Scholar
  16. Rolland C. and Grosz G. (1994) A General Framework for Describing the Requirements Engineering Process, C. IEEE Conference on Systems Man and Cybernetics, CSMC94, San Antonio, Texas.Google Scholar
  17. Rolland C., Souveyet C., Moreno M. (1995) An Approach for defining ways-of-working, Information System Journal, 20 (4) pp 337–359.CrossRefGoogle Scholar
  18. Schmitt J. R. (1993) Product Modelling in Requirements Engineering Process Modelling, IFIP TC8 Int. Conf. on “Information Systems Development Process”, North Holland (Pub.), Como, Italy.Google Scholar
  19. Si-Said S. and Ben Achour C. (1995) A Tool for Guiding the Requirements Engineering Process, in Proceedings of the 6th Workshop on the Next Generation of CASE Tools, Jyvaskyla, Finland, pp 23–42.Google Scholar
  20. Sutcliffe A.G. and Maiden N.A.M. (1994) A Theory of Domain Knowledge for Requirements Engineering, NATURE Report Deliverable D-D-2.Google Scholar
  21. Winlenga B.J., Schreiber A. Th. and Breuker J.A. (1992) KADS: A modelling approach to knowledge engineering, Knowledge acquisition 4(1), pp 5–53, Special Issue on “the KADS approach to knowledge engineering”.CrossRefGoogle Scholar

Copyright information

© IFIP International Federation for Information Processing 1996

Authors and Affiliations

  • Georges Grosz
    • 1
  • Colette Rolland
    • 1
  • Neil A. M. Maiden
    • 2
  1. 1.Centre de Recherche en InformatiqueUniversité Paris1 SorbonneParisFrance
  2. 2.Dpt. of Business ComputingCity UniversityLondonUK

Personalised recommendations