Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software architecture in practice
Software architecture in practice
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
EasyWinWin: a groupware-supported methodology for requirements negotiation
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
PASASM: a method for the performance assessment of software architectures
WOSP '02 Proceedings of the 3rd international workshop on Software and performance
An experiment on creating scenario profiles for software change
Annals of Software Engineering
Scenario-Based Generation and Evaluation of Software Architectures
GCSE '01 Proceedings of the Third International Conference on Generative and Component-Based Software Engineering
Investigating the Defect Detection Effectiveness and Cost Benefit of Nominal Inspection Teams
IEEE Transactions on Software Engineering
Analysis of Virtual Workspaces
DANTE '99 Proceedings of the 1999 International Symposium on Database Applications in Non-Traditional Environments
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
Architecture-level modifiability analysis (ALMA)
Journal of Systems and Software
Value-Based Software Engineering
Value-Based Software Engineering
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Empirical Software Engineering
An empirical investigation of scenarios gained and lost in architecture evaluation meetings
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Design and code inspections to reduce errors in program development
IBM Systems Journal
Impact of experience and team size on the quality of scenarios for architecture evaluation
EASE'08 Proceedings of the 12th international conference on Evaluation and Assessment in Software Engineering
Hi-index | 0.00 |
Software architecture change can have a major impact on product and project quality. Software architecture evaluation systematically investigates architecture variants with respect to their quality attributes, e.g., modifiability and maintainability of a software system. Scenarios and system properties are key elements to focus architecture evaluation on most likely future changes in the software architecture. Scenario elicitation processes typically include individual scenario brainstorming and a team meeting of all relevant stakeholders to create an aligned list of important scenarios. A major research question is which meeting style, face-to-face meetings, nominal (i.e., non-communicating) teams, or distributed tool-supported team meetings are most effective. In this paper we report on a controlled experiment investigating the meeting style of scenario brainstorming processes. Major result is that face-to-face meetings outperformed in the experiment tool-supported meetings in finding more important scenarios.