What is data architecture & database design? What is the Zachman Framework?

Protect your enterprise's most valuable asset. Data.

Business processes exist to manage this asset. Most designers focus on processes, creating a fragmented, redundant architecture. But a data-centric will create a highly integrated, streamlined architecture. Return to Christo van Rensburg's Homepage. Data Architecture Data Architecture (sometimes called "Information Architecture")is a sub-function of Enterprise Architecture. Data Architecture is made up of the structure of all corporate data and its relationships to itself and external systems. (The higher level role of Data Steward is sometimes referred to as Data Administrator). The conceptual data model(s) is one of the deliverables from the data architecture level. The goal is data analysis, to classify the enterprise's data, not to design a database. The typical duties of the Data Architect include: Understanding and evaluating business requirements and translating those into specific database solutions Creating data design models, database architecture and data repository designs Working with the systems and database administration staff to implement, coordinate and maintain enterprise-wide data architecture Providing leadership in establishing and documenting data standards Creating and testing database prototypes Creating enterprise data models and conceptual data models, and documenting meta-data In addition, the Data Architect is often involved with developing data governance, stewardship, management and administration programs and in implementing policies, procedures, standards and best practices, plus data-quality improvement programs (amongst others). The Data Architect's responsibilities often include Data Modelling as well. Database design is a lower level activity. Logical data modeling produces the logical data model - a much more precise and detailed artifact than the conceptual data model. During the database build activity, the physical data model is produced. The logical data model is now adapted to suit the Vendor Relational Database System the applications system is to be implemented on. The typical duties of the Data Modeller include: Analysing organisational data requirements and creating logical data models and physical data models, and often dimensional models and data flow models as well Interviewing key project stakeholders, documenting findings and making detailed recommendations Working with database administrators and reporting teams to ensure the availability of standard and ad hoc data reporting in a production environment Addressing data-quality issues with clients and management Zachman Framework John Zachman is seen as the father of Enterprise Architecture. The Zachman Framework is a classification schema used to organize an enterprise's artifacts and help facilitate thinking, reasoning, and communicating among the participants in the enterprise. It is an approach to structured technology development. The Zachman Framework is NOT the only Enterprise Architecture Framework. I am presenting it as an example here, because it is better known and more often implemented than other frameworks such as TOGAF. The Zachman Framework is widely adopted - and widely adapted. Usually other frameworks such as TOGAF can be related to the Zachman Framework, and often similar activities are conducted and similar artifacts are produced. In the representation below, I have compared the Zachman Framework (in Silver) with the traditional SLDC (Systems Development Life Cycle) (in Gray). The Zachman Framework is organized as a 6×6 matrix - 36 cells in all. In my representation below, I indicated which cells I feel more comfortable operating in at this time. These are the green and the blue cells. I have a slight preference for the green cells over the blue cells, and feel slightly more comfortable with the cells in the darker colours as opposed to the cells in the lighter hues.

Traditional SLDC Equivalent	Zachman Framework	Data (What)	Function (How)	Network (Where)	People (Who)	Time (When)	Motivation (Why)
Strategic Planning	Scope - Planner (Contextual Level) (Ballpark View)	List of entities (things) important to the business Data Steward	List of processes the business performs Business Analyst	List of locations in which the business operates Logistics Analyst, Hardware Analyst, Communication Analyst	List of organizations important to the business Business Analyst	List of events / cycles significant to the business Data Steward, Business Analyst	List of business goals / strategies Data Architect, Software Architect, Technology Architect, Business Analyst
(Transition) Requirements Analysis	Business Model - Owner (Conceptual Level) (Owner's View)	Language, Conceptual data model (Semantic Model) Data Steward, Data Architect	Business process model Business Analyst, Systems Analyst, Software Architect	Business logistics model Technology Architect, Network Architect, Business Analyst	Work flow model, Organization chart Business Analyst, Systems Analyst, Data Architect	Master schedule, State / transition diagram Data Steward, Data Architect, Systems Analyst	Business plan, tactics, policies, rules Data Architect, Software Architect, Technology Architect, Business Analyst
Requirements Analysis	System Model - Designer (Logical Level) (Designer's View)	Logical data model Data Steward, Data Architect, Data Warehouse Architect, Database Designer / Administrator	Application architecture, Data flow diagram Business Analyst, Systems Analyst, Software Architect	Distributed system architecture, Location of roles Technology Architect, Network Architect	Human interface architecture, Use cases Business Analyst, Systems Analyst, Data Architect, Software Architect	Processing structure, Entity life history Data Steward, Data Architect, Systems Analyst	Business rule model Data Architect, Software Architect, Technology Architect, Business Analyst, Systems Analyst
Design	Technology Model - Builder (Physical Level) (Builder's View)	Physical data model Database design Data Steward, Data Architect, Data Warehouse Architect, Database Designer / Administrator	Systems design, Program structures Programmer, Tester, Web Designer	Technology architecture, Hardware, software distribution Network Engineer, Systems Administrator, Network Administrator, Systems Programmer, Middleware Programmer	Presentation architecture, User interface, security design Business Analyst, Systems Analyst, Data Architect, Software Architect, Security Administrator, Web Designer	Control structure Web Designer, Data Steward, Data Architect, Systems Analyst, Software Architect	Business rule design Web Designer, Data Architect, Software Architect, Technology Architect, Business Analyst, Systems Analyst, Programmer Analyst
Construction	Detailed Representation - Subcontractor (Out of Context) (Subcontractor's view)	Physical storage design, Data definitions Database Administrator	Detailed program design Programmer, Tester, Web Master	Network architecture, protocols Network Engineer, Systems Administrator, Network Administrator, Systems Programmer, Middleware Programmer, Tester	Security architecture, Screens Programmer, Security Administrator, Webmaster, Tester	Timing definition Programmer, Webmaster, Tester	Rule specification logic Programmer, Database Administrator, Webmaster, Tester
Production	Functioning System (Actual)	Converted data Database Administrator, Technical Support	Executable programs Configuration Manager, Technical Support	Communication facilities / Network Systems Administrator, Network Administrator, Technical Support	Trained people / Organization Security Administrator, Technical Support	Business events / Schedule Systems Administrator, Technical Support	Enforced rules / Strategy Programmer, Database Administrator, Technical Support