IE 302 SYSTEMS ANALYSIS AND DESIGN

LECTURE 5_CHAPTER 6
SYSTEMS ANALYSIS: STRUCTURING SYSTEM REQUIREMENTS
CONCEPTUAL DATA MODELING
DR. HUSAM KAID
Copyright © 2015 Pearson Education, Inc. Publishing as Prentice Hall
1
 Lesson Overview
▪ This lecture introduces students to data modeling concepts.
▪ Data models show the definition, structure, and
relationships within data.
▪ The following Figure shows that data modeling is
performed during systems analysis.
▪ Data modeling is important because:
1) The characteristics of data captured during data
modeling are crucial in the design of databases,
programs, computer screens, and printed reports;
2) Data rather than processes are the most complex
aspects of many modern information systems;
3) The characteristics about data are permanent;
4) Structural information about data is essential to
generate programs automatically.
2
 Conceptual Data Modeling
▪ Representation of organizational data
▪ Purpose is to show rules about the meaning
and interrelationships among data
▪ Entity-Relationship (E-R) diagrams are
commonly used to show how data are
organized
▪ Main goal of conceptual data modeling is to
create accurate E-R diagrams
▪ Methods such as interviewing, questionnaires,
and JAD are used to collect information
▪ Consistency must be maintained among
process flow, decision logic, and data
modeling descriptions
 The Process of Conceptual Data Modeling

▪ First step is to develop a data model

for the system being replaced
▪ Next, a new conceptual data model is
built that includes all the requirements
of the new system
▪ In the design stage, the conceptual
data model is translated into a
physical design
▪ Project repository links all design and
data modeling steps performed during
SDLC
 The Process of Conceptual Data Modeling
▪ As Figure 7–2 shows,
different kinds of data
models and database
design occur during
the systems
development life cycle
 Deliverables and Outcome
▪ As Figure 7–3 shows, the entity-relationship diagram
is the primary deliverable of conceptual modeling.
▪ Conceptual modeling results in as many as four
diagrams, including:
✓ an E-R diagram that covers just the data needed in the
project’s application;
✓ an E-R diagram for the application system being
replaced;
✓ an E-R diagram for the whole database from which the
new application’s data are extracted;
✓ and an E-R diagram for the whole database from
which data for the application being replaced is drawn.
▪ Conceptual modeling also produces a set of entries
about data objects; these entries are stored in the
project repository.
 Deliverables and Outcome
▪ Sample conceptual data
model diagrams using
Visio E-R notation.
 Introduction to Entity-Relationship Modeling

▪ Notation uses three main constructs

✓Data entities

✓Relationships

✓Attributes

▪ Entity-Relationship (E-R) Diagram

✓A detailed, logical, and graphical representation of

the entities, associations and data elements for an
organization or business
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Entity
Instances of entities
✓Person: employee, student, patient
✓Place: state, region, country, branch
✓Object: machine, building, automobile,
product Dick Schwartz
✓Event: sale, registration, renewal John Jones
✓Concept: account, course, work center
✓Represented by a rectangle in E-R
diagrams
▪ Entity Type Employee
✓A collection of entities that share
common properties or characteristics
Entity
▪ Entity Instance
✓Single occurrence of an entity type
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Attribute Entity Instance of an Attributes
(employee) Attribute
✓A property or characteristic
that is common to some or
all of the instances of an ID. 1:
NAME: Smith Employee
entity. ID.
JOB: Operator
✓Examples:
o Student: student_id,
student_name, address, ID. 2:
NAME: Jones Employee
phone_number, major JOB: Supervisor Name
o Automobile: vehicle_id,
color, weight, horsepower
ID. 3:
o Employee: employee_id, NAME: Starbuck
employee_name, address, JOB: Pilot Employee
skill Job
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Attribute Hair Color
Gender

Employee Number

16482 F Brn 25

13258 M Red 18
Employee Number
Gender
Hair Color
Age
Age
Employee
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Candidate Keys
✓An attribute (or combination of attributes) that uniquely E-R diagram
identifies each instance of an entity type.
▪ Identifiers
✓A candidate key that has been selected as the unique,
identifying characteristic for an entity type.
✓For each entity, the name of the identifier is
underlined on an E-R diagram.
E-R diagram by Microsoft Visio
✓The following diagram shows the representation for a
STUDENT entity type using E-R notation:
✓The equivalent representation using Microsoft Visio
is the following:
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Multivalued attribute
✓An attribute that may take on more than one
value for each entity instance
E-R diagram
✓Suppose that Skill is one of the attributes of
EMPLOYEE.
✓If each employee can have more than one Skill,
then it is a multivalued attribute.
✓The first is to use curly brackets around the
name of the multivalued attribute, so that the
EMPLOYEE entity with its attributes is
diagrammed as follows:
 Entity-Relationship (E-R) Modeling (Key Terms)
