Enterprises need to create and maintain the fit between their business processes and their business process support (BPS) systems. This frequently requires re-engineering of business processes. If the business processes design ration-ales are made explicit, the re-engineering of the existing business processes is easier. Making the design rationales ex-plicit is useful to understand why things exist as they are, and to understand if and how they can be changed. The most common way to capture design rationales is to list the design decisions underlying the business process. In the method proposed in this publication, we capture design rationales through role modeling. We document the design rationales for each role in the analyzed business process. The roles are described as the compositions of base func-tionalities. A base functionality is the specification of a role (or of a part of a role) from the viewpoint of one of the specific specialists who design the business process. These base functionalities are composed together to describe the roles of the participants to the business process. As a result, a business process modeler can understand who is respon-sible of what in the business processes. In collaboration with the specialists, the business modeler can then ensure that no important part of the business process is missing or is unnecessary. Thanks to this work, the business process can be verified before being automated with the BPS system.
[1]
Alain Wegmann,et al.
A Synthesis of Business Role Models
,
2003
.
[2]
Alain Wegmann,et al.
On the Systemic Enterprise Architecture Methodology (Seam)
,
2003,
ICEIS.
[3]
Michael L. Begeman,et al.
gIBIS: A tool for all reasons
,
1989,
JASIS.
[4]
Mark Klein,et al.
The process recombinator: a tool for generating new business process ideas
,
1999,
ICIS.
[5]
Jintae Lee,et al.
What's in design rationale?
,
1991
.
[6]
E. Jeffrey Conklin,et al.
A process-oriented approach to design rationale
,
1991
.
[7]
Lam-Son Lê,et al.
SeamCAD 1.x: User’s Guide
,
2004
.
[8]
Alain Wegmann,et al.
Precise Graphical Representation of Roles in Requirements Engineering
,
2003
.
[9]
Alain Wegmann,et al.
Context based reasoning in business process models
,
2003,
Proceedings Fifth IEEE Workshop on Mobile Computing Systems and Applications.
[10]
Richard M. Young,et al.
Options and Criteria: Elements of design space analysis
,
1991
.
[11]
Harold Ossher,et al.
Subject-oriented programming: a critique of pure objects
,
1993,
OOPSLA '93.
[12]
James M. Coggins,et al.
Subject-Oriented Programming
,
1996
.
[13]
Trygve Reenskaug,et al.
Working with objects
,
1995
.
[14]
Gregor Kiczales,et al.
Aspect-oriented programming
,
1996,
CSUR.