Model Data Object
This module introduces the Model Data Object, covering
conceptual data models, normalization, and data model
validation. It aims to equip you with the skills to identify
entities, attributes, data types, and relationships, design ER
diagrams, apply normalization rules, and validate data models.
The module is structured into three units, each focusing on a
specific aspect of data modeling. These units will guide you
through analyzing business data operations, understanding
system scope, and documenting entity relationship diagrams.
AT
by Addisu Tesfa
Analyzing Business Data Operations
Understanding Business Operations Analyzing Business Operations
Business operations are ongoing cyclic activities Operational analysis is used to understand and
that produce value by harvesting it from tangible or develop operational processes. It measures
intangible assets. These operations encompass performance against standard costs and services,
generating recurring income, increasing asset considering how goals can be achieved better and
value, and securing income and value. more cost-effectively.
It addresses customer results, strategic and business results, financial performance, and innovation, seeking
to satisfy customer needs better and use technology to provide superior services at lower costs.
Major Data Analysis Methods
Text Analysis
Discovers patterns in large datasets using data mining
tools, transforming raw data into business information
for strategic decisions.
Statistical Analysis
Involves collecting, analyzing, interpreting, presenting,
and modeling data to analyze a dataset or sample.
Diagnostic Analysis
Identifies the causes of events by finding insights from
statistical analysis, useful for recognizing data behavior
patterns.
Defining System Scope and
Boundaries
System Scope System Boundaries
The scope defines what the Boundaries identify where
system will and will not the system starts and ends,
include, detailing functional, including databases,
non-functional, and pseudo applications, servers,
requirements. operating systems, and
gateways.
Conceptual Model
The conceptual model defines the system's boundaries,
identifying external events, actors, information flow, major
functions, and user population.
Clarifying system boundaries ensures a clear understanding of the
system's responsibilities and components.
Entities, Attributes, and Relationships
Entity Attribute
An entity is a real-world object about which data An attribute is a property that describes an entity,
can be stored, such as a school, student, or course. such as an employee's name, age, or address.
It is an abstract concept representing instances in a Attributes can be simple, composite, single-valued,
system. or multi-valued.
Relationships capture how entities are related, represented by lines between entities. These relationships can
be one-to-one, one-to-many, or many-to-many.
Normalization and Business Data
Business Data Normalization Rules
Identify suitable business data Understand normalization
by understanding business rules to eliminate redundancy
processes, conducting and improve data integrity,
stakeholder interviews, and following normal forms like
reviewing existing 1NF, 2NF, and 3NF.
documentation.
Benefits
Normalization reduces storage space, enables faster searches,
improves data integrity, and provides a more efficient database
structure.
Analyze sample data, identify key business rules, and consider future
growth to ensure the normalized database meets evolving needs.
Data Model Validation with Client
Collaboration
Involve the client throughout the data modeling process,
from requirements gathering to validation.
Requirements Alignment
Ensure the data model aligns with the client's
requirements and objectives, accurately representing
desired functionality.
Review and Feedback
Present the data model to the client for review and
feedback, allowing them to evaluate and provide input.
Validate accuracy, completeness, consistency, and usability, iterating
until the data model meets client expectations.
Documentation and Approval
Documentation Client Approval
Document the completed data model, including ER Submit the modeling data object to the client for
diagrams, entity descriptions, attribute definitions, final approval, presenting the data model and
and relationship descriptions. addressing any questions or concerns.
Maintain a version control system and obtain signed approval to ensure a clear record of the agreed-upon
data model for future reference.
