In a previous article, the spotlight fell on three biggest risks the Chief Architect needs to manage before moving onto something less tactical. Consider now the area of strategic planning and opportunities in your future state landscape. Three key sources that the chief architect needs to explore are:
It’s been far too long but I’m writing again – you see I’ve been writing a lot since I last wrote and so there are lots of pieces that should be appearing here soon – I’ll just have to figure out where to start. I’ve been doing a lot Read the rest…
Enterprise Architecture – Benefits
- Environmental Factors
- Large applications are complex and incorporate other applications & components.
- Need for standard interfaces and products
- We continually need to accommodate change, and a review of our infrastructure each time we need to make a change is cost and time prohibitive
- System design modifications & upgrades now are needed on weekly or monthly schedules
- We are finally building applications that we expect to change, and need to have a solid, well thought out foundation on which to build them
Expected Benefits
- Improved alignment of IT solutions with business strategy
- Greater ability to set realistic IT goals
- Enhanced enterprise information sharing
- Reduced software and data redundancy
- Reduced information systems complexity
- Greater reliability at implementations & updates
- Reduced dependency on key resources
- Improved accuracy in scheduling software development / implementation
- More accurate forecasting of development and support costs
- More efficient deployment of technology solutions
- Increased traceability
Tangible Benefits
- Promote better planning and decision making
- Improve communication through standardized vocabulary
- Views communicate complexity and facilitate management
- Enable strategic use of emerging technologies