By Topic

Role-centered design for evolution

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Mrva, M. ; Corp. Res. & Technol., Siemens AG, Munich, Germany

The concept of roles in a model-based design process is discussed in this article. It is shown that roles can positively contribute to, easier discovery of the right level of abstraction in a design, thus better communication between team members or designer and reuser, and raising the reusability as well as the evolvability of a component. The role concept is compared to the well-known class concept of object-oriented design and to the interface concept of the Java programming language. It is also stated that objects, being instances of classes, can take on different roles during their life-time, and-vice versa-roles can be fulfilled by different objects. The paper takes a look at design patterns, too, as well as at the Unified Modeling Language (UML) and relates them to the role concept. This is not an experience report, but rather a programmatic view at some requirements that have become important for the design of long-lasting CBS components which are designed for evolution. These requirements are accompanied by suggestions for the designers of modeling and programming languages

Published in:

Engineering of Computer-Based Systems, 1999. Proceedings. ECBS '99. IEEE Conference and Workshop on

Date of Conference:

7-12 Mar 1999