STUDENT INFORMATION MANAGEMENT SYSTEM: ASYSTEM PROPOSAL FOR

LICEO DE CAGAYAN UNIVERSITY-COLLEGE OF INFORMATION TECHNOLOGY

A Project Proposal

Presented to

Ms. Aurora Cindy Agno-Balabat

Professor of the School of the Graduate Studies

Liceo de Cagayan University

In Partial Fulfillment of the Subject

Computer System and Database Management

by

JUAN DELA CRUZ

April 2013

1 inch

Capitalized, single space

1 ½ inches

1 inch

1 inch

(centered, balanced, double space)

Make the necessary adjustments

ACKNOWLEDGMENT

The researchers wish to thank the following for their valuable contributions

toward the completion of this study.

Dr. Puerting J. Otoga, for his scholarly suggestions and for painstakingly

encouraging the researchers to finish this humble work.

The Faculty of the College of Information Technology, for their….

double space

bold

TABLE OF CONTENTS

PAGE

TITLE PAGE i

ACKNOWLEDGMENT ii

LIST OF TABLES iii

LIST OF FIGURES iv

CHAPTER

I INTRODUCTION 11.1 Background of the Study 1 1.2 Significance of the Study1.3 Scope and Limitation of the Study

II REVIEW OF LITERATURE AND STUDIES

III REQUIEREMENTS ANALYSIS AND DESIGN3.1 Analysis and Design3.2 System Design

3.2.1 Use Case Diagram3.2.2 Use Case Description3.2.3 Sequence Diagram3.2.4 Activity Diagram3.2.5 Entity Relationship Diagram3.2.6 Data Dictionary3.2.7 Design features and User Interfaces (optional)

IV SYSTEM AND HARDWARE REQUIREMENT4.1 Hardware Requirements4.2 Software Requirements4.3 System Support

V SUMMARY, CONCLUSION AND RECOMMENDATION

BIBLIOGRAPHY

APPENDIX

A List of Plates

B Curriculum Vitae

LIST OF TABLES

Table Page

1 Use Case for View Customer Record 20

2 Use Case for Update Payments 20

LIST OF FIGURES

Figure Page

1 Water Fall Model 6

2 Current System Flow Diagram 14

CHAPTER 1

INTRODUCTION

1.1 Background of the Study

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

1.2 Significance of the Study

The finding of this study will be beneficial to the following:

The Management. The result can be used as …………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

The Users ………………………………………………………………………….

………………………………………………………………………………………………

………………………………………………………………………………………………

1.3 Scope and Limitation of the Study

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

double space

double space

double space

double space

double space

bold

CHAPTER 2

REVIEW OF LITERATURE AND STUDIES

The following are reviews, which show significant leanings to the study. They are

grouped into the following headings: Local Literature, Foreign Literature, and Local

Studies, and Foreign Studies.

Local Literature

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

Foreign Literature

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

Local Studies

………………………………………………………………………………………………

Introductoryparagraph

double space

double space

………………………………………………………………………………………………

………………………………………………………………………………………

Foreign Studies

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

CHAPTER 3

REQUIREMENTS ANALYSIS AND DESIGN

This chapter begins with

………………………………………................................

………………………………………………………………………………………………

………………………………………………………………………………………………

3.1 Analysis and Design

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

Inputs

…………………………………………………………………………….....

………………………………………………………………………………………………

introductoryparagraph

………………………………………………………………………………………………

Process

………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

Outputs

………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

3.2 System Design

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

3.2.1 Use Case Diagram

Login

Curriculum Tour

Make Questionnaire

View Student Password

Exam Access

Figure 1 Use Case Diagram for Instructor, Administrator, and Registrar

Figure 2 Use Case Diagram for Student

View Student Score

Add School Year

Instructor Registration

View Instructor Password

Instructor Admin/Registrar

Add Sections

Sign-up Registration

Curriculum Tour

Take Examination

Student

Logout

Login

Logout

3.2.2 Use Case Description

Table 1Use Case for Log-in

Use case name LoginActor Admin/Registrar/Instructor/StudentDescription This use case is used by the actors to access the system.Normal Flow 1.) The user invokes the use case by clicking the “Login”

button.2.) The user enters login name and password.3.) The system verifies and validates the login name and password.4.) Use case instance terminates.

Alternate Flow If login name and password is invalid, user has to re-enter a valid user name or password.

Precondition User must be registered.Post-condition User can access the system or just exit the website.Assumption User is on the website.

