Business process modeling notations are used in requirements engineering to specify business processes that should be supported by the system under development. Comparisons of business process modeling notations with regard to their concepts do exist, but to our knowledge, little evaluation has taken place regarding their effectiveness and efficiency for typical requirements engineering tasks. Therefore, we set up experiments examining UML Activity Diagrams (ACTs) and Event-driven Process Chains (EPCs) both from a requirements engineer’s perspective with a focus on model creation and from a customer’s or end user’s perspective with a focus on model understandability. The experiments were conducted as a blocked subject-object study, where the participants had to solve several characteristic tasks. The results were then analyzed by means of statistical analysis methods. In the case of the requirements engineer, we were able to show that ACTs perform better than EPCs. In the case of the customer or end user, we cannot make a clear statement.
[1]
Edgar Erdfelder,et al.
G*Power 3: A flexible statistical power analysis program for the social, behavioral, and biomedical sciences
,
2007,
Behavior research methods.
[2]
Ivar Jacobson,et al.
The unified modeling language reference manual
,
2010
.
[3]
Barbara Paech,et al.
Task-Driven Requirements in Object-Oriented Development
,
2004
.
[4]
Dietmar Pfahl,et al.
Reporting Experiments in Software Engineering
,
2008,
Guide to Advanced Empirical Software Engineering.
[5]
Beate List,et al.
An evaluation of conceptual business process modelling languages
,
2006,
SAC.
[6]
Juan Sánchez Díaz,et al.
Business process-driven requirements engineering : a goal-based approach
,
2007
.
[7]
August-Wilhelm Scheer,et al.
ARIS - Business Process Frameworks
,
1998
.