Abstract
Compliance in service-oriented architectures (SOA) means in general complying with laws and regulations applying to a distributed software system. Unfortunately, many laws and regulations are hard to formulate. As a result, several compliance concerns are realized on a per-case basis, leading to ad hoc, hand-crafted solutions for each specific law, regulation, and standard that a system must comply with. This, in turn, leads in the long run to problems regarding complexity, understandability, and maintainability of compliance concerns in a SOA. In this book chapter, we present a case study in the field of compliance to regulatory provisions, in which we applied our view-based, model-driven approach for ensuring the compliance with ICT security issues in business processes of a large European company. The research question of this chapter is to investigate whether our model-driven, view-based approach is appropriate in the context of the case. This question is generally relevant, as the case is applicable to many other problem of requirements that are hard to specify formally (like the compliance requirements) in other business cases. To this end, we will present lessons learned as well as metrics for measuring the achieved degree of separation of concerns and reduced complexity.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
Notes
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
References
Antoniol G, Canfora G, Casazza G, De Lucia A, Merlo E (2002) Recovering traceability links between code and documentation. IEEE Trans Softw Eng 28(10):970–983
de Boer RC, Farenhorst R, Lago P, van Vliet H, Clerc V, Jansen, A (2007) Architectural knowledge: getting to the core. In: Quality of software architectures (QoSA), Boston, pp 197–214
Chidamber SR, Kemerer CF (1994) A metrics suite for object oriented design. IEEE Trans Softw Eng 20(6):476–493
Falessi D, Becker M, Cantone G (2006) Design decision rationale: experiences and steps towards a more systematic approach. SIG-SOFT software engineering notes 31 – workshop on sharing and reusing architectural knowledge 31(5)
Fenton N, Pfleeger SL (1997) Software metrics, 2nd edn, a rigorous and practical approach. PWS Publishing Co, Boston
Ghezzi C, Jazayeri M, Mandrioli D (2002) Fundamentals of software engineering, 2nd edn. Prentice Hall, Upper Saddle River
Grünbacher P, Egyed A, Medvidovic N (2003) Reconuciling software requirements and architectures with intermediate models. J Softw Syst Model 3(3):235–253
Hall JG, Jackson M, Laney RC, Nuseibeh B, Rapanotti L (2002) Relating software requirements and architectures using problem frames. In: IEEE international conference requirements engineering. IEEE Computer Society, Essen, pp 137–144
Heckel R, Engels G (2002) Relating functional requirements and soft-ware architecture: separation and consistency of concerns. J Softw Maint Evol Res Pract 14(5):371–388
Hentrich C, Zdun U (2006) Patterns for process-oriented integration in service-oriented architectures. In: Proceedings of 11th European conference pattern languages of programs (EuroPLoP 2006), Irsee, pp 1–45
IEEE (2000) Recommended practice for architectural description of software intensive systems. Technical report IEEE-Std-1471-2000
Jansen AGJ, van der Ven J, Avgeriou P, Hammer DK (2007) Tool support for architectural decisions. In: Sixth IEEE/IFIP working conference software architecture (WICSA), Mumbai
Kruchten P, Lago P, van Vliet H (2006) Building up and reasoning about architectural knowledge. In: QoSA 2006. LNCS, Vol 4214, Springer, Heidelberg, pp 43–58
Kruchten P (1995) The 4 + 1 view model of architecture. IEEE Softw 12(6):42–50
Kruchten P, Capilla R, Duenas JC (2009) The decision view’s role in software architecture practice. IEEE Softw 26:36–42
Lange CFJ (2006) Model size matters. In: Models in software engineering, workshops and symposia at MoDELS 2006. LNCS. Springer, Berlin, pp 211–216
MacLean A, Young RM, Bellotti V, Moran T (1991) Questions, options, and criteria: elements of design space analysis. HumanComput Interact 6(3–4):201–250
McCabe TJ (1976) A complexity measure. IEEE Trans Softw Eng 2(4):308–320
Papazoglou MP, Traverso P, Dustdar S, Leymann F (2008) Service-oriented computing: a research roadmap. Int J Cooperative Inf Syst 17(2):223–255
Rozanski N, Woods E (2005) Software systems architecture: working with stakeholders using viewpoints and perspectives. Addison-Wesley, Boston
Sant’Anna C, Garcia A, Chavez C, Lucena C. and v. von Staa A (2003) On the reuse and maintenance of aspect-oriented software: an assessment framework. In XVII Brazilian symposium on software Engineering, Manaus
Stahl T, Völter M (2006) Model-driven software developoment. John Wiley & Sons, Chichester
Tran H, Holmes T, Zdun U, Dustdar S (2009) Modeling process-driven SOAs – a view-based approach, IGI global. In: Handbook of research on business process modeling (Chap 2)
Tran H, Zdun U, Dustdar S (2007) View-based and model-driven approach for reducing the development complexity in process-driven SOA. In: International conference business process and services computing (BPSC), GI, LNI, vol 116, pp 105–124
Tran H, Zdun U, Dustdar S (2008) View-based integra-tion of process-driven SOA models at various abstraction levels. In: First international workshop on model-based software and data integration MBSDI 2008. Springer, Heidelberg, pp 55–66
Tran H, Zdun U, Dustdar S (2008b) View-based reverse engineering approach for enhancing model interoperability and reusability in process-driven SOAs. In: Tenth international conference software reuse (ICSR), Springer, Bejing, pp 233–244
Tran H, Zdun U, Dustdar S (2009) VbTrace: using view-based and model-driven development to support traceability in process-driven SOAs. J Softw Syst Model. doi:10.1007/s10270-009-0137-0
Tran H, Zdun U, Dustdar S (2010) Name-based view integration for enhancing the reusability in process-driven SOAs. In: First international workshop on reuse in business process management (rBPM) at BPM 2010. Springer, Heidelberg, pp 1–12
Tyree J, Ackerman A (2005) Architecture decisions: demystifying ar-chitecture. IEEE Softw 22:19–27
Wile DS (2001) Residual requirements and architectural residues. In: Fifth IEEE International symposium on requirements engineering IEEE Computer Society, Toronto, pp 194–201
Zimmermann O, Gschwind T, Kuester J, Leymann F, Schuster N (2007) Reusable architectural decision models for enterprise application development. In: Quality of software architecture (QoSA) 2007. Lecture notes in computer science, Boston
Acknowledgments
The authors would like to thank the anonymous reviewers for providing constructive, insightful comments that greatly help to improve this chapter. This work was supported by the European Union FP7 project COMPAS, grant no. 215175 and the European Union FP7 project INDENICA grant no. 257483.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Tran, H., Holmes, T., Zdun, U., Dustdar, S. (2011). Using Model-Driven Views and Trace Links to Relate Requirements and Architecture: A Case Study. In: Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrík, I. (eds) Relating Software Requirements and Architectures. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21001-3_14
Download citation
DOI: https://doi.org/10.1007/978-3-642-21001-3_14
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-21000-6
Online ISBN: 978-3-642-21001-3
eBook Packages: Computer ScienceComputer Science (R0)