I did a fourth of my presentation in PowerPoint to set the stage with a common set of vocabulary since there are still no clear definitions on all the EA perspectives. So I gave my interpretation. We spent the rest of the session whiteboard what an EA tool would look like if it was built on the Microsoft stack. I took into account the categories that you see above.
Essentially we wrapped 7 - 10 different tools into one architecture!
What are Enterprise Architecture Tools?
Purpose -
A strategic information asset base, which defines the aligned Business and IT mission
Provides information necessary to perform the mission
Contains technologies necessary to perform the mission
Proscribes processes for implementing or augmenting new and existing technologies
Includes -
A baseline architecture
Library of Architecture Patterns and Standards
Defined Future State Architecture
Architecture Technology Life Cycle
EA Tool Product Observations and Gap Analysis
Not one product covers all aspects of EA
Products address “niche” areas of concern
Integration is an issue with this scenario
Framework support is limit
Zachman is supported the majority of the time (of those tools that support a framework)
A big thank you to all that attended and participated in my session!
Comments