General Guidelines for Undergraduate Research Projects

(CS Thesis and IT Capstone Project)

RATIONALE

The Research Publication and Innovation Center (RPIC) has administrative responsibilities
in assisting not only the faculty researchers but also the undergraduate students in the preparation
of research guidelines. These guidelines were formulated through the concerted efforts of
Research Teachers representing the various disciplines of each College. In accordance with the
guidelines set forth by the RPIC, the College of Computer Studies also has formulated its own
guidelines that will fit its own standards.
TABLE OF CONTENTS

Content of the Thesis or Capstone Project Document

Mechanics for Hardbound (IMRAD format)
Research Topics/Areas
CS Thesis/IT Capstone Project Team Composition
Adviser, Technical Panel Composition and Other Professional Services
Public Presentation
Deliverables
Other Provisions
I. Content of the Research Paper

A. Preliminary Pages
a. Title Page

b. Approval Sheet
This section of the manuscript serves as proof that the group passed the final
presentation and the manuscript has been checked.

c. Abstract
This section of the manuscript provides a brief summary of the study to include key
parts (introduction, methods and materials, results and discussion). The abstract
must not exceed 250 words.

d. Acknowledgement
This section of the manuscript is intended to acknowledge key persons,
organization and the like.

e. Table of Contents
f. List of Tables
g. List of Figures
h. List of Notations

B. Introduction
a. Opening Statements (no section title)
 This section must capture the attention of the readers by providing details about
why the researchers decided to conduct their chosen study. There should be a
description as to the specific factors that drive the project. It can either be due to
technological advancements or business process improvement. This section must
also contain what are those pressing issues happening in the global, national, and
local level that the researchers would want to address. Lastly, this section should
outline the different potential advantages/ benefits for having such a project.

A comprehensive discussion of the Needs, Differentiation, Solutions, and Benefits

of the project should be included.

b. Objectives of the Study

This section contains a list of objectives. It can either have a general objective,
followed by specific objectives; or a list of specific objectives. Make sure that the
objectives are feasible and within bounds of the researchers' control, technical
know-how, available resources, and time frame.

C. Methods and Materials

a. Research Method
This section should discuss the research framework that the researchers will follow.
This will include the software process methodology that will be employed if a
software application is to be developed. The chosen methodology should be
appropriate for the thesis/capstone project and that the specified data gathering
techniques are sufficient enough to support the thesis/ capstone project.

Conceptual Framework/Theoretical Framework

This section describes the logical structure of meaning that will guide the
researchers in the development of the study. There should be a clear
illustration of the concept of the thesis/capstone and that the variables to be
analyzed in the study were appropriately identified and clearly defined. This
section also includes the coverage of the thesis/capstone project, indicating
the boundaries in terms of the research area, locale, methodology, materials,
and time frame. This section should clearly outline the range of the
implementation of the project so that readers will be able to have clear
expectations.

b. Design Procedure (Depends on the chosen methodology/software process model)

This section should describe in detail the step-by-step procedure that the researchers
will undergo following the methods specified in the previous section of the
document. Also, this section should discuss the different materials used in the
conduct of the study.

c. Testing Procedure
This section shall provide a detailed test plan (for proposal) or actual testing
 activities (final). If possible, this section should provide answers to the following
questions:

● What test/s will be conducted (proposal) or have been conducted (final)?

● Who are (proposal) or were (final) the testers?
● What are (proposal) or were (final) the selection criteria?
● Where will the test be conducted (proposal) or was the test conducted (final)?
● How will the test be conducted (proposal) or were the test conducted (final)?

For Black Box testing approach, the number of testers/evaluators must be sufficient
enough to validate test results and that the identified testers’ profile fit the type of
system to be evaluated.

For the White Box testing, there must be a clear definition of the parameters to be
tested.
d. Work Plan (Projected Timeline for Proposal | Timeline for Final)
This section shall provide a clear schedule of activities that matches the methods
indicated in the Design Procedure section of the document.

D. Results and Discussion

a. Testing and/or Implementation Results
This section should present the discoveries of the researchers during the
development and during the testing conducted. The researchers may use tables
and/or figures to better convey thoughts. Make sure to explain how such results
were generated (could be affected by the person testing, the environment, technical
issues, etc.) The discussion of the results should be aligned with the objectives of
the study.

b. Discussions / Implications
This section is dedicated for the researchers to discuss the implications of the test
results. Here, the researchers are expected to explain thoroughly what the results
imply and how it would affect the chosen area of study.

c. Conclusions and Recommendations

This section is dedicated for the researchers to make conclusions as to whether or
not they have achieved the objectives set and how it was achieved. The researchers
can then recommend future improvements to the current output.

E. References (ACM format)

