Requirements engineering based on business process models: A case study

This paper reports a study in which business process modelling was regarded as a useful tool for requirements engineering. We have used business process models as a starting point to derive alternative sets of requirements for a process-oriented system. These alternative sets capture different decisions regarding the intended “level of automation” for the various activities in a business process. The approach is demonstrated in a case study which consists of the development of a real system to manage processes in a Human Resources (HR) Department of a large organization. We use a requirements specification that was previously obtained through what we characterize as a “conventional” requirements engineering technique and we compare it with the requirements specifications derived from the business process model. We discuss the impact of the use of business process models in the completeness, correctness, consistency and traceability of requirements in the case study.

[1]  Patrick McDermott,et al.  Workflow Modeling: Tools for Process Improvement and Application Development , 2001 .

[2]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[3]  August-Wilhelm Scheer,et al.  ARIS - Business Process Modeling , 1998 .

[4]  Wil M. P. van der Aalst,et al.  From BPMN Process Models to BPEL Web Services , 2006, 2006 IEEE International Conference on Web Services (ICWS'06).

[5]  Orlena Cara Zena Gotel,et al.  Contribution structures for requirements traceability , 1995 .

[6]  Michael Rosemann,et al.  Identification and Analysis of Business and Software Services—A Consolidated Approach , 2009, IEEE Transactions on Services Computing.

[7]  Dina Neiger,et al.  Goal-Oriented Business Process Modeling with EPCs and Value-Focused Thinking , 2004, Business Process Management.

[8]  Juan Sánchez Díaz,et al.  Business process-driven requirements engineering : a goal-based approach , 2007 .

[9]  Athanasia Pouloudi,et al.  Aspects of the stakeholder concept and their implications for information systems development , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[10]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.