A simple approach to specifying concurrent systems
Communications of the ACM
Object-oriented software engineering
Object-oriented software engineering
The object advantage: business process reengineering with object technology
The object advantage: business process reengineering with object technology
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
A Foundation for the Concept of Role in Object Modelling
EDOC '00 Proceedings of the 4th International conference on Enterprise Distributed Object Computing
The role of "Roles" in use case diagrams
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
| Hi-index | 0.00 |
Use Cases are widely used for specifying systems, but their semantics are unclear in ways that make it difficult to apply use cases to complex problems. In this paper, we suggest clarifications to use case semantics so that use case modeling can be applied to relate automated systems to business processes and process specifications, particularly in situations where we need to integrate multiple systems in support of a business process. We discuss the original intentions of Ivar Jacobson and UML and we find out that use case specifications, whether written in natural language or as interaction diagrams, are misleading as to what is a use case (instance). We consider then a more natural modeling technique, and establish a relation between a use case, a joint action, and a role.