The Three Dimensions of Requirements Engineering

  • Klaus PohlEmail author


Requirements engineering (RE) is perceived as an area of growing importance. Due to the increasing effort spent for research in this area many contributions to solve different problems within RE exist. The purpose of this paper is to identify the main goals to be reached during the requirements engineering process in order to develop a framework for RE. This framework consists of the three dimensions:
  • the specification dimension

  • the representation dimension

  • the agreement dimension

Looking at the RE research using this framework, the different approaches can be classified and therefore their interrelationships become much clearer. Additionally the framework offers a first step towards a common understanding of RE.


Software Engineer IEEE Computer Society Requirement Engineering Formal Language Representation Language 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    B. Adelson and E. Soloway. The Role of Domain Experience in Software Design. IEEE Transaction on Software Engineering, 11(11), 1985.Google Scholar
  2. 2.
    Mack W. Alford. Software Requirements Engineering Methodology (SREM) at the age of two. In 4th Int. Computer Software & Applications Conference, New York, pages 866–874. IEEE, 1980.Google Scholar
  3. 3.
    R. Balzer. Tolerating Inconsistency. In Int. Conference on Software Engineering, pages 158–165, Austin, Texas, 1991.Google Scholar
  4. 4.
    R. Balzer, N. Goldman, and D. Wile. Informality in program specifications. IEEE Transactions on Software Engineering, 4(2):94–103, 1978.CrossRefGoogle Scholar
  5. 5.
    D.R. Barstow. Domain Specific Automatic Programming. IEEE Transaction on Software Engineering, 11(11), 1985.Google Scholar
  6. 6.
    James Bigelow. Hypertext and CASE. IEEE Software, pages 23–27, March 1988.Google Scholar
  7. 7.
    T. Biggerstaff and R. Richter. Reusability Framework, Assesment and Directions. IEEE Transaction on Software Engineering, 13(2), 1987.Google Scholar
  8. 8.
    D. Bjoerner and C.B. Jones. VDM'87 VDM-A Formal Method at Work. LNCS 252, Springer Verlag, 1988.Google Scholar
  9. 9.
    Alexander Borgida, Sol Greenspan, and John Mylopoulos. Knowledge Representation as the Basis for Requirements Specifications. Computer, 18(4):82–91, April 1985.CrossRefGoogle Scholar
  10. 10.
    Marilyn Bush. Improving Software Quality: The use of Formal Inspections at the Jet Propulsion Laboratory . In Proc. of the 12th Int. Conf on Software Engineering, March 26–30, Nice, France, pages 196–199, 1990.Google Scholar
  11. 11.
    B.W.Boehm. Verifying and Validating Software Requirements and Design Specifications. IEEE Software, 1(1):75–88, January 1984.CrossRefGoogle Scholar
  12. 12.
    John R. Camaron. An Overview of JSD. IEEE Transaction on Software Engineering, 12(2):222–240, February 1986.Google Scholar
  13. 13.
    P.P.S. Chen. The Entity-Relationship Approach: Towards a Unified View of Data. ACM Transactions on Database Systems, 1(1), 1976.Google Scholar
  14. 14.
    Peter Coad and Edward Yourdon. Object Oriented Analysis. Prentice-Hall, Englewood Cliffs, New Jersey, 1990.Google Scholar
  15. 15.
    J. Conklin and M. J. Begeman. giBIS: A Hypertext Tool for Exploratory Policy Discussion. ACM Transaction on Office lnfonnation Systems, 6(4):303–331, 1988.Google Scholar
  16. 16.
    P. Constantopoulos, M. Jarke, J. Mylopoulos, and Y. Vassiliou. Software Information Base: A server for reuse. ESPRIT project ITHACA, Heraklion, Crete, ICS-FORTH, 1991.Google Scholar
  17. 17.
    B. Curtis, H Krasner, and N. lscoe. Field Study of the Software Design Process for Large Systems. Communication of the ACM, 33(11):1268–1287, 1988.Google Scholar
  18. 18.
    Bill Curtis, Marc I. Kellner, and Jim Over. Process Modelling. Communications of the ACM, 35(9):75–90, September 1992.CrossRefGoogle Scholar
  19. 19.
    A. Czuchry and D. Harris. KBSA: A New Paradigm for Requirements Engineering. IEEE Expert, 3(4):21–35, 1988.CrossRefGoogle Scholar
  20. 20.
    Alan M. David. The Analysis and Specification of Systems and Software Requirements. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 119–134. IEEE Computer Society Press- Tutorial, 1990.Google Scholar
  21. 21.
    Alan M. Davids. A Comparison of Techniques for the Specification of External System Behavior. Communications of the ACM, 31(9):1098–1115, 1988.Google Scholar
  22. 22.
    V. de Antonellis, B. Pernici, and P. Samarati. F-ORM Method: Methodology for reusing Specifications. ITHACA Journal, (14):1–24, 1991.Google Scholar
  23. 23.
    W. E. Deming. Out of the Crisis. Massachusetts Institiute of Technology, Center for Advanced Engineering Study, Cambridge, 1986.Google Scholar
  24. 24.
    V. Dhar and M. Jarke. Dependency Directed Reasoning and Learning in System Maintenance Support. IEEE Transactions on Software Engineering, 14(2):211–228, 1988.CrossRefGoogle Scholar
  25. 25.
    Merlin Dorfman and Richard H. Thayer. Standards, Guidelines and Examples on System and Software Requirements Engineering. IEEE Computer Society Press- Tutorial, 1990.Google Scholar
  26. 26.
    M. Dowson. Iteration in the Software Process. In Proceedings 9th Int. Conf. on Software Engineering, April 1987.Google Scholar
  27. 27.
    C. A. Ellis, S. J. Gibbs, and G. L. Rein. Groupware: Some Issues and Experience. Conununication of the ACM, 34(1):38–58, 1991.Google Scholar
  28. 28.
    M. S. Feather and S. Fickas. Coping with Requirements Freedom. In Proceedings of the International Workshop on the Development of Intelligent lnfonnation Systems, pages 42–46, Niagara-on-the-Lake, Ontario, Canada, April 1991.Google Scholar
  29. 29.
    S. Fickas. Automating analysis: An example. In Proceedings of the 4th International Workslwp Software Specification and Design, pages 58–67, Washington, DC, April 1987.Google Scholar
  30. 30.
    S. Fickas and P. Nagarajan. Critiquing Software Specifications. IEEE Software, pages 37–47, November 1988.Google Scholar
  31. 31.
    A. Finkelstein, J. Kramer, B. Nuseibeh, L. Finkelstein, and M. Goedicke. Viewpoints: A Framework for Integration Multiple Perspectives in System Development. International Journal of Software Engineering and Knowledge Engineering, 1(2), May 1992.Google Scholar
  32. 32.
    Gerhard Fischer, Raymond McCall, and Anders Morch. JANUS: Integrating Hypertext with a Knowledge-based Design Environment. In Proceedings of Hypertext '89, November 5–8, Pittsburgh, Pennsylvania, pages 105–117, 1989.Google Scholar
  33. 33.
    R.F. Flynn and D. Dorfmann. The Automated Requirements Traceability System (ARTS): An Experience of Eight Year. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 423–438. IEEE Computer Society Press- Tutorial, 1990.Google Scholar
  34. 34.
    Martin D. Fraser, Kuldeep Kumar, and Vi jay K. Vaishnavi. Informal and Formal Requirements Specification Languages Bridging the Gap. IEEE Transactions on Software Engineering, 17(5):454–466, May 1991.Google Scholar
  35. 35.
    Daniel P. Freeman and Gerald M. Weinberg. Handbook of Walkthroughs, Inspections and Teclmical Reviews. Dorset House Publishing, New York, 1990.Google Scholar
  36. 36.
    P. Freemann, editor. Software reusability. IEEE Press- Tutorial, 1987. K. PohlGoogle Scholar
  37. 37.
    Pankaj K. Garg and Walt Scacchi. On Designing Intelligent Hypertext Systems for Information Management in Software Engineering. In Proceedings of Hypertext '87, November 13–15, Chapel Hill, North Carolina, pages 409–432, 1987.Google Scholar
  38. 38.
    Pankaj K. Garg and Walt Scacchi. A Hypertext System to Manage Software Life-Cycle Documents. IEEE Software, pages 90–98, May 1990.Google Scholar
  39. 39.
    D. Gentner. Structure Mapping: A Theoretical Framework for Analogy. Cognitive Science, 5:121–152, 1983.Google Scholar
  40. 40.
    Joseph A. Goguen, Marina Jirotka, and Matthew J. Bickerton. Research on Requirements Capture and Analysis. Technical report, Oxford University Computing Laboratory, Centre for Requirements and Foundations, December 1991.Google Scholar
  41. 41.
    S.J. Greenspan. Requirements Modeling: A Knowledge Representation Approach to Software Requirements Defmition. PhD thesis, Dept. of Computer Science, University of Toronto, 1984.Google Scholar
  42. 42.
    I. Greif, editor. Readings in Computer-Supported Cooperative Work. Morgan Kaufmann, 1988.Google Scholar
  43. 43.
    George Grosz and Colette Roland. Using artificial intelligence techniques to formalize the information system design process. In Proc. Int. Conf Databases and expert Systems Applications, pages 374–380, 1990.Google Scholar
  44. 44.
    R. Guidon and B. Curtis. Control of cognitive process during software design: What tools are needed? In E. Soloway, D. Frye, and S.B. Sheppard, editors, Proc. of CHI '88 Conference: Human Factors in Computer Systems, pages 263–269. ACM Press NY, 1991.Google Scholar
  45. 45.
    J. Hagelstein. Declarative Approach to Information Systems Requirements. Knowledge Base Systems, 1(4):211–220, 1988.CrossRefGoogle Scholar
  46. 46.
    Anthony Hall. Seven Myths of Formal Methods. IEEE Software, (9): 11–19, September 1990.Google Scholar
  47. 47.
    C.A.R. Hoare. International Conference on VDM and Z. LNCS 428, Springer Verlag, 1990.Google Scholar
  48. 48.
    IEEE. Standards, Guidelines, and Examples on System and Software Requirements Engineering. IEEE Computer Society Press - Tutorial, 1990.Google Scholar
  49. 49.
    IEEE. IEEE Std. 830–1984. In IEEE Software Engineering Standards Collection. IEEE, New York, 1991.Google Scholar
  50. 50.
    Matthias Jarke, Janis Bubenko, Colette Rolland, Allistair Sutcliffe, and Yannis Vassiliou. Theories Underlying Requirements Engineering: An Overview of NATURE at Genesis. In Proceedings of the lth Int. Symposium of Requirements Engineering, San Diego, CA, 1993. to appear.Google Scholar
  51. 51.
    Matthias Jarke, Stephan Jacobs, and Klaus Pohl et. al. Requirements Engineering: An Integrated View of Representation, Process and Domain. In submitted to: ECSE '93, 1993.Google Scholar
  52. 52.
    Matthias Jarke, Manfred Jeusfeld, and Thomas Rose. A Software Process Data Model for Knowledge Engineering in Information Systems. Information Systems, 15(1 ):85–116, 1990.CrossRefGoogle Scholar
  53. 53.
    Matthias Jarke and Klaus Pohl. Information System Quality and Quality Information Systems. In Proceedings of the IFIP 8.2 Working Conference on the Impact of Computer-Supported Techniques on Information Systems Development, 1992.Google Scholar
  54. 54.
    Matthias Jarke and T. Rose. Specification Management with CAD0• In P. Loucopoulos and R. Zicari, editors, Conceptual Modeling Databases, and CASE, 1991.Google Scholar
  55. 55.
    Manfred Jeusfeld. Anderungskontrolle in deduktiven Objektbanken. INFIX Pub, Bad Honnef, Germany, 1992.Google Scholar
  56. 56.
    P. Johannesson and K. Kalman. A Method for Translating Relational Schemas into Conceptual Schemas. In 8th bit. Conf. on Entity-Relationship Approach, pages 279–294, 1989.Google Scholar
  57. 57.
    W. Lewis Johnson. Deriving Specifications from Requirements. In Proceedings of the lOth International Conference 011 Software Engineering, pages 428–438, Singapore, April 1988.Google Scholar
  58. 58.
    W. Lewis Johnson and Martin Feather. Building An Evolution Transformation Library. In Proceedings of the 12th International Conference on Software Engineering, pages 428–438, Nice, France, March 1990.Google Scholar
  59. 59.
    W. Lewis Johnson, Martin. S. Feather, and David. R. Harris. Representation and Presentation of Requirements Knowledge. IEEE Transactions on Software Engineering, 18(10), October 1992.Google Scholar
  60. 60.
    W. Lewis Johnson and David R. Harris. The ARIES Project. In Proceedings 5th KBSA Conference, pages 121–131, Liverpool, N.Y., 1990.Google Scholar
  61. 61.
    S. E. Keller, L. G. Kahn, and R. B.Panara. Specifying Software Quality Requirements with Metric. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 145–163. IEEE Computer Society Press- Tutorial, 1990.Google Scholar
  62. 62.
    Manolis Koubarakis, John Mylopoulos, Martin Stanley, and Matthias Jarke. Telos: A Knowledge Representation Language for Requirements Modelling. Technical Report KRRTR- 89–1, Department of Computer Science, University of Toronto, 1989.Google Scholar
  63. 63.
    Julio Cesar S. P. Leite. Viewpoint Analysis: A Case Study. In Proceedings of the 5th International Workshop on Software and Design, pages 111–119, Pittsburgh, PA, 1989.Google Scholar
  64. 64.
    Julio Cesar S. P. Leite and Peter A. Freeman. Requirements Validation Through Viewpoint Resolution. IEEE Transactions on Software Engineering, 17(12):1253–1269, December 1991.Google Scholar
  65. 65.
    P. Loucopoulos and R. Champion. Knowledge-Based Approach to Requirements Engineering Using Method and Domain Knowledge. Knowledge-Based Syste1ns, 1(3), 1988.Google Scholar
  66. 66.
    M.D. Lubars and M.T. Harandi. Knowledge-Based Software Design Using Design Schemas. In Proceedings 9th Int. Conf. on Software Engineering, April 1987.Google Scholar
  67. 67.
    Neil Maiden. Analogy as a Paradigm for Specification Reuse. Software Engineering Journal, 1991.Google Scholar
  68. 68.
    Neil Maiden. Analogical specification Reuse during Requirements Analysis. PhD thesis, City University London, 1992.Google Scholar
  69. 69.
    M. Mannino and V. Tseng. Inferring Database Requirements from Examples in Forms. In Int. Conf. on Entity-Relationship Approach, pages 391–405. Elsevier Publishers B.V. (NorthHolland), 1989.Google Scholar
  70. 70.
    David Marca and Geoffrey Bock. Groupware: Software for Computer-Supported Cooperative Work. IEEE Computer Society Press, Los Alamitos, CA, 1992.Google Scholar
  71. 71.
    Stephen M. McMenamin and John F. Palmer. Essential System Analysis. Yourdon Press, Prentice Hall, Englewood Cliffs, NJ 07632, 1984.Google Scholar
  72. 72.
    Richard H. Thayer Merlin Dorfman, editor. Standards, Guidelines, and Examples on System and Software Requirements Engineering, chapter ESA Software Engineering Standards, pages 101–120. IEEE Computer Society Press Tutorial, 1990.Google Scholar
  73. 73.
    Bertrand Meyer. On Formalism in Specifications. IEEE Software, pages 6–26, January 1985.Google Scholar
  74. 74.
    Kauth Miriyala and Mehdi T. Harandi. Automatic Derivation of Formal Software Specifications Form Informal Descriptions. IEEE Transactions on Software Engineering, 17(10): 1126–1142, October 1991.CrossRefGoogle Scholar
  75. 75.
    David E. Monarchi and Gretchen I. Puhr. A Research 1)'pology for Object-Oriented Analysis and Design. Communications of the ACM, 35(9):35–47, September 1992.CrossRefGoogle Scholar
  76. 76.
    John Mylopoulos, Alex Borgida, Matthias Jarke, and Manolis Koubarakis. Telos: Representing Knowledge about Information Systems. Transactions on Information SystelllS, 8(4):325–362, 1990.CrossRefGoogle Scholar
  77. 77.
    John Mylopoulos and Hector J. Levesque. On Conceptual Modelling. Springer Verlag, 1986.Google Scholar
  78. 78.
    J. S. Oakland. Total Quality Management. In Proceedings 2nd Int. Conf. on Total Quality Management, pages 3–17. Cotswold Press Ltd., 1989.Google Scholar
  79. 79.
    Barbara Pernici. Requirements Specifications for Object Oriented Systems. ITHACA Journal, (8):43–63, January 1991.Google Scholar
  80. 80.
    Klaus Pohl and Matthias Jarke. Quality Information Systems: Repository Support for Evolving Process Models. Technical report, RWTH Aachen, Informatik-Berichte 37–92, 1992. K. PohlGoogle Scholar
  81. 81.
    M. Porter. Competitive Advantage. Free Press, New York, 1985.Google Scholar
  82. 82.
    C. Potts. A Generic Model for Representing Design Methods. In Proceedings 11th lntemational Conference on Software Engineering, 1989.Google Scholar
  83. 83.
    C. Potts and G. Bruns. Recording the Reasons for Design Decisions. In Proceedings lOth lntemational Conference on Software Engineering, 1988.Google Scholar
  84. 84.
    P. Paolo Puncello, Piero Torrigiani, Francesco Pietri, Riccardo Burlon, Bruno Cardile, and Mirella Conti. ASPIS: A Knowledge-Based CASE Environment. IEEE Software, pages 58–65, March 1988.Google Scholar
  85. 85.
    B. Ramesh and V. Dhar. Process-Knowledge Based Group Support in Requirements Engineering. IEEE Transactions on Software Engineering, 18(6), 1992.Google Scholar
  86. 86.
    Howard B. Reubenstein and Richard C. Waters. The Requirements Apprentice: Automated Assistance for Requirements Acquisition. IEEE Transactions on Software Engineering, 17(3):226–240, March 1991.Google Scholar
  87. 87.
    C. Rolland and C. Proix. A Natural Language Approach for Requirements Engineering. In Proceedings of the 4th Intemational Conference 011 Advanced lnfonnation Systems Engineering, LNCS 593, 1992.Google Scholar
  88. 88.
    T. Rose, M. Jarke, M. Gocek, C.G. Maltzahn, and H.W. Nissen. A Decision-based Configuration Process Environment. Special Issue on Software Process Support, lEE Software Engineering Journal, 6(5):332–346, 1991.Google Scholar
  89. 89.
    H.H. Sayani. PSUPSA at the Age of Fifteen. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 403–417. IEEE Computer Society PressTutorial, 1990.Google Scholar
  90. 90.
    Wall Scacchi. Managing Software Engineering Projects: A Social Analysis. IEEE Transaction on Software Engineering, 10(1):49–59, 1984.CrossRefGoogle Scholar
  91. 91.
    G. Spanoudakis and P. Constanlopoulos. Similarity for Analogical Software Reuse. In Proc. ERCIM Workshop on Methods and Tools for Software Reuse, Heraklion, Crete, 1992.Google Scholar
  92. 92.
    J.M. Spivey. An introduction to Z and formal specifications. Software Engineering Journal, 4(1):40–50, 1990.CrossRefGoogle Scholar
  93. 93.
    Alistair Sutcliffe. Object Oriented Systems Analysis: The Abstract Question. In Proc. I FIP WG 8.1 Conf. The Object Oriented Approach in Jnfonnation Systems, Quebec City, Canada, 1991.Google Scholar
  94. 94.
    Alistair Sutcliffe and Neil Maiden. Software reuseabilily: Delivering Productivity gains or short cuts. In Proceedings INTERACT, pages 948–956. North-Holland, 1990.Google Scholar
  95. 95.
    C.P. Svoboda. Structured Analysis. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 218–227. IEEE Computer Society Press-Tutorial, 1990.Google Scholar
  96. 96.
    Jeanette M. Wing. A Specifier's Introduction to Formal Methods. Computer, (9):8–24, September 1990.Google Scholar
  97. 97.
    T. Winograd and F. Flores. Understanding Computers and Cognition: A New Foundation for Design. Ablex Norwood, NJ, 1986.Google Scholar
  98. 98.
    Edward Yourdon. Modem Structured Analysis. Prentice-Hall, Englewood Cliffs, NJ, 1989.Google Scholar
  99. 99.
    Edward Yourdon. Structured Walkthroughs. Prentice-Hall, Englewood Cliffs, NJ, 1989.Google Scholar
  100. 100.
    Pamala Zave. An Insider's Evaluation of PAISLey. IEEE Transactio11 on Software Engineering, 17(3):212–225, March 1991.Google Scholar
  101. 101.
    Pamela Zave. A Comparison of the Major Approaches to Software Specification and Design. In Thayer R.H. and M. Dorfman, editors, Systems and Software Requirements Engineering, pages 197–199. IEEE Computer Society Press- Tutorial, 1990.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  1. 1.Informatik VRWTH-AachenAachenGermany

Personalised recommendations