Please enable JavaScript.
Coggle requires JavaScript to display documents.
The Implementation Methodology (IMPORTANT CONSIDERATION OF IMPLEMENT EA…
The Implementation Methodology
DEFINITION
EA methodology defines
:star: How the EA will be implemented
:star: How documentation will be developed, archived and used
FOUR PHASE/ TWENTY-STEP METHODOLOGY
PHASE 1: PROGRAM ESTABLISHMENT
Establish EA implementation methodology
Establish EA governance and links to process
Establish EA management program and identify chief architect
Develop EA communication plan
PHASE 2: EA FRAMEWORK AND TOOL SELECTION
Identify order of documentation
Identify EA documents to be documented
Select EA documentation framework
Select appropriate documentation methods
Select software tools
Select established EA repository
PHASE 3: DOCUMENTATION OF EA
Document current use of existing EA
Develop several future business and technology
Evaluate existing business and technology documentation
Identify future planning assumptions
Use scenarios, program inputs, and schedule updates
Develop EA management olan
PHASE 4: USE AND MAINTAIN EA
Update current or regular views of EA component
Maintain EA repository and modelling capabilties
Use EA information for resource or decision making
Release yearly updates for EA management plan
IMPORTANT CONSIDERATION OF IMPLEMENT EA
Approach to EA governance
Types of EA documentation
Scope of EA
EA documentation framework
Methods and techniques for develop EA documentation
How EA will be access and share
How often the EA will be updated
VALUE OF EA METHODOLOGY
:check: Reduce the risk of creating ineffective EA program/ inaccurate EA documentation
:check: Force the enterprise to think
EA AS ANALYSIS AND DESIGN METHOD
Current view of architecture
Future view of architecture
Implementation methodology
EA management plan
EA documentation framework
Threads
