EDM - E1 - Data Architecture and Modeling –

Data Modeling Overview

June 26, 2024 TCS Public
EDM – E1 – Data Architecture and Modeling – Training Lecture
Series

• EDM – E1 – Data Architecture and Modeling - Data Architecture

• EDM – E1 – Data Architecture and Modeling - Data Modeling Overview

• EDM – E1 – Data Architecture and Modeling - Normalization

• EDM – E1 – Data Architecture and Modeling – Dimensional Modeling

June 26, 2024 2

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 3

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 4

What is Data Modeling?
• Modeling is an efficient and effective way to represent the organization’s needs;
It provides information in a graphical way to the members of an organization to
understand and communicate the business rules and processes

• Data Modeling refers to structuring and organizing data in order to present

logical and graphical representation of the information needs

• Provide basis for physical implementation: These structures are then typically
implemented in a DataBase Management System

• The process of data Modeling also imposes constraints or limitations on the

data placed within the structure

• The goal of a Data Modeling exercise is to model the “perceived real world” of
the “business”

June 26, 2024 5

Data Model and Modelers
• A Data Model is a conceptual representation of data structures (tables) required
for a database and is very powerful in expressing and communicating the
business requirements.

• A Data Model visually represents the nature of data, business rules governing
the data, and how it will be organized in the database.

• A good data model is

•Built on consistent application of sound technique
•Embodies a business context
•Used to improve the business

• Data Modelers are responsible for designing the data model and they
communicate with functional team to understand the business requirements and
technical teams to implement the database.

June 26, 2024 6

Characteristics of a high-quality Data Model – Ref. 1

• Embodies Business Plans, Policies, and Strategies

• Uses Recognized Set of Rules

• Involves Domain Experts

• Can be transformed into High-quality Design

• Is created in context of other business architecture elements

• Is created in the context of Enterprise Architecture

• Is created in context of Overall Data Quality Lifecycle

• Depends on support infrastructure

• Involves the right stakeholder June 26, 2024 7

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 8

Three Schema Model – Ref. 2

• ANSI/SPARC introduced the three schema model in 1975

• It provides a framework describing the role and purpose of data Modeling

• External schema or user view (a.k.a Conceptual Data Model (CDM))

– Representation of how users view the database

• Conceptual schema (a.k.a. Logical Data Model (LDM))

– A logical view of the database containing a description of all the data and relationships
– Independent of any particular means of storing the data
– One conceptual schema usually contains many different external schemas

• Internal schema (a.k.a. Physical Data Model (PDM))

– A representation of a conceptual schema as physically stored on a particular product
– A conceptual schema can be represented by many different internal schemas

• Henceforth, We will use CDM, LDM, PDM terminology for the 3-schema model

June 26, 2024 9

Data Modeling Development Cycle

Conceptual Data
Modeling

Logical Data
Modeling

Physical Data
Modeling Database
This data model
Creation
includes all major
things that need to be This is the actual
tracked, along with
implementation of a
constraints. Usually,
specified in terms of conceptual model in a
business logical data model. This is a complete DBAs instruct the data
requirements, forms, Usually expressed in model that includes
reports etc. Modeling tool to create
terms of entities, all required tables, SQL code from
attributes, columns, physical data model.
relationships, and relationship, The SQL code is then
keys. database properties, executed on the server
referential integrity to create databases.
constraints for the
physical
implementation. June 26, 2024 10
Development Cycle - Conceptual Data Modeling
• CDM is the first step in constructing a data model in top-down approach
and is a clear and accurate visual representation of the business of an
organization. In many ways, it represents the users view of the business.

• A Conceptual Data Model (CDM) visualizes the users view of the

business and provides high-level information about the subject areas of
an organization.

• CDM discussion starts with main subject area of an organization. It

relies on specs, reports, forms, views, requirements, application demos,
and user interactions to form a conceptual view of business.

June 26, 2024 11

Development Cycle - Logical Data Modeling

• This is the next step of development after the conceptual data model.

• A Logical data model (LDM) is the version of a data model that represents the
business requirements (entire or part) of an organization and is developed before
the physical data model.

• Logical data model includes all required entities, attributes, key groups,
relationships, and functional constraints that represent business information and
define business rules. Lot of clarification on definitions and calculations is
accomplished through out the organization (especially between the data modelers
and business users/analysts) in this phase.

• Once logical data model is completed, it is then forwarded to the business users
for review and verification.

June 26, 2024 12

Development Cycle - Example of Logical Data Modeling

June 26, 2024 13

TCS: xBIDS LDMs in BIDS™ Domain Solutions
Building Blocks

• Logical Data Model

mBIDS (Manufacturing) bBIDS (Banking)

• Analytical Templates
tBIDS (Telecom) iBIDS (Insurance)

rBIDS (Retail)
• High-end Analytics
fBIDS (Integrated Solution
for Banking, Fin. Services
& Insurance)

June 26, 2024 14

What do xBIDS Logical Models contain ?
• Business Entities

• Kinds of entities – Transactions, References, Dimensions, Facts, Derived,

Aggregations

• Attributes – Data elements which depict details of the entity

• Relationships between different business entities

• Meaning of data elements

• Sources of each data element

• Changes to data depicting business processes and metrics

• How to access different data elements (Keys and indexes)

June 26, 2024 15

xBIDS Features
• Platform independent LDMs (Logical Data Model)

• Analytical Templates for reports and dashboards

• Flexibility to implement standardized metadata

• Encapsulates the essence of company's business

• Foundation for JAD (Joint Application Development)

• Customizable and extensible to accurately match changing business needs

• Complimented with pre-built analytics on leading BI technologies

June 26, 2024 16

Development Cycle - Physical Data Modeling

• Physical Data Models are used to design the internal schema of a database,
depicting the data tables (derived from the logical data entities), the data columns
of those tables (derived from the entity attributes), and the relationships between
the tables (derived from the entity relationships).

• Database performance, indexing strategy, physical storage and denormalization

are important parameters of a physical model.

• The transformations from logical model to physical model include imposing

database rules, implementation of referential integrity, super types and sub types
etc.

• Once physical data model is completed, it is then forwarded to technical teams

(developer, group lead, DBA) for review.

June 26, 2024 17

Development Cycle - Example of Physical Data Modeling

June 26, 2024 18

Development Cycle – CDM, LDM, PDM comparisons
Conceptual Logical Physical
Data Model Data Model Data Model
Provides high-level Represents business Represents the physical
information about the information and defines implementation of the model
subject areas and users business rules in a database.
view of an organization.
Subject Areas Entity Table

Things to track Attribute Column

No Keys identified Primary Key Primary Key Constraint

No Keys identified Alternate Key Unique Constraint or Unique

Index
No Rules or constraints Rule, Functional Dependencies Check Constraint, Default
Value, User Defined
constraints, referential
constraints
Relationship Relationship Foreign Key

No Definition or comment Definition Comment

June 26, 2024 19

Development Cycle - Database Creation / Development

• A physical database definition (say DDL for DB2, schema for Sybase or Oracle)
can be generated by entering the gathered information into a physical design
tool.

• This must be reviewed carefully and in all likelihood modified to some degree,
since no physical design tool generates 100 percent perfect database definitions.

• The script can then be run against the database management system to define
the physical environment.

June 26, 2024 20

Information Architecture (IA) - Steps

Perspective Owner IA Stages

Scope Planner Context Definition

Enterprise Model Program Owner / Sponsor Conceptual Data Model

System Model Information Architect Logical Data model

Technology Model DB Architect Physical Data Model

Component Model Developer Data Structures

Functioning Enterprise User Data Governance

June 26, 2024 21

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 22

E-R Model

• Entity-Relationship model is a set of concepts and graphical symbols

