Architecture Viewpoint for Modeling Business Collaboration Concerns using Workflow Patterns

Ayalew Kassahun, Bedir Tekinerdogan

2016

Abstract

Businesses today rarely operate in isolation but must collaborate with others in a coordinated fashion. To address collaboration concerns, business analysts need to design business processes. Business process designs have a direct impact on the required software systems and the corresponding architectural design. Conversely, the architectural design imposes constraints on the business process designs. Unfortunately, business processes and software architectures are often designed separately leading to a misalignment between the two. To bridge this gap we propose the architecture collaboration viewpoint to be used by teams of business analysts and software architects when addressing business collaboration concerns. The collaboration viewpoint uses elements from business process and architecture viewpoints to provide new modeling artifacts for alignment. The design artefacts are mapping tables and workflow pattern diagrams that are used to identify misalignments and redesign the business processes. The viewpoint facilitates the communication between business analysts and architects. We illustrate the collaboration viewpoint for a food supply chain transparency system from a real industrial case study.

References

  1. Autili, M., P. Inverardi and M. Tivoli (2015). "Automated Synthesis of Service Choreographies." IEEE Software 32(1): 50-57.
  2. Aversano, L., C. Grasso and M. Tortorella (2016). "Managing the alignment between business processes and software systems." Information and Software Technology 72: 171-188.
  3. Avison, D., J. Jones, P. Powell and D. Wilson (2004). "Using and validating the strategic alignment model." The Journal of Strategic Information Systems 13(3): 223-246.
  4. Bartens, Y., F. Schulte, Vo, x00Df and S. (2014). EBusiness IT Governance Revisited: An Attempt towards Outlining a Novel Bi-directional Business/IT Alignment in COBIT5. System Sciences (HICSS), 2014 47th Hawaii International Conference on.
  5. Clements, P., F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, P. Merson, R. Nord and J. Stafford (2010). Documenting software architectures: views and beyond, Addison-Wesley.
  6. Davenport, T. H. and J. E. Short (1998). "The new industrial engineering: information technology and business process redesign." IEEE Engineering Management Review 26(3): 46-60.
  7. Dumas, M., M. La Rosa, J. Mendling and H. Reijers (2013). Introduction to Business Process Management. Fundamentals of Business Process Management, Springer Berlin Heidelberg: 1-31.
  8. EC (2000). "Regulation (EC) No 1760/2000 of the European Parliament and of the Council of 17 July 2000 establishing a system for the identification and registration of bovine animals and regarding the labelling of beef and beef productsand repealing Council Regulation (EC) No 820/97." Official Journal of the European Communities (L 204): 1-10.
  9. EC (2002). "Regulation (EC) No 178/2002 of the European Parliament and of the Council of 28 January 2002 laying down the general principles and requirements of food law, establishing the European Food Safety Authority and laying down procedures in matters of food safety." Official Journal of the European Communities L 31(1): 1-24.
  10. EC (2004). "Regulation No. 911/2004 of 29 April 2004 implementing Regulation (EC) No 1760/2000 of the European Parliament and of the Council as regards eartags, passports and holding registers." Official Journal of the European Union L 163: 65-70.
  11. EC (2007). Factsheet: Tracing food through the production and distribution chain to identify and address risks and protect public health. Brussels.
  12. EC (2011). "Commission Implementing Regulation (EU) No 931/2011 of 19 September 2011 on the traceability requirements set by Regulation (EC) No 178/2002 of the European Parliament and of the Council for food of animal origin." Official Journal of the European Union L 242: 1-2.
  13. EC (2015). "Regulation (EU) No 2015/262 of 17 February 2015 laying down rules pursuant to Council Directives 90/427/EEC and 2009/156/EC as regards the methods for the identification of equidae (Equine Passport Regulation)." Official Journal of the European Union (L 59): 51.
  14. EPCglobal (2014). EPC Information Services (EPCIS) Version 1.1 Specification. GS1 Standard Version 1.1, May 2014. Brussels, Belgium, GS1 AISBL.
  15. GS1 (2015). GS1 General Specifications. Version 15 (issue 2), Jan-2015, GS1: 490.
  16. Hofmeister, C., R. Nord and D. Soni (2000). Applied software architecture, Addison-Wesley Professional.
  17. Hong-Mei, C. (2008). Towards Service Engineering: Service Orientation and Business-IT Alignment. Hawaii International Conference on System Sciences, Proceedings of the 41st Annual.
  18. ISO/IEC/IEEE (2011). Systems and software engineering -- Architecture description. ISO/IEC/IEEE Standard 42010:2011.
  19. Kruchten, P. (2004). The rational unified process: an introduction, Addison-Wesley Professional.
  20. Kruchten, P. B. (1995). "The 4+1 View Model of architecture." Software, IEEE 12(6): 42-50.
  21. Lattanze, A. J. (2008). Architecting Software Intensive Systems: A Practitioners Guide, CRC Press.
  22. Murphy, G. C., D. Notkin and K. J. Sullivan (2001). "Software reflexion models: bridging the gap between design and implementation." Software Engineering, IEEE Transactions on 27(4): 364-380.
  23. OMG (2011). Business Process Model and Notation 2.0 (BPMN 2.0).
  24. Rational Software (2001). The Zachman framework for enterprise architecture and Rational best practices and products, a Rational Software White paper, http://ww w.rational.com/.
  25. Russell, N., W. M. van der Aalst and N. Mulyar (2006). "Workflow Control-Flow Patterns: A Revised View." BPM Center Report BPM-06-22.
  26. Sharp, A. and P. McDermott (2009). Workflow modeling: tools for process improvement and applications development, Artech House.
  27. Tekinerdogan, B. (2014). Software Architecture. Computing Handbook, Third Edition, Chapman and Hall/CRC: 1-16.
  28. The Open Group (2013). ArchiMate 2.1 Specification (http://pubs.opengroup.org/architecture/archimate2-do c/toc.html).
  29. van der Aalst, W. M. P. and A. ter Hofstede. (2011). "Workflow Patterns. http://www.workflowpatterns. com/." Retrieved December 23, 2015.
  30. Van der Aalst, W. M. P., A. H. M. Ter Hofstede, B. Kiepuszewski and A. P. Barros (2003). "Workflow Patterns." Distributed and Parallel Databases 14(1): 5-51.
  31. Verdouw, C., A. Beulens and S. Wolfert (2014). Towards Software Mass Customization for Business Collaboration. Global Conference (SRII), 2014 Annual SRII.
  32. Woods, E. and N. Rozanski (2005). Using Architectural Perspectives. Software Architecture, 2005. WICSA 2005. 5th Working IEEE/IFIP Conference on.
  33. Simultaneous Execution (rf-42), Additional Resources (rf-43) Internal Data Interaction Task to Task (df-9), Block Task to Sub-Workflow Decomposition (df-10), Sub-Workflow Decomposition to Block Task (df-11), To Multiple Instance Task (df-12), From Multiple Instance Task (df-13), Case to Case (df-14)
  34. Task Data (df-1), Block Data (df-2), Scope Data, Multiple Instance Data (df-4), Case Data (df-5), Folder Data (df-6), Workflow Data (df-7), Environment Data (df-8)
Download


Paper Citation


in Harvard Style

Kassahun A. and Tekinerdogan B. (2016). Architecture Viewpoint for Modeling Business Collaboration Concerns using Workflow Patterns . In Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016) ISBN 978-989-758-194-6, pages 27-38. DOI: 10.5220/0005973600270038


in Bibtex Style

@conference{icsoft-ea16,
author={Ayalew Kassahun and Bedir Tekinerdogan},
title={Architecture Viewpoint for Modeling Business Collaboration Concerns using Workflow Patterns},
booktitle={Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016)},
year={2016},
pages={27-38},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0005973600270038},
isbn={978-989-758-194-6},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016)
TI - Architecture Viewpoint for Modeling Business Collaboration Concerns using Workflow Patterns
SN - 978-989-758-194-6
AU - Kassahun A.
AU - Tekinerdogan B.
PY - 2016
SP - 27
EP - 38
DO - 10.5220/0005973600270038