Вы находитесь на странице: 1из 9

Republic of the Philippines

HYRONS COLLEGE PHILIPPINES, INC.


Sto. Niño, Tukuran, Zamboanga Del Sur

DEPARTMENT OF INFORMATION TECHNOLOGY

Outcomes-Based Education Syllabus in IT

DATABASE MANAGEMENT 2
Course Syllabus

First Semester
S.Y. 2019 – 2020
VISION
The IT department as a leader institution in the development of competent and skilled professionals that
contribute to the promotion of quality in changing life of the people of Tukuran, Zamboanga del Sur and to the nearby
municipalities.

MISSION
Pursuant to the vision, the College commits to:

 Continuously improve the value we can deliver and the impact we can create - one opportunity, one individual at
a time;
 Empowering innovation in our society by enabling ground-breaking organizations in the province of Zamboanga
del Sur to work with exceptional individuals; and
 Provide potential IT expert to be relevant to the changing needs of the community.

GOALS AND OBJECTIVES


A. Goals
The IT Department aims to:
1. Demand excellence in its IT systems which should be reliable, efficient, robust, secure and fit for
purpose;
2. Provide competent and skilled professionals, technical and updated instructions in various disciplines;
and
3. Inculcate socio-economic, cultural, political, moral and spiritual values.

B. Objectives

1. To be responsive to the requirements of the college;


2. To embed quality management throughout the life-cycle of IT services and projects;
3. Hone skills of students in academic excellence through competitive and desirable work ethics.

Course no. : IT 302


prerequisite : IT 203
Type of course : Discussion/ Hands-on/Actual
Units : 3

Course Description
This course is a continuation of ( IT 203- Database Management 1) This gives emphasis of the students to develop and design simple
program using the different SQL commands. The course reviews topics such as conceptual data modelling, relational data model, relational
query languages, relational database design and transaction processing and current technologies such as semantic web, parallel and noSQL
databases.
Course learning Outcomes:
Upon completion of this course, the students will be able to:

LO 1: Have a broad understanding of database concepts and database management system software

LO 2: Have a high-level understanding of major DBMS components and their function

LO3: Be able to model an application’s data requirements using conceptual modeling tools like ER diagrams and design
database schemas based on the conceptual model.

LO4: Be able to write SQL commands to create tables and indexes, insert/update/delete data, and query data in a relational
DBMS.

LO5: Be able to design interface using forms


MAJOR COURSE OUTPUT:

LEARNING OUTCOME REQUIRED OUTPUT DATE

LO 1: MCO 1:
Have a broad understanding of database concepts and  Understand terms related to database design
database management system software and management an Understand the objectives
of data and information management

LO 2: MCO 2:
Have a high-level understanding of major DBMS  Understand the database development process
components and their function and Understand the relational model and
relational database management system

LO 3: MCO 3:
Be able to model an application’s data requirements using  Assess data and information requirements and
conceptual modeling tools like ER diagrams and design Construct conceptual data models
database schemas based on the conceptual model

MCO4:
LO4;  Develop physical data models for relational
Be able to write SQL commands to create tables and database management systems and Implement
indexes, insert/update/delete data, and query data in a relational databases using a MySQL DBMS
relational DBMS.

Learning Plan:
Class Schedule
LO Topics and Readings Learning activities
(weeks)
Database system
What is DBMS and what is provides
LO1 When to use files and when to use a DBMS Week 1-4  Lecture and Discussion
How data can be encoded and stored files  Written Assignments
Writing a program to query large CSV files

 Exam (Prelim) Week 5


Difference between different types of query languages
Set semantics and bag semantics
 Demonstration
Algebra operators including extended operators under both set and bag
LO2 Week 6-8
semantics  Written Assignments
datalog
Queries using both relational algebra and datalog  Presentation (Reporting)
 Exam(Midterm) Week 9
SQL
Single block SQL queries

LO3 SQL queries using set (and bag) operators. Week 10-12

SQL queries with correlated sub queries  Lecture and discussion


Structure data using Data models  Presentation
(reporting)
Conceptualize data using different data models
Data modeling tools like entity-Relationship diagram
 Exam (Semi-Final) Week 13
Translate data models into relational table schema  Lecture and Discussion
Data Normalization  Presentation
LO4 Week 15
Functional dependencies and their relationship to keys
BCNF and 3NF
Identify tables that are not normalize
Decompose unnormalized tables into BCNF and/or 3NF compliant tables
LO5 Week 16-17
Query processing in DBMS
How queries are processed, optimized and evaluated in a DBMS
Query execution plan
Creating Forms
Customizing Forms

create tables and indexes, insert/update/delete data, and query data in a


relational DBMS
 Lecture and Discussion
 Presentation
 Reporting
 Exam (Final) Week 18

