1

CAPSTONES PROJECT GUIDELINES

For IS 25 (Capstone 1) and IS 27 (Capstone 2)
I. Introduction
The BSIS program is based on the policies and standards for Information Technology
Education (ITE) Programs and competencies on the ICT sector recognized by Technical
Education Skills and Development Authority (TESDA) and the standards set by the Association
for Computing Machinery (ACM), the world’s largest educational and scientific society. The
program is ladderized from Associate in Computer Technology (ACT) to Bachelor of
Information Systems (BSIS) to meet the CHED Memo Order No. 37 Series of 006 Revised
Policies, Standards and Guidelines on the Implementation of the Ladderized Interface between
Technical-Vocational Education Training (TVET) and Higher Education (HE).
The program prepares students to IT Professionals and be expert on design and
implementation of IS for business processes. After satisfactorily completing all the requirements
leading to BSIS degree, students may qualify for but not limited to be : business process analyst,
data quality specialist, entrepreneur in IT industry, IS instructor, system auditor, quality
assurance analyst, system implementer officer and technical support specialist.
Capstone Project is required for the BSIS program. It is a culminating activity that
generates an output useful in the development of solutions. It maybe but not limited to business
application development, systems analysis and design, or an Information Systems plan (CMO 53
s. 2006). It focuses on business processes and the implications of introducing a computing
solution to a problem and the students must discuss clearly the changes on the
affected business processes, information flow, and information policies. The skills, methods and
theories learned by the students in their stay in the BSIS program are applied in this output-
oriented course. This is a very special course in the BSIS program. Students do it in the final year
of studies and it is their opportunity to demonstrate that they can indeed meet the levels
of performance expected of an IT professional. The Capstone Project includes project proposal,
feasibility studies, intellectual property, teamwork, budget, schedule, management, professional
communications (i.e. reports, presentations), planning, design, implementation, deployment,
and testing. Students will be expected to meet a number of strictly enforced milestones and to
take considerable initiative in realizing specific goals. Moreover, the Capstone Project is a way
of determining whether students are ready to graduate.
The guidelines set in this document are planned to establish uniformity and consistency on
the format and organizational structure of the thesis and capstone projects in the Information
Technology department. Information Systems students preparing a capstone project are
encouraged to read and follow the style and format recommended on this manual with the
guidance of their research instructor and/or thesis/capstone project faculty adviser.
II. CP 1 & 2 Description and Objectives
IS 25 - Capstone 1 Description
A course requiring a more defined system specifications and preliminary design
of the capstone project. As a completion of this course, the groups (usually composed
 2

of 3-5 members) are required to present the complete functional prototype of the
capstone project to a panel.
IS 27 -Capstone 2 Description
This course is all about the culminating project that incorporates the knowledge
and skills that the IS students have developed during their stay in the college. The
project is the demonstration/manifestation that the group (same group from Capstone
1) developed an integrated understanding of their major field of study and that they
can apply the necessary information and communications (ICT) tools and in so doing,
generate new knowledge. In preparing the project, they will be guided by an adviser
and towards the end of the term; they will have to defend their project to the panel.

Capstone Project Objectives:

Although each Capstone Project is different and the relative emphasis will
vary, the course will involve students in:
• Bringing together and integrating knowledge and skills in the program as a
whole;
• Reinforcing and developing competencies that have not been
sufficiently emphasized in the fundamental subjects;
• Defining a substantial engineering study or design task and carrying it to
completion within a specified time and to a professional standard;
• Completing a comprehensive written and bound report that places the
Capstone Project in context, defines its objectives, and describes the
work done with the resulting conclusions or recommendations;
• Bridging the gap between the undergraduate studies and the
professional future, and demonstrating professional competencies and
capabilities;
• Demonstrating initiative and creativity, taking pride in the achievement of a
difficult task.

Through this course, students are prepared in their respective careers. The bulk of the
work (i.e., Capstone Project work itself) is to be done outside of the classroom.
III. Capstone Project Agenda
The Capstone Project agenda/thrust of the department are the following, but not limited
to:

 Policy Research on Information Technology

 Technological research for the advancement of Philippine Information Technology
 Breakthrough or pioneering researches
 Grid and cluster computing
 Low cost computing and open source
 Wired and wireless network technologies including internet connectivity to SUCs.
 3

 Foundations of computer science.

 Knowledge based technologies/Emerging technologies.

IV. Suggested Areas of Capstone Project

The Capstone Project must be useful to any establishment of the same nature or scope. It
must not exist or have been proposed by previous Proponents/Researchers. The Capstone Project
must not be developed using the off-the-shelf application programs. The proposed computerized
system may fall in any of the following categories, but not limited to:
1.) Software Development
- software customization
- information systems development for a actual client
- web applications development
- mobile computing systems
- decision support systems
- expert systems
- management information systems
- enterprise-wide systems
2.) IS Planning
- Enterprise Resource Plan
- Information Systems Strategic Plan
- Information Technology Planning, Management and Governance
3.) Analysis and Design of a sufficiently complex business system

