You are on page 1of 18

UNIVERSITY

OF SAN CARLOS
SCHOOL OF ARTS AND SCIENCES
DEPARTMENT OF COMPUTER AND INFORMATION SCIENCES

Database Management Project Guidelines and Documentation Format


This aims to guide the database management students of the Department of Computer and
Information Sciences in determining system proposal and documentation.

Prepared by:

Glenn B. Pepito
S.Y. 2015 2016, 2nd Semester


TABLE OF CONTENTS

Section 1. What is a Database Project?


Database Project
A database project is required for BSIT, BSCS and BSICT undertaking Database
Management courses.
The Project focuses on developing data-driven and dynamic applications to
address the needs or improve current organizational processes or transactions,
specially in handling information.
The project may be in the form of a:
Web Application
Mobile Application
Desktop Application
It is expressly understood that Database projects need not require surveys,
statistics, and descriptive methods, unless deemed necessary.

Section 2. Scope of a Database Project

The Project should integrate the different principles and best practices in database
management. Students are expected to apply database management principles and
concept to solve problems and improve management of data in organizations.
The course instructor will determine the appropriate complexity level of the specific
problem being addressed and the proposed solution, considering the duration of the
project, the composition of the team, time frame and the resources available.
Section 3. Suggested Areas for DB Project

Information Systems Development for an actual client


Web Applications Development
Mobile Computing Systems
E-Learning Systems
Interactive Systems
Information Kiosks

ii

Section 4. Suggested Themes


How can database management be able to contribute to the following:
Food
Health
Water
Waste
Energy
Disaster and Risk Management
Governance
Education
Business
Section 5. Project Duration
Students are given ample time to finish their projects.
Students will enroll two semesters to complete their project
Information Technology

IT 130 Database Management I (3 units)


IT 136 Database Management II (3 units)

Information and Communications Technology

ICT 131 Database Management I (3 units)


ICT 136 Database Management II (3 units)

Computer Science

CS 130 Database Management I (3 units)


CS 134 Database Management II (3 units)

Section 6. Composition of Groups

Students will work in teams of four (4) members depending on the complexity of the
project.

iii

Section 9. Proposal Guidelines

DOCUMENT FORMAT GUIDELINES

Paper and Font. Use 8.5 X 11. Use one side of the page only. Use Arial for font style and
font size 12-point.

Margins. Left 1.5 inches; top, bottom, and right, 1 inch.

Spacing. Use 1.5 spacing for the text. Use single space for table and figure captions.

Figures and Illustrations. Figures, tables, graphs, etc., should be positioned and labeled
appropriately. Figure # should be placed bottom center of the figure. Table # should be
placed upper left of the table

Page Number. Show page number at the bottom right side of the page

Title Page. No page number but counted as page i

Approval Sheet. No page number but counted as page ii

Acknowledgement. Counted as page iii. Page number shown

Abstract. Counted as page iv. Page number shown

Table of Contents. Counted as page v. Page number shown

List of Figures. Counted as page vi. Page number shown

List of Tables. Counted as page vii. Page number shown

Chapter 1. Begin page number at 1, page number is shown and onwards


White Short Bond Paper (8.5 X 11)

1.5

1
iv

PROPOSAL ORAL EXAMINATION GUIDELINES


All students are required to undergo a PROPOSAL ORAL EXAMINATION at the end of the
semester for Database Management I.

a. The three possible verdicts after the defense are:


ACCEPT WITH REVISIONS. Minor revisions are necessary to enhance the document, but
they do not have to be presented in front of the panelists. The panelists are tasked to make
sure that all the revisions are made.

REPROPOSE. Another presentation is necessary because the proponent failed to present


his/her project properly and/or the documentation contains major errors.

b. After revisions are made, the proposal will then be approved for Database Management II.

Marvels E-Commerce System

Presented to the
Department of Computer Science
University of San Carlos Technological Center

In partial fulfillment of the requirements for


CS 134 - Database Management

Submitted by:
Glenn B. Pepito
Glenn B. Pepito
Glenn B. Pepito
Glenn B. Pepito
Submitted to:
Mr. Glenn B. Pepito, MBA

March 2015

vi

Acknowledgement

Table of Contents
Acknowledgement ............................................................................................................................... i
List of Figures ..................................................................................................................................... iii
List of Tables ...................................................................................................................................... iv
1. Introduction ................................................................................................................................. 1
1.1
1.2
1.2.1
1.2.2
1.3
1.4
1.4.1
1.4.2

System Rationale .......................................................................................................................... 1


System Objectives ........................................................................................................................ 1
General Objective ................................................................................................................. 1
Specific Objectives ................................................................................................................ 1
Significance of the System ............................................................................................................ 1
Scope and Limitations .................................................................................................................. 1
Scope .................................................................................................................................... 1
Limitation ............................................................................................................................. 1

2. Design .......................................................................................................................................... 2
2.1
2.1.1
2.1.2
2.2
2.3
2.4
2.5
2.6

Business Process ........................................................................................................................... 2


Old Process ........................................................................................................................... 2
New Process.......................................................................................................................... 2
ERD ............................................................................................................................................... 2
Normalization (3rd NF) ................................................................................................................. 2
Design Issues ................................................................................................................................ 2
Hardware Interface ...................................................................................................................... 2
Software Interface ........................................................................................................................ 2

3. Conclusion and Recommendation .............................................................................................. 3


3.1
3.2

Conclusion .................................................................................................................................... 3
Recommendation ......................................................................................................................... 3

Appendix ............................................................................................................................................. 4
Panel Recommendation and Suggestions .......................................................................................... 5
Installation Manual ............................................................................................................................. 6
User Manual ........................................................................................................................................ 8

ii

List of Figures

iii

List of Tables

iv

1. Introduction
1.1 System Rationale
This section discusses the reason and relevance of the study. It should contain the
following information:

Trends
Company background
Problem
How it can be addressed using database driven applications

1.2 System Objectives


1.2.1

General Objective

State your objective in just one sentence.


1.2.2

Specific Objectives

State the underlying objectives that must be met to attain your main objective.

1.3 Significance of the System


Enumerate the beneficiaries of your system and how/what they can benefit from your
system

1.4 Scope and Limitations


1.4.1

Scope
Discuss the capabilities of your system

1.4.2

Limitation
Discuss what your system cant do in relation to what is generally expected of
your system.

2. Design
2.1 Business Process
2.1.1

Old Process

Provide a flowchart and a textual description of that flowchart


2.1.2

New Process

Provide a flowchart and a textual description of that flowchart of the process with the system

2.2 ERD
One page make sure it is readable

2.3 Normalization (3rd NF)


One page make sure it is readable

2.4 Design Issues


What were the issue that you met when designing the system or implementing the system?

2.5 Hardware Interface


What are the hardware components that we need to run, operate or access the system?

2.6 Software Interface


What are the software that we need to run and operate the system?

3. Conclusion and Recommendation


3.1 Conclusion
Based on the system you have developed, did you meet your objectives?

3.2 Recommendation
What can you recommend to the future developers who reads this, in terms of features, design, etc.

Appendix

Panel Recommendation and Suggestions


Installation Manual

User Manual