When designers are facing the question how to build an application architecture practically, they often have to consider various arguments and factors coming from different perspectives: decomposition criteria in architecture design, dialog independence in user interface (UI) design, methodology to follow in a development team. These factors are not easy to conciliate, forcing designers to make trade offs or unbalanced choices. In this paper, we discuss an architecture model, which is part of TRIDENT project, that addresses these issues. It consists of a generic architecture model for highly interactive business oriented applications. It is accompanied with a practical task-based methodology for building an architecture that automatically preserves desired criteria. Assumptions made for the architecture model, its content and the semantics of relationships are explained. The systematic approach is exemplified by a complete architecture case throughout the paper. Software Architecture Analysis Method (SAAM) is finally applied to prove the benefits of this architecture and to evaluate it with respect to relevant criteria. This paper suggest first steps towards a systematic building of a software architecture.
Bodart, F., Hennebert, A.-M., Leheureux, J.-M., Provot, I., Sacré, B., & Vanderdonckt, J. (1995). Towards a Systematic Building of Software Architecture: the TRIDENT Methodological Guide. In Editors : Philippe Palanque, Rémi Bastide (ed.), Eurographics : Design, Specification and Verification of Interactive Systems ’95 (p. p. 262-278). https://doi.org/10.1007/978-3-7091-9437-9_16