SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Database Systems: The Complete Book
Database Systems: The Complete Book
The Art of Software Architecture: Design Methods and Techniques
The Art of Software Architecture: Design Methods and Techniques
Less is More with Minimalist Architecture
IT Professional
A survey on software architecture analysis methods
IEEE Transactions on Software Engineering
Software Architecture in Practice
Software Architecture in Practice
Loosely Coupled: The Missing Pieces of Web Services
Loosely Coupled: The Missing Pieces of Web Services
Architecture Decisions: Demystifying Architecture
IEEE Software
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
IBM Systems Journal
Applying the ATAM to an architecture for decentralized control of a transportation system
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
Hi-index | 0.00 |
Large scale software developments require substantial investment and are exposed to high level of risk. Architectural decisions taken at early stages of the development can substantially influence the entire level of technical risk. In this paper architectural decisions are divided into two basic groups: early - top level system organization decision establishing system organization patterns (the notion introduced in this paper) and detailed ones. However as it was shown on notable examples of large scale developments carried out in recent ten years in Poland, wrong decisions concerning system organization pattern can trigger severe risks that can lead to the development crisis. These risks are frequently connected with the complexity explosion syndrome - sudden, undetected growth of design complexity that exceeds the capabiblity of the development team and time budget. To manage these risks properly appropriate architecture analysis method has been introduced. On the contrary to the traditional scenario-based architecture analysis methods, like ATAM, it was based on GQM approach. A complete assessement framework have been defined comprising three goals: complexity control, organizational adequacy and satisfactory perforormance and reliability; a set of questions related to these goals, as well as metrics for the qualities expressed by these questions. The conclusion contains ex post analysis of exemplary large scale systems showing that the proposed framework provides adequate assessement of design risk. It has also been indicated that the critical risks identified during the evalution of the system organization pattern should be carefully managed.