V. Pre-requisites
The student must finish the following courses that prepare him/her to undergo a formal
capstone project/research study:
• IS 22 (ICT Project Research Methods) - for research methodologies (e.g. descriptive
research method)
• Eng 13 (Technical Writing/Communication for IT) - for formal articles/writing and
presentation skills
• IS 16 (Systems Analysis and Design) - for Software Development steps or life cycle
• IS 17 (Software and Information Engineering) - for software development paradigms
• IS 15 (Business Organization and Management– for business processes
• IS 21 (Evaluation of Business Performance)– for business process evaluation

VI. Capstone Project Team

The Capstone Project team is composed of at most five (5) members. The following are the roles
that the proponents/researchers should play:
 Project Manager (PM) - The person with authority to manage a Capstone
Project. This includes leading the planning and the development of all Capstone
Project deliverables. The project manager is responsible for the budget, work plan
 4

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
system’s 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
the Capstone Project study document, both the system and the Capstone
Project manuscript. He/she coordinates well with the SE/P.

Duties and Responsibilities of the Proponents

1. Keep informed of the Capstone Project Guidelines and Policies.
2. Keeps a log book recording all project work carried out and details of their project - dates,
results, references, calculations etc. This should be available at all times for possible
inspection by the adviser.
3. Get his / her log book signed by the adviser at an absolute minimum of once every 2 weeks.
4. Keep informed of the schedule of Capstone Project activities, required deliverables and
deadlines posted by Adviser and Dean.
5. Submit on time all deliverables specified in this document as well as those to be specified
by the Adviser and Dean.
6. Submit on time all requirements identified by the Capstone Project Oral Defense
Panel during the Oral Defense.
7. Submit on time the requirements identified by the adviser throughout the duration
of the Capstone Project.
8. Schedule regular meetings (at least once a month) with the Adviser throughout the
duration of the Capstone Project. The meetings serve as a venue for the proponent
to report the progress of their work, as well as raise any issues or concerns.
9. Schedule regular meetings (at least once in a semester) with the Dean throughout
the duration of the Capstone Project.
10. Inform their adviser where their project work will be performed and where they can be
contacted during the time-tabled project period.
11. Submit all documents and information on the dates prescribed.
12. In special cases, inform and ask approval of the adviser and the panel of examiners for
the changes that will be done on the topic presented and approved in the proposal.
 5

13. Strictly follow the schedule of project activities and required documents posted by
Adviser, Department Chairman, Dean and the Defense Panel.

Policy on Regrouping
Regrouping is allowed if less than 3 members of the group remain from IS 25
CAPSTONE1 to IS 27 / CAPSTONE2. Should this happen, the group may be disbanded and
members of these affected groups may join in other groups for as long as the maximum number
for each group is followed. However, if the remaining member(s) decide(s) to continue with
his/their Capstone Project, regrouping may not apply but with consent of the Adviser and
the Dean. Revision of the scope may then be an option. The title/topic to be pursued will then
be decided among the team members and the Dean.

Duties and Responsibilities as the Subject Teacher

1) Announce Capstone Project areas (at the start of the each semester) to the
students;
2) Conduct general meetings with the students to discuss the Capstone Project
Guidelines, Policies and Deliverables, and to allow the students to raise and clarify
issues;
3) Schedule Capstone Project activities, such as the deadlines of deliverables and
Proposal Hearing and Oral Defense sessions.
4) Post schedules, Proposal Hearing and Oral Defense guidelines, requirements
guidelines, and other announcements;
5) Furnish every member of the Proposal Hearing and Oral Defense panel with
all the necessary Capstone Project documents before the Proposal Hearing or Oral
Defense;
6) File at least one copy of the Proposal Hearing and Oral Defense panel's
evaluation (including revisions) and the Revised and Approved Deliverables at
every stage of the Capstone Project.
7) Submit collated grades of students under his/her section for that term.
Duties and Responsibilities as the Adviser
1) Ensures that the study proposed by the students conforms to the standard of the College
and has immediate or potential impact on the research thrust of the university.
2) Guides the Capstone Project students in the following tasks while in the proposal stage:
a. Defining the research objectives in clear specific terms.
b. Building a working bibliography for the research.
c. Identifying variables and formulating hypothesis, if any.
d. Determining research design, population to be studied, research environment,
instruments to be used and the data collection procedures.
3) Meets the team regularly (at least twice a month, NOTE: the team must seek
proper appointment) to answer questions and help resolve impasses and conflicts.
 6

4) Keep a record of their contact with the student and the project work done in accordance
with guidelines prescribed herein.
5) Points out errors in the development work, in the analysis, or in the
documentation. The adviser must remind the Proponents to do their work properly.
6) Reviews thoroughly all deliverables at every stage of the Capstone Project, to
ensure that they meet the department's standards. The adviser may also require
his/her Proponents to submit progress reports regularly.
7) Recommends the Proponents for Proposal Hearing and Oral Defense. The adviser should
not sign the Proposal Hearing Notice and the Oral Defense Notice if he/she believes
that the Proponents are not yet ready for Proposal Hearing and Oral Defense,
respectively. Thus, if the Proponents/Researchers fail in the Proposal Hearing or Oral
Defense, it is partially the adviser's fault.
8) Clarifies points during the Proposal Hearing and Oral Defense.
9) Must be physically present during the proposal and final oral presentation to provide
support and clarifications for and in behalf of the team.
10) Ensure that all necessary revisions, suggestions and recommendations are included in the
deliverables before final submission and acceptance.
11) Keeps informed of the schedule of Capstone Project activities, required deliverables and
deadlines.
12) Compute and submit the final grades of the students in the thesis/capstone project.
13) Recommends to the Proposal Hearing and Oral Defense panel the nomination of
his/her Capstone Project for an award.
14) As a special adviser, he/she is responsible to be:
i. A “parent”
ii. A provider
iii. An encourager
iv. A dictator
v. A pushy boss
vi. A connector
vii. An employment agency

VII. Panel Composition

The panel is composed of 1 Chairman, 2 members, and may include content experts and
recorder as assigned if necessary. Their duties and responsibilities include the following, but
not limited to:
Duties and Responsibilities of the Panel
Chairman
1) Brief the Proponents/Researchers about the Proposal Hearing or Oral Defense program
during the actual Proposal Hearing or Oral Defense, respectively.
 7

2) Issue the verdict. The verdict is a unanimous decision among the three members of
the Capstone Project Proposal Hearing or Oral Defense panel. Once issued, it is final
and irrevocable.
3) Nominate a Capstone Project for the Outstanding Capstone Project Award. Guidelines
for the Outstanding Research / Capstone Project Award will be provided separately.
Panel Members / Content Expert
1) Validate the endorsement of the adviser. The panel serves as "Internal
Auditors", putting some form of check and control on the kinds of
Capstone Projects being approved by the College.
2) Evaluate the deliverables.
3) Recommend a verdict.
4) Listen and consider the request of the adviser and/or the Proponents.
5) Nominate a Capstone Project for the Outstanding Capstone Project Award.
Guidelines for the Outstanding Capstone Project Award will be provided
separately.

VIII. Capstone Project Duration

The BSIS Capstone Project shall be completed within two semesters (IS 25 /
CAPSTONE1 and IS 27 / CAPSTONE2) with the following phases:
Pre-proposal Stage
• Course Enrolment
• Capstone Project Orientation
• Short Listing of Possible Research / Capstone Projects
• Title Critiquing and Patentability Check (Patent Searching) – via ITSO
• Pre-Proposal Statement Preparation
• Pre-Proposal Hearing
Proposal Stage
• Practical Examination of the chosen Programming Language (by team) - optional
• Writing of Chapters I, II, III, and IV (planning and design only)
• Proposal Manuscript Submission
• Proposal Hearing
• Proposal Manuscript Revisions
Oral Defense Stage
• Analysis
• Design
• Development
• Testing
• Prototype Submission (3 Loops)
1st loop- 30 50, 2nd loop- 51 to 70, 3rdloop- 71 to 99%
• Oral Defense Manuscript Submission (3 Loops)
• Oral Defense Proper
 8