that can be used to create LDMs and PDMs

• Four versions
– Original E-R model by Peter Chen (1976), foll0wed by
– Extended E-R model: widely used model
– Information Engineering (IE) by James Martin (1990) – (Bachman’s
notation uses Crow’s Feet Notation)
– IDEF1X national standard by the National Institute of Standards and
Technology. This is also widely used.
– Unified Modeling Language (UML) supporting
object-oriented methodology

June 26, 2024 23

IE (Information Engineering)
• Information Engineering provides data analysis and database design techniques that can
be used by database administrators (DBA’s) and by systems analysts to develop database
designs and systems.

• The IE notation is simple and easy to read, and is well suited for high-level logical and
enterprise data Modeling.

• Some IE techniques that are used are:

– Entity analysis
– Function analysis and process dependency
– Process logic analysis
– Entity type lifecycle analysis
– Matrix cross-checking
– Normalization
– Cluster analysis
– Data flow and data analysis

June 26, 2024 24

E-R Model

For the purposes of this class, we will focus on

the IDEF1X notation and
briefly
touch upon Extended ER and UML notations.

We will now use the Extended ER model to

explain some modeling concepts.

June 26, 2024 25

Entity-Relationship (ER) Modeling

• The entity-relationship model (or ER model) is a way of graphically representing

the logical relationships of entities (or objects) in order to create a database.

• In ER Modeling, the structure for a database is portrayed as a diagram, called an

entity-relationship diagram (or ER diagram)

• Entities are rendered as points, polygons, circles, or ovals. Relationships are

portrayed as lines connecting the points, polygons, circles, or ovals.

• An ER diagram is used to represent the Logical and Physical Data Model of an

organization.

June 26, 2024 26

Entity-Relationship (ER) Modeling (contd.)

• In a logical sense, entities are the equivalent of grammatical nouns, such as

employees or departments. An entity can be defined by means of its properties,
called attributes.

• Relationships are the equivalent of verbs or associations, such as being a

member of a group, or being a supervisor of a department. A relationship can be
defined according to the number of entities associated with it, known as the
degree.

• Mapping can be of
the following types

1-to-1 1-to Many Many-to-1 Many-to-Many

June 26, 2024 27

The Extended E-R Model

June 26, 2024 28

Example: E-R Diagram

June 26, 2024 29

Entities

• Something that can be identified and the users want to track

– Entity class is a collection of entities described by the entity format
in that class
– Entity instance is the representation of a particular entity

• There are usually many instances of an entity in an entity class

• Typically, entities are “Nouns”, “Important Things”, “Objects”, “Roles”,

etc. who possess certain characteristics, and are possibly related to
each other

June 26, 2024 30

Example: Entity: Customer

June 26, 2024 31

Attributes

• Description of the entity’s characteristics

• All instances of a given entity class have the same attributes

– Composite attribute: attribute consisting of the group of attributes
– Multi-value attributes: attribute with more than one possible value

June 26, 2024 32

Identifiers

• Identifiers are attributes that name, or identify, entity instances

• The identifier of an entity instance consists of one or more of the entity’s

attributes

• An identifier may be either unique or non-unique

– Unique identifier: the value identifies one and only one entity
instance
– Non-unique identifier: the value identifies a set of instances

• Composite identifiers: Identifiers that consist of two or more attributes

June 26, 2024 33

Relationships

• Entities can be associated with one another in relationships

– Relationship classes: associations among entity classes
– Relationship instances: associations among entity instances

• Relationships can have attributes

• A relationship class can involve many entity classes

• Degree of the relationship is the number of entity classes in the

relationship

• A relationship cannot be associated with another relationship

June 26, 2024 34

Example: Degree of the relationship

Relationships of degree 2 are very common and are often referred to by

the term binary relationships

June 26, 2024 35

Binary Relationships – 3 Types

• 1:1
• 1:N
• N:M

June 26, 2024 36

Recursive Relationship

• Recursive relationships are

relationships among entities
of a single class

June 26, 2024 37

Cardinality

• Maximum cardinality indicates the maximum number of entities that can

be involved in a relationship

• Minimum cardinality indicate that there may or may not be an entity in a

relationship

June 26, 2024 38

Weak Entities

• Weak entities are those that must logically depend on another entity

• Weak entities cannot exist in the database unless another type of entity
(strong entity) also exists in the database
– ID-dependent entity: the identifier of one entity includes the identifier
of another entity

June 26, 2024 39

Example: Weak Entities

June 26, 2024 40

Example: Weak Entities

June 26, 2024 41

Subtype Entities

• Subtype entity is an entity that represents a special case of another

entity, called supertype

• Sometimes called an IS-A relationship

• Entities with an IS-A relationship should have the same identifier

June 26, 2024 42

Example: Supertype (without) Subtype Entities

June 26, 2024 43

Example: Subtype Entities

June 26, 2024 44

Example: Subtype Entities

June 26, 2024 45

UML-style E-R Diagrams

• The Unified Modeling Language (UML) is a set of structures and techniques for
modeling and designing object-oriented programs (OOP) and applications

• The concept of UML entities, relationships, and attributes are very similar to
those of the extended E-R model

• Several OOP constructs are added:

– <Persistent> indicates that the entity class exist in the database
– UML allows entity class attributes
– UML supports visibility of attributes and methods
– UML entities specify constraints and methods in the third segment of the
entity classes

• Currently, the object-oriented notation is of limited practical value

June 26, 2024 46

Example: UML

June 26, 2024 47

Example: UML

June 26, 2024 48

Example: UML

June 26, 2024 49

UML: Weak Entities

June 26, 2024 50

UML: Subtypes

June 26, 2024 51

IDEF1X Standard

• IDEF1X (Integrated Definition 1, Extended) was announced as a national standard in 1993

• It defines entities, relationships, and attributes in more specific meanings

• It changed some of the E-R graphical symbols

• It includes definition of domains, a component not present in the extended E-R model

• Four Relationship Types

– Non-Identifying Connection Relationships
– Identifying Connection Relationships
– Non-Specific Relationships
– Categorization Relationships

• Products supporting IDEF1X: ERWin, Visio, Design/2000

June 26, 2024 52

IDEF1X (Integration Definition for Information Modeling)
• IDEF1X is a method for designing relational databases with a syntax
designed to support the semantic constructs necessary in developing a
LDM.

• IDEF1 deals with Information Modeling and was further extended to

IDEF1X for Data Modeling.

• Entities, Connection Relationships, Categorization Relationships,

Attributes, Keys, and Foreign Keys comprise the syntax and semantics
of IDEF1X.

• If the target system is not a relational system, for example, an object-

oriented system, IDEF1X is not the best method.

June 26, 2024 53

Example: IDEF1X

June 26, 2024 54

Non-Identifying Connection Relationships

• Represent relationship with a dashed line from a parent to a child entity

• Default cardinality is 1:N with a mandatory parent and an optional child

– 1 indicates exactly one child is required
– Z indicates zero or one children
– A “hollow diamond” indicates zero or one parent i.e. optional parent
– P indicates one or more child is required i.e. mandatory child

June 26, 2024 55

Non-Identifying Connection Relationships

June 26, 2024 56

Identifying Connection Relationships

• Same as ID-dependent relationships in the extended E-R model

• Parent’s identifier is always part of the child’s identifier

• Relationship are indicated with solid lines, child entities are shown with
rounded corners
(ID-dependent entities only)

June 26, 2024 57

Identifying Connection Relationships

June 26, 2024 58

Non-Specific Relationships

• Simply a many-to-many relationship

• Relationships are shown with a filled-in circle on each end of the solid
relationship line

• Cannot set minimum cardinalities of a non-specific relationship

June 26, 2024 59

Non-Specific Relationships

