The missing link in requirements engineering

ABSTRACT

Especially the early phase of requirements engineering is one of the most important and least supported parts of the software life cycle. Since pure natural language has its disadvantages, and directly arriving at a formal representation is very difficult, a link through a mediating representation is missing. We use hypertext for this purpose, providing also links among requirements statements and the representation of objects in a domain model. This possibility of explicit representation of links allows the users and analysts to make relationships and dependencies explicit and helps to be aware of them. Actually, our approach and the tool supporting it use a combination of various technologies, including also object-oriented approaches and a grain of artificial intelligence (in particular frames). Therefore, inheritance is provided by our tool already in the early phase of requirements engineering. In particular, we found it very useful to view requirements as objects. A key idea is to support the ordering of ideas especially through classification already in the early stages. While our approach is not intended to substitute useful existing techniques emphasizing more formal representations, it can be combined with them.

REFERENCES

• 1: [1] R. Balzer. Final report on GIST. USC/ISI, Marina del Rey, Technical Report, 1981.
• 2: [2] A. Borgida, S. Greenspan and J. Mylopoulos. Knowledge representation as the basis for requirements specifications. IEEE Computer 18(4), 1985, 82-91.
• 3: P. J. Brown, Do we need maps to navigate round hypertext documents?, Electronic Publishing—Origination, Dissemination, and Design, v.2 n.2, p.91-100, July 1989
• 4: Peter Coad , Edward Yourdon, Object-oriented analysis (2nd ed.), Yourdon Press, Upper Saddle River, NJ, 1991
• 5: Andrew J. Czuchry, Jr. , David R. Harris, KBRA: A New Paradigm for Requirements Engineering, IEEE Expert: Intelligent Systems and Their Applications, v.3 n.4, p.21-24, 26-32, 34-35, December 1988 [doi>10.1109/64.10017]
• 6: Alan M. Davis, Software requirements: analysis and specification, Prentice Hall Press, Upper Saddle River, NJ, 1990
• 7: Dennis de Champeaux , Penelope Faure, A comparative study of object-oriented analysis methods, Journal of Object-Oriented Programming, v.5 n.1, p.21-33, March/April 1992
• 8: [8] P. Hayes. The Logic of Frames. In Frame Conceptions and Text Understanding, ed. D. Metzing, 46-61. Berlin, Germany: de Gruyter, 1979.
• 9: [9] W. L. Johnson, M. S. Feather and D. R. Harris. Integrating domain knowledge, requirements, and specifications. Journal of Systems Integration 1, 1991, 283-320.
• 10: [10] H. Kaindl. Object-Oriented Approaches in Software Engineering and Artificial Intelligence, to appear in Journal of Object-Oriented Programming (JOOP), 1993.
• 11: [11] H. Kaindl and S. Korner. Differences between Object-Oriented Languages and Frame Systems, to appear in IEEE Transactions on Software Engineering (SE), 1993.
• 12: Hermann Kaindl , Mikael Snaprud, Hypertext and Structured Object Representation: A Unifying View, Verteilte Künstliche Intelligenz und kooperatives Arbeiten, 4. Internationaler GI-Kongress Wissensbasierte Systeme, p.231-242, October 23-24, 1991
• 13: Hermann Kaindl , Holger G. Ziegeler, HyperAuthor - An Authoring Tool Based on Hypertext, Hypertext/Hypermedia, Tagung der GI, SI und OCG, p.156-163, May 27-28, 1991
• 14: Horst Morgenbrod, Requirements Engineering in großen Projekten, GI/OCG/ÖGI-Jahrestagung 1985, Wirtschaftsuniversität Wien, Übersichtsbeiträge und Fachgespräche zu den Themenschwerpunkten Softwaretechnologie / Standardsoftware / Bürokommunikation / Bildschirmtext, p.3-14, September 16-19, 1995
• 15: John Mylopoulos , Alex Borgida , Matthias Jarke , Manolis Koubarakis, Telos: representing knowledge about information systems, ACM Transactions on Information Systems (TOIS), v.8 n.4, p.325-362, Oct. 1990 [doi>10.1145/102675.102676]
• 16: J. Mylopoulos , L. Chung , B. Nixon, Representing and Using Nonfunctional Requirements: A Process-Oriented Approach, IEEE Transactions on Software Engineering, v.18 n.6, p.483-497, June 1992 [doi>10.1109/32.142871]
• 17: Jakob Nielsen, Hypertext and hypermedia, Academic Press Professional, Inc., San Diego, CA, 1990
• 18: James Martin , James J. Odell, Object-oriented analysis and design, Prentice-Hall, Inc., Upper Saddle River, NJ, 1992
• 19: [19] H. Partsch. Requirements Engineering. Handbuch der Informatik, Munich, Germany: Oldenbourg Verlag, 1991.
• 20: Balasubramaniam Ramesh , Vasant Dhar, Supporting Systems Development by Capturing Deliberations During Requirements Engineering, IEEE Transactions on Software Engineering, v.18 n.6, p.498-510, June 1992 [doi>10.1109/32.142872]
• 21: Howard B. Reubenstein , Richard C. Waters, The Requirements Apprentice: Automated Assistance for Requirements Acquisition, IEEE Transactions on Software Engineering, v.17 n.3, p.226-240, March 1991 [doi>10.1109/32.75413]
• 22: [22] G.-C. Roman. A taxonomy of current issues in requirements engineering, IEEE Computer 18(4), 1985, 14-22.
• 23: James Rumbaugh , Michael Blaha , William Premerlani , Frederick Eddy , William Lorensen, Object-oriented modeling and design, Prentice-Hall, Inc., Upper Saddle River, NJ, 1991
• 24: [24] W. E. Rzepka and Y. Ohno. Requirements engineering environments: software tools for modeling user needs, IEEE Computer 18(4), 1985, 9-12.
• 25: [25] M. Snaprud and H. Kaindl. Knowledge Acquisition Using Hypertext, Expert Systems with Applications: An International Journal 5(3/4), 1992, 369-375. Earlier versions are available in Proc. World Congress on Expert Systems, Orlando, Florida, December 1991, in Proc. AAAI-91 Workshop on Knowledge Acquisition, Anaheim, CA., July 1991, and in Proc. Artificial Intelligence and Knowledge-Based Systems for Space, ESTEC, Noordwijk, May 1991.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Life cycle

General Terms:
Design