Advertisement

Improving Requirements Analysis through Business Process Modelling: A Participative Approach

  • Jose Luis de la Vara
  • Juan Sánchez
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 7)

Abstract

Although requirements analysis is acknowledged as a critical success factor of information system development for organizations, mistakes are frequent at the requirements stage. Two of these mistakes are the lack of understanding of the business by requirements engineers and the miscommunication between business people and systems analysts. As a result of these problems, information systems may not fulfill organizational needs. To prevent these problems, this paper describes an approach based on business process modeling. The business environment is modeled in the form of BPMN diagrams. The diagrams are validated by end-users and are then analyzed by systems analysts in order to reach an agreement on the effect that the information system will have on the organization. Finally, requirements are specified by means of the description of the business process tasks to be supported by the information system.

Keywords

Requirements analysis understanding of the business communication business process BPMN 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Alexander, I., Bider, I., Regev, G.: Workshop on Requirements Engineering for Business Process Support (REBPS 2003), Klagenfurt/Velden, Austria (2003)Google Scholar
  2. 2.
    Attaran, M.: Exploring the relationship between information technology and business process reengineering. Information & Management 41, 585–596 (2003)CrossRefGoogle Scholar
  3. 3.
    Bleistein, S.: B-SCP: an integrated approach for validating alignment of organizational IT requirements with competitive business strategy. PhD Thesis, The University of New South Wales, Sidney, Australia (2006)Google Scholar
  4. 4.
    Bubenko, J., Persson, A., Stirna, J.E.: User Guide (online) (2001), http://www.dsv.su.se/~js/ekd_user_guide.html
  5. 5.
    CARE Technlogies, http://www.care-t.com
  6. 6.
    Castro, J., Kolp, M., Mylopoulos, J.: Towards requirements-driven information systems engineering: the Tropos Project. Information Systems 27, 365–389 (2002)CrossRefGoogle Scholar
  7. 7.
    Constantine, L., Lockwood, L.: Software for Use: A Practical Guide to the Models and Methods of Usage- Centered Design. Addison Wesley, Reading (1999)Google Scholar
  8. 8.
    Curtis, B., Kellner, M., Over, J.: Process Modelling. Communications of the ACM 35(9), 75–90 (1992)CrossRefGoogle Scholar
  9. 9.
    Dardenne, van Lamsweerde, A., Fickas, S.: Goal-directed Requirements Acquisition. Science of Computer Programming 20, 3–50 (1993)CrossRefGoogle Scholar
  10. 10.
    Daoudi, F., Nurcan, S.: A Benchmarking Framework for Methods to Design Flexible Business Process. Software Process Improvement and Practice 12, 51–63 (2007)CrossRefGoogle Scholar
  11. 11.
    Dobing, B., Parsoms, J.: Understanding the role of use cases in UML: a review and research agenda. Journal of Database Management 11(4), 28–36 (2000)Google Scholar
  12. 12.
    Dumas, M., van der Aalst, W., ter Hofstede, A.: Process-Aware Information Systems. Wiley, Chichester (2005)CrossRefGoogle Scholar
  13. 13.
    Eriksson, H., Penker, M.: Business Modeling with UML: Business Patterns at Work. John Wiley and Sons, Chichester (2000)Google Scholar
  14. 14.
    Estrada, H., et al.: An Empirical Evaluation if the i* Framework in a Model-Based Software Generation Environment. In: Dubois, E., Pohl, K. (eds.) CAiSE 2006. LNCS, vol. 4001, Springer, Heidelberg (2006)CrossRefGoogle Scholar
  15. 15.
    International Institute of Business Analysis. Business Analysis Body of Knowledge (online) (2006), http://www.iiba.com
  16. 16.
    International Organization for Standardization. ISO 9001:2000, http://www.iso.ch
  17. 17.
    Holtzblatt, K., Beyer, H.: Requirements gathering: the human factor. Communications of the ACM 38(5), 31–32 (1995)CrossRefGoogle Scholar
  18. 18.
    Lauesen, S.: Task Descriptions as Functional Requirements. IEEE Software 20(2), 58–65 (2003)CrossRefGoogle Scholar
  19. 19.
    Luftman, J., Raymond, R., Brier, T.: Enablers and Inhibitors of Business-IT Alignment. Communications of AIS 1 (1999)Google Scholar
  20. 20.
    Lukaitis, S., Cybulski, J.: The Role of Stakeholder Understanding in Aligning IT with Business Objectives. In: REBNITA 2005, Paris, France (2005)Google Scholar
  21. 21.
    Marshall, C.: Enterprise Modeling with UML. Addison-Wesley, Reading (2001)Google Scholar
  22. 22.
    Nysetvold, A., Krogstie, J.: Assessing Business Process Modeling Languages Using a Generic Quality Framework. Advanced topics in database research 5, 79–93 (2006)Google Scholar
  23. 23.
    OMG. Business Process Modeling Notation (BPMN) Specification (online) (2006), http://www.bpmn.org
  24. 24.
    OO Method project, http://oomethod.dsic.upv.es
  25. 25.
    Ould, M.: Business Processes: modelling and analysis for re-engineering and improvement. Wiley, Chichester (1995)Google Scholar
  26. 26.
    Pastor, O., Molina, J.C.: Model-Driven Architecture in Practice: A Software Production Environment Based on Conceptual Modeling. Springer, Heidelberg (2007)Google Scholar
  27. 27.
    Reich, B., Benbasat, I.: Factors That Influence the Social Dimension of Alignment Between Business and Information Technology. MIS Quarterly 24(1), 81–113 (2000)CrossRefGoogle Scholar
  28. 28.
    Rubens, J.: Business analysis and requirements engineering? The same, only different? Requirements Engineering 12, 121–123 (2007)CrossRefGoogle Scholar
  29. 29.
    Scheer, A.-W.: ARIS - Business Process Frameworks, 3rd edn. Springer, Berlin (1999)Google Scholar
  30. 30.
    Siau, K.: The Psychology of Information Modeling. Advanced topics in database research 1, 116–118 (2002)Google Scholar
  31. 31.
    Smith, H., Fingar, P.: Business Process Management: The Third Wave. Meghan-Kiffer Press (2002)Google Scholar
  32. 32.
    Standish Group. Chaos, http://www.standishgorup.com
  33. 33.
    Vessey, I., Coner, S.: Requirements Specification: Learning Object, Process, and Data Methodologies. Communications of the ACM 37(5), 102–113 (1994)CrossRefGoogle Scholar
  34. 34.
    WfMC. Workflow Management Coalition: Terminology & Glossary (1999)Google Scholar
  35. 35.
    Wahl, T., Sindre, G.: An Analytical Evaluation of BPMN Using a Semiotic Quality Framework. Advanced topics in database research 5, 94–105 (2006)Google Scholar
  36. 36.
    Wohed, P., et al.: On the suitability of BPMN for Business Process Modelling. In: Dustdar, S., Fiadeiro, J.L., Sheth, A.P. (eds.) BPM 2006. LNCS, vol. 4102, Springer, Heidelberg (2006)CrossRefGoogle Scholar
  37. 37.
    Yu, E.: Modeling Strategic Relationships for Process Reengineering. PhD Thesis, University of Toronto, Canada (1995)Google Scholar
  38. 38.
    Zave, P., Jackson, M.: Four Dark Corners of Requirements Engineering. ACM Transactions on Software Engineering and Methodology 6(1), 1–30 (1997)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Jose Luis de la Vara
    • 1
  • Juan Sánchez
    • 1
  1. 1.Department of Information SystemsValencia University of TechnologyValenciaSpain

Personalised recommendations