I.

CAPSTONE PROJECT AGENDA

The capstone project agenda of the Information Technology and Management
Department are the following, but not limited to:
1.
2.
3.
4.
5.
6.
7.
8.

II.

Education studies
Health studies
Industry/Business studies
Agriculture studies
Environment studies
Government studies
Socioeconomic Development and poverty alleviation studies
Social Networking studies

DESCRIPTION OF CAPSTONE PROJECTS

A. BS IT Capstone Project
BS IT Capstone Project focuses on system development for infrastructure,
application or processes which serves as innovative computing solution.
B. BS IS Capstone Project
BS IS Capstone Project focuses on system development primarily on designing
and developing infrastructure system plan based on IT frameworks which
serves as a computing solution for the evaluation, creation or improvement of
business processes.

III.

IT RESEARCH BY ACM (American Computing Machinery)

The document format is following the ACM format.

IV. SUGGESTED AREAS OF CAPSTONE PROJECT

The Capstone Project should integrate the different courses, knowledge, and
competencies learned in the curriculum. Students are encouraged to produce

innovative results, generate new knowledge or theories, or explore new frontiers of

knowledge or application areas.
The following are suggested research areas for each capstone project:
Bachelor of Science in Information Technology
1. Software Development

Software Customization
Information Systems Development for an actual client (with final testing
and implementation)
Web Applications Development (with final testing on live servers)
Mobile Computing Systems-apps

2. Multimedia Systems

Game Development
e-Learning Systems
Interactive Systems/Moodle
Information Kiosks

3. Network Design and Implementation and Server Farm Configuration

and Management
4. IT Management

V.

IT Strategic Plan for sufficiently complex enterprises

IT Security Analysis, Planning and Implementation

CAPSTONE PROJECT TEAM

The Capstone Project team is composed of at most four (4) members. The
following are the roles that the Proponentsshould play:

Leader-Project Manager (PM) - The person with authority to manage

aCapstone Project. This includes leading the planning and the development of
allCapstone Project deliverables. The project manager is responsible for the
budget, work plan and all Project Management Procedures (scope management,
issues management, risk management, etc.). He/She is responsible for the
success of the entire activity.

Systems Analyst / Database Designer (SA/DD) the person who checks that
all parts of the system are coordinated. The person who makes sure that the
database design is complete and robust. He/She coordinates well with the PM.
Network Designer / UI Designer (ND/UID) The person who masters the
systems network design and prepares the User-Interface design (Forms/ Screen
Shots/ Storyboard). He/She coordinates well with the SA/DD.
Software Engineer / Programmer (SE/P) - The person who design, write, and
test computer programs. He/She coordinates well with the ND/UID.
QA Tester/ Technical Writer (QA/TW) - A person who ensures the quality of the
software product and help find and eliminate any bugs. He/She determines the
functionality of every aspect of a particular application. A person who finalizes
theCapstone Project study document. He/She coordinates well with the SE/P.

Duties and Responsibilities of the Proponents

1. Must comply on the Capstone Project Guidelines and Policies of the
department.
2. Must comply of the schedule ofCapstone Project activities, required
deliverables and deadlines posted by the Class Instructor.
3. Must meet all deadlines for deliverables specified in this document including
specified requirements by the Class Instructor and Technical Adviser.
4. Must comply on time of all the requirements identified by the Capstone
Project Defense Panel.
5. Must comply the requirements identified by the Class Instructor and Technical
Adviser throughout the duration of the Capstone Project.
6. Must meet the Class Instructor for consultation before the Capstone Project
Defense.The meetings serve as a venue for the proponent to report the
progress of their work, as well as raise any issues or concerns.
7. Must comply with the requirements of the beneficiary provided that it
harmonizes with the panelist suggestions and recommendations during the
defense. In case conflict arises the Proponents must consult the Technical
Adviser.
Guidelines on Regrouping
1. Regrouping will be allowed only during ITRP1 with valid reason (i.e.
irreconcilable differences)
2. Regrouping will be allowed if less than 3 of the group members remain.
Should this happen, the group may be disbanded and members of the
affected group may join other groups provided they donot exceed 4 members.
a. Regrouping with Passing Grade

The remaining members must continue with their proposal. In case of

topic ownership conflict and/or change of scope, the members must seek
consent from the Class Instructor for approval.
b. Regrouping with Failing Grade
The members may be allowed to regroup but cannot use the existing
proposal.
VI.

GRADING SYSTEM
The Proponents grade will be computed using the following breakdown:
BS Information Technology
IT Capstone Project 1
Class Adviser 10%
Technical Adviser 15%
Pre-Defense 30%
Final Defense 40%

XIV.

IT Capstone Project 2
Class Adviser 10%
Technical Adviser 10%
Pre-Defense 20%
Final Defense 60%

LIST OF DELIVERABLES
A. Documentation
Chapter 1 PROBLEM AND ITS BACKGROUND
1.1 Project Context
1.1.1 Introduction
1.1.2 Background of the Study
1.2 Purpose and Description
1.3 Objectives of the Study
1.3.1 General Objective
1.3.2 Specific Objectives
1.4 Scope and Limitations
1.5 Significance of the Study
1.6 Definition of Terms
Chapter 2 REVIEW OF RELATED LITERATURES AND STUDIES
2.1 Local Literatures
2.2 Local Studies/Systems
2.3 Foreign Literatures
2.4 Foreign Studies
Chapter 3 METHODOLOGY, RESULTS, AND DISCUSSION
3.1 Requirement Analysis
3.1.1 SDLC/MDLC
3.1.2 Conceptual Paradigm

3.1.3 Flow of Existing System

3.1.3.1 Flowchart/Wireframe
3.1.3.2 DFD/UML(Use Case)
3.1.4 Flow of the Proposed System
3.1.4.1 Flowchart/Wireframe
3.1.4.2 DFD/UML(Use Case)
3.2 Requirement Documentation
3.2.1 Methods of Research
3.2.2 Research Instruments
3.3 Technical Background
3.3.1 Product Description
3.3.2 Economic Use of the Product
3.3.3 User Requirements
3.3.4 System Requirements
3.4 Development and Testing
3.5 Description of Application
3.6 Implementation Plan
3.7 Implementation Result
Chapter 4 SUMMARY, CONCLUSION, AND RECOMMENDATION
4.1 Summary
4.2 Conclusion
4.3 Recommendation
Chapter 5 ACKNOWLEDGEMENT
Chapter 6 REFERENCES
APPENDICES
A. Gantt Chart of Development Schedule
B. Presentation of Findings
C. SurveyForms(Initial and Final)
D. Approval for Testing (Initial and Final)
E. Certificate of Implementation
F. Certificate of Authentic Authorship
G. Users Manual
H. Curriculum Vitae