I. Charter Purpose

This document is intended to describe the work and charter for the data and information team.  Below is a description of the various artifacts to be produced in order to provide a comprehensive detailed view of the data and information architecture for Danforth Manufacturing Company (DMC).

II. EA3 Data and Information Artifacts

The artifacts described in this section are based Enterprise Architecture “Cube”, or EA3, framework developed by Dr. Scott A. Bernard.  More in-depth definition and detail are published in Dr. Bernard’s textbook An Introduction to Enterprise Architecture – 2^nd Edition, published in 2005.  The readers and stakeholders are encouraged to use the book as a resource to improve their understanding of these artifacts.  

D-1: Knowledge Management Plan

This artifact will be a diagram showing how data and information sharing support and provide value to the business. The value of this artifact is to provide a detailed view of how the organization shares knowledge, information, and data across the enterprise. 

D-2: Information Exchange Matrix

The Information Exchange Matrix describes the attributes of data exchanged between systems, including size, physical specifications for the storage media, timeliness of the data and data retention policy, as well as security classifications and other attributes.  As an alternative, these attributes may be included in artifact D-1 and eliminate the need for a separate Information Exchange Matrix.

D-3: Object State Transition Diagram

The Object State Transition Diagram will use UML methodologies to show the lifecycle of various data objects.  Further, this diagram will show entry points, as well as changes and transitions of data elements and attributes resulting from system events or triggers. 

D-4: Object Event Trace Diagram

The Object Event Trace Diagram traces actions and sequencing of events thru a set of operational scenarios.  This artifact will only be produced if business rules define the scenarios and requirements for this diagram.

D-5:  Logical Data Model

The Logical Data Model will use UML methodology to produce a class diagram showing the static relationships of the data objects and the logical flow of the data.  UML is chosen for consistency in modeling the data and information artifacts. 

D-6:  Physical Data Model

The Physical Data Model will show the database repository standards (DB2, ORACLE, SQLServer), file structures, interface standards and messaging format, and physical schema mapping the logical data model to the physical data model. 

D-7:  Activity / Entity Matrix

The Activity /  Entity Matrix identifies the types of data transformations (Create, Read, Update, Delete) that can be performed based on business activities and rules. This artifact is produced to map business function to access rules.

D-8:  Data Dictionary

The Data Dictionary defines all of the data entities produced and maintained by the organization, including data descriptions and relationships, attributes, standards, and keys.   One of the primary purposes of the data dictionary is to document what types are data are available for use or sharing by other systems and applications. 

III. 2008 Next Steps

The team will work to existing architecture artifacts for the current state and build on those to produce the future state for Danforth Manufacturing Company. 

The Data and Information team will be scheduling meetings with the Products and Services team to understand the business requirements and Systems and Applications team to ensure integration with new applications.  Further, there will be meetings with the Security team to ensure compliance with security policy and standards.  Meetings may be required with the Network and Infrastructure team to work availability requirements and latency issues.