June 26, 2024 60

Categorization Relationships

• A relationship between a generic entity and another entity called a

category entity

• Called specialization of subtype/generalization relationships (IS-A

relationships) in the extended E-R model

• Within category clusters, category entities are mutually exclusive

• Two types of category clusters:

– Complete: every possible type of category for the cluster is shown
(denoted by two horizontal lines with a gap in-between)
– Incomplete: at least one category is missing (denoted by placing the
category cluster circle on top of a single line, no gap between
horizontal lines)

June 26, 2024 61

Categorization Relationships

• The relationship between a subtype and a supertype (generic) can be

read as an “IS-A” relationship.

• The relationship between a supertype and a “Complete” subtype

category cluster can be read as a “MUST-BE” relationship.

• The relationship between a supertype and an “Incomplete” subtype

category cluster can be read as a “CAN-BE” relationship.

• Cardinality is not specified for the category entity since it is always zero
or one.

June 26, 2024 62

Example: Categorization Relationships
• Since an instance of the generic entity cannot be associated with an instance of
more than one of the category entities in the same cluster, the category entities
are mutually exclusive. In the example, this implies that an employee cannot be
both manager and staff. However, an entity can be the generic entity in more
than one category cluster, and the category entities in one cluster are not
mutually exclusive with those in others. In other words, an employee can be a
manager and a tech writer.

June 26, 2024 63

Example: IDEF1X Model With Relationship Names

June 26, 2024 64

Example: IDEF1X Model With Relationship Names

June 26, 2024 65

Domains

• A domain is a named set of values that an attribute can have

• It can be a specific list of values or a pre-defined data characteristic,

e.g. character string of length less than 75

• Domains reduce ambiguity in data modeling and are practically useful

• Two types of domains

– Base domain: have a data type and possibly a value list or range
definition
– Type domain: a subset of a base domain or a subset of another
type domain

June 26, 2024 66

Example: Domain Hierarchy

June 26, 2024 67

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 68

Enterprise Data Modeling (EDM)
• EDM is a framework used for enterprise wide information integration.

• The development of a common consistent view and understanding of data

elements and their relationships across the enterprise is referred to as Enterprise
Data Modeling.

• Enterprise Data Modeling, also called as global business model, captures the
entire information about the enterprise in the form of entities.

• When an enterprise logical data model is transformed to a physical data model,

length of table names, column names etc may exceed the maximum number of
the characters allowed by the database.

• Building an Enterprise data model follows a four-phase approach. These phases

explain the process of Modeling an Enterprise Data warehouse or information
integration, however the Modeling technique remains the same.

June 26, 2024 69

Phase 1 – Identify the Major Subject Areas

HUMAN
CUSTOMER ITEM FACILITY RESOURCES

GEOGRAPHIC CORPORATE
MARKETING VENDOR AREA

FINANCE
MERCHANDISING

Key Principle : The number of major subject areas in an enterprise

should be approximately 10 – 20 (maximum)

June 26, 2024 70

Phase 2 – Identify Major Entities for all areas

Sears Enterprise Conceptual Data Model

CORPORATE
uses Address : 1
HUMAN Model Source Legend
Corporation FINANCE CUSTOMER ITEM FACILITY RESOURCES Sourced from:
can be contacted via Chart of Accounts
Email Address
is either Ledger T ype
Customer Demographics is characterized by submits ART S Model Sears
Credit Application

Individual is charged to
CUSTOMER party to contains tracks against GEOGRAPHIC CORPORATE
T erms and Conditions
Budget : 1
MARKETING VENDOR
is Party
Contract
AREA
describes
Ledger
Competitor : 2 authenticates Audit Control
filed in forecasts
Legal Jurisdiction
Customer Segment : 1 Household
party to FINANCE
submits Worker : 2 creates
Customer Comment Case
subject to
posted to MERCHANDISING
Legal Action posts to Revenue Forecast
Regulatory Compliance
:4
Vendor : 2 Conceptual Data Model
T ransaction : 2 Geographic Area : 2
conform to belongs to Model: Enterprise Conceptual Data Model
is grouped into Package:
Financial Asset owns
Diagram: Enterprise Conceptual Data Model
responds to
Customer : 1 Investor : 2 Author: Drake, Pacocha, Georgas-Gait, Strickland Date : 11/20/2003
Customer are protected by
Press Release issues projects taxed by Version :
Preference may relate to

is insured under
protects is granted is made up of
Insurance Policy
T ax Rate ITEM
Credit Account taxes at contains levied by is responsible for
Organization Hierarchy reports to T ax T ax Authority
provides credit for T ax Jurisdiction
T ax Rule are classified by Item T ype
Regulatory Compliance taxes
sent to
Customer Survey :1 sends
Organization : 1 Investory Communication Investor : 1
charged to owns or leases Item Group are grouped by
Real Estate
participates in define
is a response to organizes work efforts via
establishes sets timeline for offers Vendor Deal
purchases develops Related Item
have relationships with
Vendor : 3 Retail T ransaction is a Calendar : 1
establishes
Events marked on
T ransaction : 1 Policy
issues Financial
describes Vendor Product Relationship are applied against Purchasing Guideline are purchased based on
Sale Regulation Merchandising
Regulatory Body may cover
Return executes Advertising and Promotions
Event
Exchange
fulfills Customer
Payment Business Plan
Fullfillment Budget : 3 Facility Catalog
are ordered through offers
Brand :1
owns right to T rademark
Intangible Asset Vender Item Offering Item Preparation
can be associated to Patent
Software is imported by are contained within
occurs at
Item : 4 Data determines finances for
Import Merchandise
describes purchases defines Service
performs activity for is created or modified by describes
Merchandise Parts
may be to provide Project : 2 Protection Plan
Distribution Service Provider may cover is affected by
is part of 3rd Party Logistics Not for Resale Supply
can be associated to Channel may relate to
Vendor Item Offering T ype adheres to Credit Product
Facility Layout Preferred Vendor
hired through describes
FACILITY can require
may be to build/open/modify Geographic Area : 3
Vehicle Regulatory are purchased at
Worker : 1 is responsible for tracks offers
POS Device Compliance : 3
may file
Computer Hardware Vendor Subsidy Item : 1
Store manages
Employee is governed by
Grievance Website Item Cost
Recruitment uses Equipment : is peformed on offers
Warehouse is made up of Vendor : 1 Vender T rading T erm bought at
Shipments Facility Configuration Equipment Maintenance
1
Distribution Facility
has acquired
Office
is hired as Vender Payment Agreement purchases
accepts groups
has authority for
create carries is specific to
are included in is responsible for Facility Catalog2
employs Facility : 1 Zoning Compliance
Contractor is specific to have measurements of
Vendor : 4 maintains must meet are shipped by Item Constraint
Vendor Performance Standard
Worker Role Worker
Compentency manages VENDOR are sold at
is at
Worker Positon Facility
ItemCatalog
:2
is compensated via :2
are defined at incurrs Item Attribute
Worker Pay describes receives Vendor Compliance Item Price
Employee Facility Operations Profile Utility Service
selects has authority for
maintains
Weight, Color,
store establishes Vendor Certification
Size, Height,
Global T rade Packaging
locates T ransaction : 3 Width, Color,
Employee Benefit assigned during Calendar : 2 Size, Brand,
Item Hierarchy : 3 requires Security
Inventory T raits, etc.
Quantity
may take can be
is protected by Fulfillment Replishment Method Item Case Pack can be sold by
is motivated by are defined by based on
Rule
Geographic Area Role
is classified by replenishes
is engaged in Replenishment Rule
Geographic Area : 1 replenishes
Regulatory is depicted via scheduled via
Performance Management Compliance : 2 Inventory
T raining assigned to work on Project : 1 T ype Item Purchase
Item Hierarchy : 2 contains
groups
Facility : 2 determines item assortment for
Assortment Plan assorts
is grouped into describes
Geographic Area Map Map
is characterized by
HUMAN assigned to
Address : 2 is recorded within Budget : 2
RESOURCES defines Road Map Store Cluster scheduled via
Item Allocation distributes

