Why You Need Enterprise Architecture Softwareposted by John Spacey, April 06, 2011
Enterprise architecture (EA) software has come a long way in recent years. Today there is one fundamental reason that every EA department needs a tool:
EA artifacts quickly become stale shelfware — a tool allows customized, targeted EA artifacts to be generated on the fly.
Have a meeting with the head of sales? — generate a one page dashboard of the health, gaps, projects and strategy for her systems.
This ability to generate timely and targeted presentations — helps to make EA relevant and productive.
The ProcessModel your EA in the tool and then artifacts can be generated on the fly.
Tools often support multiple methodologies with TOGAF being the most pervasive.
ExamplesEA software can generate EA artifacts and reports by location, business unit, process, data entity etc... This allows the enterprise architect to quickly answer questions such as:
What does the sales department's technology stack look like?
What processes are supported by Siebel CRM?
What are the gaps in the quote to cash process?
Which systems will be unable to keep up with projected business volume?
Which business units are in compliance with technology governance?
Are there business units licensing the same products (opportunities for global licensing)?
Where is customer data being rekeyed?
Where are there opportunities to cut costs by retiring legacy systems?
What departments are using common tools such as our ESB and which departments are doing their own thing?
As you can imagine — the ability to answer such questions makes the EA team popular with decision makers throughout the business.
Imagine your hardcore IT geek talking to a company executive. What would they talk about? |
Understand the threats to your organization.|
CxO level executives are demanding metrics for EA — can you deliver? |
Explaining complex business and technical concepts in layman's terms.|