%0 Journal Article %1 Kazman1996 %A Kazman, R. %A Abowd, G. %A Bass, L. %A Clements, P. %D 1996 %J IEEE Software %K softwaredevelopmentmanagement highleveldesignneeds qualitycriteria softwarereliability softwarearchitecture usecontexts systemsanalysis qualityattributes casestudyreport scenariobasedanalysis developerviews anticipatedsystemuses softwarequality SoftwareArchitectureAnalysisMethod %N 6 %P 47--55 %R 10.1109/52.542294 %T Scenario-based analysis of software architecture %V 13 %X Despite advances in clarifying high level design needs, analyzing a system's ability to meet desired quality criteria is still difficult. The authors propose using scenarios to make analysis more straightforward. In their case study report, they analyze lessons learned with this approach. They developed the Software Architecture Analysis Method, an approach that uses scenarios to gain information about a system's ability to meet desired quality attributes. Scenarios are brief narratives of expected or anticipated system uses from both user and developer views and they provide a look at how the system satisfies quality attributes in various use contexts

@article{Kazman1996, abstract = {Despite advances in clarifying high level design needs, analyzing a system's ability to meet desired quality criteria is still difficult. The authors propose using scenarios to make analysis more straightforward. In their case study report, they analyze lessons learned with this approach. They developed the Software Architecture Analysis Method, an approach that uses scenarios to gain information about a system's ability to meet desired quality attributes. Scenarios are brief narratives of expected or anticipated system uses from both user and developer views and they provide a look at how the system satisfies quality attributes in various use contexts}, added-at = {2010-03-22T14:17:15.000+0100}, author = {Kazman, R. and Abowd, G. and Bass, L. and Clements, P.}, biburl = {https://www.bibsonomy.org/bibtex/246bf4ee348231df9184aea8b792876fb/ramkumarrs}, doi = {10.1109/52.542294}, interhash = {27021ab27df5bcd0f18803f4348b3ea8}, intrahash = {46bf4ee348231df9184aea8b792876fb}, issn = {0740-7459}, journal = {IEEE Software}, keywords = {softwaredevelopmentmanagement highleveldesignneeds qualitycriteria softwarereliability softwarearchitecture usecontexts systemsanalysis qualityattributes casestudyreport scenariobasedanalysis developerviews anticipatedsystemuses softwarequality SoftwareArchitectureAnalysisMethod}, number = 6, pages = {47--55}, timestamp = {2010-03-22T14:17:15.000+0100}, title = {Scenario-based analysis of software architecture}, volume = 13, year = 1996 }