From Conceptual Modeling to Requirements Engineering

A number of studies show [1][2][3][4] that systems fail due to an inadequate or insufficient understanding of the requirements they seek to address. Further, the amount of effort needed to fix these systems has been found to be very high [5]. To correct this situation, it is necessary to address the issue of requirements elicitation, validation, and specification in a relatively more focussed manner. The expectation is that as a result of this, more acceptable systems will be developed in the future. The field of requirements engineering has emerged to meet this expectation.

[1]  Jan Bosch,et al.  On the notion of variability in software product lines , 2001, Proceedings Working IEEE/IFIP Conference on Software Architecture.

[2]  Linda H. Rosenberg,et al.  Doing Requirements Right the First Time , 1998 .

[3]  Colette Rolland.  Modelling Multi-Facetted Purposes of Artefacts , 2005, SoMeT.

[4]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[5]  William N. Robinson,et al.  Conflict-Oriented Requirements Restructuring , 2007 .

[6]  E. Dubois,et al.  From early to late formal requirements: a process-control case study , 1998, Proceedings Ninth International Workshop on Software Specification and Design.

[7]  Camille Salinesi,et al.  Managing requirements in a co-evolution context , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[8]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[9]  Jan Bosch,et al.  Variability Issues in Software Product Lines , 2001, PFE.

[10]  Hermann Kaindl,et al.  A design process based on a model combining scenarios with goals and functions , 2000, IEEE Trans. Syst. Man Cybern. Part A.

[11]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[12]  Karan Harbison,et al.  User-Centered Requirements: The Scenario-Based Engineering Process , 1997 .

[13]  Colette Rolland,et al.  Eliciting gaps in requirements change , 2004, Requirements Engineering.

[14]  John Mylopoulos,et al.  Requirements analysis for customizable software: a goals-skills-preferences framework , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[15]  Balasubramaniam Ramesh,et al.  Implementing requirements traceability: a case study , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[16]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[17]  Janis A. Bubenko,et al.  Facilitating "fuzzy to formal" requirements modelling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[18]  Colette Rolland,et al.  Experience with goal-scenario coupling in requirements engineering , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[19]  Joachim Karlsson,et al.  Improved practical support for large-scale requirements prioritising , 1997, Requirements Engineering.

[20]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[21]  Hoh Peter In,et al.  Multi-criteria preference analysis for systematic requirements negotiation , 2002, Proceedings 26th Annual International Computer Software and Applications.

[22]  Colette Rolland,et al.  Bridging the Gap Between Organisational Needs and ERP Functionality , 2000, Requirements Engineering.

[23]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[24]  Anthony Finkelstein,et al.  ViewPoint Oriented Software Development , 1990 .

[25]  Jack Mostow,et al.  Toward Better Models of the Design Process , 1985, AI Mag..

[26]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[27]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[28]  Frank Moisiadis,et al.  The fundamentals of prioritising requirements , 2002 .

[29]  Leonard J. Bass,et al.  Managing variability in software architectures , 2001, SSR '01.

[30]  Matthias Jarke,et al.  Establishing Visions in Context: Towards a Model of Requirements Processes , 1994, EMISA Forum.

[31]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[32]  Karl Cox,et al.  Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams , 2006, J. Syst. Softw..

[33]  Colette Rolland,et al.  Modeling Goals and Reasoning with Them , 2005 .

[34]  Jan Bosch,et al.  Managing Variability in Software Product Lines , 2000 .

[35]  Klaus Pohl,et al.  Communicating the variability of a software-product family to customers , 2004, Informatik Forschung und Entwicklung.

[36]  William N. Robinson,et al.  Supporting the negotiation life cycle , 1998, CACM.

[37]  Barry W. Boehm,et al.  Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[38]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[39]  Steve Easterbrook,et al.  Resolving requirements conflicts with computer-supported negotiation , 1994 .