An Introduction to Enterprise Architecture: Third Edition by Scott A. Bernard

Author:Scott A. Bernard [Bernard, Scott A.]
Language: eng
Format: mobi
ISBN: 9781477258019
Publisher: AuthorHouse
Published: 2012-08-12T16:00:00+00:00

EA Components:

• Knowledge Warehouses

• Information Systems

• Databases

EA Artifacts:

• Knowledge Management Plan (D-1)

• Information Exchange Matrix (D-2)

• Object State-Transition Diagram (D-3)

• Object Event Sequence Diagram (D-4)

• Logical Data Model (D-5)

• Physical Data Model (D-6)

• Activity/Entity (CRUD) Matrix (D-7)

• Data Dictionary/Object Library (D-8)

Documenting information flows involves the development of data models that show the structure and flow of data in the enterprise’s business services and supporting IT systems/services. Data can be modeled and analyzed using “traditional” and/or “object-oriented” methods, depending on how the resulting documentation is intended to be used. For example, if the intended use is with relational databases and/or third-generation procedural programming languages (i.e., C, FORTRAN, or COBOL) then the use of traditional methods (i.e., Entity-Relationship Diagrams and Data Flow Diagrams) is called for. If the intended use of data is with object-oriented databases, fourth generation object-oriented (OO) programming languages and associated object-oriented diagrams that use the Universal Modeling Language (UML) are called for (e.g.., Java, C++, ADA, and Smalltalk). This OO approach also uses what is called the Common Object Reuse Brokered Architecture (CORBA).

Data Structure and Data Flow Diagrams

Modeling Information Structure. The “traditional” approach to information systems development is based on the modeling technique called Entity Relationship Diagramming (ERD). ERDs are used by IT systems analysts and programmers to identify the “things” (data entities) that an enterprise wants IT systems to capture, as well at those external entities that a system interfaces with. ERDs also provide data entity descriptions, attributes, relationships, and the rules for the frequency of those relationships. In that enterprise architecture seeks to provide an enterprise-wide view of all IT resources, it is important that ERDs show not only what is in each system, but also how systems interface with each other. ERDs are not decomposed per se, but they can serve to show several systems, or parts of large complex systems. Figure 7-5 on the next page shows an example of an ERD diagram for a hypothetical real estate tracking system.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.