Sei sulla pagina 1di 11

(DATABASE MANAGEMENT SYSTEMS 1)

EXERCISE

1
(Exploring the environment of the Oracle 11g)

Name of Student
Kimberly S. Belo
Date Performed
August 26, 2016

Name of Professor
Mr. Anthony Aquino
Date Submitted
August 26, 2016

I. OBJECTIVES
At the end of this exercise, students must be able to:
a) Know how to use SLQ Developer Data modeler
b) Knows how to install oracle 11g database
c) Familiar with the short options used in modeling data

II. BACKGROUND INFORMATION

1.
2.
3.
4.

1. Menu Bar Consists of the File, Edit, View, Team, Tools and Help.
2. Browser Toolbar It consists the overview of the Logical Model (3) and Relational
Model (4) of the ERD.
3. Logical Model
This part consists of the Entities, Relations, Inheritances, Views, Subviews, and Display
which will be used during the ER modeling
These will all appear if your click on the + sign of the Logical model

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

By default, the relational model will be labeled Relational_1.

III. PROCEDURES
Instructions:
I.
Starting a Logical Model
Right click on the Logical tab inside the Browser toolbar and click Show

Then you will see in the center the Logical (Untitled 1) as your work area

Your work area

And you will see these Logical model tools above when your Logical Model
work area is opened
Logical Model
tools

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

Lets go over the common buttons used in Logical Model tools

Default size
New
Zoom1:N
in (One To many)
Delete
Fit
Screen
relation
New M:N(Many to Many)
Zoom out
relation
select

New entity

New 1:1 (One To One)


Relation

Engineer to Relational
Model

II.

The select button selects the entities available.


The new entity button creates a new entity.
The new M:N relation button creates a many to many relationship between
entities.
The new 1:N relation button creates a one to many relationship between
entities.
The new 1:1 relation button creates a one to one relationship between entities.
The delete button deletes the object on the Logical model work area.
The Engineer to Relational Model button converts the Logical model to a
relational model.
The Zoom in button zooms in the object or the area
The Zoom out button zooms out the object or the area
The Fit screen button fits the object on the size of the screen
The Default size button makes the area in default screen size.

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

Step 2: On the general tab, on the name text box, write the name Department. Do not close
the window yet. Click on the Attributes tab. You will have something like this:

Step 3: On the attributes, click the + sign to add an attribute.

On the attributes properties type in the following:


Name: DeptId
Datatype: Logical
Type: Numeric
Precision: 11
Scale: 2
Tick the Primary UID because this attribute is the primary key, and then click Apply.
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: 2
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
Then click ok.

You should be having something like this:

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:

Step 6: The current logical diagram notation above is Barker notation. Let us change it to
Information Engineering notation by clicking on the View tab of the Menu bar, then click on
Logical Diagram notation, and click Information Engineering notation.

Your diagram will look like this:

VI. Assessment
Department
Subject Code
Description
Term/Academic Year

Information Technology
ITESPEC1
Database Management Systems 1
1

Topic

The database environment and


development process

Lab Activity No 1
Lab Activity
Exploring the environment
of the Oracle 11g and SQL
data modeler
CLO
1
Note: The following rubrics/metrics will be used to grade students output in the lab
exercise 1.

Criteria
Creation of entity

Descriptions
Points
The two entities in the example is done 20
properly

Completeness of attributes

The attributes and attribute properties


are done correctly and completely.
This is for the entity department and
employee
Used the 1:M relation button to create
the relationship between entities
Correct label and correct options were
made
The notation was changed to
information engineering notation

Relationship
Relationship properties
Information Engineering
notation
Total

40

20
10
10
100%

V. REFERENCES
Young, M. (2010). Oracle Data Modeling and Relational Database Design, Vol. 1 Student
Guide, Oracle.

Potrebbero piacerti anche