|
|
|
|
|
|
|
|
|
|
|
|
|
Capital investment decisions, budgeting effort
and procurement should based on the overall enterprise architecture design
and the priorities in the transition plan. |
|
|
|
|
Projects are initiated, evaluate and selected
based the need identified in the transition plan rather then individual
justification effort. |
|
Holistic project management relies on EA to
allocate the resources. |
|
|
|
|
|
|
Risk management relies on EA for holistic risk
management assessment and mitigation. |
|
Risk management depends on EA to identify the
pattern of risk. |
|
|
|
|
Business architecture in EA is considered as the
holistic requirement management. |
|
System requirement can be derived from the
business architecture. |
|
Enterprise identify the system requirement
pattern from business architecture. |
|
|
|
|
|
|
|
EA establish the common foundation and building
blocks to enable |
|
Application development agility. |
|
Application development simplicity. |
|
Application development cost efficiency. |
|
|
|
|
|
|
|
Service Oriented Architecture do not replace EA. |
|
The challenge of SOA is to provide the right
services based business need. |
|
EA describe the holistic enterprise business
function and enable the selection of the right SOA. |
|
EA describe the holistic business workload and
enable the placement of right services. |
|
|
|
|
|
|
IV & V leverage on EA system catalog to
target systems for validation and verification. |
|
IV &
V leverage on EA workload analysis in stress test. |
|
IV & V leverage on EA to see the whole for
integration test. |
|
|
|
|
Security management depends on EA to determine
what to secure. |
|
Security management depends on EA to determine
the priority of security level. |
|
|
|