title: A toolbox for software architecture design
title: Un Insieme di strumenti per la progettazione architetturale di sistemi software
titleType: AlternativeTitle
Creators: name: FALESSI, DAVIDE
Publisher: name: Università degli Studi di Roma "Tor Vergata"
Year: 2008
Subjects: subject: ingegneria del software; progettazione software; architettura software; ingegneria del software basata sull'evidenza; documentazione delle decisioni progettuali; tecniche decisionali
subject: ingegneria del software
subject: progettazione software
subject: architettura software
subject: ingegneria del software basata sull'evidenza
subject: documentazione delle decisioni progettuali
subject: tecniche decisionali

description: 20. ciclo
description: 1. Introduction - 1.1 Research objective and approach - 1.2 Dissertation outline - 1.3 Overview of research domain - 1.3.1 Software Architecture - 1.3.2 Software architecture design - 1.3.3 Design decision rationale documentation - 2. A characterization of empirical software engineering methods in being applied on software architecture - 2.1 Introduction - 2.2 Empirical software engineering and software architecture: detecting cultural misalignments - 2.3 Ten challenges in applying empirical software engineering to software architecture - 2.3.1 Defining software architecture â goodnessâ - 2.3.2 Describing a software architecture evaluation technique - 2.3.3 Selecting the software architecture evaluation input - 2.3.4 Describing the software architecture evaluation scenarios - 2.3.5 Describing the software architecture evaluation results - 2.3.6 Evaluating software architecture without analyzing also the resulting system - 2.3.7 Affording the cost of professional reviews - 2.3.8 Adopting a complex system as experiment object - 2.3.9 Defining the boundaries of software architecture - 2.3.10 Affording the cost of experienced subjects - 2.4 Characterizing empirical methods with respect to software architecture - 2.4.1 Real ongoing project - 2.4.2 Completed real project - 2.4.3 Ad-hoc project - 2.4.4 Challenges in synthesis - 2.5 Our experiences - 2.5.1 Impact of the Boundary-Control-Entity architectural pattern - 2.5.2 Impact of the Design Decision Rationale Documentation - 2.6 Conclusion - 3. A characterization of software architecture design methods - 3.1 Introduction - 3.2 Context and background - 3.2.1 Survey of software architecture design methods - 3.2.2 Software architecture design methods - 3.3 Rationale of our approach - 3.4 Architects seeds - 3.4.1 Abstraction and refinement - 3.4.2 Empirical validation - 3.4.3 Risk management - 3.4.4 Interaction management - 3.4.5 Tool support - 3.4.6 Concerns - 3.4.7 Knowledge base - 3.4.8 Requirements change management - 3.4.9 Number of supported activities - 3.5 Architects needs and methods not taken into consideration - 3.6 Results and comments - 3.6.1 Introduction, limits and threats to validity - 3.6.2 Reference for helping an architect to select the SADM mostly appropriate for the needs - 3.6.3 Areas of improvement in SADMs - 3.7 Conclusion and future work - 3.8 Acknowledgements. - 4. Resolving tradeoffs in architecture design: a characterization schema of decision-making techniques - 4.1 Introduction - 4.1.1 Context and motivation - 4.1.2 Contribution - 4.1.3 Scope - 4.1.4 Vocabulary - 4.1.5 Structure - 4.2 Related work - 4.3 The proposal - 4.3.1 Key idea - 4.3.2 Approach - 4.3.3 Limitations - 4.4 Troubles in decision-making - 4.4.1 Attribute interpretation - 4.4.2 Solution properties misunderstandings - 4.4.3 Managing stakeholders effort - 4.4.4 Solution selection - 4.4.5 Stakeholders disagreement - 4.5 Components of the characterization schema - 4.5.1 Attribute identification - 4.5.2 Need modeling - 4.5.3 Type of fulfillment description - 4.5.4 Risk description - 4.5.5 Time for expressing the issue - 4.6 Characterization schema - 4.7 Software engineering current practice - 4.8 Open problems in multi attribute decision-making - 4.9 Suggestions - 4.10 Conclusion. - 5. Assessing the importance of documenting design decision rationale - 5.1 Introduction - 5.2 Study motivation and research hypotheses - 5.3 Related work - 5.3.1 Empirical evaluation of Design Decision Rationale - 5.3.2 Cooperation - 5.3.3 Agility - 5.4 The DDRD DGA technique - 5.4.1 Expected effects on collaboration - 5.4.2 Expected effects on agility - 5.5 Experiment planning and operation - 5.5.1 Experiment definition and setting - 5.5.2 Training - 5.5.3 Subjects - 5.5.4 Objects and materials - 5.5.5 Factor and parameters - 5.5.6 Dependent variables - 5.6 Experiments results and data analysis - 5.6.1 Data set reduction - 5.6.2 Descriptive statistics - 5.6.3 Hypotheses testing - 5.7 Result discussion - 5.7.1 Individual decision-making - 5.7.2 Team decision-making - 5.8 Threats to validity - 5.8.1 Conclusion validity - 5.8.2 Construct validity - 5.8.3 Internal validity - 5.8.4 External validity - 5.9 Conclusion and future works. - 6. A value-based approach for the documentation of design decision rationale: principles and empirical feasibility study - 6.1 Introduction - 6.2 Study motivation - 6.2.1 Value-based software engineering - 6.2.2 Design decision rationale documentation - 6.2.3 Related works - 6.3 A value-based approach for documenting design decision rationale - 6.3.1 Rationale - 6.3.2 DDRD Use-cases - 6.3.3 Key idea - 6.3.4 Process - 6.3.5 Expected advantages - 6.4 Empirical feasibility study - 6.4.1 Experiment process description - 6.4.2 Experiment Result Description - 6.5 Conclusion and future work. - 7. Conclusion. - 8. References