Architectural Analysis

 

Objectives: Architectural Analysis

Architectural Analysis







Understand the purpose of Architectural Analysis and where in the lifecycle it is performed Describe a representative architectural pattern and set of analysis mechanisms, and how they affect the architecture Understand how to read and interpret the results of  Architectural Analysis  Architectural Layers and their relationships  Architectural relationships  High-level packages and their relationships  Key concepts  Modeling conventions 

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

1

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

 Architectural  Analysis

 Architectural Describe Design Concurrency

Describe Distribution

Review the  Architecture Reviewer   Architecture

Glossary Supplementary Specifications Use-Case  Analysis

Subsystem Design

Designer 

Use-Case Design

Review the Design

 Architecture Document Design Guidelines

Design Reviewer 

Architectural Analysis

Class Design

3

R

    



Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints



5

4

R

Architectural Analysis Topics

Key Architectural Analysis Concepts Modeling Conventions  Analysis Mechanisms

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Use Case Realizatio

Design Model

Use-Case Model

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Architectural Analysis Topics 

Design Guidelines

Design Model

Database Design

Database Designer 

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

Architectural Analysis Overview

So Where Are We?

 Architect

2

 

 

R

Key Architectural Analysis Concepts Modeling Conventions  Analysis Mechanisms Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Page 1

6

R

 

What is Architecture Architecture:: The “4+1 View” Model

Logical Logi cal View

Analysts/Designers Structure

What is a Package?

Implementation Implementatio n View

End-user Functionality 



 A package is a general purpose mechanism for organizing elements into groups



 A model element which can contain other model elements

Programmers Software management 

Use-Case View

Process View

Deployment View System engineering System topology  Delivery, installation communication

System integrators Performance Scalability  Throughput 

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Package Name

Organize the model under development  A unit of configuration management management



R

7

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Package Relationships: Dependency 

Uses



R

8

Avoiding Circular Dependencies

Packages can related to one another using a dependency

 A  A

relationship Dependency relationship ClientPackage

B

SupplierPackage

Hierarchy should be acyclic 

B

 A 

Dependency Implications

C

• Changes to the the Supplier pa package ckage may affec affectt the Client package

B  A'

• The Client package package cannot be reused inde independently pendently because because it depends on the Supplier package OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

9

C

Circular dependencies make it impossible to reuse one package without the other  R

R

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Architectural Analysis Topics      

Modeling Conventions

Key Architectural Analysis Concepts Modeling Conventions  Analysis Mechanisms



11

What Are They? What diagrams and modeling elements to use  Rules for the use of modeling elements and diagrams  Naming conventions 

Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

10



Examples What modeling constructs should not be used  What diagrams must exist  What diagrams should be used to model the architectural views 

R

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Page 2

12

R

 

Architectural Analysis Topics

Example: Modeling Conventions 

Use Case View 





Use Cases will be named with short active phrases such as “Submit Grades”

 

Logical View



 A Use Case Realization pack package age will be ccreated reated that includes:





• At least one realization realization pe perr use case trace tracedd to the use case



• A “View Of Parti Participating cipating Classes” diagram that shows shows the participants in the realization and their relevant relationships 

13

R

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Architectural Mechanisms: What Are They?  Architectural Mechanisms  Analysis Mechanisms Mechanisms (con (conceptual) ceptual)  Design Mechanisms (concrete)  Implementation Mechanisms (actual)

Persistency



Communication (IPC and RPC) Message routing Distribution Transaction management Process control and synchronization (resource contention) Information exchange, format conversion Security Error detection / handling / reporting Redundancy Legacy Interface R

 

    

15

R



OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Analysis Mechanism Characteristics Persistency



Granularity  Volume  Duration  Access mechanism mechanism  Access frequency frequency (cr (creation/deletion, eation/deletion, update, rea read) d)  Reliability

Latency  Duration  Access mechanism mechanism  Access frequency frequency 

Data granularity  User granularity  Security rules  Privilege types

Latency  Synchronicity 

Message Size Protocol



17

Security 



OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Legacy interface 

Communication



16

