Professional Documents
Culture Documents
Employee Customer
Job
Data Flow Diagram
Context Diagram
Customer Request
Confirm-
ation
Babysitter
Information Availability
System
Assignment
Employee
Data Flow Diagram
Level 1
Request
Assignment
Confirm- 1. Availability
ation Assign Avail 2.
Employee Times Record
New Avail-
Current ability Avail
Job
D1 | Customer Times
Assign
D2 | Employee
D3 | Jobs
Communications Model
• A representation of the location at
which data is stored and processed and
the communications links that connect
them.
Entity Relationship Models
A good E-R model has
One table for every entity in the business
system
Correctly drawn relationships indicating 1-1
or 1-m cardinalities
Optionality indicators to support needed
referential integrity
ENTITY:
A person, place, object, event, or
concept about which the
organization wishes to maintain
data.
• Must need to store data
• Must have at least two attributes
• Must have at least two records
ENTITY TYPES
classes of people, objects or concepts
about which we wish to store data.
become tables in a new computer
system.
Instances are rows
explicitly need
• Must have the same data type for all
entity occurrences
RELATIONSHIP: .
A connection between entity instances in
different entity classes
• Must specify what row connects with
Entity
Key
Attribute ...... Attribute
Diagrams:
Repeating Groups
Course
SectionNum
E-R MODEL:
• MULTI-VALUED ATTRIBUTES can be indicated
on an E-R graph by using a double line
around the bubble..
• REPEATING GROUPS are stored differently in
structured models (hierarchical or network)
than in relational models.
• DERIVED VALUES: cause data consistency
problems and are not normally included in a
database.
PREMIERE PRODUCTS
EXAMPLE
The Premier Products Company is a wholesale
hardware company that provides products to
customers. Each customer is served by a
salesman who processes orders. The
salesmen is paid from commissions earned on
each customer order. A customer places an
order by calling the company and contacting
the salesman. The salesman records the
ordering person, products and quantity
ordered.
PREMIERE PRODUCTS:
REPEATING GROUPS
In the Premier Products Company each
salesmen is paid from commissions earned on
each customer order. A customer places an
order by calling the company and contacting
the salesman. The salesman records the
ordering person, products and quantity
ordered. The order consists of Customer data,
Salesman data and a list of products, price,
and quantity for the products that the customer
wants delivered. The attributes {PRODUCT,
PRICE, QUANTITY} constitute a repeating
group.
Example: Order
ORDER PRODUCT PRICE QUANTITY
5103 IRON 17.95 11
SKILLET 19.95 6
Section
CourseSection
Instructor
InstructorID
Diagrams:
m:n Relationships
CourseSection StudentID
Section Student-Section
CourseSection
Student
StudentID
Optionality
(Referential Integrity)
Records in a table that have a relationship
with another table may be restricted by
optionality requirements.
Relationship Optional
integrity enforced)
Optionality
Optional (0 allowed)
1
Optionality
A constraint should be mandatory only if
the relationship must be known
whenever a record is first entered.
Most relationships are optional.
Maintaining Integrity
If a parent record is deleted then an
optionality relationships can be
maintained in several ways
Cascade delete
Cascade update
Cascade null
Data