| Sl.
No |
Title |
Duration
|
| 1.
|
Enterprise
IT Architecture & how to apply
(Rational 4+1 & Zachman Framework)
|
|
|
|
Goals of IT
Architecture |
|
|
|
How do EA fits into the context of multiple disciplines? |
|
|
|
What’s the Technology Landscape for an Architect? |
|
|
|
Architecture Framework and uses |
|
|
|
Architecture
Frameworks and Related Standards |
|
|
|
Rational Unified
Process (RUP) |
|
|
|
Architecture
views in RUP |
|
|
|
Rational 4+1
View Model |
|
|
|
4+1 Views
and UML diagrams |
|
|
|
What is Zachman
Framework? |
|
|
|
Zachman Framework
.Row 1, Row 2, Row 3, Row 4, Row 5, Row 6 |
|
|
|
Applications
of the Zachman Framework |
|
|
|
How to use
Zachman Framework? |
|
|
|
Mapping UML
diagrams to Zachman Framework |
|
|
|
Mapping RUP
Artifacts to Zachman Framework |
|
|
|
Overview of TOGAF &
TOGAF ADM |
|
|
|
FEA Reference Models |
|
|
|
Maping FEA Reference Models to Zachman Framework |
|
|
|
Comparing EA Frameworks |
|
| |
Quiz |
|
|
2. |
Architecture
Reference Model, RM-ODP |
|
|
|
Introduction
to RM-ODP |
|
| |
|
ODP Standardization-
Fundamental Elements |
|
| |
|
Representative
Use of RM-ODP |
|
| |
|
Goals of ODP |
|
|
|
Zachman Framework
vs RM-ODP |
|
|
|
Elements of
RM-ODP Architecture (Terminology, Viewpoints,
Infrastructure Models, Conformance) |
|
|
|
Relationship
across the viewpoints (Enterprise,
Information, Computational, Engineering and
Technology) |
|
|
|
RM-ODP Framework
to aid Standardization |
|
|
|
RM-ODP and
EDOC |
|
|
|
RM-ODP Architecture
Lifecycle |
|
|
|
Extending
RM-ODP model as a specification exchange services |
|
|
|
Why Reference
Architecture? |
|
|
|
Developing
Reference Architecture with RM-ODP |
|
|
|
Mapping Zachman
Framework to RM-ODP viewpoints |
|
|
|
Relationship
between UML diagrams and RM-ODP viewpoints |
|
|
|
Exercise |
|
| 3(a).
|
Architecture
Software Notations, Representations
and Specification |
|
|
|
OMG Metamodel Architecture |
|
|
|
UML Profiles and related standards |
|
|
|
OMG UML 2.0 specification |
|
|
|
UML Language Structure |
|
|
|
UML2.0 Diagrams Types |
|
|
|
Composite Structure Diagram |
|
|
|
UML 2.0 Ports |
|
|
|
UML 2.0 Component diagram |
|
|
|
Interaction Overview Diagram |
|
|
|
Action Semantics |
|
|
|
Representation and Specification |
|
| |
|
Overview |
|
| |
|
Specification |
|
| |
|
Representation |
|
| |
|
RM-ODP Architecture Specification Concepts |
|
| |
|
Components and Composition
|
|
| |
|
Some Behavioral Specification Techniques |
|
| |
|
Interaction and Interception Framework |
|
| |
|
Areas of mismatch to watch out |
|
| |
|
Minimizing mismatch through behavioral
Specification |
|
| |
|
Relationship between Specification and
Representation |
|
| |
|
Example of QoS Characteristics and related
QoS Parameters |
|
| |
BPMN for Business work flows & process
definition |
|
| |
UML vs BPMN |
|
| |
Quiz |
|
| 3(b).
|
Architecture Development
Process and Intelligence Gathering
Techniques |
|
 |
Solving Software Problems |
|
|
Architecture Process (System life-cycle
vs. Project life-cycle) |
|
|
Architecture Activities and Associated
Roles
|
|
|
Architecture and multiple versions
|
|
|
Planning Benefits |
|
|
Intelligence Operations |
|
|
Intelligence Gathering Techniques |
|
|
|
|
Architecture Mining Process |
|
|
|
|
Design Elements |
|
|
|
|
Architecture Judgement |
|
|
|
|
The
Macro and Micro Process |
|
|
|
|
Strategies to be used with Architecture
Iteration |
|
|
|
Working with Use Cases |
|
|
|
Life-Cycle Phases in RUP |
|
|
|
Example - Architecture Centered Development
Process with RUP |
|
|
|
Example – Architecture Centered Development
Process with RM-ODP |
|
|
|
Example – Architecture Centered Development
Process with Zachman |
|
|
|
Example - TOGAF Architecture Methodology |
|
|
|
UML (Metamodel) QoS Elements |
|
|
|
QoS Characteristics and Parameters |
|
|
|
Identifying components, ports & assembly |
|
|
|
Managing Non-Functional/Operational requirements
across multiple versions |
|
|
|
Strategies to support modifiability |
|
| |
Case
Study |
|
| |
Examples and Exercises |
|
| 4.
|
Realizing
Product line Architecture with Application
by Assembly of Components |
|
|
|
What is component assembly ? |
|
|
|
Defining component assembly, ports etc. |
|
|
|
Component
instance creation, connections, configuration
for assembly |
|
|
|
Behavioral semantics of interaction |
|
|
|
Defining host and process collocation
|
|
|
|
Define cardinality |
|
|
|
Maintenance of system by substitution
of parts |
|
|
|
Reuse strategy |
|
|
|
OMG Reusable Asset Specification (RAS) |
|
|
|
Elements of cost-effective software manufacturing |
|
|
|
Developing product lines by reusing domain
components |
|
|
|
Examples & Exercises |
|
| |
|
|
|
| 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
