Enterprise Architecture and Business-Focused Change Management: Part III

by Sebastian Konkol

When asking a typical IT manager about a single area where an enterprise architecture (EA) effort should be able to prove its value, probably the most expected answer would be "giving support to projects being run." It is not my ambition here to present the whole scope of possibilities in which EA could support running projects but rather to focus on the refactoring needs concept introduced in Part I of this Executive Update series [2]. Recall that Part II presented refactoring needs in the context of an actual case study in which I worked [3]. Here in Part III, I continue with that case and get into more details about how the refactoring needs built on an EA could support and synergize ongoing software development projects.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Enterprise Architecture and Business-Focused Change Management: Part III31 December 2007