2025-01-18

8
System Analysis and Design
Course Code IT223
Faculty of Computing and Information Technology

Structuring System Data Requirements

Dr. Mohammed Shobail

1

Conceptual Data Modeling

Conceptual data modeling:

a detailed model that captures the overall structure of data in an
organization

Independent of any database management system (DBMS)

or other implementation considerations

1
 2025-01-18

The Conceptual Data Modeling Process

Develop a data model for the current system.
Develop a new conceptual data model that includes all requirements
of the new system.

In the design stage, the conceptual data model is translated into a
physical design.

Deliverables and Outcome

Entity-relationship (E-R) diagram or UML class diagram
Entities (or classes) – categories of data, represented as rectangles

Relationships (or associations) – lines between the entities

2
 2025-01-18

Deliverables and Outcome (Cont.)

Set of entries about data objects to be stored in repository project
dictionary, or data modeling software

Repository links data, process, and logic models of an information system.

Data elements included in the data flow diagram (DFD) must appear in
the data model and vice versa.

Each data store in a process model must relate to business objects

represented in the data model.

Definitions and Symbols

6
FIGURE 8-1: Sample conceptual data model

3
 2025-01-18

Gathering Information for Conceptual Data Modeling

Two perspectives on data modeling:
Top-down approach for a data model is derived from an intimate
understanding of the business.
Bottom-up approach for a data model is derived by reviewing
specifications and business documents.

Introduction to Entity-Relationship(E-R)Modeling
Entity-Relationship data model (E-R model): a detailed, logical
representation of the entities, associations and data elements for an
organization or business area
Entity-Relationship diagram (E-R diagram): a graphical representation
of an E-R model

4
 2025-01-18

Introduction to Entity-Relationship(E-R)Modeling

9
FIGURE 8-2: (E-R Model) and (E-R Diagram)

Introduction to Entity-Relationship (E-R)

Modeling (Cont.)

Entity: a person, place, object, event or concept in the user

environment about which data is to be maintained
Entity type: collection of entities that share common properties or
characteristics
Entity instance: single occurrence of an entity type

10

5
 2025-01-18

Introduction to Entity-Relationship (E-R)

Modeling (Cont.)

11
FIGURE 8-3: Basic E-R notation

Introduction to Entity-Relationship (E-R)

Modeling (Cont.)

12
FIGURE 8-4: Basic E-R notation

6
 2025-01-18

Introduction to Entity-Relationship (E-R)

Modeling (Cont.)
Unary relationship: a relationship between the instances of one
entity type
Also called a recursive relationship
Binary relationship: a relationship between instances of two entity
types
Most common type of relationship encountered in data modeling
Ternary relationship: a simultaneous relationship among
instances of three entity types
13

Naming and Defining Entity Types

An entity type name should be:
A singular noun.

Descriptive and specific to the organization.

Concise.

Event entity type should be named for the result of the event, not the
activity or process of the event.

14

7
 2025-01-18

Attributes
Attribute: a named property or characteristic of an entity that is of
interest to the organization
Naming an attribute: i.e. Student_ID
Place its name inside the rectangle for the associated entity in
the E-R diagram.

15

Naming and Defining Attributes

An attribute name is a noun and should be unique.
To make an attribute name unique and for clarity, each attribute
name should follow a standard format.
Similar attributes of different entity types should use similar but
distinguishing names.

16

8
 2025-01-18

Candidate Keys and Identifiers.

Candidate key: an attribute (or combination of attributes) that
uniquely identifies each instance of an entity type
Identifier: a candidate key that has been selected as the unique,
identifying characteristic for an entity type

17

Other Attribute Types

Multivalued attribute: an attribute that may take on more than one
value for each entity instance
Repeating group: a set of two or more multivalued attributes that
are logically related

18

9
 2025-01-18

Other Attribute Types

19
FIGURE 8-5: Multivalued attributes and repeating groups

Relationships
Relationship: an association between the instances of one or more
entity types that is of interest to the organization
Degree: the number of entity types that participate in a relationship

20

10
 2025-01-18

Relationships

21
FIGURE 8-6: Examples of relationships of different degrees

Naming and Defining Relationships

A relationship name is a verb phrase; avoid vague names.

A relationship definition:
Explains what action is to be taken and possibly why it is important.
Gives examples to clarify the action.

22

11
 2025-01-18

Representing Supertypes and Subtypes

Subtype: a subgrouping of the entities in an entity type
Is meaningful to the organization
Shares common attributes or relationships distinct from other
subgroupings
Supertype: a generic entity type that has a relationship with one or
more subtypes

23

Representing Supertypes and Subtypes

24
FIGURE 8-19: Example of supertype/subtype hierarchy

12
 2025-01-18

Assignment

What are the difference between Structuring

System Data Requirements and Structuring
System Process Requirements ?

‫ما هو الفرق بين متطلبات بيانات نظام الهيكلة ومتطلبات عملية‬

‫نظام الهيكلة؟‬
25

13