Please enable JavaScript.
Coggle requires JavaScript to display documents.
4 phase/20 steps in EA methodology - Coggle Diagram
4 phase/20 steps in EA methodology
Phase 1: EA PROGRAM ESTABLISHMENT
this phase are designed to ->
Get the EA program initially start.
Identify key players
Communicate the EA implementation plan to the executive sponsors and other stakeholders to gain stakeholder buy-in and support
This pre-documentation activities are important to ensuring that the EA program has clear goals, remain focused, and is accepted throughout the enterprise.
Steps
Establish EA governance and links to other management processes.
Develop an EA communication plan and gain stakeholder buy-in.
Establishing an EA implementation methodology
Establish the EA management
Phase 2: EA FRAMEWORK AND TOOL SELECTION
this phase are serve to select an EA framework that ->
Guide the techniques for the modelling of current view, develop future scenarios and associated modelling
Establish an online repository that will archive all the EA documentation artifact.
Defines the scope of the architecture
Steps
Select an EA framework
Identify the EA lines of business and crosscuts the order of their documentation.
Identify the EA document to be documented.
Select documentation method appropriate for the framework
Select software application/tools to supports automated EA documentation
Select and established an EA online repository for documentation.
Phase 3: DOCUMENTATION OF EA
where the actual documentation of current and future views of the architecture occurs which involves ->
analyzing and documenting the current strategy, business, information, services and infrastructure of the enterprise.
the development of artifacts that reflect changes, identify possible courses of action and resource changes.
concludes with the development of EA management plan to describe how the architecture will transition over time.
Steps
Develop several future business and technology operating scenarios
Identify future planning assumptions for each of future scenarios.
Document current use of existing EA components in all framework area.
Use scenarios, program inputs, and schedules update to drive documentation of future components in all framework areas.
Evaluate existing business and technology documentation for use in the EA.
Develop an EA management plan to sequence planned changes In the EA.
By documenting the future and current views, along with an EA management plan, the EA;
Helps to prioritize resource utilization
Helps to lower the risk of project failures.
Improves planning aglity
Phase 4: EA USE AND MAINTAIN THE EA
<- the activities where
the EA is used throughout the enterprise to support planning and decision-making
regular updates are performed to keep the EA relevant and adding value
Steps
Release yearly updates to the EA management plan.
Maintain the EA repository and modelling capabilities.
Regularly update current/future views of EA components
Use EA information for resource planning/decision-making