Enhancing RUP business model with client-oriented requirements models
UML and the unified process
Integrating activity theory and organizational modeling for context of use analysis
CLIHC '05 Proceedings of the 2005 Latin American conference on Human-computer interaction
PRiM: An i*-based process reengineering method for information systems specification
Information and Software Technology
Elaboration of use case specifications: an approach based on use case fragments
Proceedings of the 2008 ACM symposium on Applied computing
ReeF: defining a customizable reengineering framework
CAiSE'07 Proceedings of the 19th international conference on Advanced information systems engineering
Integration of aspects with i* models
AOIS'06 Proceedings of the 8th international Bi conference on Agent-oriented information systems IV
Framework for decisional business modeling and requirements modeling in data mining projects
IDEAL'09 Proceedings of the 10th international conference on Intelligent data engineering and automated learning
Requirements engineering for large-scale multi-agent systems
Software engineering for large-scale multi-agent systems
Towards transformation guidelines from secure tropos to misuse cases (position paper)
Proceedings of the 7th International Workshop on Software Engineering for Secure Systems
Capturing Process Knowledge for Multi-Channel Information Systems: A Case Study
International Journal of Information System Modeling and Design
| Hi-index | 0.00 |
Use Cases Diagrams in the Unified Language Modeling (UML) have been used for capturing system functional requirements. However, the system development occurs in a context where organizational 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, etc. Unfortunately, UML is 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 requirementsrepresented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from the i* organizational models.