defined by T opographical Map

Geographic Area scheduled via

Hierarchy is input to
GEOGRAPHIC Regional characterized by
Calendar : 3 aligned to
Merchandise Plan
plans revenue by
Geodemographic plans revenue by
AREA based on
Item Hierarchy : 1 is a buyer for
Sears, Roebuck and Co., Proprietary and Confidential
- For Internal Use Only - operates in
Demand Forecast Plan is input to
measures demand for
aligned to
can vary by
Organization : 2 Market
operates within distributed in
Promotional Plan is input to Worker : 3
sets is responsible for
promotes items from
Media
Competitor Location promotes
competes within

plans space for

supports
advertises within Space Management is input to
sells at feeds
uses
Competitive Item Offerings offers Competitor : 1

Organization : 3
Marketing Campaign Equipment :
scheduled by uses
advertises via 2

MERCHANDISING
supports

compare to Item : 3 advertises

Direct Marketing supports

Key Principle : Focus

is targetted to
Customer : 2
MARKETING

Customer Segment : 2

on major entities and

is targeted to

relationships

June 26, 2024 71

Phase 3 – Drill Down a specific Subject Area

Salary
Administration sets
Employee Pay Plan
Geographic
Employee may be authorized by type
Employee Area : 1
Incentive Full/Part
Category Employee Role
is based on
classifies (Reg/ Employee Overtime Equipment
Component Time Code defines
Temp) : 1 Type : 1 is defined for Rule
Role Type Software Computer
differs by classifies
Sears Application Hardware Tool Vehicle
Hourly / Salaried / Salary
Sears Target is motivated by company defines Organization : 4 determines :1 :1
Benefits Incentive Employee Exception Facility : 3 Grade : 1
Organization : 1 Salary
Status Role
Range may be needed for
may be defined for Job Code Expertise
may define is paid either requires
Pay
Vendor : provides
Employee Employee defines general work of
earns is assigned
Dependent Employee Compensation is paid as defines
1
:2 Tax is assigned Job Code : 3 Hourly Role
Performance Role may allow or disallow
Exemption files is paid Rate Equipment
Benefit Plan has
Review Action
Range Action Department
Option e.g. W-4
Employer General
identifies (Number) :
Pay Deduction offers is covered by Paid Tax is included in Ledger 2
Code : 1 Draw Sears employs
Employee assesses is defined to Sears Department
may be elected Amount Organization identifies
Reporting e.g. FICA Organization : ID : 1
Tax Job code may be performed or not performed by Facility : 1
is assessed
2 posts to
Statement covers
may have sets Ledger : 1
Benefit
receives
may be altered for
Compensation may relate to
indicates e.g. W-2, 1099
Election elects Employee : 1 Plan Code (P, Action (Speaking)
is credited for defines is performed by manages works
C,H,D,S,B) sets pays by may pertain to Language :
is offered to
may perform Draw Rule 2
defines Commission Job Code :
Benefit define classifies Modifier 1
Sears identifies the general work of Job
Plan may be selected by Commission Type Calendar
Organization : 7 has assigned
Training :
identifies the type of Modifier credits
relates to 2
Benefit Commission Facility Employee : 2 possesses Expertise (
offers is paid by Sales Credit is effective
is offered by Program Rate Calendar Action Job Skill,
Benefit Employee has deposited is fulfilled by Sale/ performs Employee is possessed
is paid Employee Area of Accomplishment
Type Code Pay Check Return Employee fulfills Expertise
accounts for Role : 2 fulfills Knowledge) :2
Line Item Role : 1
may have Item e.g. Certification
Geographic is offered by Employee records sale has may specify
Area : 2 provides Bank Action types
is rated defines
Account Non Retail
General totals works manages
Ledger Tax Payroll Transaction may be a may set Facility : 2 defines
assigns Technical
is paid for via
Department Financial Taxable Line Item Skill
accumulate Facility : 4 Logical
ID : 3 Institution : Income Employee Role Item : 2 Department Level of Project
Retail
1 Transaction Expertise Role
Employee Tax is acted upon
has Line Item Sears Expertise
Pay Check Jurisdiction is subject to Business
levies is entered against Department may define Organization : 3 Knowledge
Line Item Pay Check identifies
requries receives Pay has (Number) : Project
Taxes Project
Deduction 1 Assignment is fulfilled
is either taxes Role is defined by
Code : 2
Pay
Employee
Ledger : 3 Earnings Deduction renders is made up of
receives the Garnishment Jurisdiction Sears
accounts for Subject to Tuition Balance establishes
Legal Organization
Tax Reimbursement reports to is paid for via
Action Hierarchy
Project Ledger : 2
Pay Employee Organization requires
defines Pay may be taxed by Garnishment
Pay Check Check Role
Earnings Earnings can have Garnishment Financial creates
Deduction Earnings may indicate Payee
Code is totaled Balance Ruling Institution :
2

Employee Sourced from:

Employee Dependent
is a child of
Computer
:1 can be Item Hierarchy Group Associated Item Hierarchy Group
Hardware is a parent of
:2 receives email at Email ARTS Model Sears
describes
Address
Party Role Type Party Role receives calls at
has Sears defines parent
uses
is accessed via Organization : 5 classifies
Log-in ID
is accessed via employs
is involved in Telephone Item Hierarchy Level
categorizes
Party Address Telephone Type
Organization
Item Hierarchy HUMAN RESOURCES
has parent CUSTOMER ITEM FACILITY
is supplied
Software
Application : Employee : 3 is a Party
2
may have is used by
Employee Accomplishment Individual NonStandardized
Item : 1
is associated with Disability :1 (Person) Address GEOGRAPHIC CORPORATE
MARKETING VENDOR AREA
Disability e.g. Certification is identified via is assigned to
accomplishes Employee may-be
Accomplishment is accomplished by
Employee speaks has built
Address Standardized
is spoken by Speaking
Address FINANCE
Vendor : Language
2 (Speaking) Employee Category (
is preferred by identifies MERCHANDISING
Language : Salary Reg/Temp) : 2 Party Identification may also be
may be changed distinguishes
1 Grade : 2
Item Group
Employee completes Employee Job may be changed Social Security Number,
Job is completed by Drivers License Number, etc.
Job current
History may employ
provides Training : Address
1 Training Job Code : Type
is assigned has working at
2 Standardized
General Standardized
Party Identification Type Foreign Address Domestic Address
Ledger Conceptual Data Model
Sears employs Department Model: HR Logical Data Model Sears, Roebuck and Co., Proprietary and Confidential
Facility : 5 - For Internal Use Only -
Organization : 6 ID : 2 Package:
Employee Type : 2 Diagram: Employee
defines Author: Georgas-Gait, Casey, Strickland
Version : 1.0

Key Principle : Drill down each subject areas with increasing detail

June 26, 2024 72

Phase 4 – Drill down to develop attribute detail

Employee Pay Salary Administration Plan is defined for

Salary Administration Plan Code
Employee Role
Salary Administration Plan Status Code
defines
Salary Administration Plan Description

Key Principle :
Salary Administrative Plan Short Description
Salary Matrix Code