• Oral Defense Manuscript Revisions

Patent Process (via ITSO – optional)
• Patent Drafting
• Patent Application (if possible)
• Technology Transfer
Public Presentation (CHED Memo Order. 53 Series of 2006)
• Public Presentation
• Public presentation is required. It should be a school-based presentation open for
public which may include the Poster category
• Other Options
-Regional Student Congress
-Presentations to Philippine Computing Science Congress of CSP, National
Conference on IT Education of PSITE
IX. Grading System
Proposal Stage (IS 25 / CAPSTONE1)
The Final Grade of each proponent will comprise of the following:
Average grade of the Panel Members including the Chairman 60%
Adviser of the Capstone Project / Group 30%
Co-Researcher (Peer Grading) 10%
TOTAL 100%

The rating of each proponent per panel member shall be based on the following rubric for
objective evaluation purposes:
Capstone Project Proposal Manuscript (group/team grade) 40%
Initial Pages 2
 Table of contents, list of figures, lit of tables is consistent
 Acknowledgement is brief and formal
 Executive summary is brief but complete
Chapter 1 10
 Project context is intact and provides clear overview of the entire
 Capstone Project
 Objectives of the project is SMART
 Purpose and description of the project is evidently discussed and
explained.
 Scope and Delimitation of the Capstone Project are clearly defined
 Terms are arranged alphabetically and defined operationally
Chapter 2 5
 Related literatures are recent and relevant
 Anchor provides solid background of the Capstone Project
 Auxiliary theories are evident
 Sources are appropriately cited and noted
 Related studies are relevant and includes global and local scope
 9

Chapter 3 & 4 15
 Methodology strictly follows the SDLC (esp. for Software Development)
 There should be comprehensive discussions on the technologies
(hardware/software) involved in the Capstone Project and its related
Capstone Projects in the past
 Methodology includes project management techniques appropriate for the
chosen Capstone Project.
 Requirements Specification is more or less complete and answers the
objectives
 Design Tools used are relevant and appropriate which should be
based on requirements
 Development Plan is concrete and should be consistent with the Design
Testing techniques to be used should assess all aspects of the developed
Capstone Project
 Implementation Plan should be aligned with the objectives
Final Pages 3
 Summary and Conclusions are attuned with the objectives
 Recommendations are feasible and practical
 References should be in university prescribed Format
 Appendices are relevant and help support the principal content
Manuscript Mechanics 5
 Organization and Fluidity of ideas are apparent
 Formatting and layout are consistent
 All parts of the manuscript should be grammatically correct

Oral Examination (Individual grade) 20%

Comprehensiveness of the Answer/Ideas 10
Contribution/Support to the Team 7
Delivery / Command of the English Language 3
The rating/evaluation of the subject/adviser for each of the Proponents/Researchers shall
be based on the following:
Subject/Adviser’s Grade 30%
Deliverables 20
Attendance 5
Journal Entries / Attitude / Behavior 5

Verdicts
 10

There will be three (3) possible verdicts after the Proposal Hearing. The verdict is
a unanimous decision among the three members of the Capstone Project Oral Defense
panel. Once issued, it is final and irrevocable.
APPROVED. Minor revisions are necessary but they do not have to be presented in
front of and checked by all panelists.35 – 40 (based on proposal manuscript score)
APPROVED WITH REVISIONS. Major revisions shall be incorporated in the final copy of
the revised Project Proposal summary. These must be checked by the panelists. 24 - 34
DISAPPROVED. The Proponents failed to propose a researchable or scholarly
Capstone Project. Below 24
System Oral Defense (IS 27 / CAPSTONE 2)
Capstone Project Output (Group Grade) 60%
Oral Examination (Individual Grade) same rubric with proposal 20%
Skills Test 20%
TOTAL 100%

Capstone Project Output (Group Grade) 60%

The output should be consistent with the objectives as defined 25
during the proposal stage
All major modules and features of the system’s output as defined after 25
the proposal stage are delivered. The credit shall be based on the
percentage of delivered items.
Group Debugging 10
• The team shall display competence in resolving planted bugs.
Verdicts
ACCEPTED WITH REVISIONS. Revisions are necessary but they do not have to be
presented
in front and checked by all panelists.56 to 80 (based on lowest score in the group and
excluding Skills Test score)
REORAL DEFENSE. Another Oral Defense session, in which all panelists must be present, is
necessary to further clarify the objectives and scope of the capstone project. Student must re-
apply for another Hearing Notice Form from the Office of the Dean if the Oral Defense is
scheduled after the semester ends.52 to 55 and upon the panel’s unanimous decision
NOT ACCEPTED. The proponent failed to achieve the objectives of the research established
in the proposal. The panelists’ numeric grades are not anymore needed. Below 52
 11

X. GUIDELINES
IS 25 / CAPSTONE1
1) The students shall form a team of 3-5 members. They then decide who plays the
pertinent roles. The team then submits Project Team Assignments Form
(Deliverable D1- Please refer to Appendix A. Project Team Assignments Form)
with signatures, to the Subject Teachers or the Dean’s Office.
2) The Proponents of the Capstone Project shall prepare 10 different possible
topics/titles, and present/consult these topics to any of the IT teachers or
any expert of the field. The Team shall ensure the novelty or patentability of the
Capstone Project using patent libraries online. The project manager would then
select 3 - 5 out of the 10 possible titles.
3) The Proponents shall make the Pre-Proposal Statements (Deliverable D2- Please
refer to Appendix B. Pre-Proposal Statement Template) of each of the selected
topics/titles.
4) The Pre-Proposal Hearing will be scheduled upon the completion of the
Pre-Proposal Statements. During this hearing, the team members, subject
teachers and the Dean shall convene and select only one of the 3 - 5 topics/titles
presented. Only the approved Capstone Project topics should proceed to the
research proposal stage. After a topic/title is finally chosen, the team then
accomplishes (in triplicate) a Project Working Title Form (Deliverable D3 - refer
to Appendix C. Project Working Title Form) which will then indicate the name
of the appropriate adviser as decided by the team of advisers together with the
proponents.
5) The team shall prepare all the parts of the proposal manuscript on time with the
set/agreed dates. The team always seeks approval from the adviser all the
required deliverables, by letting him sign/conform with the submitted
documents. By conforming, it means that the deliverable had been
checked/corrected diligently.
6) The researchers will ensure that the proposal is refined. Please refer to the
Capstone Project Study Manuscript Outline in Appendix D. Capstone Project
Manuscript Outline.
7) The researchers will prepare 4 copies of the Complete Proposal Manuscript
(Deliverable D4) for the Proposal Hearing. The Proposal Hearing Notice Form
(Deliverable D5 - refer to Appendix E. Capstone Project Hearing Notice Form)
from the Dean's Office should be filled out and complied. This notice and
the 4 copies of complete proposal manuscript must be submitted to the Adviser.
8) The Adviser forwards the Proposal Hearing Notice and the Complete Proposal
Manuscripts to the Dean's Office.
9) The Office will then arrange the date and time of the proposal hearing and
distribute the manuscripts to the identified members of the proposal hearing panel.
 12

