From Principles to Details: Integrated Framework for Architecture Modelling of Large Scale Software Systems

• Autorzy: Zalewski A. , Kijas S.
• Języki publikacji: EN

Abstrakty

EN

There exist numerous models of software architecture (box models, ADL’s, UML, architectural decisions), architecture modelling frameworks (views, enterprise architecture frameworks) and even standards recommending practice for the architectural description. We show in this paper, that there is still a gap between these rather abstract frameworks/standards and existing architecture models. Frameworks and standards define what should be modelled rather than which models should be used and how these models are related to each other. We intend to prove that a less abstract modelling framework is needed for the effective modelling of large scale software intensive systems. It should provide a more precise guidance kinds of models to be employed and how they should relate to each other. The paper defines principles that can serve as base for an integrated model. Finally, structure of such a model has been proposed. It comprises three layers: the upper one – architectural policy – reflects corporate policy and strategies in architectural terms, the middle one –system organisation pattern – represents the core structural concepts and their rationale at a given level of scope, the lower one contains detailed architecture models. Architectural decisions play an important role here: they model the core architectural concepts explaining detailed models as well as organise the entire integrated model and the relations between its submodels.

Słowa kluczowe

EN

numerous models of software architecture; Integrated Framework; Architecture Modelling; Large Scale Software Systems

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2013
• Tom: Vol. 7, nr 1
• Strony: 45--52
• Opis fizyczny: Bibliogr. 16 poz., rys.

Twórcy

autor

Zalewski A.

• Institute of Automatic Control and Computational Engineering, Warsaw University of Technology

autor

Kijas S.

• Institute of Automatic Control and Computational Engineering, Warsaw University of Technology

Bibliografia

• [1] Recommended Practice for Architectural Description of Software-Intensive Systems, http://standards.ieee.org/findstds/standard/1471-2000.html, IEEE Std., 2000.
• [2] P. Kruchten, “The 4+1 view model of architecture,” IEEE Software, Vol. Volume 12, No. 6, 1995, pp. 45–50.
• [3] R. C. Philippe Kruchten and J. C. Dueñas, “The decision view’s role in software architecture prac52 Andrzej Zalewski, Szymon Kijas tice,” IEEE Software, Vol. Volume 26, No. 2, Mar/Apr 2009, pp. 36–42.
• [4] J. Zachman, “Framework for information systems architecture,” IBM Systems Journal, Vol. Volume 26, No. 3, 1987, pp. 276–292.
• [5] ——. (2010) Zachman framework. http://www.address.org/.
• [6] The Open Group Architecture Framework (TOGAF). http://www.zifa.com. The Open Group.
• [7] A. W. Kamal and P. Avgeriou, “An evaluation of ADLs on modeling patterns for software architecture,” LNCS Springer, Nov 2007, 3rd International Workshop on Rapid Integration of Software Engineering techniques (RISE).
• [8] A. Jansen and J. Bosch, “Software architecture as a set of architectural design decisions,” IEEE Computer Society, 2005, pp. 109–120, 5thWorking IEEE/IFIP Conference on Software Architecture (WICSA’05).
• [9] J. Tyree and A. Akerman, “Architecture decisions: Demystifying architecture,” IEEE Software, Vol. Volume 22, No. 2, Mar 2005, pp. 19–27.
• [10] A. Zalewski and S. Kijas, “Architecture decision-making in support of complexity control,” LNCS Springer, Vol. Volume 6285, 2010, pp. 501–504.
• [11] F. N. Rafael Capilla and J. C. Dueñas, “Modeling and documenting the evolution of architectural design decisions,” IEEE CS Press, 2007, proc. 2nd Workshop Sharing and Reusing Architectural Knowledge Architecture, Rationale and Design Intent.
• [12] P. Kruchten, “An ontology of architectural design decisions,” Rijksuniversiteit Groningen, Oct 2004, pp. 54–61, in 2nd Groningen Workshop on Software Variability Management.
• [13] ArchiMate R 1.0 specification. http://www.opengroup.org/archimate/doc/ts_archimate/.
• [14] R. Malan and D. Bredemeyer, “Less is more with minimalist architecture,” IEEE’s IT Professional, Sep/Oct 2002.
• [15] A. Zalewski, “Beyond ATAM: Architecture analysis in the development of large scale software systems,” LNCS Springer, Vol. Volume 4758, Sep 2007, pp. 92–105, first European Conference, ECSA 2007 Aranjuez, Spain.
• [16] P. A. Neil B. Harrison and U. Zdun, “Using patterns to capture architectural decisions,” IEEE Software, Vol. Volume 24, No. 4, Jul/Aug 2007, pp. 38–45.