Overtime Rule
Incentive Component Overtime Rule ID
Employee Dependent : Salary Grade : 1
Benefits 2
Incentive Component ID
Salary Grade Code
Incentive Component T arget Description
Salary Grade Status Code
may be authorized by Equipment type
Employee Dependent Number Incentive Component T arget Value
Performance Review Salary Grade Description Equipment ID
Incentive Component Amount
Salary Grade Short Description Equipment Category Code
Performance Review Entry Date
Salary Matrix Code
Salary Equipment Manufacturer
Performance Review Sequence Number Range
Rating Scale
Next Performance Review Date
Minimum Hourly Rate
Software Application : 2 Computer Hardware : 1 Tool Vehicle
Minimum Salary
Benefit Plan Option Performance Review T ype Code

80% of the
Mid Point Hourly Rate Mid-Point Salary Software Application ID Computer Hardware ID T ool ID Vehicle ID
Benefit Plan Option
is based on Performance Review Code Employee Full/Part Time Maximum Hourly Rate
Job Code Software Application Name T ool T ype Code
Performance Review Rating Code Maximum Salary Computer Hardware T ype Code Vehicle T ype Code
Benefit Plan Option Description Code Minimum Monthly Rate Pay Software Application Version
Vendor : 1 Reviewed with Employee Flag
is paid either
Role Type Computer Hardware Model Vehicle Make
Employee Cost Employee Full/Part T ime Code Mid Point Monthly Rate Computer Hardware Serial Number Vehicle Model
provides Performance Review Period Starting Date Role T ype Code
Vendor ID Maximum Monthly Rate Vehicle VIN Number
Performance Review Period Ending Date Employee Full/Part T ime Description Hourly Rate classifies Role T ype Description
Target Minimum Annual Rate
Performance Review Date
Mid Point Annual Rate Range
Incentive Role Role
Facility : 2 Maximum Annual Rate Minimum Hourly Rate may be needed for
is covered Incentive Year Mid-Point Hourly Rate Action Expertise
Employee Facility ID Number
may be elected Maximum Hourly Rate
may have Employee Category ( Location Number Equipment may allow or disallow
Compensation classifies is paid Role requires Department (
Reg/Temp) : 1 Sears Action identifies
Benefit Type Code may be defined for Role ID General Ledger Number) : 1
Employee Category Code Organization Role Name Department Number
Benefit T ype Code identifies the type of assesses is assessed is assigned
Employee Category Description Job code
defines defines Department ID : 1

attributes in each
Benefit T ype Description Benefit Plan : 1 Department Name
is motivated by Department ID
Benefit Plan Code may be selected by Department Name
Benefit Plan Description
Employee Status Job Code : 1 may be performed or not performed by Facility : 4 identifies
Benefit Plan Effective Date
defines Job Code Facility ID Number
Benefit Plan Short Description Employee Status Code may define
Job Code Status Code Location Number
Benefit Plan Group Number Employee Status Description
Job Code Description
Benefit Election earns Employee : 3 Job Code Short Description
elects is included in
Benefit Election Effective Date Employee Identification Number Job Function Code
Employee Status Code
has
Management Level Code
may relate to Action works manages
Pay Deduction Code : 1
Employee Original Hire Date Job Default Standard Hours
has assigned
Ledger : 1
Action ID
Employee Tax Employee Last T ermination Date Compensation Frequency Code
Action Name
posts to Ledger ID
Pay Deduction Code Employee Last Rehire Date Workers Compensation Pay Code
is offered to Exemption files Employee Type : 1 may pertain to
Pay Deduction Code Effective Date Employee Service Date Fair Labor Standards Act Status Code
is paid as

subject area can

Pay Deduction Code Description Number of Dependents Claimed Expected Leave of Absence Return Date Employee T ype Code Equal Employment Opportunity Labor T ype 1 Code
Pay Deduction Code Short Description Benefit Program Additional Withholding Amount Employee Marital Status Code Employee T ype Description Equal Employment Opportunity Lab Job Code : 3
Deduction Priority Code offers Benefit Program Code Employee Birth Country Equal Employment Opportunity Labor T ype 5 Code Job Code
Garnishment Rule Processing Flag Benefit Program Description e.g. W-4 Employee Date of Death
Hourly / Salaried /
Equal Employment Opportunity Labor T ype 6 Code Job Code Status Code Employee : 2
Maximum Payback Code Employee Cost
Employee Highest Educational Level Achieved Job Code Description
receives Exception defines general work of Calendar Employee Identification Number
Withholding Cycle Reporting Tax Full T ime Student Flag Job Code Short Description
Draw Rule Facility Employee Status Code
Statement Employee Referral Source Code Calendar ID Job Function Code Employee Original Hire Date possesses
Referring Employee Identification Number Draw Rule Identifier Action Management Level Code Employee Last T ermination Date
Expertise (Job Skill,
Specific Referral Source Draw Rule Job Default Standard Hours Area of Knowledge)
Employer Paid Tax Employee Citizenship Flag
Employee Last Rehire Date
defines type of Compensation Frequency Code
e.g. W-2, 1099 Employee Service Date Equipment ID
Pay Period Employee USA Work Elgibility Flag Draw Workers Compensation Pay Code
covers is defined to Expected Leave of Absence Return Date is possessed Equipment Category Code
Employer Paid T ax Amount Military Status Code Amount Commission Fair Labor Standards Act Status Code Employee Marital Status Code
is paid for Bilingual Code is assigned identifies the general work of
Draw Date Rate Equal Employment Opportunity Labor T ype 1 Code Employee Birth Country Employee
Employee Actual Last Date Worked Equal Employment Opportunity Lab
e.g. FICA Draw Amount relates to Employee Date of Death
Fixed Dollar Amount Expertise

be identified with
Employee Last Base Pay Change Date defines Equal Employment Opportunity Labor T ype 5 Code
Commission Rate Highest Educational Level Achieved types
Employee Owns 5 Percent Flag
General Ledger may specify Equal Employment Opportunity Labor T ype 6 Code Full T ime Student Flag Last Year Used defines
Benefit Rate
Department ID : 3 Employee Pay Check is paid by Previous Benefit Rate
Employee Referral Source Code
may be altered for Referring Employee Identification Number
Department ID Pay Group Code Benefit Rate Overridden Flag Compensation Plan
use Specific Referral Source
Department Name pays for Pay Period Ending Date Employee Benefits Grandfathered Flag Code (P,C,H,D,S,B) Employee Citizenship Flag
Employee Pay Check Off Cycle Code Expected Annual Vacation Days is credited for
Payroll Page Number is paid Commission Plan Code Facility : 3 Employee Role : 1 Employee USA Work Elgibility Flag (Speaking)
Employee Last Compensation Plan Change Date Facility : 1
Line Item Payroll Line Number Commission Commission Plan Description Military Status Code Language : 2
Facility ID Number Employee Position Start Date Bilingual Code Level of
Pay Check Line Item Number has Separate Check Flag Modifier may set Location Number
Facility ID Number
Employee Position End Date Language ID
Pay Check Line Item Amount Pay Check Form Code Location Number is performed by Employee Actual Last Date Worked Expertise Language Name
is rated
Employee Last Base Pay Change Date
Bank Check Number Expertise Level
has deposited performs Employee Owns 5 Percent Flag Project
Pay Check T otal Gross Pay
Pay Check T otal T axes (Sales Credit) credits Benefit Rate Role
is either Commission Modifier Previous Benefit Rate Expertise Job Training : 2

20% of the effort.

