Steps in an Architectural Tradeoff
Analysis Method: Quality Attribute Models
and Analysis
[Top]
[Prev]
[Next]
[Bottom]
[PDF]
|
REPORT DOCUMENTATION PAGE
|
Form Approved
OMB No. 0704-0188
|
|---|
|
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.
|
|
1. agency use only (leave blank)
|
2. report date
May 1998
|
3. report type and dates covered
Final
|
|
|
4. title and subtitle
Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis
|
5. funding numbers
C - F19628-95-C-0003
|
|
6. author(s)
Barbacci, M.; Carriere, S.; Feiler, P.; Kazman, R.; Klein, M.; Lipson, H.; Longstaff, T.; Weinstock, C.
|
|
7. performing organization name(s) and address(es)
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, PA 15213
|
8. performing organization
report number
CMU/SEI-97-TR-029
|
|
9. sponsoring/monitoring agency name(s) and address(es)
HQ ESC/AXS
5 Eglin Street
Hanscom AFB, MA 01731-2116
|
10. sponsoring/monitoring
agency report number
ESC-TR-97-029
|
|
11. supplementary notes
|
|
12.a distribution/availability statement
Unclassified/Unlimited, DTIC, NTIS
|
12.b distribution code
|
|
13. abstract (maximum 200 words)
This paper presents some of the steps in an emerging architecture tradeoff analysis method (ATAM). The objective of the method is to provide a principled way to understand a software architecture's fitness with respect to multiple competing quality attributes: modifiability, security, performance, availability, and so forth. These attributes can interact or conflict-improving one often comes at the price of worsening one or more of the others, thus it is necessary to trade off among multiple software quality attributes at the time the software architecture of a system is specified, and before the system is developed. This report illustrates typical quality attribute models, analyses, and tradeoffs using a small real-time industrial application.
|
|
14. subject terms
architecture business cycle, architecture tradeoffs, attribute models, availability, performance, quality attributes, security, software architecture
|
15. number of pages
32
|
16. Price Code
|
17. security classification
of report
UNCLASSIFIED
|
18. security classification of this page
UNCLASSIFIED
|
19. security classification
of abstract
UNCLASSIFIED
|
20. limitation of abstract
UL
|
|
NSN 7540-01-280-5500
|
|
|
Standard Form 298 (Rev. 2-89)
Prescribed by ANSI Std. Z39-18
298-102
|
[Top] [Prev]
[Next] [Bottom] [PDF]
