From Early to Late Requirements: A Goal-Based Approach

The Software Engineering community is placing increasing emphasis on understanding the organizational context of a new software system before its development. In this context, several research projects focus on mechanisms that facilitate the generation of a software system from early requirements specifications. However, none of these has proposed so far a systematic process for transforming an organizational model into a late requirements one. This paper presents a methodological approach to precisely this problem. In the proposed method, business goals constitute the basis for determining the relevant plans to be supported by the system-to-be. A pattern language is then used to systematically carry out the transformation from an organizational model into a late requirements model. The Tropos framework serves as baseline for this work. However, our work extends Tropos by proposing rules that support the model transformation process, thereby making organizational modeling an integral part of the software development process.

[1]  Axel van Lamsweerde,et al.  Reasoning about partial goal satisfaction for requirements and design engineering , 2004, SIGSOFT '04/FSE-12.

[2]  Hugo Estrada,et al.  A pattern language to join early and late requirements , 2005 .

[3]  John Mylopoulos,et al.  Modeling Social and Individual Trust in Requirements Engineering Methodologies , 2005, iTrust.

[4]  John Mylopoulos,et al.  Organizational Patterns for Early Requirements Analysis , 2003, CAiSE.

[5]  Vicente Pelechano,et al.  The OO-method approach for information systems modeling: from object-oriented conceptual modeling to automated programming , 2001, Inf. Syst..

[6]  Colette Rolland,et al.  Method Enhancement with Scenario Based Techniques , 1999, CAiSE.

[7]  Gerhard Goos,et al.  Fast Software Encryption , 2001, Lecture Notes in Computer Science.

[8]  John Mylopoulos,et al.  Goal-oriented requirements analysis and reasoning in the Tropos methodology , 2005, Eng. Appl. Artif. Intell..

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

[10]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[11]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[12]  Mark Lycett,et al.  Business Modelling with UML: Distilling Directions for Future Research , 2002, ICEIS.

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

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

[15]  Oscar Pastor,et al.  A pattern language to join early and late requirements , 2004, WER.

[16]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

[17]  Ken Frazer,et al.  Review of "Use cases, requirements in context by Daryl Kulak and Eamon Guiney." Addison-Wesley 2004 , 2004, SOEN.

[18]  Ana I. Anton,et al.  Goal identification and refinement in the specification of software-based information systems , 1997 .

[19]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[20]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.