10) The Dean assigns qualified and competent faculty members who will constitute
the proposal-hearing panel. The proposal-hearing panel shall be composed of the
following:
1 Chairman - preferably the Dean or a faculty with at least a master's
degree.
2 Members (one may be a content expert)
11) At the end of the proposal hearing, the chair makes a synthesis and announces the
panel’s verdict.
12) The chairman and the adviser shall ensure that all recommendations for
improvement by the proposal-hearing panel are incorporated in the Proposal
Manuscript. This may include grammar, accuracy of language, adequacy of data,
interpretation of results, etc.
13) The proposal is revised based on the recommendation of the panel members
during the proposal hearing.
14) The adviser shall guide the student researchers throughout the conduct of
the approved project proposal. The adviser is responsible for monitoring the
students and ensuring that the approved project design and methodology are
followed; appropriate data are gathered, analyzed and interpreted.
15) One copy of the Revised Proposal Manuscript (Deliverable D6) together
with the Grammarians Certificate (Deliverable D7 – refer to Appendix F.
Grammarian’s Certificate Template) shall be routed to the Adviser, Panel
members, and Chairman for the confirmation of revisions. Approval Sheet
(Deliverable D8 - refer Appendix J Approval Sheet) may be routed too for their
signatures if already amenable.
16) The hardbound copy containing the Approval Sheet and the Final Proposal
Manuscript (Deliverable D9) with the with the Proposal CD (Deliverable D10
– refer to Appendix L. CD Labeling Format) in a CD Jacket at the inlet portion
of the back cover should be submitted to the Dean’s Office. The color of the
hardbound is black with gold/yellow text. The CD Copy shall contain the
following:
a. Final Proposal Manuscript (word copy) – filename: Research /
Capstone Project Alias
b. Final Proposal Manuscript (pdf copy) – filename: Research /
Capstone Project Alias
c. Other pertinent files
17) Binding
a. Three (3) hard bound copies are required for submission.
b. The color of the hard bound cover of the thesis/capstone project document for
the bachelor’s program is brown.
c. All letters in the cover shall be in gold, font 14 using Bookman Old Style, and
all capital letters.
 13

IS 27 / CAPSTONE2
1) The team shall submit to their adviser on time (as scheduled) the 1st
prototype (30% to 50%) plus 1st draft (Deliverable D11); 2nd
prototype (51% to 70%) plus 2 draft (Deliverable D12); and 3rd
nd

prototype (71% to 99%) plus 3rd draft (Deliverable D13) of the

System/Output plus Oral Defense Manuscript, respectively. For monitoring
purposes, the team shall secure the Consultation Logs Form (Deliverable DX –
refer to Appendix M. Consultation Logs Form (Sample)).
2) If the 3rd prototype of the System/Output reaches the appropriate percentage to
completion as against major modules and features and the 3 rd draft of the
Oral Defense Manuscript is acceptable as evaluated and signed by the adviser
through Deliverable DX, team shall then prepare and submit to the Adviser the
Oral Defense Hearing Notice (Deliverable D14), 5 copies of the 8-10 page
Journal Format Paper (Deliverable D15 - refer to Appendix N.) and 1 copy of
the Complete Oral Defense Manuscript (Deliverable D16) ready for Oral
Defense.
3) The researchers will ensure that the Complete Oral Defense Manuscript is
refined which will be basis for the final 8-10 page Journal Format Paper. Please
refer to the Complete Oral Defense Manuscript Outline in Appendix D. Capstone
Project Manuscript Outline. The Adviser forwards the Oral Defense Hearing
Notice, 5 copies of the 8-10 page Journal Format Paper and 1 copy of the
Complete Oral Defense Manuscript to the Dean's Office.
4) The Office will then arrange the date and time of the oral defense and distribute
the 8-10 page Journal Format Paper to the identified members of the oral defense
panel.
5) The Dean assigns qualified and competent faculty members who will constitute
the Oral Defense panel. The Oral Defense panel shall be composed of the
following:
1 Chairman - preferably the Dean or at a faculty with least master's degree.
2 Members (one may be a content expert)
6) One of the members of the Oral Defense panel may be invited from outside the
University if the study requires his/her expertise.
7) During the Oral Defense, the adviser shall be the moderator who clarifies and
mediates over issues raised.
8) The college secretary or a designated recorder is tasked to record all the
suggestions and recommendations of the panel during the Oral Defense.
9) At the end of the Oral Defense, the chair makes a synthesis and announces the
verdict.
10) The Oral Defense panel chair and the adviser shall ensure that all
recommendations for improvement by the Oral Defense panel are
 14

incorporated in the final copies. This may include grammar, accuracy of

language, adequacy of data, interpretation of results, etc.
11) The team shall prepare and provide for the honoraria of the panel of examiners
immediately after the proceedings.
12) Approval Sheet (Deliverable D17), this time for the IS 27 / CAPSTONE2, is
necessary prior to the final submission of the manuscript and other research
transcripts.
13) The researchers must submit the 2copies of Oral Defense CD’s (Deliverable D18
– refer to Appendix O. CD Labeling Format). Each of the Oral defense CD’s
should contain the following:
Complete documentation
i. Final Oral Defense Manuscript (word file)
ii. Final Oral Defense Manuscript (pdf file)
iii. Final 8-10 page Journal Format Paper (word file)
iv. Final 8-10 page Journal Format Paper (pdf file)
Developed system.
i. Installation or Setup Files/Folders
ii. /or Users’ Guide

XI. ARRANGEMENT OF PAGES AND ITS CONTENTS

Below is the list of parts, optional and necessary, that must be followed. It is
already arranged in chronological order for easy reference.

Each thesis or report must be arranged in the following order.

