(Group-3) Formative Assessment 1
(Group-3) Formative Assessment 1
CCS0021L
(INFORMATION MANAGEMENT)
[F1-FORMATIVE]
Formative Assessment 1
EXERCISE
1
EXPLORING THE ORACLE ENVIRONMENT AND DATA
MODELING USING E-R MODEL
Name Role
Miguel Osinada Leader
Members (if Group): Carlos Aguila Member
Christian Valdez Member
Jhone Bautista Member
Section:
TW291
Professor:
Prof. Regina Santos
4. Relational Models
This part consists the Tables, Views, Foreign keys, Schemas, Subviews, Physical Models and
Displays of the Logical Model when converted to its relational model equivalent.
These will appear when the + button is clicked beside the Relational Models
BACKGROUND INFORMATION
Logical Data Model
Entity-Relationship Diagram (ERD) is a detailed, logical and graphical representation of the entities,
associations and data elements for an organization or business area.
Associative entity is 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. It is a relationship that can be
modeled as an entity type.
Relationship Types
● One-to-One (1:1)
● One-to-Many (1:M) or Many-to-One (M:1)
● Many-to-Many (M:M)
● Then you will see in the center the Logical (Untitled 1) as your work area
● Note: If the
Logical Model tool is not found,
just right click on the blue area
near the Menu bar and click
Logical Model on the options found
II. Now let us create a sample entity relationship model using the example below.
Create an entity relationship diagram of the following:
In this ERD, the business rule indicates that each department can have one or more employees or
many employees work in only one department.
Step 1: On the logical model work area, add a new entity by clicking on the “new entity” button.
Then click the + cursor on the work area, you will have something like this
Add another attribute by clicking the green + sign, then on the attribute properties type in the following:
Name: DeptName
Datatype: Logical
Type: varchar
Size: 100
Click “Mandatory” because a department name should not be blank
Then click ok.
Step 4: Create another entity using steps 1-3 but for the Employee entity.
Add the following attributes to the Employee entity
Attribute 1:
Name: EmployeeId
Datatype: Logical
Type: Numeric
Precision: 11
Scale: 0
Tick the “Primary UID” because this attribute is the primary key, and then click Apply.
Attribute 2:
Name: EmployeeName
Datatype: Logical
Type: varchar
Size: 100
Click “Mandatory” because a name of the employee should not be blank
Step 5: Let us add a relationship between entities. Since the relationship is one to many, click the button
“1:M relation” button. Then click on the entity Department entity and click on the employee entity to get a
new dialog box like this:
Then type the details and options found on the picture above. Then click ok and you will have something
like this:
Prepare an E-R diagram for an online shop. The following describes this organization:
Business Rules:
Task 1
Analyze the business rule and fill-in the relationship matrix in Table 2.2 to track the existence of
relationships between entities.
Draw a fully attributed ERD with keys based from the relationship
matrix you have created in Task 1. Draw it in Oracle SQL Developer Data Modeler. Once the model is
done, take a screenshot of your work and paste it here.
DOCUMENTATION:
● Hoffer, Jeff (2016). Modern Database Management 12th edition. Pearson Education Limited
● Young, M. (2010). Oracle Data Modeling and Relational Database Design, Vol. 1 Student Guide,
Oracle.