3.2.3 Sequence Diagram

Admin/Instructor/Student

Figure 3 Sequence Diagram for Login

3.2.4 Activity Diagram

Figure 4 Activity Diagram for Login

SAMPLE3.2.5 Entity Relationship Diagram

manpower_qualificationhas

3.2.5 Entity Relationship Diagram

Figure 6. Entity Relationship Diagram

Diagram

user_type

has

has

project_order

has

has

services

service_template

equipment

skills

client

manpower_profile

manpower_assignment

has

has

has project_orderdetails

has

has

has

has

has

has

branch

project_progress

progress_chart has

has

has

has

equipment_detail ha

shas

has

manpower_skills

progress_chart_details

has

has

Figure 7. project_order Table

end_date

amount

has

client_id

po_number

start_date project_order

service_id

project_orderdetails

duration

status

Figure 8. client Table

user_id

password

project_order

company

has

client_id

client

contact

emailAddressss

firstname lastnamebranch_id

3.2.6 Data Dictionary

FIELD NAME DATA TYPE SIZE VALUE DESCRIPTION

client_id Integer 11 NOT NULL (PK)Client ID

firstname Varchar 50 NOT NULLClient’s First

Name

lastname Varchar 25 NOT NULLClient’s Last

Name

contact Varchar 50 NOT NULL Client’s Contact

company Varchar 50 NOT NULL Company Name

email Varchar 11 NOT NULLCompany Email

Address

branch_id Integer 11 NOT NULL (FK)Branch ID

password Varchar 100 NOT NULL Client password

user_id Integer 11 NOT NULL (FK)User Type

FIELD NAME DATA TYPE SIZE VALUE DESCRIPTION

po_number Integer 11 NOT NULL(PK)Project

Order Number

start_date Date/Time NOT NULLProject Start

Date

Amount Integer 6 NOT NULL Amount/Budget

end_date Date/Time 11 NOT NULLProject End

Date

client_id Integer 11 NOT NULL (FK)ID of Client

service_id Integer 11 NOT NULL(FK) Service ID

availed

Duration Integer 3 NOT NULL Duration

Status Integer 2 NOT NULL Project Status

client(Keeps client information)

project_order(Keeps record of project orders)

3.2.8 Design Features and User Interface

Figure 9. Client Registration Panel

Figure 10. Login Dropdown Panel

CHAPTER 3

SYSTEM AND HARDWARE REQUIREMENTS

4.1 Hardware Requirements

A. Server

B. Client

4.2 Software Requirement

Visual Basic, Visual Fox Pro, C++, Delphi

4.3 System Support

System Analyst, Programmer, Network Administrator

CHAPTER 4

SUMMARY, FINDINGS, CONCLUSIONS, AND RECOMMENDATIONS

This chapter presents the …………………………………………………………...

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

SUMMARY (paragraph form)

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

FINDINGS (itemized)

1. ………………………………………………………………………………

2. ………………………………………………………………………………

CONCLUSIONS (paragraph form)

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………………

………………………………………………………………………………………

RECOMMENDATIONS (itemized)

1. ………………………………………………………………………………

2. ………………………………………………………………………………

Introductory paragraph

3. ………………………………………………………………………………

BIBLIOGRAPHY

Books

1. McFadden Fred and Jeffrey Hoffer. Modern Database Management. Addison-Wesley Educational Publishers, Inc., 1999.

2. Sommerville, Ian. Software Engineering. England: Addison Wesley Publishing Company, Inc., 1994.

Journal and Periodicals

1. Computer World “State University Computerized Registration Process” (Oct., 15, 1999) pp. 8.

2. Smart Computing “Online Learning” (Nov., 1999) Vol. 10 Iss. 11, pp. 36-38

Internet Web Pages

1. Computer Assisted Personalized Approach: assignments, quizzes, and examinations in an active learning environment.http://www.capa.msu.edu

2. Online Classhttp://www.onlineclass.com

APPENDIX

A. LIST OF PLATES

Plate Page

1 Interview with the hospital administrator 52

B. CURRICULUM VITAE

A. Personal Background

NAME :ADDRESS :DATE OF BIRTH :AGE :CITIZENSHIP :STATUS :MOTHERS NAME :FATHERS NAME :HEIGHT :WEIGHT :HOBBIES :

B. Educational Attainment

ELEMENTARY :

SECONDARY :

COLLEGE :

DEGRESS :

GRADUATESTUDY :

C. Job Experiences

YEAR COMPANY POSITION