Developing Use Cases from Organizational Modeling

Victor F.A. SantanderJaelson F. B. Castro

The object oriented development paradigm has attracted many supporters in the Software Engineering community. One of the most important advances was the Unified Language Modeling (UML), a standard for visual modeling. Use Cases Diagrams have been used for capturing system functional requirements. However, the system development occurs in a context where organization processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization goals, why it is necessary, what are the possible alternatives, what are the implications to the involved parts, etc. Unfortunately, UML and other scenario-based techniques are ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of use cases from the organizational models represented by i* technique

Caso o link acima esteja inválido, faça uma busca pelo texto completo na Web: Buscar na Web

Biblioteca Digital Brasileira de Computação - Contato:
     Mantida por: