Architectural Analysis

Architectural Analysis
Objectives: 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
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

So Where Are We?
Architect
Architectural
Analysis
Architectural Analysis Overview
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
Architectural
Analysis
Design
Reviewer
Class
Design
Architectural Analysis Topics
Key Architectural Analysis Concepts

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

Use Case Realization
Design Model
Use-Case Model

Design
Guidelines
Design Model
Database
Design
Database
Designer


Analysis Mechanisms
Key System Concepts

Page 1
1
What is Architecture: The 4+1 View Model
Logical View
Analysts/Designers
Structure
What is a Package?
A package is a general purpose mechanism for organizing
elements into groups
A model element which can contain other model elements
Implementation View
End-user
Functionality
Programmers
Software management
Use-Case View
Process View
Deployment View
Uses
System engineering
System topology
Delivery, installation
communication
System integrators
Performance
Scalability
Throughput

Package Name
Organize the model under development

A unit of configuration management

Package Relationships: Dependency
Avoiding Circular Dependencies
Packages can related to one another using a dependency

relationship
A
A
Dependency relationship
ClientPackage
SupplierPackage
Hierarchy
should be
acyclic
Dependency Implications
Changes to the Supplier package may affect the Client

package
The Client package cannot be reused independently because it
depends on the Supplier package
B
A'
C
Circular dependencies make it impossible to reuse

one package without the other

11

Analysis Mechanisms
Key System Concepts

10
What Are They?

What diagrams and modeling elements to use
Rules for the use of modeling elements and diagrams
Naming conventions
Examples
What modeling constructs should not be used
What diagrams must exist
What diagrams should be used to model the architectural
views

12
Page 2
2
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 package will be created that includes:
At least one realization per use case traced to the use case
A View Of Participating Classes diagram that shows the
participants in the realization and their relevant relationships

Analysis Mechanisms
Key System Concepts
Classes will be named with noun names matching the

problem domain as much as possible.

13

Architectural Mechanisms: What Are They?
Analysis Mechanisms (conceptual)

Design Mechanisms (concrete)
Implementation Mechanisms (actual)
15
Legacy interface
Granularity
Volume
Duration
Access mechanism
Access frequency (creation/deletion, update, read)
Reliability
Latency
Duration
Access mechanism
Access frequency
Security
Data granularity
User granularity
Security rules
Privilege types
Communication
17
16
Analysis Mechanism Characteristics (cont.)
Persistency

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

Analysis Mechanism Characteristics
Latency
Synchronicity
Message Size
Protocol
Sample Analysis Mechanisms
Architectural Mechanisms

14
etc.

18
Page 3
3
Describing Analysis Mechanisms
Describing Analysis Mechanisms - Example
Collect all analysis mechanisms in a list

Draw a map of the client classes to the analysis
mechanisms
Analysis Class
Client
Analysis
Class
Mechanism
(Conceptual)
Analysis Mechanism(s)
Course
Student
Persistency
Persistency
Identify characteristics of the Analysis Mechanisms

RegistrationController

Analysis
19

Distribution
20
Identify Key Concepts

Analysis Mechanisms
Key System Concepts
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
21

Example: Key Concepts

<<entity>>
Student
(from University Artifacts)
<<entity>>
Grade
<<entity>>
CourseCatalog
<<entity>>
CourseOffering
<<entity>>
Course
(from Course Catalog)

<<entity>>
Professor
<<entity>>
Schedule
22
23

Analysis Mechanisms
Key System Concepts

24
Page 4
4
Patterns and Frameworks
Design Patterns
Pattern
A design pattern is a solution to a common design problem
A common solution to a common problem in a context
Describes a common design problem

Describes the solution to the problem
Discusses the results and trade-offs of applying the pattern
Analysis/Design Pattern
A solution to a narrowly-scoped technical problem
A fragment of a solution, or a piece of the puzzle
Design patterns provide the capability to reuse successful

designs
Framework
Defines the general approach to solving the problem
Skeletal solution, whose details may be analysis/design
patterns

Pattern Name
Parameterized
collaboration
25

Architectural Patterns
Context
26
Collaboration
Typical Layering Approach
Layers
Model-view-controller (M-V-C)
Pipes and filters
Blackboard
Specific
functionality
General
functionality
27

Example: High-Level Organization of the Model

StudentInterface
(from User Interface)
Registration
(from Business Services)
Finance System
User Interface Layer

RegistrarInterface
28
ProfessorInterface
Student Evaluation

Analysis Mechanisms
Key System Concepts
Business Services Layer
Course Catalog
(from Business Objects)
Business Objects Layer
University Artifacts
(from Business Objects)
29

30
Page 5
5
Architectural Analysis Checkpoints (cont.)
General
Classes
Is the package partitioning and layering done in a logically

consistent way?
Have the necessary analysis mechanisms been identified?
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?
Packages
Have we provided a comprehensive picture of the services of
the packages in upper-level layers?

31

32
Page 6
6

Architectural Analysis

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Architectural Analysis

Hochgeladen von

Copyright:

Verfügbare Formate

Architectural Analysis

Objectives: Architectural Analysis

OOAD Using the UML - Architectural Analysis, v 4.0

OOAD Using the UML - Architectural Analysis, v 4.0

So Where Are We?