Rubrics
Criteria Outstanding Adequate Not adequate
Overall crow’s Logically designed the database design Exhibited a partial understanding of
foot model exhibiting a firm understanding of Crow's Foot database design and Exhibited minimal understanding of Crows's
Crow's Foot notation manipulation. Foot database design and manipulation
Completely and accurately explained Some minor innaccuracy when Inaccurate design explanation in regard to design
design usage and purpose explaining design usage and purpose usage and purpose
Table creation Created all of the tables defined in Created most of the tables defined in
project requirements project requirements Partially created some of the tables defined in
Named tables appropriately in regard to Table name was a little unclear in project requirements
their data elements regard to its data elements Table name did not correlate to its data elements
Relation and Correctly Interpreted most Business Incorrectly Interpreted the Business Rules, few
cardinalities Correctly interpreted all the Business Rules and created most of the necessary relations were created and few indications to
Rules and created all necessary relations with some indication to Cardinalities and Normal forms
relations with clear indication to the cardinalities and observing at least two
cardinalities and observing the three normal forms.
normalizations forms.
Keys and entities Correctly choose all primary and Correctly choose most of the primary Incorrectly choose most of the primary and
foreign keys respecting the naming and foreign keys respecting the naming foreign Keys, and somehow respected the
convention convention naming convention
Implementation Completely populated tables with Populated tables with majority of data Populated tables with minimal data elements
correct data elements reflecting the elements outlined in the ERD design defined in project the ERD design
ERD design
Mechanics Accurately entered data elements into Entered data elements into tables with Multiple keypunch errors when entering data
tables with no keypunch errors minimal keypunch errors elements into tables
No spelling or grammar errors in Some minor spelling or grammar errors Numerous errors.
database documentation evident in documentation
Reports Created all of the reports needed for Created some of the reports needed for Created minimal reports needed for the
the as defined in project requirements the company as defined in project company as defined in project requirements.
Report name is indicative of data it will requirements Report names does not indicate what data will
return Report name partially correlates to the be returned
data it will return

I. SUGGESTED https://whatis.techtarget.com/definition/operating-system-OS
READINGS:
https://www.includehelp.com/operating-systems/process-management-of-operating-system.aspx
https://www.techopedia.com/definition/1832/file-management-system
II. REFERENCES/ 1. Operating System Concepts (2012) by Silberschatz, Galvin and Gagne. 
BOOKS :
2. https://www.includehelp.com/operating-systems/process-management-of-operating-system.aspx
III. GRADING SYSTEM The grading system is averaging, that is,
Final Grade = Prelim Grade + Midterm Grade + Tentative Final Grade
3
Computation Formula (In all Criteria)
50/PS x SS + 50 = SG Where: PS = Perfect Score
SS = Student Score
SG = Student’s Grade
Major Examinations (Prelim, Midterm, Final)- 40%
Quizzes 30%
Other Requirements 30%
Total 100%
IV. INSTRUCTOR’S CLASSROOM POLICY Quizzes and Examination. All quizzes are announced. No special quiz shall be given to a student who fails to
take a quiz even for a valid reason. The Examinations are compulsory; failure to take any of them will result in
an Incomplete (INC) grade.
Class Participation and Attendance. Class decorum and attendance of NMSC students are governed by the
norms and rules set in the HCPI student manual.
The following Computer Laboratory User Guidelines are to be followed at all times:
 Only bona fide students of the subject /course during the period as well as authorized personnel of the school
are allowed inside the Computer Laboratory (lab).
 Students are not allowed to stay inside the lab without the supervision of the instructor.
 Students can only bring pen and notebook/paper in their designated work areas. All other personal belongings of
students must be deposited in the shelves.
 Students are enjoined to work with minimal noise, even in group work.
 Everyone is encouraged to back up their work proactively.
 Eating, drinking, smoking inside the laboratory and vandalism on the computer facilities are strictly prohibited.
 Unauthorized changing of the settings/configuration of lab facilities and units is strictly prohibited.
 Use of lab computers is for class-related work. Recreational and personal use of lab facilities (e.g., use of internet
for personal concerns, use of computer unit to edit the work of a family member/friend, games not intended for
class/teaching work) are strictly prohibited.
 Pornography is strictly prohibited.
 Diskettes, CDs, flash disks and software from unreliable sources must first be scanned for possible virus
infection/computer damage and cleared with the instructor before being used in the lab.
 Use of electronic gadgets (e.g. mobile phones, video cameras, computer peripherals not needed in class) inside
the lab is strictly prohibited. Mobile phones must be in silent mode at all times.
 Lab users must observe cleanliness and orderliness in the lab. Before leaving the lab, students must rearrange all
chairs and properly turn off computer units.
 Students of the last class for the day must properly turn off all equipment and units, and the instructor must lock
the door.
 Attendance logbook shall be properly filled up by the students/users and countersigned by the
instructor before and after the use of facilitie.
Prepared by: Recommending by: Approved:

ANTOINETTE JANE CRAUSOS ROSHERME F. MUNOZ,MSIT DIANALYN C. PAUBSANON


Instructor Dean, IT Department Academic Head

Вам также может понравиться