Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
An experiment on creating scenario profiles for software change
Annals of Software Engineering
Experiences with ALMA: architecture-level modifiability analysis
Journal of Systems and Software
Communication and Organization: An Empirical Study of Discussion in Inspection Meetings
IEEE Transactions on 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
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Empirical Software Engineering
A controlled experiment on team meeting style in software architecture evaluation
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
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 |
Studying the effectiveness of scenario development meetings in the software architecture process is important to improve meeting effectiveness. This paper reports initial findings from analyzing the data collected in a controlled experiment aimed at studying the effectiveness of meetings in terms of gained and lost scenarios of individuals, real and nominal (non-communicating) teams. Our findings question the effectiveness of holding meetings since more important scenarios were lost than gained in these meetings. In the study nominal teams performed better than individuals and real teams.