Integrating Organizational Requirements and Object Oriented Modeling

  • Authors:
  • Jaelson F. Castro;John Mylopoulos;Fernanda M. R. Alencar;Gilberto A. Cysneiros Filho

  • Affiliations:
  • -;-;-;-

  • Venue:
  • RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
  • Year:
  • 2001

Quantified Score

Hi-index 0.00

Visualization

Abstract

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.