Reference no: EM133167707
Describe the mutual dependent relationship between a single EA repository and EA documentation tools. What challenges would an organization face if they chose to :
- Use neither
- Use only an EA repository....single or multiple
- Use only documentation tools but not a unique single EA repository
A mature EA practice would have both a robust EA repository and various EA documentation tools that complement the process. The EA repository is a database or document management system that manages all the copious amounts of documentation created to support current and future state architectures relating to goals and initiatives, products and services, data and information, systems and applications, networks and infrastructure and also security systems. EA documentation tools provide an easier and more robust way to document things like knowledge warehouses, reference architecture, asset inventories, security monitoring tools, system design tools, data analysis tools, business workflow tools, strategic planning tools, project tracking, business plans, and balanced scorecards.
If an organization decided to not use either an EA repository or EA documentation tools, it would be possible, but it would also be a bear to manage. The EA would need to have very tight controls over the documentation developed or risk the possibility of losing the documentation. If the EA were to set up a shared drive to allow for collaboration, the risk of someone changing a document or moving it to an unknown location grows. Everyone has a different way of organizing their files. On my small team of 5 we struggle to keep our shared space clean. Without tools to help with the documentation means there wouldn't be a set standard template. If a template was standardized, it would be difficult to enforce. I believe the documentation would have only limited searchability and an organized structure would not be sustainable.