Knowledge acquisition using structured interviewing: an empirical investigation
Journal of Management Information Systems
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
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
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
Toward a discipline of scenario-based architectural engineering
Annals of Software Engineering
An experiment on creating scenario profiles for software change
Annals of Software Engineering
Empirical Software Engineering
Experiences with ALMA: architecture-level modifiability analysis
Journal of Systems and Software
Scenario-Based Analysis of Software Architecture
IEEE Software
Analysis of Virtual Workspaces
DANTE '99 Proceedings of the 1999 International Symposium on Database Applications in Non-Traditional Environments
How well can we predict changes at architecture design time?
Journal of Systems and Software
Architecture-level modifiability analysis (ALMA)
Journal of Systems and Software
A Framework for Classifying and Comparing Software Architecture Evaluation Methods
ASWEC '04 Proceedings of the 2004 Australian Software Engineering Conference
ASWEC '06 Proceedings of the Australian Software Engineering Conference
An empirical study of groupware support for distributed software architecture evaluation process
Journal of Systems and Software - Special issue: Selected papers from the 11th Asia Pacific software engineering conference (APSEC 2004)
WoSQ '07 Proceedings of the 5th International Workshop on Software Quality
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
Using domain knowledge to boost software architecture evaluation
ECSA'10 Proceedings of the 4th European conference on Software architecture
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 |
Scenarios are extensively used in software architecture evaluation. These scenarios are elicited from stakeholders using either a topdown or bottom-up approach. The former approach uses categorization schemes to focus stakeholders on developing scenarios for each required category. The latter approach uses brainstorming without any explicit categories of scenarios. It is claimed that top-down approach can result in improved quality of scenarios. However, there has been no empirical evidence on the relative effectiveness of the scenario elicitation techniques. In this paper we report on a controlled experiment with 24 subjects (postgraduate and final year undergraduate students with industry experience) in an academic context with the goal to assess the relative effectiveness of the two scenario elicitation approaches. Two groups developed scenarios to characterize quality attributes: the treatment group was given software change categories, the control group was not. The outcome variable was the quality of the scenarios produced by each participant. The average quality score for individual scenario profiles in the treatment group was significantly greater than the control group. All participants using the change categories reported that the knowledge of change categories helped them develop better quality scenarios. Our results support the claim that the provision of domainspecific software change categories helps generate better quality scenarios.