F. Appendices
a. Screenshots of the Prototype (Proposal Stage) or Screenshot of the System (Final
Output)
b. Communication Letters or Forms used
c. Minutes of the interview, Focus Group Discussions, etc. (if applicable)
d. ACM Paper Format
 e. Other Related Documents (may include here the document proof-read using
Grammarly software)

II. Mechanics (for Hardbound)

For the final submission, I would like to suggest that manuscripts should follow the
ACM format.

III. Research Topic Areas

The thesis/capstone project should prioritize areas of concern that are aligned with the
students’ chosen specialization which falls under Health (Computational Health
Informatics for the CS students, Healthcare Technologies for IT students), and Education
(Learning Technologies for IT students).

The following are examples of topics under Education and Health:

Education
● Gamified Distance Learning
● Interactive Technologies for Special Education
● Data Analytics on Board Examination performance

Health
● Bioinformatics and Biotechnology
● Use of artificial intelligence and robotics technologies
● Use of Interactive technologies for community health
● Use of advanced technologies for Nutrition and Food safety

IV. CS Thesis/IT Capstone Project Team Composition

The Thesis/Capstone Project team should be composed of at most four (4) members. The
following are the roles that the proponents/researchers should play:

Project Manager (PM)

The PM is someone with authority to manage the overall conduct of the thesis/capstone
project. The role of the PM includes leading the planning and the development of all
research deliverables as well as seeing to it that all members of the team are fully
functional. The PM is also responsible for the budget, work plan and all Project
Management Procedures (scope management, issues management, risk management, etc.).
The PM is responsible for the success of the entire study.

Systems Analyst and Database Designer (SA and DD)

As the SA, the person will take charge in the identification and documentation of system
requirements (proposal) and checks that all these are implemented and coordinated (final).
As the DD, the same person will be responsible in making sure that the database design is
complete, appropriate and robust.
 Network Designer (ND)
The ND is someone who will be responsible for the identification of the system’s network
requirements and designs the network appropriately based on these requirements.

UI Designer (UID)
The UID is someone who will be responsible for the User Interface (UI) design from
conceptualization to the actual implementation as well as all other aesthetics of the system.
The UID shall coordinates well with the SA/DD.

Software Engineer/Programmer (SE/P)

The SE/P is someone who is technically skilled and will take charge in the development of
the proposed solution. The SE/P shall coordinate well with the ND/UID.

QA Tester (QA)
The QA is someone who is very keen in details and will ensure the quality of the developed
solution. The QA shall also help find and eliminate any bugs.
Technical Writer (TW)
The TW is someone who is scrupulous and shall take charge of the overall documentation
of the study. The TW coordinates well with the SE/P.

V. Adviser, Technical Panel Composition and Other Professional Services The College of
Computer Studies shall follow the Adviser/Panel Composition as stipulated under the
CHED/PSITE Framework for Undergraduate Thesis/Capstone Project as indicated below:

The thesis/capstone project is prepared under the guidance of an adviser. The adviser
should have a degree in an ITE or allied program and must have completed a CS/IT
project/research successfully beyond the bachelor’s degree project. As much as possible,
the adviser should be a full-time faculty member of the HEI otherwise a full-time faculty
co-adviser is required. As a general rule, faculty advisers should handle at most five groups
and CS Thesis/IT Capstone Project faculty cannot be an adviser of any group belonging to
their class.

The team should fill up a consultation monitoring form (Appendix A) every time they seek
advice from their adviser and/or consultant.

The thesis/capstone project should also be presented and accepted by a Panel composed of
at least 3 members where 1 member should be an area expert. Except for the area expert,
the Panel members should have a degree in an ITE or allied program. At least one of the
panel members must have a master’s degree in ITE (preferably MSCS, MIT,MIM, MIS) or
allied program.

Prior to the final submission of the manuscript, it should have been proof read by a credible
proofreader or should pass through a proofreading and grammar checking tool (e.g.
 Grammarly). A proofreader request form should be filled up and given to the proofreader
for acceptance (Appendix E).

The professional fees shall be based on the institutional policies.

VI. Ethical Review

Aside from the technical review, each group shall also go through an ethical review which
will be facilitated by the Ethics Review Committee of the Research Publication and
Innovation Center. The review is generally classified into the following:

● Exemption
● Partial Review
● Full Review

VII. Deliverables
Each member of the team should prepare a Weekly Progress Report (Form B). The
individual progress report will be collated by the PM and shall be submitted together with
the Consultation Monitoring Form (Form A) signed by the adviser. It is recommended that
before the adviser reviews the document of the student researchers, it should have been
checked already through Grammarly with at least a score of 90%.

VIII. Public Presentation

The researchers are required to present their thesis/capstone project to a local, national or
international public forum or any school-based presentation that is open to public.

IX. Other Provisions