Pay Check T otal Deductions
Pay Check Net Pay
Type Item Benefit Rate Overridden Flag
Sale/ Employee Benefits Grandfathered Flag Job T raining ID
Pay Check Date Commission Modifier T ype Action
Pay Check Status Code Commission Modifier Description classifies Return Expected Annual Vacation Days Job T raining Name
Pay Check Option Code Non Payroll Taxable Income Line Item Employee Last Compensation Plan Change Date
Paycheck Employee Name Non Payroll T axable Income T ype Project
Pay Check Deduction Pay Check Retail
has
Pay Check Address Line 1 Non Payroll T axable Income Amount Employee Role : 2 is fulfilled by Department ( Role Accomplishment : 2
Pay Deduction Pre/After T ax Code
Taxes Pay Check Address Line 2 Non Payroll T axable Income Comment fulfills Transaction
Pay Check Address Line 3 may perform Employee Position Start Date Number) : 2 Project Role ID
is defined by Accomplishment T ype Code
Pay Deduction Amount T ax Class Code
Employee Position End Date Line Item Accomplishment Description
T ax Resident Flag Pay Check City Department Number
Pay Check County
Employee Role Department Name
T ax Paid Amount
Pay Check State
Logical
Tax Pay Check Postal Code Legal Action e.g. Certification
may be a Department Project
Pay Check Country
Jurisdiction Court Document ID fulfills
Deposit Amount Employee Bank is entered against
establishes
Project ID
T ax Jurisdiction ID
Account
Documentation Received Date Project Name Technical Skill
requries Response Required By Date
Retail records sale
is fulfilled Project Status T echnical Skill ID
Pay Check Earnings Bank T ransit Number Transaction requires
Project Start Date
Tax Bank Account Number Line Item
T echnical Skill Name
Earnings Period End Date Project End Date
T ax ID Bank Account T ype Code
Hourly Rate levies
Pay Hours
renders
Jurisdiction Business Knowledge
Hourly Pay Earnings Amount taxes has Sears
Pay Earnings Amount totals Jurisdiction ID
Organization is paid for via Business Knowledge T ype Code
Deduction Subset Code Financial Jurisdiction Name
Item : 2 Hierarchy
Earnings State Code provides Institution : 1 Project Assignment
Item Internal ID
Locality Code
Financial Institution ID Employee Garnishment Item Purge Date Organization Project Assignment Start Date
T ax Period Code
Pay Earnings Tuition Reimbursement Item Subject T o Additional Handling At Store Flag Role Project Assignment Allocation Percent
Ledger : 2
T ax Method Code Employee Garnishment Number
Subject to Tax Item Assemble Before Delivery Flag Project Assignment End Date Ledger ID
Pay Check Earnings Sequence Number T uition Reimbursement Request Date Garnishment Status Code
Item Authorized to Return to Vendor Flag
Earnings Rate Used Code School Name Garnishment T ype Code
Class Name receives Garnishment Priority Level Code Employee Garnishment Item Bin T icket Required Flag
Item Catalog Flag
Class Grade Value is subject to Garnishment Limit Amount Ruling
Item Components Sold Separately Flag
T uition Reimbursement Amount Garnishment Limit Balance Amount
Garnishment Rule ID Item Direct Delivery to Customer Flag
Garnishment Monthly Limit Amount
Garnishment State Code Item Defective Merchandise Disposal Code
Company Garnishment Fee Amount
Garnishment State Rule Code Item Subject to Deterioration Flag
Garnishment Start Date can have
may be taxed by Garnishment Exemption Amount Item Direct Delivery Flag is acted upon
Earnings Balance Garnishment End Date
Garnishment Frequency Code Item Fashion Flag
Garnishment Payroll Code
may indicate Earnings Balance Year Item Sold in Fractional Denominations Flag
Garnishment Calculation Code
Earnings Balance Quarter Item FHV Suffix Code
Garnishment Percent
Earnings Balance Month Item Flame Resistent Flag
Garnishment Amount
T otal Hours Year T o Date Item Installation Available Flag
Garnishment Frequency
Pay Earnings Code T otal Hours Quarter T o Date accumulates
Company Fee Percent
Item Is Also a Part Flag
T otal Hours Month T o Date Item Product Registration Required Flag
Pay Earnings Code Company Fee Amount
T otal Earnings Year T o Date Amount Item Shipped Prepaid Flag
Pay Earnings Code Effective Date Payee Fee Percent receives the

Key Principle :
T otal Earnings Quarter T o Date Amount Item Prefix
Pay Earnings Code Status Code Payee Fee Amount
defines T otal Earnings Month T o Date Amount Item Royalites Required For Item Flag
Pay Earnings Code Description Prorate In Effect Flag
Item Retail Special Order System Flag
Pay Earnings Code Short Description is totaled Garnishment Prorate Rule ID
Ledger : 3 Hours Only Flag Garnishment Support T ype
Item Special Order Flag
Item Serviceable Flag
Ledger ID Shift Differential Elgible Flag Garnishment Remarks
Garnishment Payee Item Subject to T extile Products Act Flag
Multiplication Factor
Item T rack Serial Numbers Flag
is charged for T ax Method Code Pay Deduction Code : 2 Deduction Balance Garnishment Payee Number Item Subject to Wool Label Act Flag
Earnings Annual Cap Amount
Pay Deduction Code Deduction Balance Year
Amount or Hours Code
Pay Deduction Code Effective Date Deduction Balance Quarter
Earnings Effect on Benefit Rate Calculation
Financial Pay Deduction Code Description identifies type of Deduction Balance Month
Benefit Rate Used Flag
Pay Deduction Code Short Description Pay Deduction Pre/After T ax Code
Accrual in General Ledger Flag Institution : 2 Deduction Priority Code T otal Deduction Year to Date Amount
Benefit Plan : 2
Gross Up Flag T otal Deduction Quarter T o Date Amount can identify
Financial Institution ID Garnishment Rule Processing Flag Benefit Plan Code
Maximum Payback Code T otal Deduction Month T o Date Amount Benefit Plan Description
Benefit Plan Effective Date
Benefit Plan Short Description
Benefit Plan Group Number

Subject Areas
Party Role describes
Employee can be Party Role Effective Date
receives email at
has parent
Party Role Expiration Date
receives calls at

Item Hierarchy Level

Party Role Type Item Hierarchy Group
is a child of Item Hierarchy Level ID
Item Hierarchy ID Associated Item
Party Role T ype Code Item Hierarchy Level Code
Computer Hardware : 2 Party Role T ype Name
Item Hierarchy Code
Hierarchy Group Item Hierarchy Level Parent
defines parent
is involved in Item Hierarchy Description is a parent of
Computer Hardware ID Party Role Description Item Hierarchy Level Description
Item Hierarchy Effective Date
Computer Hardware T ype Code
Item Hierarchy End Date
Computer Hardware Model

may be chosen
Computer Hardware Serial Number Individual (
Person) Party Email Address Item : 1
Individual Party ID Party ID Email Address ID
Log-in ID Employee : 1 Item Internal ID
is accessed via Salutation Organization T ype Code Item Purge Date
Log-in ID is supplied Employee Identification Number First Name Party T ype Code
Item Item Subject T o Additional Handling At Store Flag
Log-in Status Code Employee Status Code First Name T ype
reports to Item Assemble Before Delivery Flag
Log-in Password Employee Original Hire Date Middle Names
is a uses Hierarchy is assigned to
Item Authorized to Return to Vendor Flag
is accessed via Employee Last T ermination Date classifies
Log-in Password Date Last Updated Middle Name T ype Telephone Item Bin T icket Required Flag
Employee Last Rehire Date Last Name
T elephone Country Code Item Catalog Flag
Employee Service Date Last Name T ype
Area Code Item Components Sold Separately Flag
Expected Leave of Absence Return Date Suffix
T elephone Number Item Direct Delivery to Customer Flag
Employee Marital Status Code Gender T ype Item Defective Merchandise Disposal Code
Employee Birth Country has Employee Dependent : 1 Birth Date
Extension Number
Software Application : 1 Employee
Item Subject to Deterioration Flag

for drill down in

