Click here to know various questions associated with EA tools implementations and ways to speed it up to get better results.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Most EA managers recommend first working out if the tool will accommodate your EA meta model (the definition and relationships of all the terms EA uses in their model that describes the design of the company’s operations), before being distracted by different features and functionality.
In most cases, and supported by most EA tools, an Excel import is available and very effective for this purpose. However it does assume that for your core architecture components you have the data available. Things like an excel document with your applications, business functions, relationships between components etc. Getting the data into the tool is usually not the problem, collecting the data, cleaning it etc. takes the most time.
The range of questions an EA tool could answer is huge, it all depends on your priorities and meta-model scope. Having a clear definition of which questions you expect an EA tool to answer is a great accelerator.
There might be some overlap with existing tools. It is important to properly position the EA tool for its intended purpose and how it will align with other tools. A prime example of this is a project & portfolio management tool.
The EA tool will only be useful if the data inside the repository is up-to-date and can be trusted. So having a clear understanding of who is maintaining the data is critical. Many EA initiatives die a slow death when after an initial implementation the data is not kept up-to-date.
Last but not least is around tool adoption and having a clear approach to who will be using the EA tool (besides the obvious enterprise architects who else). That wider adoption approach should be done before deploying / implementing the tool. It is also related to all of the above. By defining the complete user base you essentially are setting scope for all of the above items as well.
We hope this presentation will help you a lot to understand various factors that should be considered to speed up EA Tools Implementation.
For More Information visit our website
422 Richards St, Suite 170
Vancouver, BC V6B 2Z4
Email: [email protected]