The role of "Roles" in use case diagrams

Authors:
Alain Wegmann;Guy Genilloud
Affiliations:
Institute for computer Communication and Application, Swiss Federal Institute of Technology, Lausanne, Switzerland;Institute for computer Communication and Application, Swiss Federal Institute of Technology, Lausanne, Switzerland
Venue:
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Year:
2000

Citing 5
Cited 4

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
Requirements engineering and rapid development: an object-oriented approach

Requirements engineering and rapid development: an object-oriented approach
Multifaceted object modeling with roles: a comprehensive approach

Information Sciences: an International Journal
A Foundation for the Concept of Role in Object Modelling

EDOC '00 Proceedings of the 4th International conference on Enterprise Distributed Object Computing

Applying and extending a semantic foundation for role-related concepts in enterprise modelling

Enterprise Information Systems - Towards Model-driven Service-oriented Enterprise Computing - 12th International IEEE EDOC Enterprise Computing Conference (EDOC 2008)
Consolidating diagram types from several agent-oriented methodologies

Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10
A methodology of visual modeling language evaluation

SOFSEM'05 Proceedings of the 31st international conference on Theory and Practice of Computer Science
Use cases, actions, and roles

MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS

Quantified Score

Hi-index	0.00

Visualization

Abstract

Use cases are the modeling technique of UML for formalizing the functional requirements placed on systems. This technique has limitations in modeling the context of a system, in relating systems involved in a same business process, in reusing use cases, and in specifying various constraints such as execution constraints between use case occurrences. These limitations can be overcome to some extent by the realization of multiple diagrams of various types, but with unclear relationships between them. Thus, the specification activity becomes complex and error prone. In this paper, we show how to overcome the limitations of use cases by making the roles of actors explicit. Interestingly, our contributions not only make UML a more expressive specification language, they also make it simpler to use and more consistent.