may have Employee Date of Death Employee Dependent Number Sorting Name is identified via Item Direct Delivery Flag
Software Application ID Disability Highest Educational Level Achieved Mailing Name Item Fashion Flag
Software Application Name Full T ime Student Flag Official Name
Disability is associated with Item Sold in Fractional Denominations Flag
Software Application Version Employee Referral Source Code
Item FHV Suffix Code
Disability T ype Code Referring Employee Identification Number
Specific Referral Source
Party Address categorizes Item Flame Resistent Flag
Disability Description Item Installation Available Flag
Employee Citizenship Flag Party Address Status Code
Item Is Also a Part Flag
Employee USA Work Elgibility Flag Party Address Effective Date
Employee Organization Item Product Registration Required Flag
Employee Military Status Code accomplishes Party Address Expiration Date
Item Shipped Prepaid Flag
Bilingual Code Accomplishment Organization Party ID Telephone Type
is spoken by
Speaking speaks
Employee Actual Last Date Worked Accomplishment Date Organization Name T elephone T ype ID
Item Group Item Prefix
Language Employee Last Base Pay Change Date Organization T ax ID
Item Royalites Required For Item Flag
T elephone T ype Description Item Retail Special Order System Flag
Employee Owns 5 Percent Flag Organization Legal Status Code Party Identification Item Special Order Flag
Benefit Rate Organization Federal T ax ID
Party Identifier Item Serviceable Flag

accordance with
Previous Benefit Rate Organization State T ax ID
Party Identifier Expiration Date Item Subject to T extile Products Act Flag
Benefit Rate Overridden Flag
(Speaking) is preferred by Party Identification Image Item T rack Serial Numbers Flag
Employee Benefits Grandfathered Flag
Language : 1 Expected Annual Vacation Days
is accomplished by Social Security Number Verified Flag Item Subject to Wool Label Act Flag

Language ID Employee Last Compensation Plan Change Date

Language Name
Social Security Number, Address NonStandardized
Drivers License Number, etc.
Accomplishment : 1 Address Id Address
is used by
Address Line 1
Accomplishment T ype Code
Employee Address Line 2
Accomplishment Description
Vendor : 2 Job Unit Name
Job Training : 1 Training completes has built T erritory Name
is completed by
Vendor ID provides e.g. Certification Country Name
Job T raining ID may be
Postal Code
Job T raining Name County Name

Project priorities
Party Identification Type
Employee Job History
Job Code : 2 Party Identification T ype Code identifies
Job History Effective Date General Ledger Salary Grade : 2
Party Identification T ype Description Address Type Standardized Address
Job Code Job History Sequence Number Department ID : 2 Salary Grade Code Sourced from:
Job Code Status Code current Employement Status Code Salary Grade Status Code Address T ype Code distinguishes Foreign Domestic T ype Code
employs Department ID
Job Code Description Employee Job History Change Code Salary Grade Description Address T ype Description HUMAN RESOURCES
Department Name CUST OMER IT EM FACILIT Y
Job Code Short Description is assigned Employee Job History Change Entry Date Salary Grade Short Description Address T ype Business Name
Job Function Code Employee Job History Change Reason Code Salary Matrix Code ART S Model Sears
Management Level Code Department ID Change Date Rating Scale
Job Default Standard Hours Shift Differential Pay Flag Minimum Hourly Rate
Compensation Frequency Code Shift Rate may be altered Mid Point Hourly Rate Standardized Domestic Address
Workers Compensation Pay Code Shift Factor Maximum Hourly Rate may be either
Employee Type : 2 define type of Address Line 1
Fair Labor Standards Act Status Code Pay Group Code Minimum Monthly Rate Address Line 2 CORPORAT E
Equal Employment Opportunity Labor T ype 1 Code Employee T ype Code GEOGRAPHIC
Benefit Elgibility Code Mid Point Monthly Rate City VENDOR
Equal Employment Opportunity Lab Employee T ype Description MARKET ING AREA
Cobra Elgibility Code Facility : 5 Maximum Monthly Rate State
Equal Employment Opportunity Labor T ype 5 Code Employee Standard Hours Minimum Annual Rate Postal Code
Equal Employment Opportunity Labor T ype 6 Code Employee Benefit Class Code is employed by Facility ID Number Mid Point Annual Rate
Compensation Frequency Code Location Number Maximum Annual Rate
Base Pay Rate
Base Pay Change Amount FINANCE
Base Pay Change Percent
Annual Pay Rate Standardized Foreign
MERCHANDISING
Monthly Pay Rate Employee Category ( Address
identifies type of
Hourly Pay Rate Reg/Temp) : 2 Address Line 1
Annual Benefit Base Pay Rate Address Line 2
Employee Category Code
Fair Labor Standards Act Status Code City
Employee Category Description
Postal Code
T erritory Conceptual Data Model
Country Code Model: HR Logical Data Model
Package:
Diagram: HR ELDM Attributed Model
Sears, Roebuck and Co., Proprietary and Confidential
- For Internal Use Only - Author: Georgas-Gait, Casey, Strickland
Version : 1.0

June 26, 2024 73

Example of Enterprise Data Modeling

June 26, 2024 74

Data Modeling Standardization - Needs
• Several data modelers may work on the different subject areas of a data
model and all data modelers should use the same naming convention, writing
definitions and business rules.

• Inconsistency across column names and definition can create chaos across
the business.

• For example, when a data warehouse is designed, it may get data from
several source systems and each source may have its own names, data
types etc. These anomalies can be eliminated if a proper standardization is
maintained across the organization.

June 26, 2024 75

Table Names Standardization
• Giving a full name to the tables will give an idea about the data present in the
table.

• Generally, the table names are not abbreviated; however this may differ
according to organization’s standards.

• If the table name’s length exceeds the database standards, then try to
abbreviate the table names.

• Some general guidelines are listed below that may be used as a prefix or
suffix for the table.
• Lookup – LKP
e.g. Credit Card Type Lookup – CREDIT_CARD_TYPE_LKP
• Statistics – STAT
e.g. Credit Card Web Statistics – CREDIT_CARD_WEB_STAT

June 26, 2024 76

Column Names Standardization
• Key – KEY - System generated surrogate key.
e.g. Credit Card Key – CRDT_CARD_KEY

• Identifier – ID - Character column that is used as an identifier.

e.g. Credit Card Identifier – CRDT_CARD_ID

• Code – CD - Numeric or alphanumeric column that is used as an identifying

attribute.
e.g. State Code – ST_CD

• Description – DESC - Description for a code, identifier or a key.

e.g. State Description – ST_DESC

• Indicator – IND – to denote indicator columns.

e.g. Gender Indicator – GNDR_IND

June 26, 2024 77

Database Parameters Standardization
• Index – IDX – for index names.
e.g. Credit Card Fact IDX01 – CRDT_CARD_FCT_IDX01

• Primary Key – PK – for Primary key constraint names.

e.g. CREDIT Card Fact PK01- CRDT-CARD_FCT_PK01

• Alternate Keys – AK – for Alternate key names.

e.g. Credit Card Fact AK01 – CRDT_CARD_FCT_AK01

• Foreign Keys – FK – for Foreign key constraint names.

e.g. Credit Card Fact FK01 – CRDT_CARD_FCT_FK01

June 26, 2024 78