Analysis Mechanism Characteristics (cont.)





R





OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

14

Sample Analysis Mechanisms





Modeling Conventions  Analysis Mechanisms Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

Classes will be named with noun names matching the problem domain as much as possible.

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved



Key Architectural Analysis Concepts

R

etc.

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Page 3

18

R

 

Describing Analysis Mechanisms Mechanisms - Example

Describing Analysis Mechanisms

Client



Collect all analysis mechanisms in a list



Draw a map of the client classes to the analysis mechanisms Analysis Class

 Analysis

Class

Mechanism (Conceptual)

Analysis Mechanism(s)

Course

Student



Persistency

Persistency

Identify characteristics of the Analysis Mechanisms RegistrationController 

Distribution Analysis OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

19

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

    

R

Identify Key Concepts

Architectural Analysis Topics 

20

Key Architectural Analysis Concepts



Modeling Conventions  Analysis Mechanisms Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

Define preliminary entity analysis classes 

Domain knowledge Requirements  Glossary  Domain Model, or the Business Model (if exists) 

 

Define analysis class relationships Model analysis classes and relationships on Class Diagrams 



Include brief description of analysis class

Map analysis classes to necessary analysis mechanisms  Analysis classes will evolve

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

21

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

<<entity>> Professor 

<<entity>> Student

(from University Artifacts)

(from University Artifacts)

   

(from University Artifacts)

<<entity>> Grade



(from University Artifacts) 

<<entity>> CourseCatalog

<<entity>> CourseOffering

(from Course Catalog)

(from University Artifacts)

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

Architectural Analysis Topics

Example: Key Concepts

<<entity>> Schedule

22

23

Key Architectural Analysis Concepts Modeling Conventions  Analysis Mechanisms Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

<<entity>> Course (from University Artifacts)

R

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Page 4

24

R

 

Design Patterns

Patterns and Frameworks 

Pattern



Describes a common design problem  Describes the solution to the problem  Discusses the results and trade-offs of applying the pattern

 A common solution to a common pproblem roblem in a ccontext ontext







 Analysis/Design Pattern  A solution to a narrowlynarrowly-scoped scoped tech technical nical problem  A fragment of a solut solution, ion, or a ppiece iece of the puzzle 





Framework  

Defines the general approach to solving the problem Skeletal solution, whose details may be analysis/desig analysis/designn patterns

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Parameterized  collaboration OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved



Layers



Model-view-controller (M-V-C) Pipes and filters Blackboard



Cont ext 26

Collaborat ion

R

Typical Layering Approach

Architectural Patterns



Design patterns provide the capability to reuse successful designs

Pattern Name

R

25

 A design pattern is a solution to a common design problem

Specific functionality

General functionality

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

R

27

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Example: High-Level Organization of the Model



StudentInterface (from User Interface)

ProfessorInterface (from User Interface)

  

Registration (from Business Services)

Student Evaluation (from Business Services)

 

Finance System (from Business Services)

R

Architectural Analysis Topics

User Interface Layer  RegistrarInterface (from User Interface)

28

Key Architectural Analysis Concepts Modeling Conventions  Analysis Mechanisms Key System Concepts Initial Architectural Layers  Architectural Analysis Checkpoints

Business Services Layer 

Course Catalog (from Business Objects)

Business Objects Layer 

University Artifacts (from Business Objects) OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

29

R

OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

Page 5

30

R

Page 5  

Architectural Analysis Checkpoints (cont.)

Architectural Analysis Checkpoints 

General



Is the package partitioning and layering done in a logically consistent way?  Have the necessary analysis mechanisms mechanisms been identified? 



Packages 

Have we provided a comprehensive picture of the services of the packages in upper-level layers?

OOAD Using the UML - Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

31

R

Classes Have the key entity classes and their relationships been identified and accurately modeled?  Does the name of each class clearly reflect the role it plays?  Have the entity classes been mapped to the necessary analysis mechanisms? mechanisms?



OOAD Using the UML -Architectural Analysis, v 4.0 Copyright  1994-1998 Rational Software, all rights reserved

32

R