Advertisement

Representing the knowledge used during the Requirement engineering activity with generic structures

  • Georges Grosz
  • Colette Rolland
Methodologies
Part of the Lecture Notes in Computer Science book series (LNCS, volume 689)

Abstract

Abstracting informal requirements in terms of formal specifications of the future information system is the aim of the Requirement Engineering activity (RE). It is a cognitive activity mostly based on analogical reasoning. Skilled designers reuse the experience gain from previous design when they recognise similarities between different applications. In order to build truly intelligent systems to efficiently support RE, we believe mandatory to represent the knowledge underlying this experience. Using this representation allows to re-use part of the design process and thus, brings quality as well as productivity improvements. Our solution relies on the concept of generic structure. It is based on the following observation: many real-world phenomena, apparently different, are described in the same way. A generic structure is the expression of this common denominator, it describes behavioural as well as statical aspects. In this paper, we present the concept of generic structure and how it can be used with a simple example.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    E. Dubois, J. Hagelstein, E. Lahou, F. Ponsaert, A. Rifaut: “A Knowledge Representation Language for Requirements Engineering”, Proceedings of the IEEE, Vol. 74, Nb. 10, pp. 1431–1444, 1986.Google Scholar
  2. 2.
    B.W. Boehm: “Verifying and Validating. Software Requirements and Design Specifications”, IEEE Software, Vol. 1, Nb 1, January 1984.Google Scholar
  3. 3.
    A. M. Davis: “Software requirements, analysis and specification”. Prentice Hall ed, 1990.Google Scholar
  4. 4.
    N. Maiden and A. Sutcliffe: “Specification Reuse by Analogy”, proceedings of 2nd Workshop on the Next Generation of CASE tools, Trondheim, Norway, May 1991.Google Scholar
  5. 5.
    G. Grosz, J. Brunet: “Transformation of Informal Entities into Object Schemas using Generic Structures”, submitted paper.Google Scholar
  6. 6.
    G. Grosz: “Formalisation des connaissances réutilisables pour la conception des systèmes d'information”, PhD dissertation University Paris 6, December 1991.Google Scholar
  7. 7.
    G. Grosz: “Building Information System Requirements using Generic Structures”, to appear in the Proceedings of the 16th COMPSAC Conference, Chicago, September 1992.Google Scholar
  8. 8.
    G. Grosz, C. Rolland: “Knowledge Support for Information System Design”, in the proceedings of “The 5th Jerusalem Conference on Information Technology”, pp 261–268, October 1990, Jerusalem, Israel.Google Scholar
  9. 9.
    V. Seppanen, M. Heikkinen, R. Lintulampi, “SPADE — Towards CASE Tools That Can Guide Design”, proceedings of the CAiSE 91 Conference, pp 222–239, Trondheim, Norway, May 1991.Google Scholar
  10. 10.
    M. G. Fugini, B. Pernici: “RECAST: A Tool for Reusing Requirements, in Advanced Information Systems Engineering”, B. Steiner, A. Solvberg, L. Bergman (eds.). Springer Verlag Lecture Notes In Computer Science, 1990.Google Scholar
  11. 11.
    Rolland, C., Proix, C.: “An Expert System Approach to Information System Design”, in IFIP World Congress 86, Dublin, 1986.Google Scholar
  12. 12.
    M. Bouzeghoub, G. Gardarin, E. Metais: “Database Design Tool: an Expert System Approach,” Proc. of the 11th VLDB Conference, Stockolm, August 1985.Google Scholar
  13. 13.
    M. V. Mannino, V. P. Tseng: “Inferring Data base Requirements from Examples in Forms”, 7th International Conference on Entity-Relationship Approach, pp 1–25, Rome, Italy, 1988.Google Scholar
  14. 14.
    Talldal B., Wangler B.: “Extracting a Conceptual Model from Examples of Filled in Forms”, Proc. of Int. conference. COMAD, pp 327–350, N. Prakash (ed), New Delhi, India, December 1990.Google Scholar
  15. 15.
    H.B. Reubenstein, R.C. Waters: “The Requirements Apprentice: Automated Assistance for Requirements Acquisition”, IEEE Transactions on Software Engineering, Vol. 17, Nb. 3, pp 226–240, March 1991.Google Scholar
  16. 16.
    G. Arango, P. Freeman: “Modeling knowledge for software development”, in Proc. 3rd Workshop on Software Specification and Design, IEEE Computer Society Press (ed), London, August 1985, pp63–66.Google Scholar
  17. 17.
    R. T. Mittermeir, M. Oppitz: “Software Bases for the Flexible Composition of Applications Systems”, IEEE Transaction on Software Engineering, Vol 13, No 4, pp440–460, April 1987.Google Scholar
  18. 18.
    S. Katz, CA. Richter, K.S. The: “PARIS: A System for Reusing Partially Interpreted Schemas”, in the proceedings of the 9th Software Engineering Conference, pp 377–384, 1987.Google Scholar
  19. 19.
    M. T. Harandi, F. H. Young: “Template Based Specification and Design”, in Proc. 3rd Workshop on Software Specification and Design, IEEE Computer Society Press (ed), London, August 1985, pp94–97.Google Scholar
  20. 20.
    B. Pernici, G. Vaccari, R. Villa: “INTRES: INTelligent REquirements Specification”, proceedings IJCAI'89 Workshop on Automatic Software Design, Detroit, Michigan, USA, August 1989.Google Scholar
  21. 21.
    G. Grosz, C Kung, C. Rolland: “Generic Structures: A Reuse-Based Approach to Conceptual Design of Information Systems”, proceedings WITS conference, Dallas, Texas, December 1992.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Georges Grosz
    • 1
  • Colette Rolland
    • 1
  1. 1.Equipe C. Rolland, C.R.I.Université Paris1-SorbonneParisFrance

Personalised recommendations