|
Rakesh
Radhakrishnan is a Lead IT Architect in the Communications
Market Area of Sun Client Solutions. He has covered Telecom
Companies, Network Equipment Providers (NEP) and Service Provider
accounts in Europe, Canada, USA and Latin America.
He has over
15 years of experience and has an MBA (MIS) and MS (MIT).
He is an active member of Customer Engineering Technology
Council (CETC) and was the Chairman of a Working Group on
Container Alignment Engine (CAE patent received from Europe
and US) at Sun. He has published more that 15 papers on IT
Architectures (Frameworks, Process and Techniques) and
is a frequent speaker in conferences including OMG, TOG,
CMG, IRM, SuperG, SunNetwork, Java ONE, etc. He has led multiple
Architecture Workshops and Architecture Assessments for
IT Consolidation and Network Identity projects. He was recently
featured on Officer
Outlook for
his work on Aligning Architectural Approaches (Sun's WS-Incite
Award for 2005).
Rakesh is also Certified by
TOG (on TOGAF 8), SEI (as a SW Architect) and OGC (Prince
2 and ITIL). He has Green Belt Six Sigma training and is
a ECCSE (Enterprise Computing Certified Systems Engineer
-Competency 2000) and as a Systems Architect Pro (from Peoplesoft).
|
|
|
|
Presentation
Aligning ADM with ADDM
PDF document: SYNERGIZING
METHDOLOGIES TO ACHIEVE ARCHITECTURE TARGETS
(Includes TOOLS & TECHNIQUES)
The Architecture Development Methodology (ADM) as an Enterprise Architecture
Methodology from The Open Group (TOG) already refers to the Architecture Trade-off
Analysis Method (ATAM) and the Capability Maturity Model (CMM/I) from the Software
Engineering Institute (SEI), at the appropriate stages (Phase 3 of ADM and
as reference for Architecture Maturity Models).
This presentation will highlight the alignment that exists
between the Attribute-Driven Design Method (ADDM) from SEI
as a Information System Design Method (Effective implementation
of both Data and Application Architecture) and the respective
Architecture Creation Phase in the ADM.
The ADDM is based on knowing both the functional and quality
requirements for your systems and knowing the architectural
approaches and architectural patterns that have proven successful
in achieving those qualities in other systems. It is a iterative
process and also included the ATAM. It can include Enterprise
level standards, constraints and guidance as key inputs in
the initial stages, including artifacts from an EA effort
based on TOGAF, stemming from the SIB (standards information
base), TRM (technical reference model), the IIIRM (integrated
information infrastructure reference model) and any ABB (Architectural
Building Blocks), such as a Standard Enterprise Identity
System and its API that can be leveraged across a family
of systems.
return
to program
|
|
|