Skip to main content
SpringerLink
Log in

From conceptual modelling to requirements engineering

  • Published:
Annals of Software Engineering

Abstract

Conceptual modelling is situated in the broader view of information systems requirements engineering. Requirements Engineering (RE) explores the objectives of different stakeholders and the activities carried out by them to meet these objectives in order to derive purposeful system requirements and therefore lead to better quality systems, i.e., systems that meet the requirements of their users. Thus RE product models use concepts for modelling these instead of concepts like data, process, events, etc., used in conceptual models. Since the former are more stable than the latter, requirements engineering manages change better. The paper gives the rationale for extending traditional conceptual models and introduces some RE product models. Furthermore, in contrast to conceptual modelling, requirements engineering lays great stress on the engineering process employed. The paper introduces some RE process models and considers their effect on tool support.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Brinkkemper, S. (1990), "Formalisation of Information Systems Modelling," Ph.D. Thesis, University of Nijmegen, Thesis Publishers, Amsterdam.

    Google Scholar 

  • Brunet J., C. Cauvet and L. Lasoudris (1990), "Why Using Events in a High-level Specification," In Proceedings of the International Conference on Entity-Relationship Modelling, ER90, Lausanne, Switzerland.

  • Bubenko, J.A. and B. Wangler (1992), "Research Directions in Conceptual Specification Development in Conceptual Modelling, Databases, and CASE," In P. Loucopoulos and R. Zicari, Eds., Wiley, pp. 389–412.

  • Bubenko, J.A. and M. Kirikova (1994), "Worlds in Requirements Acquisition an Modelling," In 4th European-Japanese Seminar on Information Modelling and Knowledge Bases, Kangassalo and Wangler, Eds., Kista, Sweden, IOS.

  • Bubenko, J., C. Rolland, P. Loucopoulos and V. De Antonnellis (1994), "Facilitating Fuzzy to Formal Requirements Modelling," In Proc. Int. Conf. on Requirements Engineering (ICRE), Colorado Springs, USA.

  • Curtis, B., H. Krasner and N. Iscoe (1988), "A Field Study of the Software Design Process for Large Systems," Communications ACM31, 11, 1268–1287.

    Article  Google Scholar 

  • Dardenne, A., S. Fickas and A. van Lamsweerde (1991), "Goal-directed Concept Acquisition in Requirements Elicitation," In Proc. 6th IEEE Workshop System Specification and Design, Como, Italy, pp. 14–21.

  • Dardenne, A., A. van Laamsweerde and S. Fickas (1993), "Goal Directed Requirements Acquisition," Science of Computer Programming 20, 1–2, 3–50.

    Article  MATH  Google Scholar 

  • Desfray, P. (1994), Object Engineering, The Fourth Dimension, Addison-Wesley/Masson.

  • DoD-2667A Military Standard (1988), "Defence System Software Development," Department of Defence.

  • Dowson, M. and C. Fernstrom (1994), "Towards Requirements for Enactment Mechanisms," In Proc.European Workshop on Software Process Technology.

  • Dubois, E., J. Hagelstein and A. Rifaut (1989), "Formal Requirements Engineering with ERAE," Philips Journal of Research 43, 4.

    Google Scholar 

  • Feiler, P.H. and W.S. Humphrey (1993), "Software Process Development and Enactment: Concepts and Definitions," In Proceedings of the Second Intl. Conf. on Software Process.

  • Finkelstein, A., J. Kramer and M. Goedicke (1990), "ViewPoint Oriented Software Development," In Proc. Conf. Le G´enie Logiciel et ses Applications, Toulouse, pp. 337–351.

  • Franckson, M. and C. Peugeot (1991), "Specification of the Object and Process Modeling Language," ESF Report No. D122-OPML-1. 0.

  • Gotel, O. and A. Finkelstein (1994), "Modelling the Contribution Structure Underlying Requirements," In Proc. First Int. Workshop on Requirements Engineering: Foundation of Software Quality, Utrecht, The Netherlands.

  • Harker, S.D.P., K.D. Eason and J.E. Dobson (1993), "The Change and Evolution of Requirements as a Challenge to the Practice of Software Engineering," In IEEE Symposium on Requirements Engineering, RE93, San Diego, CA, pp. 266–272.

  • Harmsen, F. and S. Brinkkemper (1993), "Computer Aided Method Engineering Based on Existing Meta-Case Technology," In Proc. of the Fourth Workshop on the Next Generation of CASE Tools (NGCT93), Paris, France.

  • Haumer, P., K. Pohl and K. Weidenhaupt (1998), "Requirements Elicitation and Validation with Real World Scenes," IEEE Transactions on Software Engineering 24, 12.

    Article  Google Scholar 

  • Huang, R. (1998), "Making Active CASE TOOLs-Towards the Next Generation of CASE Tools," Software Engineering Notes 23, 1, 47–50.

    Article  Google Scholar 

  • Humphrey, W.S. and M.I. Kellner (1989), "Software Process Modeling: Principles of Entity Process Models," In Proc. 11th Int. Conf. on Software Engineering.

  • IEEE-830 (1984), "Guide to Software Requirements Specification," ANSI/IEEE Std 830.

  • IRDS, Information Resource Dictionary System (1990), "Framework," ISO/IEC International Standard.

  • Jackson, M., Ed. (1994), "Problems, Methods and Specialisation," Special Issue of the SE Journal on Software Engineering in the Year 2001.

  • Jackson, M. and P. Zave (1993), "Domain Descriptions," In IEEE Symposium on Requirements Engineering, IEEE Computer Society Press, pp. 56–64.

  • Jacobson, I. (1995), "The Use Case Construct in Object-Oriented Software Engineering," In Scenario-Based Design: Envisioning Work and Technology in System Development, J.M. Carroll, Ed., Wiley, New York, pp. 309–336.

    Google Scholar 

  • Jarke, M. and K. Pohl (1993), "Establishing Visions in Context: Towards a Model of Requirements Processes," In Proc. 12th Intl. Conf. Information Systems, Orlando, FL.

  • Johnson, J. (1995), "Chaos: the Dollar Drain of IT Project Failures," In Application Development Trends, pp. 41–47.

  • Kardasis, P. and P. Loucopoulos (1998), "Aligning Legacy Information Systems to Business Processes," In Proceedings of the 10th Conference on Advanced Information Systems Engineering, CAiSE98, Pisa, Italy.

  • Kelly, S., K. Lyyttinen and M. Rossi (1996), "Meta-Edit+: A Fully Configurable, Multi-user and Multitool CASE and CAME Environment," In Proceedings of the CAISE96 Conference, Springer-Verlag.

  • Loucopoulos, P., V. Kavakli, N. Prekas, I. Dimitromanolaki, C. Yilmazturk, C. Rolland, G. Grosz, S. Nurcan, D. Beis and G. Vgontzas (1998), "The ELEKTRA Project: Enterprise Knowledge Modelling for Change in the Distribution Unit of Public Power Corporation," In 2nd IMACS International Conference on Circuits, Systems and Computers (IMACS-CSC98), Athens, Greece, pp. 352–357.

  • Lubars, M., C. Potts and C. Richer (1993), "A Review of the State of the Practice in Requirements Modeling," In Proc. IEEE Symp. Requirements Engineering, San Diego.

  • Martin, J. and J. Odell (1992), Object Oriented Analysis & Design, Prentice-Hall, Englewoods Cliffs, NJ.

    Google Scholar 

  • Marttiin, P. (1994), "Methodology Engineering in CASE Shells: Design Issue and Current Practice," Ph.D. Thesis, Computer Science and Information Systems Reports, Technical Report TR-4.

  • McGraw, K. and K. Harbison (1997), User Centered Requirements, The Scenario-Based Engineering Process, Lawrence Erlbaum Associates Publishers.

  • Mylopoulos, J., L. Chung and B. Nixon, (1992), "Representing and Using Non Functional Requirements: A Process-oriented Approach," IEEE Transactions Software Engineering 18, 6.

    Article  Google Scholar 

  • Nardi, B.A. (1992), "The Use of Scenarios in Design," SIGCHI Bulletin 24, 4.

    Google Scholar 

  • Norman, R. and G. Forte, Eds. (1992), "CASE in the 90's," Special Section of the CACM.

  • Olle, T.W., J. Hagelstein, I.G. MacDonald, C. Rolland, H.G. Sol, F.J.M. Van Assche and A.A. Verrijn-Stuart (1988), Information Systems Methodologies: A Framework for Understanding, Addison-Wesley, Reading, MA.

    Google Scholar 

  • Plihon, V., J. Ralyté, A. Benjamen, N.A.M. Maiden, A. Sutcliffe, E. Dubois and P. Heymans (1998), "A Reuse-oriented Approach for the Construction of Scenario Based Methods," In Proceedings of the International Software Process Associations 5th International Conference on Software Process (ICSP'98), Chicago.

  • Pohl, K. (1994), "The Three Dimensions of Requirements Engineering: A Framework and Its Application," Information Systems 19, 3, 243–258.

    Article  Google Scholar 

  • Pohl, K. (1996), Process Centered Requirements Engineering, Wiley, New York.

    Google Scholar 

  • Potts, C. (1989), "A Generic Model for Representing Design Methods," In Proc. 11th Int. Conf. on Software Engineering.

  • Potts, C. (1997), "Fitness for Use: The System Quality that Matters Most," In Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 15–28.

  • Prakash, N. (1997), "Towards A Formal Definition of Methods," The Requirements Engineering Journal 23–50.

  • Prat, N. (1997), "Goal Formalisation and Classification for Requirements Engineering," In Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 145–156.

  • Ralyte, J., C. Rolland and V. Plihon, Eds. (1999), Proceedings of the 11th Intl. Conf. On Advanced Information Systems Engineering (CAISE99), Springer-Verlag.

  • Ramesh, B. (1993), "A Model of Requirements Traceability for Systems Development," Technical Report, Naval Postgraduate School, Monterey, CA.

  • Ramesh, B. and M. Edwards (1993), "Issues in the Development of a Requirements Traceability Model," In Proc. IEEE Symp. on Requirements Engineering, IEEE Computer Society Press, San Diego, CA.

    Google Scholar 

  • Ramesh, B., T. Powers, C. Stubbs and M. Edwards (1995), "Implementing Requirements Traceability: A Case Study," In Proceedings of the 2nd Symposium on Requirements Engineering (RE'95), UK, pp. 89–95.

  • Rolland, C. and C. Ben Achour (1997), "Guiding the Construction of Textual Use Case Specifications," Data & Knowledge Engineering Journal 25, 1, 125–160.

    Article  Google Scholar 

  • Rolland, C. and C. Cauvet (1991), "ALECSI: An Expert System for Requirements Engineering," In Proc.3th Int. Conf. on Advanced Information Systems Engineering (CAISE'91), Springer-Verlag.

  • Rolland, C. and N. Prakash (1994), "A Contextual Approach for the Requirements Engineering Process," In Proc. Int. IEEE Conf. on Software Engineering and Knowledge Engineering (SEKE94), Riga.

  • Rolland, C., C. Souveyet and M. Moreno (1995), "An Approach for Defining Ways-of-Working," Information Systems Journal 20, 4, 337–359.

    Article  Google Scholar 

  • Rolland, C., S. Nurcan and G. Grosz (1997), "A Way of Working for Change Processes," In International Research Symposium '97-Effective Organisations, Dorset, UK, pp. 201–204.

  • Rolland, C., C. Souveyet and C. Ben Achour (1998a), "Guiding Goal Modelling using Scenarios," IEEE Transactions on Software Engineering 24, 12, Special Issue on Scenario Management, 1055–1071.

    Article  Google Scholar 

  • Rolland, C., P. Loucopoulos, V. Kavakli and S. Nurcan (1998b), "Intention Based Modelling of Organisational Change," to appear.

  • Rolland, C., C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois and P. Heymans (1998c), "A Proposal for a Scenario Classification Framework," Requirements Engineering Journal 3, 1, 23–47.

    Google Scholar 

  • Rolland, C., N. Prakash and A. Benjamen (1999), "A Multi-model View of Process Modelling," The Requirements Engineering Journal, to appear.

  • Royce, W.W. (1970), "Managing the Development of Large Software Systems," Proc. IEEE WESCON 08.

  • Rumbaugh, J., M. Blaha, W. Premerlani, F. Eddy and W. Lorensen (1991), Object-oriented Modelling and Design, Prentice-Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Si-Said, S., C. Rolland and G. Grosz (1996), "MENTOR: A Computer Aided Requirements Engineering Environment," In Proc 8th Int. Conf. on Advanced Information Systems Engineering (CAISE'96), Springer-Verlag.

  • Sutcliffe, A.G. and N.A.M. Maiden (1994), "A Theory of Domain Knowledge for Requirements Engineering," Nature Report Deliverable D-D-2.

  • Sutcliffe, A.G., N.A.M. Maiden, S. Minocha and D. Manuel (1998), "Supporting Scenario-based Requirements Engineering," IEEE Transactions on Software Engineering 24, 12, Special Issue on Scenario Management, 1072–1088.

    Article  Google Scholar 

  • Tawbi, M., C. Souveyet and C. Rolland (1998), "L'ECRITOIRE-A Tool to Support a Goal-scenario Based Approach to Requirements Engineering," Information and Software Technology Journal(under communication).

  • The Standish Group (1995), Chaos, Standish Group Internal Report, http://www.standishgroup.com/chaos.html.

  • Van Lamsweerde, A., R. Dairmont and P. Massonet (1995), "Goal Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learnt," In Proc. of RE'95, 2nd Int. Symp. on Requirements Engineering, York, pp. 194–204.

  • Wijers, G.M. (1991), "Modeling Support in Information Systems Development," Ph.D. Thesis, Thesis Publishers, Amsterdam.

  • Wynekoop, J.D. and N.L. Russo (1993), "System Development Methodologies: Unanswered Questions and the Research-practice Gap," In Proc. of 14th ICIS, J.I. DeGross, R.P. Bostrom and D. Robey, Eds., pp. 181–190.

  • Yourdon, E.E (1989), Modern Structured Analysis, Prentice-Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Yu, E.S.K and J. Mylopoulos (1994a), "Understanding Why in Software Process, Modelling, Analysis, and Desig," In Proc. of the 16th International Conference on Software Engineering, Sorrento, Italy.

  • Yu, E.S.K and J. Mylopoulos (1994b), "From ER to AR modelling Strategic Actor Relationships for Business Process Reengineering," In Proc. of the 13th International Conference on the Entity-Relationship Approach, Manchester, UK.

  • Yu, E.S.K and J. Mylopoulos (1994c), "Towards Modelling Strategic Actor Relationships for Information Systems Development-with Examples from Business Process Reengineering," In Proc. of the 4th Workshop on Information Technologies and Systems, Vancouver, Canada.

Download references

Author information

Authors and Affiliations

  1. Université Paris 1-Sorbonne, 17, rue de la Sorbonne, 75231, Paris Cedex 5, France E-mail

    Colette Rolland

  2. Delhi Institute of Technology, Pappankala, 110045, Delhi, India E-mail

    Naveen Prakash

Authors
  1. Colette Rolland
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Naveen Prakash
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Rolland, C., Prakash, N. From conceptual modelling to requirements engineering. Annals of Software Engineering 10, 151–176 (2000). https://doi.org/10.1023/A:1018939700514

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1018939700514

Keywords

Search

Navigation