Tuesday, January 26, 2010

Enterprise Architecture - Entity Relationship Diagram


Introduction:

With many sorts of EA tools and Meta Models surfacing and claiming to offered the best method of doing EA. Currently there are probably three very big questions that many Enterprises will ask when they get their EA tool or select a reference or meta model for their enterprise:

  1. What information should we be recording?
  2. What are the relationships between what we record?
  3. What is the best method of recording this and managing this information?

The first part of this project is discovering what information we should be recording and how the information is related.

The Above Diagram:

The diagram has been initially constructed using what has been discovered in Zachman and FIAF as EA information components. The information components have been deconstructed and related in the following way to give the viewer an idea of what they should be recording when they are carrying out EA.

The most important part of this project is to obtain a meta model that will map directly to an ERD where a database could possibly be built.

The Project Objectives:

  1. To identify all informational component of EA and create a dictionary for a common understanding of these components
  2. To bring together all of the informational components of EA and identify the relationships between them.
  3. To create a meta model that will map the informational component directly to an ERD where a database could possibly be built.
  4. To maintain the ability to view the information from any point of view i.e. Zachman , FIAF etc:

I would like to thank the following contributors:

Please feel free to email me any information and state how it may be used to: maclarkson@hotmail.com

3 comments:

  1. Go for IBM System Architect, which is the best suite for EA implementation

    ReplyDelete
  2. I would check some other EA software and research the capabilities of the tool and map functionality to what you are trying to achieve. System Architect may not meet your needs. Other tools such as ARIS, MEGA,CaseWise, Enterprise Elements and ProVision should at least be looked at to ensure you are getting the best bang for your buck and it has the capabilities you need to achieve your goals.

    ReplyDelete
  3. None of those tools will allow you to easily input your own meta-model. ABACUS (www.avolution.eu) is the only one that is built on top of a completely flexible repository that allows you to have any entities, relationships, attributes, viewpoints you like.

    ReplyDelete