Understanding businesses and how they work can help software engineers build systems that really meet the corresponding business goals. For instance, methods such as the Rational Unified Process (RUP) include activities to model a business before eliciting requirements. However, during our software development practice in academic and ”real-life” projects, we found problems using these artefacts with stakeholders. Here we present our experience on integrating BPMN (Business Process Modeling and Notation) diagrams with RUP, aiming to improve the elicitation of software requirements. These diagrams appeared to be easier to understand by stakeholders. The current paper discusses the challenges we faced in using RUP and the way in which we integrate conceptual maps and BPMN into the process. In addition, we illustrate the changes using models that reflect real project implementations realized by using this approach.
[1]
Adam Przybylek,et al.
A business-oriented approach to requirements elicitation
,
2014,
2014 9th International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE).
[2]
A. Abran,et al.
On the expressiveness of business process modeling notations for software requirements elicitation
,
2012,
IECON 2012 - 38th Annual Conference on IEEE Industrial Electronics Society.
[3]
Dieter Landes,et al.
Using business process models to foster competencies in requirements engineering
,
2014,
2014 IEEE 27th Conference on Software Engineering Education and Training (CSEE&T).
[4]
Ivar Jacobson,et al.
The Unified Software Development Process
,
1999
.