While enterprise information technology architecture (EITA) has been used successfully to improve operational efficiencies in many organizations, few have been successful with leveraging EITA as a strategic value-creation tool. We contend that one reason for this is that in many instances, EITA lacks the business relevance and context necessary to align IT direction with business strategy in other than an incidental fashion. Enterprise business architecture (EBA) holds promise as a source of requirements for EITA.
A Requirements Approach to Enterprise Technology Architecture
Posted November 30, 2008 | Technology |
About The Author
Dan Berglove is a Cutter Expert and has more than 20 years’ IT leadership and consulting experience, including 15 years’ experience with implementing strategic technology architecture in the insurance, banking, database marketing, mortgage, and medical industries. Mr. Berglove began his career in application development and has managed and directed development organizations consisting of up to 100 people. He has led enterprise-scale application… Read More
Jeroen van Tyn has served as enterprise IT architect, business architect, business analyst, project manager, team lead, developer, consultant and mentor on a wide variety of enterprise architecture, software development and business analysis projects for global corporations. He has led and mentored teams in industries ranging from finance, insurance and health care to manufacturing and telecommunications. Mr. van Tyn has delivered formal… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.