Software Architecture Analysis Method

Slides:



Advertisements
Similar presentations
Main issues: • Why is reuse so difficult • How to realize reuse
Advertisements

What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Mr. Brooks Foundations of Technology.  Students will: ◦ Develop an understanding of the relationships among technologies and connections with other fields.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
Software Testing and Quality Assurance
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
Chapter 2 Introduction to Systems Architecture. Chapter goals Discuss the development of automated computing Describe the general capabilities of a computer.
Methods and Models for Evaluating Software Product Line Architecture Hyotaeg Jung Computer Science Department Univ. of Texas at Dallas Software Architecture.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Backward Design Lesson Planning Lyn Steed University of West Georgia.
Lecture 9: Chapter 9 Architectural Design
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
Software Measurement & Metrics
Henry Muccini - Computer Science Department, Universita' dell'Aquila, Italy Paola Inverardi - Computer Science Department, Universita'
12.1 Introduction Checklists are used as a technique to give status information in a formalized manner about all aspects of the test process. This chapter.
Chapter 6 Architectural Design.
Team Think For You. Outline  Introduction  Process  Requirements Engineering  Architecture  Detailed Design  Testing  Demo  Extensibility  Conclusions.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
Agile: Lessons Learned (a retrospective) Tony
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
Evaluating Algebraic Equations
Object-oriented design IS Outline  CRC cards  Group activity.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Copyright ©2004 Cezary Z Janikow 1 OOAD Overview n OO language – Necessary for OO systems? – Sufficient for OO systems? Owning a hummer doesn’t make you.
1 آزمايشگاه سيستم های هوشمند ( معماری سيستمهای با مقياس بزرگ آزمايشگاه سيستمهای هوشمند پاييز 93.
Scenario-Based Analysis of Software Architecture Rick Kazman, Gregory Abowd, Len Bass, and Paul Clements Presented by Cuauhtémoc Muñoz.
Overall Evaluation of Software Architecture By Ashwin Somaiah.
1 reTHINK Deliverables, How To Read reThink deliverables quick starter.
SOFTWARE ARCHITECTURE FOR A KWIC SYSTEM TEAM: GLOBAL 14.
Web Services Architecture Presentation for ECE8813 Spring 2003 By: Mohamed Mansour.
UML - Development Process 1 Software Development Process Using UML.
CONNECTING COMPONENT Pertemuan Matakuliah: M Analisis dan Perancangan Sistem Informasi Lanjut Tahun:
Lecture 17 Enterprise Systems Development ( CSC447 ) COMSATS Islamabad Muhammad Usman, Assistant Professor.
Methodology Review Chapter 7 Part 2: Design Methodology Object-Oriented Modeling and Design Byung-Hyun Ha
Documenting Software Architectures. Outline  Introduction  Uses of Architectural Documentation  Views  Choosing the Relevant Views  Documenting a.
What is the order of the graph?
MATH Mathematical Literacy for College Students II
A Survey on Software Architecture Analysis Methods
Fundamentals of Information Systems, Sixth Edition
Evaluating Existing Systems
Object-Oriented Techniques
7th Grade Big Ideas.
Evaluating Existing Systems
Gestione di Service Level Agreements (SLA) in sistemi Grid
SWOT and A’WOT analysis
Object-Oriented Analysis
مبررات إدخال الحاسوب في رياض الأطفال
Solve: 1. 4<
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Technology Lesson 1.1 Words To Know.
L1-6 Notes: Algebra: Variables and Expressions
The Vision of Autonomic Computing
Agenda – week 9 6:00 – 6:10 Questions, announcements 6:10 – 6:30
واسط كاربري هوشمند Intelligent User Interface
21twelveinteractive.com/ twitter.com/21twelveI/ facebook.com/21twelveinteractive/ linkedin.com/company/21twelve-interactive/ pinterest.com/21twelveinteractive/
Strategic Human Resource Management
Scientific Theory Scientific Law Comparison Table
POWER CHALLENGES Several Ways To Solve 7 CHALLENGES.
Software Architecture Analysis Method
Important Things to Remember
Social Practice of the language: Describe and share information
Brokering as a Core Element of EarthCube’s Cyberinfrastructure
LANGUAGE EDUCATION.
Upcoming Constraint Editor and Language Enhancements
Software Development Process Using UML Recap
DAE Model D = describe the event. A = analyse the event/object/photo several ways. E = evaluate your results.
Presentation transcript:

Software Architecture Analysis Method About SAAM Software Architecture Analysis Method

The problem SAAM solves How to compare software architectures? Two major barriers to effective comparison No common architecture description language Inventing new terms Using existing terms in different ways Usually hard to connect an architecture with its qualities

Steps in SAAM Describe each candidate architecture Define and prioritize scenarios Scenario evaluations for each architecture Direct (supported by the architecture) Indirect (anticipated changes) Determine interactions among indirect scenarios (fewer interactions are better) Overall evaluation based on scenario weighting

Indirect scenarios A scenario is indirectly supported by an architecture if it requires modifications Types of modifications include Extension of capabilities Adaptation to new operating environments Removal of unneeded capabilities Usually, pay attention only to the first two