(Enter summary)
Abstract: : Architectural decisions have a great impact on the consequent
quality of software systems. As a result, it is important to evaluate how a
software architecture meets its quality demands. Though much focus has been
placed on modeling and describing the software architecture as a design
artifact, we found that relatively little is known about the current experience with
software architecture evaluation.
This report details the results of two workshops on software architecture
evaluation, held... (Update)
Context of citations to this paper: More
.... 97 SR 019 27 architectural evaluation checklists, 1 and Rational s application of use cases to validate architectures [Kruchten 95] Abowd 97] provides a summary and discussion of current practice in architectural evaluation. Communicating COTS based architectures The BOG...
.... a large number of different stakeholders allows their concerns to be aired in a common understandable language, often for the first time ([1], 5] 27] The second way that architecture serves as a communication vehicle is that it is a technical blueprint for the system that...
Cited by: More
Evaluating Software Architectures: Development, Stability.. - Rami Bahsoon And (2003)
(Correct)
i ACKNOWLEDGMENTS - First Of All
(Correct)
Does the Code Match the Design? A Process for Architecture .. - Tvedt, Costa, Lindvall (2002)
(Correct)
Active bibliography (related documents): More All
0.5: Performance Engineering in Agent-based Systems Concepts.. - Wille, Dumke, Stojanov (2001)
(Correct)
0.1: Software Architecture: An Executive Overview - Clements, Northrop (1996)
(Correct)
0.1: Classifying COTS products - Jaccheri, Torchiano (2002)
(Correct)
Similar documents based on text: More All
1.6: A Case Study in Structural Modeling - Chastek, Brownsword (1996)
(Correct)
1.4: Documenting Software Architecture: Documenting Behavior - Bachmann, Bass.. (2002)
(Correct)
1.1: Architecture-Based Development - Bass, Kazman (1999)
(Correct)
Related documents from co-citation: More All
5: Scenario-based analysis of software architecture
- Kazman, Abowd et al. - 1996
4: Software Architecture in Practice (context) - Bass, Clements et al. - 1998
3: The Architecture Trade-off Analysis Method (context) - Kazman, Klein et al. - 1998
BibTeX entry: (Update)
G. Abowd, L. Bass, P. Clements, R. Kazman, L. Northrop, A. Zaremski, "Recommended Best Industrial Practice for Software Architecture Evaluation", Software Engineering Institute Technical Report, CMU/SEI-96-TR-025, 1996. http://citeseer.ist.psu.edu/abowd97recommended.html More
@misc{ abowd96recommended,
author = "G. Abowd and L. Bass and P. Clements and R. Kazman and L. Northrop and
A. Zaremski",
title = "Recommended Best Industrial Practice for Software Architecture Evaluation",
text = "G. Abowd, L. Bass, P. Clements, R. Kazman, L. Northrop, A. Zaremski, Recommended
Best Industrial Practice for Software Architecture Evaluation, Software
Engineering Institute Technical Report, CMU/SEI-96-TR-025, 1996.",
year = "1996",
url = "citeseer.ist.psu.edu/abowd97recommended.html" }
Citations (may not include all citations):
131
The Mythical Man-Month: Essays in Software Engineering (context) - Brooks - 1995
89
SAAM: A Method for Analyzing the Properties Software Archite..
- Kazman, Bass et al. - 1994
62
Software Structure Metrics Based on Information Flow (context) - Henry, Kafura - 1981
60
Scenario-Based Analysis of Software Architecture
- Kazman, Abowd et al. - 1996
10
The 4+1 View Model of Architecture (context) - Kruchten - 1995
8
A Software System Evaluation Framework (context) - Germinal, Pierre - 1995
2
Performance Engineering (context) - Smith - 1994
1
Software Risk Evaluation Method (context) - Sujoe, Frank - 1994
1
Interconnectivity Analysis for Large Software Systems (context) - Richard, Reimer - 1995
The graph only includes citing articles where the year of publication is known.
Documents on the same site (http://www.sei.cmu.edu/publications/documents/doc.list/1996.htm): More
Domain Analysis Workshop Report for the Automated Prompt and.. - Krut (1996)
(Correct)
A Controlled Experiment Measuring the Effect of Procedure.. - Tichy, Prechelt (1996)
(Correct)
Concept of Operations for the ESC Product Line Approach - Sholom Cohen
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC