DOC PREVIEW
USC CSCI 578 - AnalysisTech

This preview shows page 1-2-14-15-29-30 out of 30 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Analysis TechniquesArchitectural Analysis in a NutshellAnalysis Technique CategoriesArchitectural Inspections and ReviewsInspections and Reviews in a NutshellExample – ATAMATAM ProcessATAM Business DriversATAM ScenariosSlide 10ATAM ArchitectureSlide 12ATAM AnalysisATAM in a NutshellModel-Based Architectural AnalysisModel-Based Analysis in a NutshellModel-Based Analysis in ADLsADLs’ Analysis Foci in a NutshellArchitectural Reliability AnalysisReliability MetricsAssessing Reliability at Architectural LevelArchitectural Reliability Analysis in a NutshellSimulation-Based AnalysisArchitectural and Simulation ModelsSimulation-Based Analysis in a NutshellExample – XTEAMExample XTEAM ModelExample XTEAM AnalysisXTEAM in a NutshellClosing RemarksCopyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved.Analysis TechniquesFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture2Architectural Analysis in a NutshellSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.Foundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture3Analysis Technique CategoriesInspection- and review-basedModel-basedSimulation-basedFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture4Architectural Inspections and ReviewsArchitectural models studied by human stakeholders for specific propertiesThe stakeholders define analysis objectiveManual techniquesCan be expensiveUseful in the case of informal architectural descriptionsUseful in establishing “soft” system propertiesE.g., scalability or adaptabilityAble to consider multiple stakeholders’ objectives and multiple architectural propertiesFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture5Inspections and Reviews in a NutshellAnalysis Goals – anyAnalysis Scope – any Analysis Concern – any, but particularly suited for non-functional propertiesArchitectural Models – any, but must be geared to stakeholder needs and analysis objectivesAnalysis Types – mostly static and scenario-basedAutomation Level – manual, human intensiveStakeholders – any, except perhaps component vendorsFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture6Example – ATAM Stands for architectural trade-off analysis methodHuman-centric process for identifying risks early on in software designFocuses specifically on four quality attributes (NFPs)ModifiabilitySecurityPerformanceReliabilityReveals how well an architecture satisfies quality goals and how those goals trade-ofFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture7ATAM ProcessSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.Foundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture8ATAM Business DriversThe system’s critical functionalityAny technical, managerial, economic, or political constraintsThe project’s business goals and contextThe major stakeholdersThe principal quality attribute (NFP) goalsFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture9ATAM ScenariosUse-case scenariosDescribe how the system is envisioned by the stakeholders to be usedGrowth scenariosDescribe planned and envisioned modifications to the architectureExploratory scenariosTry to establish the limits of architecture’s adaptability with respect tosystem’s functionalityoperational profilesunderlying execution platformsScenarios are prioritized based on importance to stakeholdersFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture10ATAM ProcessSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.Foundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture11ATAM ArchitectureTechnical constraintsRequired hardware platforms, OS, middleware, programming languages, and OTS functionalityAny other systems with which the system must interactArchitectural approaches that have been used to meet the quality requirementsSets of architectural design decisions employed to solve a problemTypically architectural patterns and stylesFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture12ATAM ProcessSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.Foundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture13ATAM AnalysisKey step in ATAMObjective is to establish relationship between architectural approaches and quality attributesFor each architectural approach a set of analysis questions are formulatedTargeted at the approach and quality attributes in questionSystem architects and ATAM evaluation team work together to answer these questions and identifyRisks  these are distilled into risk themesNon-RisksSensitivity pointsTrade-of pointsBased on answers, further analysis may be performedFoundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture14ATAM in a NutshellGoalsCompletenessConsistencyCompatibilityCorrectness`ScopeSubsystem- and system-levelData exchangeConcern Non-functionalModelsInformalSemi-formalType Scenario-drivenAutomation Level ManualStakeholdersArchitectsDevelopersManagersCustomersSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.Foundations, Theory, and PracticeSoftware ArchitectureSoftware Architecture15Model-Based Architectural AnalysisAnalysis techniques that manipulate architectural description to discover architectural propertiesTool-driven, hence potentially less costlyTypically useful for establishing “hard” architectural properties onlyUnable to capture design intent and rationaleUsually focus on a single architectural aspectE.g., syntactic correctness, deadlock freedom, adherence to a styleScalability may be an issueTechniques typically


View Full Document

USC CSCI 578 - AnalysisTech

Download AnalysisTech
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view AnalysisTech and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view AnalysisTech 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?