Key Roles – Enterprise Data Modeling Process
Role Title Desription of Primary Responsibility Allocation
Senior Data Architect Owns and executes the Enterprise Logical Data Modeling activity. Is responsible for Full time
constructing the Logical Data Model, deliverable. Plays a lead role in shaping the course of
the Data Modeling activity, by facilititating thorough understanding the entities and
relationships.
Data Architect Reports to the Seniot Data Architect, and performs the functions of a junior data modeler. Full time
May oaccasionally lead a modeling session. Helps in drilling down into lower levels of detail in
specific subject areas, as well as in documenting issues and resolving conflicts, in addition to
drawing the E-R diagrams and capturing the meta data.
Meta Data Administrator Supports the Enterprise Data Modeling exercise with a robust set of tools for capture and Full time
reporting of meta data. Responsible for ensuring that the meta data tools are up and
available, and also able to respond to evolving meta data needs in the organization.
Business Process owner Owns one or more of the business processes that interact with the data being modeled. The Part time
process owners can in most cases identify 80% of the key attributes of an entity, in a group
of entities.
Business Analyst Creates process models for all processes that interact with the Data. Can drill down into very Full time
low levels of detail about the business process. Primarily focuses on the Business Process -
Entity /Attribute detaiil
Application Architect Supports the Enterprise Data Modeling exercise with a robust set of tools for capture and Part time
reporting of meta data. Responsible for ensuring that the meta data tools are up and
available, and also able to respond to evolving meta data needs in the organiza
Data Base Administrator Owns the physical data base at the table, columns, views and indexes level of detail. Part time
Sometimes, a DBA can contribute to the development of a semantic model owing to their
deep insight into the existing views and meanings of data.
Subject Area Expert A person who is an expert in the specific subject area being discussed. During the course of Part time
an Enterprise Data Exercise, many different subject matter experts will be consulted to help
the team better understand the processes and the underlying detail.

June 26, 2024 79

Phase-wise activities performed by a Data Modeler
1. Business Requirement Analysis
• Interact with Business Analysts to understand the functional requirements.
• Interact with end users and find out the reporting needs.
• Conduct interviews, brain storming discussions with project team to get additional requirements.
• Gather accurate data by data and functional analysis.
• Validation

2. Development of Data Model

• Create standard abbreviation document for logical, physical and dimensional data models.
• Create logical, physical and dimensional data models
• Document logical, physical and dimensional data models
• Handle metadata related activities such as creation of logical and physical metadata, importing the logical
metadata, etc.
• Validation
3. Creation of Reports
• Generate various kinds of reports from the data model
• Validation
4. Creation of Database
• Create sql code from data model and co-ordinate with DBAs to create database.
• Check to see data models and databases are synchronized
• Validation
5. Support and Maintenance
• Assist developers, ETL, BI team and end users to understand the data model.
• Maintain change log for each data model.
• Validation

June 26, 2024 80

Data Modeling Tools
• A number of Data Modeling tools exist to transform business requirements into
logical data model , and logical data model to physical data model.

• From physical data model , these tools can be instructed to generate SQL code
for instantiating the physical schema.
Examples of Data Modeling tools
Tool Name Company Name
ERWin Computer Associates

Embarcadero Embarcadero Technologies

Rational Rose IBM Corporation

Adex TCS

Power Designer Sybase Corporation

Oracle Designer Oracle Corporation

Xcase RESolution LTD.

June 26, 2024 81

Data Modeling Reports
• From Data Modeling tools, reports can be easily generated for technical
and business needs.

• The reports that have been generated from logical data model and
physical data model are called as business reports and technical reports
respectively.

• Most of the data Modeling tools provide default reports like subject area
reports, entity reports, attribute reports, table reports, column reports,
indexing reports, relationship reports etc.

• Other than default reports provided by data Modeling tools, a data

modeler can also create customized reports as per the needs of an
organization.

June 26, 2024 82

ERWin
• All Fusion ERWin Data Modeler commonly known as ERWin, is a powerful
and leading data Modeling tool from Computer Associates

• ERWin can generate the DDL (sql) scripts from a data model or it can create
data models from the existing database

• ERWin workplace consists of the following main areas:

–Logical: In this view, data model represents business requirements like
entities, attributes etc.
–Physical: In this view, data model represents physical structures like
tables, columns, data types etc.
–Modelmart: Many users can work with a same data model concurrently.

June 26, 2024 83

What can be done with ERWin ?
• Logical, Physical and dimensional data models can be created.

• Data Models can be created from existing systems (rdbms, dbms, files etc.).

• Different versions of a data model can be compared.

• Data model and database can be compared.

• SQL scripts can be generated to create databases from data model.

• Reports can be generated in different file formats like .html, .rtf, and .txt.

• Data models can be opened and saved in several different file types
like .er1, .ert, .bpx, .xml, .ers, .sql, .cmt, .df, .dbf, and .mdb files.

• By using ModelMart, concurrent users can work on the same data model.

June 26, 2024 84

ERWin Tool

June 26, 2024 85

Challenges while developing/redeveloping a Data Model

• A new application for OLTP (Online Transaction Processing), ODS

(Operational Data Store), data warehouse and data marts.

• Existing systems that need to change reports may require data

models to be re-written.

• Incorrect data Modeling in the existing systems.

• Constraints or limitations imposed (implicitly or explicitly) on the data

placed within the structure.

June 26, 2024 86

Data Modeling Overview Agenda
• Data Modeling Overview
• Database Development Cycle
• Three Schema Model
• TCS BIDS Domain Solutions
• Entity-Relationship (ER) Modeling
• Extended ER
• UML
• IDEF1X
• 4 Types of Relationships
• Domains
• Enterprise Data Modeling
• Standardization
• Roles
• Tools
• Challenges
• Other Topics
• Normalization
• Dimensional Modeling
• References

June 26, 2024 87

ER Modeling Normalization
• Normalization is a technique for producing a set of relations with desirable
properties, given the data requirements of an enterprise.

• The process of normalization is a formal method that identifies relations based on

their primary or candidate keys and the functional dependencies among their
attributes.

• Normalization is often executed as a series of steps. Each step corresponds to a

specific normal form that has known properties.

• As normalization proceeds, the relations become progressively more restricted in

format, and also less vulnerable to update anomalies.

• For the relational data model, it is important to recognize that it is only first normal
form (1NF) that is critical in creating relations. All the subsequent normal forms
are optional.

• Will be covering Normalization as a separate topic

June 26, 2024 88

Dimensional Modeling
• Dimensional Data Modeling comprises of one or more dimension tables and fact
tables.

• Dimension table is one that describes the business entities of an enterprise,

represented as hierarchical, categorical information such as time, departments,
locations, and products. Dimension tables are sometimes called lookup or
reference tables.

• A fact (measure) table contains measures (sales gross value, total units sold) and
dimension columns. These dimension columns are actually foreign keys from the
respective dimension tables.

• The performance of dimensional data Modeling can be significantly increased

when materialized views are used.

• Materialized view is a pre-computed table comprising aggregated or joined data

from fact and possibly dimension tables which also known as a summary or
aggregate table.

June 26, 2024 89

Example of Dimensional Modeling

June 26, 2024 90

Dimensional Modeling (contd.)
• A dimensional database is designed and tuned to support the analysis of
business trends and projections.

• Dimensional Modeling optimizes the database for data retrieval and analysis.

• Some of the decisions to be made during the design of a dimensional model are:
– The business processes to be selected for analysis of the subject area to be
modeled.
– Granularity of the fact tables.
– Dimensions and hierarchies to be identified for each fact table.
– Measures for the fact tables.
– Attributes for each dimension table.
– Pattern selection (Star schema, Snowflake schema or Starflake schema)

• Will be covering Dimensional Modeling as a separate topic

June 26, 2024 91

References

1. The Data Modeling Handbook – A Best-Practice Approach to Building Quality Data

Models – Michael Reingruber, William W. Gregory, John Wiley & Sons, Inc., ISBN 0-
471-05290-6

2. Database Concepts – 2nd edition, David M. Kroenke, Pearson Prentice Hall, ISBN 0-13-
145141-3

June 26, 2024 92

June 26, 2024 93