1. University Seal Page (Appendix G). Do not include this page in the pretext page count
and do not place a page number on it.
2. Title Page (Appendix H). This page contains the title of the research, name of
proponents. It also contains the name of the institution, to which the thesis/capstone
project is being submitted, and the month and year of submission. Include this page in the
pretext page count, but do not place a page number on it.
3. Approval Sheet Page (Appendix I, J). This page bears the name of the proponents/s and
the title of the research, together with the signature of the adviser, the Chairman and
members of the oral defense panel. This page certifies that the thesis/capstone project has
been duly approved, and must bear the date of approval. Begin placing pretext lowercase
Roman numerals at the bottom of this page, counting all preceding pretext material
except for the fly page. Page number is centered one inch from the bottom of page.
4. Executive Summary (Appendix L). The Executive Summary summarizes everything
about the project. It includes the idea behind the conceptualization of the project, its
significance, the project’s major functionalities, the implementation techniques, results,
conclusions and recommendations.
It should briefly highlight the following:
i. A clear articulation of systems requirements,
 15

ii. The importance of developing a software application or technology to solve

specific systems need,
iii. The proposed application developed to address specific systems need, the
recommended infrastructure and manpower training to operationalize the use of
the developed software application or technology (if applicable)
iv. The implications on other systems
Like the abstract, executive summary normally should not include any reference to the
literature. Continue pretext page numbering with lowercase Roman numerals.
5. Dedication. This page is optional. If used, make it brief and centered in one
page.Continue pretext page numbering with lowercase Roman numerals.
6. Acknowledgment. This section recognizes persons and organizations who/which assisted
the proponents in the completion of the thesis/capstone project. Acknowledgements
should be expressed simply and tactfully. Continue pretext page numbering with
lowercase Roman numerals.
a. Table of Contents (APPENDIX P). A sequential listing of all major parts of the research
with corresponding page numbers. Included in the table of contents are titles of chapters,
sections and subsections, bibliography and appendices. Also included are titles of the
preliminary pages as well as the required forms. All materials following the Table of contents
are listed. The title of parts, sections, or chapters and their principal subdivisions should be
listed and must be worded exactly as they appear in the body of the document. Continue
pretext page numbering with lowercase Roman numerals.
7. List of Tables. Continue pretext page numbering with lowercase Roman numerals.
8. List of Figures (Sample F). Continue pretext page numbering with lowercase Roman
numerals.
9. Text . All pages from the first page of text through the Vita are numbered consecutively
in Arabic numerals, beginning with Arabic numeral “2” on the second page of the thesis
since the first page of each chapter has no page number.
10. References. Continue page numbering with Arabic numerals. The bibliography is the last
page of the thesis or report and the last page listed on the Table of Contents if the author
chooses not to include a Vita page
11. Appendix. Continue page numbering with Arabic numerals.
12. Curriculum Vitae (APPENDIX U). When included, this brief biographical sketch of the
author is the last page of the thesis or report and the last page listed on the Table of
Contents. Continue page numbering with Arabic numerals.
PAGE FORMAT AND LAYOUT

1. Page Layout
Paper Size: 8.5 x 11
Orientation: Portrait
2. Font : Times New Roman
3. Font size :
Text must be a minimum of 12 point for proportional fonts. Proportional fonts
10 point or smaller are not acceptable for the body of the thesis. A smaller size
proportional font such as 8-, 9- or 10 point (depending on the style of your primary text
font) may be used for some tables and appendix materials when necessary to fit the
material within the margins. The guide is readability--all material must be easy to read in
 16

the smallest font. Be sure that the font size and style used for the text matches the page
number font.
4. Margins
All pages, including figures, tables, and appendix material must conform to the
margin requirements. If wide tables or figures require the page to be in the landscape
position, the tops of the figures/tables must be at the binding edge (the side with the 1.50"
margin). The page number will remain in the portrait position.
1.50" left margin (binding margin)
1.0" top and right
1.0" from the bottom edge of the page for the page number. In Word, be sure to
set the footer margin to 1.0". If you do not set the footer, your bottom margin will not be
1.0". Setting the bottom margin as described here will automatically result in the distance
between the last line of text and the page number being 0.25". See "standard typing rules"
for exception to the .25" margin (this distance may be larger in some instances, but never
smaller).

5. Justification
A ragged right margin is preferable to a justified right margin. Right justification may be
used only if this can be achieved without leaving large gaps of white space, or “rivers," on
the page or visible extra spaces between the words. When using right justification, be sure
that punctuation marks remain after the character. Punctuation cannot wrap to the next line.
For example, a period or comma must remain after the last character of the word and not as
the first character on the next line.
6. Line Spacing
Double space the text except as noted below.
Single space: Block quotations; table/figure captions; table/figure notes but
double space between notes; entries in the reference list but double space between
entries; headings that are typed on more than one line; all listings in the contents, list of
tables, and list of figures that require more than one line, but double space between
subheadings and each table/figure caption; itemized lists may be single spaced but double
space between items.
Single or double space appendix material and tables. Let readability of these items
be your guide in whether to single space or double space. You may choose to single
space some appendix material or a table and double space others.

7. Indenting
 Paragraphs. Indent the first line of all paragraphs .50" or use the first default
