Mohammad Hossein Danesh
University of Toronto
Who am I ?
Education
PhD Student, Software Engineering
Enabling Decision Making Among Architectural Alterna
tives
Masters in E-Business
Expertise
Enterprise Application Integration
SOA Architect
IBM WebSphere, WSO2, .Net Biztalk
What I am Going to Talk About
1.
2.
3.
4.
5.
6.
7.
Why is Software Architecture Important
How to Choose Among Design Patterns
Enterprise Systems
System of Systems
Orchestration vs Choreography
Service Oriented Architecture
Challenges
1
Software Architecture
specification should answer
What is the Nature of the elements
Why are they Separated
What are they Responsible for
What is the significance of the Connections?
What is the significance of the Layout?
Software Architecture
Is high level design of the Overall System
Accounts for early design decisions
Constrains future implementation choices
Inhibits or enables Quality Attributes
Performance
Modifiability
Scalability
Reusability
…
2
Scanario
Base
Analysis
System Priority
Risk of Achievement
8
(Kazman et al., 2006, 2005)
3
Definitions
Business Process
a specific ordering of work activities across time and place,
with a beginning, an end, and clearly identified inputs and o
utputs
Information System
A configuration of IT resources and organizational processes
whereby the IT resources (and the information they provide)
are applied to support organizational processes
processes
INFORMATION
SYSTEMS
IT resources
Typical Architecture of
Enterprise Systems
Prentice Hall
Evolution of Enterprise System
Requirements
Enterprise Systems
Traditional View of Systems
Prentice Hall
4
Definition & Applications
Arrangement of Independent & Useful System
Deliver Unique Capabilities
Collaborative Integration (Choreography)
Examples of Software Engineering approaches in
Enterprise Offices
Telemedicine
E-Business
Automotive &Avionic
(Nakagawa et al - 2013)
Characteristics of
Systems of Systems
1. Operational Independence
2. Managerial Independence
3. Evolutionary Development
4. Emergent Behavior
5. Geographically Distributed
(Nakagawa et al - 2013)
5
Centralized Management
Decomposition in Implementation
Centralized Decision Making
Collaborative Management
Autonomous in Implementation
Collaborative Decision Making
6
SOA Conceptual Model
SOA Reference Architecture
(Arsanjani et al - 2007)
How did SOA Evolve
Service
Interface
Service
Interface
App
App
App
App
Service
Interface
Service
Interface
Service
Interface
Service
Interface
Service
Interface
Service
Interface
Service
Interface
Service
Interface
App
App
App
App
Service
Interface
Service
Interface
SOA Infrastructure
Service
Interface
Service
Interface
Service
Interface
Service
Interface
Components of a SOA Solution
Service Desk
Unified Management
BAM
Business rules
Business Rule Engine
Process Manager
ESB
CEP
BPEL Process Manager
Interaction
SOA infrastructure
UDDI
SOA Characteristics
Interoperability
Service Loose Coupling
Service Abstraction
Service Reusability
Service Autonomy
Standardize Service Contract
7
Challenges
What is the right level of Service Granularity?
Is there a solution that Fits all Organizations?
Can a chosen solution address new Requirements?
Does everyone want/interpret the same Quality attributes?
Architectural Governance is Dependent on
Enterprise Specific Requirements
Scale Current Approaches
Shorter Cycles
of Development
Prioritization ????
Agile
Customization/
Development
Connectivity &
Interoperability
in APIs
On-Demand Change
in BP Config
Standard Data
Type &
Interfaces
Loose Schema
Definition &
Binding
Flexibility in Data
Type Definition
Cause &
Effects


Depict Cause & Effects of Dependencies
Depict Cause & Effects of NFRs



Requirement
Models 

Tool Support
Traceability & Reasoning
Qualitative
Quantitative


Describe Alternatives
Perform Boundary
Reconfiguration
Refine Adaptability NFR
Present Architectural Styles
Depict Adaptability Behavior



Require Refinement of Adaptability
Require Domain Metrics
Analyze Evolution & Scalability for Future
Impact
Analysis



10
2
47
0
9
29
0
2
14
0
2
0
22
1
11
12
0
27
30
0
65
66
31
2
16
6
15
1
16
13
5
32
0
2
2
16
0
23
1
4
143
4
1
5
3
21
16
33
24
0
1
34
28
7
13
48
3
13
25
49
Strategy Executive
Technology Transformation
Competitive Potential
Service Level
Suppressing Value Relation
13
DFi
50
ID
ID
Alternate 1
10
46
10
10
10
20
41
45
43
42
Alternate 2
Value Exchange ID
Enhancing Value Relation
Perform Change Impact Analysis

Qualitative
Quantitative
Basis for Quantitative Evaluation


Use to Define Dependency Metrics
Use Grouping of nodes to define Acto
Metrics