A pattern language to join early and late requirements
Keywords:Organizational Model, Early Requirements, Late Requirements, Pattern Design
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 abstraction level between early requirements and late requirements in a systematic way. This is done in an MDA-based approach.
 Bresciani P, Giorgini P., Giunchiglia F., Mylopoulos J., and Perini A., TROPOS: An Agent-Oriented Software Development Methodology. In Journal of Autonomous Agents and Multi-Agent Systems, 8(3), Kluwer Academic Publishers, May 2004, pp. 203-236.
 Bubenko, J. A., Jr and M. Kirikova, Worlds in Requirements Acquisition and Modeling. In 4th European-Japanese Seminar on Information Modelingand Knowledge Bases, edited by K. Sweden, H. Kangassalo and B. Wangler, IOS Press, The Netherlands, 1994, pp. 159-174.
 Buschmann, R. Meunier, H. Rohnert, P. Sommerlandand M. Stal, Pattern - Oriented software Architecture: A system of Patterns. John Wiley & Sons, England 1998.
 Castro J. Kolp M. Mylopoulos J. Towards Requirements-Driven Information Systems Engineering: The Tropos Project. In Information System 27(2), Elsevier, 2002, pp. 365-389.
 Cesare S. Mark Lycett, Business Modelling with UML, distilling directions for future research, Proceedings of the Information Systems Analysis and Specification Ciudad. Real, Spain, 2002, pp. 570-579.
 Cockburn Alistair, Writing Effective Use Cases, Addison-Wesley, USA, 2001.
 Frankel S. David, Model driven Architecture, applying MDA to enterprise computing, John Wiley& Sons, USA, 2003.
 Gamma E., R. Helm, R. Johnson, and J. Vlissides. Design Patterns, Addison-Wesley, USA, 1995.
 Kleppe A., Warmer J., Bast W. MDA Explained, the model driven architecture: practice and promise, Addison-Wesley, USA, 2003.
 Kulak Daryl Eamonn Guiney, Use Cases requirements in context, Addison-Wesley, USA, 2003.
 Martínez Alicia, Castro Jaelson, Pastor Oscar, Estrada Hugo, Closing the gap between Organizational Modeling and Information System Modeling, Proceedings of the VI Workshop on Requirements Engineering (WER 2003), Brazil, 2003, pp 93-108.
 Meszaros G. and J. Doble, A Pattern Language for Pattern Writing, in Pattern Languages of Program Design 3, edited by Robert Martin, D. Riehle and F. Buschmann, Addison-Wesley, USA, 1998, pp. 529-574.
 Pastor Oscar, Gómez Jaime, Infrán E. and PelechanoV., The OO-Method approach for information systems modeling: from object-oriented conceptual modelingto automated programming. In Information Systems 26(7), Elsevier, 2001, pp. 507-534.
 Rolland R., Souveyet, C., Plihon, V., Method Enhancement with Scenario Based Techniques, Proceedings of the 11th International Conference on Advanced Information System Engineering(CAISE’99), Germany, 1999, pp 14-18.
 Yu Eric, Modelling Strategic Relationships for Process Reengineering, PhD Thesis, University of Toronto, Toronto, 1995.