Architectural Design-Object Oriented Analysis and Design-Lecture Slides, Slides of Object Oriented Analysis and Design

Download Architectural Design-Object Oriented Analysis and Design-Lecture Slides and more Slides Object Oriented Analysis and Design in PDF only on Docsity!

Architectural Design^ 

Overall structure design of a softwaresystem

Multiple architecture design modules(styles) may need for architecturaldesign.

docsity.com

Architecture Model Types^ 

General architectural models (styles)

Domain-specific architecture models

Generic model – Compiler Model

Reference model – OSI

docsity.com

Architectural Design Process^ 

System structuring and partitioning

Decomposition of software system intosub-systems and communicationsbetween sub-systems

Sub-system is an independent systemfrom other sub-systems.

docsity.com

Architectural Design Process^ 

Controlling Models

Control relationships between differentsub-systems

Data flow controlling

Control flow controlling

docsity.com

Architectural Design Process

docsity.com

Architectural Styles^ 

Pattern, common form design,organizational principles, and structurefor certain classes of software

Trade-off in selecting one style over another

docsity.com

Architectural Design CASE^ 

Static structural model

Use CASE, UML

Dynamic process model

Sequence diagram

DFD

docsity.com

Architecture Style^ 

Component (vocabulary)



Service provider or requester



Client, server, filer, layer, database



Connectors



Interaction among components



Procedure call, event broadcast, pipe



Constraints



Combination of components and connectors

docsity.com

Software Architecture DesignMethods^ 

Structured-oriented Design

Object-oriented Design

Component-oriented Design

Service-oriented Design

Aspect-oriented Design

docsity.com

Software Architecture^ 

Software architecture is the structure of asoftware system consisting of softwarecomponents, connection betweencomponents, attributes or properties



A software component is a software entitywith a well defined interface. It can be anobject, package, DB, API, or a subsystem



One system requirement may result inmultiple architectures by different architects

docsity.com

Architectural Attributes(Quality Attributes)^ 

Run-time attributes (observable at run-time)



Availability - Dual server, risk of shut down,failures of hardware, software, network.



Security - Firewall, authentication, or algorithm,risk of unsecured



Performance - Turnaround time, throughput, riskof poor performance accuracy, speed, space



Usability & Functionality - Completeness,correctness, compatibility

docsity.com

Architectural Attributes^ 

Implementation attributes (Not observable atrun-time)



Maintenance - Evolution, change, risk ofunchangeable expandability



Testability - Quality assurance, risk of bugs, faults



Portability - OS independent, risk of tightdependency



Scalability - Adaptive to volume, risk of neck bottle



Interoperability - Universal accessibility, risk oftight dependency of infrastructure

Contd.

docsity.com

Architectural Attributes^ 

Trade off between attributes



Choose right architecture to reduce the risks



Impact of architecture on quality attributes



Trade off between space vs. time



Trade off between dependability andperformance



Trade off between liability and performance



Required quality attributes are identified inrequirement process.

Contd.

docsity.com

Architecture Design Processing^ 

Analyze requirement - domain



Create business–use - case



Select architecture style (component, link )



Communicating architecture tostakeholders (prototypes)



Evaluate architecture



Implementation architecture - detail design

docsity.com