| 5.
|
Deployment
Architecture for enabling QoS |
|
|
|
Deployment Principle |
|
|
|
QoS Characterisitcs and parameters |
|
|
|
Component Deployment Process |
|
|
|
Key concerns at deployment |
|
|
|
Deployment concerns of Real Time Systems |
|
|
|
Deployment
View – N tier Architectural Style |
|
|
|
Deployment
of Assembly (Application) |
|
|
|
Deployment
Descriptors General Structure |
|
|
|
The
Component Deployment Process |
|
|
|
Strategies
for high Performance |
|
|
|
Fault
Tolerance Architecture Overview |
|
|
|
Overview
- Load Balancing Services |
|
|
|
Mapping
QoS need in an architectural development
stages |
|
|
|
How
to ensure performance management, scalability
and availability |
|
|
|
Deployment
architecture using distributed clustering,
fail-over, load-balancing |
|
|
|
CBAM
= Cost Benefit Analysis Model |
|
| |
Examples & Exercises |
|
| 6. |
Enterprise MDA |
|
|
|
Modeling Maturity Levels & Use of
UML Models |
|
|
|
UML as a Foundation for MDA Implementations |
|
|
|
Overview - Model Driven Architecture |
|
|
|
Key standards for defining Architecture
(UML, MOF, CWM, XMI, IDL) |
|
|
|
Platform Independent Model (PIM) &
Platform Specific Model (PSM) |
|
|
|
Developing in MDA - Single Target Platform
& Multiple Target Platform |
|
|
|
Levels of MDA Models |
|
|
|
Use MDA for developing architecture models,
model-to-model transformation and model-to-code
generation |
|
|
|
Relationship between RM-ODP and MDA |
|
|
|
Relationship between Zachman Framework
and MDA |
|
|
|
Developing in MDA - Single Target Platform
(STP) |
|
|
|
Developing in the MDA - Multiple Target
Platforms |
|
|
|
MDA with UML patterns |
|
|
|
MDA centric software development life
cycle |
|
|
|
Model Driven Integration |
|
| |
Exercise |
|
| |
|
|
|
7.
|
Achieving
EAI with Service-Oriented Architecture
(SOA) |
|
 |
Integration
Architecture |
|
| |
|
Aspects in Integration
Architecture |
|
| |
|
Straight through Processing(STP) |
|
| |
|
Zero Latency Management |
|
|
Middleware
Infrastructure |
|
| |
|
Integration Brokers |
|
| |
|
Application Servers / Component Servers |
|
|
Integration
Issues |
|
|
Migrating
a legacy application to component/service
architecture |
|
|
Componentize
the enterprise architecture towards
the service assembly line: |
|
|
Need for
Enterprise Service Bus (ESB) |
|
|
Enterprise
Application – integration levels |
|
|
|
How does components and Web Services
fit together? |
|
|
|
Developing web services with components(CORBA/CCM,
EJB/J2EE, .NET) |
|
|
|
Web Services Software Development Lifecycle
|
|
|
|
BPEL for Web Services |
|
|
|
Modeling BPEL (Web Services) with UML |
|
|
|
EAI Stack vs Web Services Stack |
|
|
|
Web Services Security Issues |
|
|
How to
ensure maintainability, reusability
and performance management of integrated
systems |
|
|
Integration
strategy for integrating 2 systems vs
several systems |
|
|
Performance
Comparison of IIOP based integration
vs with SOAP based integration |
|
|
Wrapping
legacy apps as component and exposing
as a web services |
|
|
COTS Integration
checklist |
|
|
.NET /CCM/J2EE
Inter-working |
|
|
Integration
Governance |
|
| |
Example
& Exercises |
|
| 8. |
Architecture
Assessment, Governance & Metrics
|
|
|
|
Assessment Overview |
|
|
|
Architecture Tradeoff
Analysis MethodSM
(ATAM) - Steps
|
|
|
|
Conceptual Flow of ATAM |
|
|
|
Architecture characteristics
(Utility Tree) |
|
|
|
Business Service Analysis
Process |
|
|
|
Manageability and Serviceability
Assessment |
|
|
|
Identify communication
tier-architectures. |
|
|
|
Security, Performance,
Scalability & Availability Assessment
|
|
|
|
Delivering the Assessment
(template, documentation approach) |
|
|
|
EA Management Guidance |
|
|
|
EA based IT performance
metrics |
|
|
|
EA for Operational Decision
Making
|
|
|
|
EA for Capital Investment
Process |
|
|
|
IT Strategic Management
(ITSM) Framework –
|
|
|
|
Understanding the EA program
road map and implementation plan |
|
|
|
Value Measuring Methodoly
(VMM)
|
|
|
|
Mock Session |
|
| 9. |
Architecture Team, EA Maturity Model
- sugessions and lessions learned |
|
|
|
Organization structure
((Product vs Services companies) |
|
|
|
Enterprise Architects
Team |
|
|
|
Chief Enterprise Architect |
|
|
|
Solutions Architects Team |
|
|
|
Chief Solutions Architect |
|
|
|
Architecture teams and
its relationship with other teams |
|
|
|
Where the architecture
team is supposed to report to… |
|
|
|
Responsibilities –
Architect vs Managers |
|
|
|
Skill areas and roles
defined in TOGAF |
|
|
|
Enterprise Architecture
Skills & Methods |
|
|
|
Architect
Competency framework |
|
|
|
Seven
habits of highly successful Architects |
|
|
|
Technology Architecture
Management |
|
|
|
Enterprise Architecture
- Maturity Framework |
|
|
|
Critical Success Attributes
& Core Elements |
|
|
|
Business Value of Enhancing
EA Maturity |
|
|
|
Tool for Assessing EA
Management Maturity
|
|
|
|
SEI Process Categories |
|
|
|
The process and role of
Architecture in a SEI-CMM enterprise |
|
|
|
Suggestions & lessons
learned |
|
| |
| Case
studies to be discussed during the workshop
|
|
1
|
How to
apply Zachman & RM-ODP frameworks
and how to use them in your
enterprise
|
|
2
|
Applying
RUP/UML Models with Zachman
and RM-ODP
|
|
3
|
Component
Modeling with UML2.0 for Business
domains
|
|
4
|
Product
Line Architecture, COTS selection
and component assembly
|
|
5
|
Use MDA
for developing architecture
models, model-to-model transformation
and model-to-code generation.
|
|
6
|
Deployment
architecture using distributed
clustering, fail-over, load-balancing
for large-scale business
applications
|
|
7
|
Legacy
transformation and defining
product vision and rationalization
|
|
8
|
Web Services
Software Development Lifecycle
and BPEL
|
|
9
|
.NET,
J2EE, CCM based application
and interworking among them
|
|
10
|
The process
and role of Architecture in
a SEI-CMM enterprise and strategy
to introduce architecture
team
|
|
Request A Call Back
