The Community for Technology Leaders
Proceedings Fifth IEEE International Symposium on Requirements Engineering (2001)
Toronto, Canada
Aug. 27, 2001 to Aug. 31, 2001
ISBN: 0-7695-1125-2
pp: 0146
Jaelson F. Castro , Universidade Federal de Pernambuco
John Mylopoulos , University of Toronto
Fernanda M. R. Alencar , Universidade Federal de Pernambuco
Gilberto A. Cysneiros Filho , Universidade Federal de Pernambuco
Abstract: In recent years we have observed a growing influence of the object-orientation paradigm. Unfortunately, the current dominant object oriented modeling technique, i.e. the Unified Modeling Language - UML, is ill equipped for modeling early requirements which are typically informal and often focus on stakeholder objectives. Instead, UML is suitable for later phases of requirement capture which usually focus on completeness, consistency, and automated verification of functional requirements for the new system. In this paper, we present a set of guidelines for the integration of early and late requirements specifications. For early (organizational) modeling we rely on the i* framework, whereas for late (functional) requirements specification, we rely on a precise subset of UML. A small example is used to illustrate how the requirements process iterates between early and late requirements.
Organizational Modeling, Object Oriented Development, UML, Requirements Modeling.

J. F. Castro, J. Mylopoulos, F. M. Alencar and G. A. Cysneiros Filho, "Integrating Organizational Requirements and Object Oriented Modeling," Proceedings Fifth IEEE International Symposium on Requirements Engineering(RE), Toronto, Canada, 2001, pp. 0146.
80 ms
(Ver 3.3 (11022016))