Database Systems: Design, Implementation, and Management 13 Edition
Database Systems: Design, Implementation, and Management 13 Edition
3
DATABASE SYSTEMS, 13TH EDITION
Data Model Basic Building Blocks
Entity: anything about which data are to be
collected and stored
Attribute: a characteristic of an entity
Relationship: describes an association among
entities
One-to-many (1:M) relationship
Many-to-many (M:N or M:M) relationship
One-to-one (1:1) relationship
Constraint: a restriction placed on the data
4
DATABASE SYSTEMS, 13TH EDITION
Business Rules
Descriptions of policies, procedures, or principles within
a specific organization
Apply to any organization that stores and uses data to
generate information
Description of operations to create/enforce actions
within an organization’s environment
Must be in writing and kept up to date
Must be easy to understand and widely disseminated
Describe characteristics of data as viewed by the
company
5
DATABASE SYSTEMS, 13TH EDITION
Discovering Business Rules
Sources of business rules:
Company managers
Policy makers
Department managers
Written documentation
Procedures
Standards
Operations manuals
Direct interviews with end users
6
DATABASE SYSTEMS, 13TH EDITION
The process of identifying and documenting business
rules is essential to database design for several
reasons:
They help standardize the company’s view of data.
They can be a communications tool between users
and designers.
They allow the designer to understand the nature,
role, and scope of the data.
They allow the designer to understand business
processes.
They allow the designer to develop appropriate
relationship participation rules, constraints and to
select an accurate data model.
7
DATABASE SYSTEMS, 13TH EDITION
Examples of Business Rules
A customer may generate many invoices.
An invoice is generated by only one
customer.
A training session cannot be scheduled for
fewer than 10 employees or for more than 30
employees.
8
DATABASE SYSTEMS, 13TH EDITION
Examples of Business Rules
Note that those business rules establish entities,
relationships, and constraints.
For example: the first two business rules establish
two entities (CUSTOMER and INVOICE) and a
1:M relationship between those two entities.
The third business rule establishes a constraint (no
fewer than 10 people and no more than 30 people),
two entities (EMPLOYEE and TRAINING), and a
relationship between EMPLOYEE and
TRAINING.
9
DATABASE SYSTEMS, 13TH EDITION
Another Example:
Of course, not all business rules can be
modeled.
For example, a business rule that
specifies that “no pilot can fly more
than 10 hours within any 24-hour
period” cannot be modeled.
However, such a business rule can be enforced by
application software.
10
DATABASE SYSTEMS, 13TH EDITION