A pattern language to join early and late requirements

At present, the early phase of Requirements Engineering is a new research area in the Software Engineering field. This phase is concerned with the analysis of the organizational context in which a software system will be used. The models used in this phase allow us to describe an organizational environment using actors, goals, business processes and relationships. The late phase of Requirements Engineering, which is focused on representing the expected functionality of the software system, is more developed, so there are multiple techniques and tools to describe the software system that will be developed inside its operational environment. However, although there are methodologies which give separate support to each phase of requirements engineering, the development of methods to derive late requirements from the early requirements in a methodological way has been neglected in recent research works. This is due, in great measure, to the large difference between the abstraction levels of these two specification models. The objective of this paper is to propose a pattern language which allows us to reduce the

[1]  Oscar Pastor,et al.  Closing the Gap between Organizational Modeling and Information System Modeling , 2003, WER.

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

[3]  Gerard G. Meszaros,et al.  A pattern language for pattern writing , 1997 .

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

[5]  Anneke Kleppe,et al.  MDA explained - the Model Driven Architecture: practice and promise , 2003, Addison Wesley object technology series.

[6]  David Frankel,et al.  Model Driven Architecture: Applying MDA to Enterprise Computing , 2003 .

[7]  Oscar Pastor,et al.  Goal-Based Business Modeling Oriented towards Late Requirements Generation , 2003, ER.

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

[9]  Peter Sommerlad,et al.  Pattern-Oriented Software Architecture: A System of Patterns: John Wiley & Sons , 1987 .

[10]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[11]  Oscar Pastor López,et al.  A requirements engineering approach for object-oriented conceptual modeling , 2003 .

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

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

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