Transitional architectures for enterprise evolution

Most IT architecture projects start with long, expensive effort to define the current state followed by the production of an abundant set of future-state blueprints. This paper introduced the idea of change within the architecture process. By following this approach, you will quickly learn which areas you need to focus on before moving forward with the architecture models and blueprints. The method also yields several important benefits, including a focus on delivering architecture features that matter most to the business; effective mitigation, expectation management, and requirements traceability; and lower costs