tab in Word or WordPerfect. Begin second and subsequent lines of the
paragraph at the left margin (1.50").
 Block quotes. Quotations longer than 4 lines must be formatted as block
quotes. Indent all lines of block quotes .50" from the left margin and type the
 17

entire quotation on the indented margin. Do not indent the right margin for
block quotes. Single space all lines. If the quotation is more than one
paragraph, indent the first line of this second paragraph (and any subsequent
paragraphs) an additional .50" from the new margin.
 Block quotes may be material you quote from interviews, focus groups, or
material from open-ended questions from your data collection instrument as
well as from published or unpublished sources.
8. Pagination
Assign a number to every page of the thesis. A distinction must be made between
counting and numbering the pages. Counting means, counting the page in the pagination
sequence but not necessarily placing a page number on that page. Numbering means that
the page is counted in the pagination sequence and does have a page number printed on
it.
9. Preliminary Pages
 Use lower case roman numerals (ii, iii, iv, and so on).
 Center all page numbers 1.0" from the bottom edge of the page.
 The approval page is the first page to receive a number (ii).
 Do not embellish any page number with hyphens or any other character.
10. Text and Back Matter
 Flush all page numbers to the right margin on the top of the page. Do not
embellish these page numbers.
 Begin with page 1 immediately after the last preliminary page and continue
in numerical order to the end of the document. Use Arabic numerals for all
text page numbers, meaning use Arabic numerals for everything after the last
page of the contents.
 The first page of each chapter has no page number but is included in the
counting.
11. Table Titles (APPENDIX X,Y)
 All tables must have a table heading (Table 1, for example) and a caption
(title) above the table.
 Do not extend the caption beyond the table margins. Instead, break the caption
into two or more lines using hanging indention.
 Single space between lines of captions that are longer than one line.
 Table captions must be listed in the list of tables. Do not include in the list of
tables any explanatory information that may follow the caption (nothing past
the first period). The caption wording, capitalization, and punctuation must be
exactly the same on the table as it is in the list of tables.
 Tables must be numbered in numerical order throughout the text of the paper.
Tables may not be numbered Table 9a, 9b and so on. The table 9b must be
labeled table 10.
.
 18

Landscape Tables
 A table may be prepared in the landscape (broadside) position if it will not fit
in the portrait (normal) position. Rotate the table so that the table heading and
caption are parallel to the binding margin (1.50").

 Remember that the page numbers still must be in the portrait position (1" from
the bottom edge of the 8.5" side of the page; this will be the left margin of the
table when holding it in the reading position for a landscape page).

 Some horizontal lines are required in tables. Vertical lines are not required.
Overuse of vertical lines can detract from the readability of a table. Use
vertical lines with caution.
12. Figures (APPENDIX W)
The overall format requirements for figures are the same as that for tables--
placement on the page, spacing, pagination, font style and size, numbering, landscape
orientation, captioning, and so on.
Figures are graphical representations of the data reported in the paper as opposed
to numerical presentations typically found in tables. Figures include but are not limited to
the following: graphs, charts, drawings, maps, photographs, blueprints, flow charts,
sample items from surveys, sample answer sheets, and so on. Whatever forms the
illustration takes, in the thesis it will be referred to as “Figure." Hand drawn figures are
not acceptable.
Whether in the body of the thesis or in an appendix, figures must be complete on
one page. If a figure won't fit on one page then the figure may be placed on a fold-out
page.
Place all figure captions below the figures.
For landscape figures:
Figures must be rotated 90 degrees so that the top of the figure is parallel to the
binding edge (1.50", left margin). Captions must also be rotated to remain under the
figures. On a facing page or any other figure, the caption must be landscape if the figure
is landscape and portrait if the figure is portrait. Page numbers are never rotated. They
are in the same place on landscape pages as they are on the portrait pages. In order to get
the page number on a landscape table or figure you must make two passes through the
printer--once for the table or figure and a second time for the page number.

DOCUMENT STRUCTURE
Preliminary Pages
Use lowercase roman numerals for all of the preliminary pages:

Title Page (numeral i is assigned but not shown on the page). The copyright
notice is placed at the bottom of this page if you are copyrighting. (APPENDIX H, I)
Dedication This page is optional.
 19

Type the word DEDICATION (in bold) 1.25" from the top of the page, insert two
double spaced blank lines and begin the text--double spacing all lines and indenting the
first line of every paragraph.
Acknowledgment
This page is optional.
Type the word ACKNOWLEDGMENT (in bold) 1.25" from the top of the page,
insert two double-spaced blank lines and begin the text, double spacing all lines. Indent
the first line of every paragraph.
The acknowledgment is the place to thank the faculty, staff, family, and friends
who have assisted you in preparing your thesis or dissertation. You may also
acknowledge any financial support or special research materials given to you.
Executive Summary
 Type the title in Uppercase in inverted pyramid style (the title must be
worded the same here as on the title page), bolded, 1.25" from the top of the
page
 Type the word Executive Summary (lower case), bolded.
 Double space all lines and indent the first line of all paragraphs .50".
 The Executive Summary must have a (1) statement of the problem, (2) an
exposition of methods and procedures, and (3) a summary of the findings.
 The length may not exceed 200 words.

Table of Contents (APPENDIX P)

 Type TABLE OF CONTENTS 1.25" from the top of the page, centered,
bolded.
 Type the word Page flush to the right margin, bolded.
 Type the preliminary pages in upper case letters, do not use boldface.
 All page numbers should be flush to the right margin.
 Include all chapter numbers in lower case letters and the chapter titles in upper
case letters, bolded and all subheads in lowercase, use the same wording and
capitalization as that given in the text.
 List References next in uppercase, bolded.
 List appendices next.
 Each appendix must be designated with a letter or numeral and a descriptive
title.
 Double space between each title. Single space titles longer than about 4" in
length and/or that require more than one line.

List of Tables (Figures) (APPENDIX W, X, Y)

 Place each list on a separate page with the table or figure title and a page
number at the right margin.
 Double space between each caption and single space captions longer than one
line.
 Number all tables/figures consecutively from chapter 1 through the last
chapter of the thesis.
 20

XII. MAIN BODY OR THE CHAPTERS AND ITS CONTENTS

The main body of the BSIS capstone project document will be divided into chapters and
sub-topics. The chapter’s title, contents (subtopics) and format were based on the
recommendation of the Information Technology Education (ITE) technical panel with slight
adjustments to fit the university format.

Chapter 1 INTRODUCTION

In general, the Introduction begins with a broader perspective of the problem and
becomes narrower as the Introduction proceeds. The Introduction narrows the focus of
the study and provides a brief rationale for why the particular study is worth pursuing.
This chapter serves as a backgrounder for readers to have an overview of the
study even without prior reference to other publications on the topic. The introductory
pages are important because they create the first and perhaps lasting impression on the
examiner. It should articulate the motivation of the author(s) in undertaking the project or
thesis. The first chapter should describe the importance of the study, the expectation and
its impact on the specific areas once it is completed.
Project Context
 This will be the general overview of the project
 Introduce your project by capturing the reader’s interest in the first paragraph.
 Discuss the problem background and why you decided to develop your project.
What’s wrong with the traditional method?
 What are the necessary knowledge, programming software, API’s, hardware, etc
needed?
Please remember the following:
 Refrain from placing citations or quotes.
 Avoid using or beginning your sentences with “This paper/
document/thesis/study/projects, entitled …..”

Purpose and Description (for BSIS Capstone Project - this is the equivalent of
Significance of the Study)
 Provide a short description of the project being specified and its purpose, including
relevant benefits (or beneficiaries)
 What is your main purpose in doing the project?
 Who is/are your target clients, end user/s or beneficiaries of the project?
 What are the necessary knowledge, programming software, API’s, hardware, etc
needed?

Objectives of the Project

 Detailed statements or elaboration of the project goal and should be clearly stated and
logically presented
 21

 Present the sub-objectives in a logical sequence from factual to analytical along

mutually exclusive dimensions (no overlaps) with the exclusion of the overview,
expected conclusions, implications and recommendations of the project.
 Specific objectives should be SMART. Specific, Measurable, Achievable, Realistic
and Time-bounded.
Scope and Delimitations of the Study
 Discuss here the boundaries of the study and those likely part of the study
researcher/s do not intend to accomplish (or what the design of the study inherently
will not allow)
 Describe any global limitations or constraints that have a significant impact on the
design of the system/software (and describe the associated impact).
 Describe any items or issues that will limit the options available to the developers.
These might include: corporate or regulatory policies; hardware limitations (timing
requirements, memory requirements); interfaces to other applications; specific
technologies, tools, and databases to be used; parallel operations; language
requirements; communications protocols; security considerations; design
conventions or programming standards
 Limitations that are not readily apparent at the start of the research project may
develop or become apparent as the study progresses. In any case, limitations should
not be considered alibis or excuses; they are simply factors or conditions that help
the reader get a truer sense of what the study results mean and how widely they can
be generalized. While all research/project have some inherent limitations, you should
address only those that may have a significant effect on your particular study.
Operational Definition of Terms (APPENDIX V)
 This section provides definitions for terms used in the proposal that are unusual or
not widely understood. In addition, common terms that have special meaning in the
study should be defined in this section.
 Important terms from the title, statement of the problem or objectives and paradigm
should also be defined. Define terms operationally or how you use such term in the
project.
 Acronyms (except those in common usage) frequently require definition at this
point.
 A brief introductory statement usually precedes the actual list of definitions that are
italicized, first-line indented, and listed in alphabetical order.

Chapter 2 REVIEW OF LITERATURE AND STUDIES

Research or Related Literature

Research Literature is the discussion of existing data and developments within a
particular research that you are presently undertaking. It usually shows the advancement
of findings throughout time. It examines articles, books and other sources relevant to a
particular issue, area of research, or theory, providing description, summary, and critical
evaluation of each work. It evaluates previous and current research in regard to how
 22

relevant or useful it is and how it relates to your own research. Sources should come from
referred books, journals and other publications.
Related Studies
Related studies are the previous studies relevant to the present research. This part
is an examination and discussion of the previous and present researches and projects
undertaken that gives the researchers/proponents a better idea and had motivated them in
pursuing the specific field of study. It is more than an annotated bibliography or a
summary, because you are organizing and presenting your sources in terms of their
overall relationship to your study. This section shows evidence that you have enough
knowledge of the proposal based on the research/project conducted by previous
researchers.
Related Systems
This will be the same as the related studies. A review of related systems contains
description of existing systems that are relevant to the proposed capstone project.
Discussion of specific features of other systems that you intend to replicate and improve
will help define what is to be expected in your project.

The following should be considered for this chapter:

 Organize thematically to conform to the variables of the specific problems.
 Follow proper documentation using parenthetical citation with author and date
 Highlight major findings and how one’s project would fit in the body of knowledge on
the subject matter and make a critique per topic as to whether the results cohere or
differ from each other.
 The last part should be a clinching paragraph to show how the literature or systems has
assisted the project proponent in the present study.

Chapter 3 TECHNICAL BACKGROUND

This section may include sufficient discussion of the integrated existing software
products. If there are special hardware (e.g. biometrics, server, etc. and software systems
(e.g. OS) that are essential in the actual project implementation, those should also be
described.
 The technical background should serve as a reference for technical details of the
software programming tools, interfaces, and special hardware, used in the study.
 The following should be followed:
o Discussions should be elaborated as much as possible in layman’s term.
However, it should not be too detailed that you end up repeating or lifting
practically the discussion from different sources.
o It should not be too shallow or vague that the discussion becomes useless.
o It should contain enough detail to help the readers appreciate its application in
the thesis or capstone project.
 23

o It must be written in narrative form. It is important that the section starts with a
paragraph that describes what the readers should expect on it. Subheadings are
recommended for discussions that are substantially long.
o Topic items should be arranged logically by order of importance or by theme.

Chapter 4 DESIGN AND METHODOLOGY

 This chapter includes discussion on conceptual design / system architecture/ block

diagrams and algorithms
 It is important that the methodology used is correct and appropriate from the start.
 This is the part where students need the expert technical and theoretical inputs. This
is why students need good advisers who will teach them on:
 Correct systems analysis tools and techniques
 Correct and appropriate algorithms to use
 Appropriate usability tests
 Correct and appropriate hardware
 Appropriate software tools

The following can be the contents of this chapter (Sta. Romana et al., 2012):

 The Project Concepts – The narrative description of the design to achieve your
project objectives. Most of the concept is illustrated in a graphical diagram to
visually present the structure of the concept of the research or project.
 System Analysis and Design – Should either Structured or Object-Oriented
approach. Present and discuss only the system analysis and design tools that
were actually used in the development of the project.

o System analysis focuses on system requirement description; defines the

system functional requirements, and requirement specification of the
proposed system.
o System design provides the technical specification and construction of the
solution for the requirements identified during the system analysis phase of
the research/project. This should include but not limited to: details of data
structures, architecture, interfaces, and procedural detail of software
component of the research/project.
o System implementation is the installation and delivery of the proposed
system to be conducted by the researchers/developers. It includes conversion
and integration plan, database installation, system testing, user training and
other production activities.

The documentation of system analysis to actual deployment should include

presentations in the form of tables, figures, and other similar diagrams used in either
structured or object-oriented approach. These are the approaches and procedures learned
by the students in “System Analysis and Design” and in “Software Engineering”.
 24

 Development Model – This may include the following models: Conventional

waterfall type, Incremental, Throw-away, prototyping, Evolutionary prototyping
and any other model which is most appropriate to the kind of research project
being undertaken.
 Development Approach – This may include either Top down or Bottom-up
approach of development.
 Software Development Tools- It should contain the discussion about the
programming language tools to be used specifically on : front and Back-end;
Reuse or not; Open vs. Licensed software- Criteria for selection ,i.e.
maintainability, support, HCI capability, database connectivity, simplicity, eases
of use, etc.
 Schedule and Timeline (for Proposal only) – It may contain Gant Chart, Activity
Chart, Critical Path Analysis and other scheduling techniques that will list the
activities to be done in order to achieve the objective. Usually it includes the
phases and its sub-phase of the systems development life cycle.
 Project Teams and their Responsibilities - It should contain the assignments of
modules and activities to be done by each team member.
 Budget Cost Management Plan – It should contain a detailed budget proposal
and how each cost is to be managed effectively in the conduct of the research
study.
 Verification, Validation and Testing Plans – It should contain the plan of
activities to: verify and validate if you are developing the system right and test
the system if it works correctly without any bugs or errors. Most importantly, use
of any quantitative and qualitative measures should be planned in order to
achieve the research projects specific objectives.
 Order of discussion is based on the chronology of the statement of the
problem/objectives.
 In presenting this chapter the following should be considered :
 The actual and honest observations of the researchers
 The scientific generalizations
 .Articulation of novel contributions
 The presentation and precise analysis of results
o Validation and Testing
o Interpretation/Discussion of results

Chapter 5 SUMMARY, CONCLUSIONS AND RECOMMENDATIONS

This is the last chapter of the thesis /capstone project manuscript and the most
important part because it is here where the findings, and the whole thesis/project for that
matter, are summarized; generalizations in the form of conclusions are made; and the
recommendations for the solution of problems discovered in the study are addressed.
 25

a. Summary of Findings - Introductory paragraph on this part may include the statement
of the problem/objectives and synthesized methodology. The salient findings for each
of the specific problems/objectives should be enumerated.
b. Conclusions. These are generalized statements from a micro to a macro level based
on the answers to each of the specific problems ur each of the specific objectives.
c. Recommendations. These should be based on the findings and conclusions.
Recommendations should be feasible, workable, flexible and adaptable in a non-
technical language and may include suggestions for further studies.

XIII. BACK MATTER

The back matter consists of the reference and appendices in that order.
Page numbers continue as Arabic numerals for all back matter:

References

This is a list of works cited, as well as works consulted but not cited in the
construction of the research or capstone project.
Categorize references as published and unpublished. Under published materials are
references from and sub-categorized as books, encyclopedia, dictionary, magazines,
newspapers, journals, electronic downloads and under unpublished materials are thesis
and dissertations.
The list of references is arranged alphabetically and single-spaced, but separated by
blank line. Type the first line of an entry from the left but indent the succeeding lines by
five letter spaces.
Use APA format 6th Edition in citing references. (See Separate Sheet)
Appendices (APPENDIX S)
An appendix or appendices, if any, should be after the Bibliography. Appendices
may include the following:
o Relevant Source Code
o Evaluation Tool
o Sample Input / Output / Reports
o Users Guide
o Other Relevant Documents
o Grammarian’s Certification
o Curriculum Vitae

Appendices should be arranged chronologically as they are cited in the main text.
Use capital letters of the English alphabet to track appendices.
Half Title Pages
A half title page is required before the appendix section.
 The half title page for the appendix section will have APPENDIX or
APPENDICES (as appropriate) typed in all caps and centered, centered on the
 26

page, font size 36. Count the page in the pagination sequence but do not print
a page number on.
Appendix
 The appendix (or appendices, if more than one) is labeled as Appendix A,
Appendix B, etc., with descriptive titles given for each. You may use half-title
pages which carry the appendix label and descriptive title (typed centered in
inverted pyramid style and in all caps) before the actual appendix material or
you may simply place the appendix label and descriptive title at the top of the
page (top margin 1.25"), double space, then start the actual appendix material.

 Remember to observe the margins and the page numbering requirements. Use
Arabic numerals, numbered consecutively with the text.
Curriculum Vitae (APPENDIX U)
 Type the word CURRICULUM VITAE, bold faced 1.25" from the top of the
page, insert two double-spaced lines and begin.
 Remember to observe the margins and the page numbering requirements. Use
Arabic numerals, numbered consecutively with the text.
For the researchers photo. Use passport size (4.5 x 3.5 cms), background
color: Royal Blue or white, Full frontal Image of the applicant should occupy
approximately 70 –80% of the photograph. There should be at least 8 mm – 10
mm space at the top of the photo. Wearing decent attire with collar (no short
sleeves/sleeveless/plunging necklines for women). Use of eyeglasses is acceptable
provided there is no glare from the glasses and the eyes are distinctly shown. As
much as possible, both ears should be visible. Use of head scarf for religious or
medical reasons is allowed (i.e., Muslim women/nuns/cancer patients with hair
loss/ Alopecia). However, the scarf should not cover the eyebrows/eyes. Use of
caps or head gear is not allowed. Use of contact lenses for medical reasons is all
right PROVIDED the contact lenses do not change the applicant’s true eye color.
Use of earrings is acceptable for women ONLY provided the earrings are small.

XIV. List of Deliverables/Activities

Deliverable Due Date
D1 Project Team Assignments Form (Appendix A)
D2 Pre-Proposal Statements (3 – 5) (Appendix B)
D3 Project Working Title Form (Appendix C)
D4 Complete Proposal Manuscript (Appendix D)
D5 Proposal Hearing Notice Form (Appendix E)
D6 Revised Proposal Manuscript
D7 Grammarians Certificate (Appendix F)
D8 Approval Sheet (IS 25 / CAPSTONE1) (Appendix J)
D9 Final Proposal Manuscript (Hardbound)
D10 2 Proposal Defense CD’s(Appendix N)
DX Consultation Logs Form (Appendix M)
D11 1st prototype (30% to 50%) plus 1st draft
 27

D12 2nd prototype (51% to 70%) plus 2nd draft

D13 3rd prototype (71% to 99%) plus 3rd draft
D14 Oral Defense Hearing Notice (Appendix E)
D15 Journal Formatted Manuscript (Appendix O)
D16 Complete Oral Defense Manuscript (Appendix D)
D17 Approval Sheet (IS 27 / CAPSTONE2) (Appendix K)
D18 2Oral Defense CD’s (Appendix N)
D19 Individual Journals
• 1 Long Brown Envelope (per team)

References

Berndtsson, M. et al. 2008. Thesis Projects A Guide for Students in Computer Science and
Information System. Second Edition. Springer-Verlag London Limited.

Commission on Higher Education (CHED). CHED Memorandum Order No. 6 Series of 2006.
Policies and Standards for Information Technology Education Programs. Retrieved March
10, 2012 from http://www.ched.gov.ph/chedwww/index.php/eng/ Information/CHED-
Memorandum-Orders/2006-CHED-Memorandum-Orders.

Dawson, C.W. (2005). Projects in Computing and Information Systems: A Student's Guide.
Addison-Wesley.

Laviña, C. et.al. 2014. Outcomes-Based Practical Guide to Thesis and Capstone Project Writing
and Computing.

Sta. Romana, CL., Gamboa. R.S., Marcial. D.E. et al. (2012). Undergraduate Research and
Capstone Project Manual. Philippine Society of Information Technology Educators, Inc.

Oates, B.J. (2006). Researching Information System and Computing. New Delhi, India: Sage
Publications.
___________________.2012. Capstone ProjectGuidelines For IT 415/CAPSTONE4 and
IT420/CAPSTONE42. University of Cebu-CICS.