▪ Relationship
✓An association between the
instances of one or more entity types
that is of interest to the organization
✓Relationships are always labeled
with verb phrases
✓For example, a training department
in a company is interested in
tracking which training courses each
of its employees has completed
(called Completes, between the
EMPLOYEE and COURSE entity)
types that we diagram as follows:
 Conceptual Data Modeling and the E-R Model

▪ Goal

✓Capture as much of the meaning of the data as possible

▪ Result

▪ A better design that is easier to maintain

 Degree of Relationship
▪ Degree
› Number of entity types that
participate in a relationship
▪ Three Cases:
› Unary
o A relationship between the instances
of one entity type
› Binary
o A relationship between the instances
of two entity types
› Ternary
o A simultaneous relationship among
the instances of three entity types
o Not the same as three binary
relationships
 Cardinalities in Relationships
▪ Suppose that two entity types, A and B, are
connected by a relationship
▪ The cardinality of a relationship is the
number of instances of entity B that can (or
must) be associated with each instance of
entity A.
▪ Minimum Cardinality
✓The minimum number of instances of
entity B that may be associated with each
instance of entity A
▪ Maximum Cardinality
✓The maximum number of instances of
entity B that may be associated with each
instance of entity A
 Associative Entity
▪ An entity type that associates the instances
of one or more entity types and contains
attributes that are peculiar to the
relationship between those entity instances
▪ For example, suppose that the organization
wishes to record the date (month and year)
when an employee completes each course.
Some sample data follow:
 An Example of Conceptual Data Modeling at Hoosier Burger
▪ The Hoosier Burger’s
food ordering system
example illustrates how to
prepare a conceptual data
model
▪ Figure 7–9 is the level-0
data flow diagram for
Hoosier Burger’s new
logical inventory control
system
 An Example of Conceptual Data Modeling at Hoosier Burger
▪ Figure 7–10 is the
preliminary E-R
diagram for Hoosier
Burger’s inventory
control system
 An Example of Conceptual Data Modeling at Hoosier Burger
▪ Figure 7–11 is
the final E-R
diagram for
Hoosier
Burger’s
inventory
control system
Exercises from Textbook
7-17. Assume that at Pine Valley Furniture each product (described by Product No., Description, and
Cost) is comprised of at least three components (described by Component No., Description, and Unit of
Measure) and components are used to make one or many products (i.e., must be used in at least one
product). In addition, assume that components are used to make other components and that raw
materials are also considered to be components. In both cases of components being used to make other
components, we need to keep track of how many components go into making something else. Draw an
E-R diagram for this situation and place minimum and maximum cardinalities on the diagram.
PE # 1

Product Component
PK Product No PK ComponentNo

Cost C_Description
P_Description UnitOfMeasure

Comprised Of GoesInto
3 PK,FK2,I2 Product No PK,FK1,I1 ComponentNo
PK,FK1,I1 Component No PK SubComponentNo

C_Quantity Quantity
Exercises from Textbook
7-19. A restaurant chain has several
store locations in a city (with a name Restaurant Manager
Restaurant_ID Manager_ID
and zipcode stored for each), and each Name Name
is managed by one manager. Managers zipcode
manage only one store. Each restaurant
location has its own unique set of
menus. Most have more than one menu
(e.g., lunch and dinner menus). Each Menu
Menu_ID
menu has many menu items, and items Type
can appear on multiple menus, and
with different prices on different
menus. Represent this situation of
restaurants with an E-R diagram.
Menu_Menu_Item Menu_Item
Menu_ID Menu_Item_ID
Menu_Item_ID Name
Price
Exercises from Textbook
7-24. Draw an E-R diagram
to represent the sample
customer order in the
following Figure.
Exercises from Textbook
7-24. Draw an E-R diagram for each of the following situation:
A laboratory has several chemists who work on one or more projects. Chemists also
may use certain kinds of equipment on each project.
• Attributes of CHEMIST include: Employee_ID (identifier), Name, and Phone_No.
• Attributes of PROJECT include: Project_ID (identifier) and Start_ Date.
• Attributes of EQUIPMENT include: Serial_No and Cost.
• The organization wishes to record Assign_Date—that is, the date when a given
equipment item was assigned to a particular chemist working on a specified project.
• A chemist must be assigned to at least one project and one equipment item.
• A given equipment item need not be assigned, and a given project need not be
assigned either a chemist or an equipment item.
• Provide good definitions for all of the relationships in this situation.
Exercises from Textbook
7-24. Solution:
Questions?

27