Parts of Proposal Paper

Title Page
Executive Summary
Approval Sheet
Acknowledgments
Table of Contents
List of Figures
List of Tables
List of Notations
Chapter I – Introduction
A. Project Context
This part should be at least two pages of presentation and discussions. This should introduce the
presentation of the problem, that is, what the problem is all about. The proponent should
describe the existing and prevailing problem situation based on his/her experience. This scope
may be global, national, or regional. The project context gives a strong justification for choosing
such a research problem based on his/her capacity. Finally, in the project context, provide a
statement that shows the relationship between the rationale of the study and the proposed
research problem.

B. Statement of the Problem

This part is used in research work as a claim that outlines the problem addressed by a study. The
statement of the problem briefly addresses the question: What is the problem that the research
will address?
The ultimate goal of a statement of the problem is to transform a generalized problem
(something that bothers you; a perceived lack) into a targeted, well-defined problem; one that
can be resolved through focused research and careful decision-making.
Writing a statement of the problem should help you clearly identify the purpose of the research
project you will propose. Often, the statement of the problem will also serve as the basis for the
introductory section of your final proposal, directing your reader’s attention quickly to the
issues that your proposed project will address and providing the reader with a concise
statement of the proposed project itself.
A statement of problem need not be long and elaborate: one page is more than enough for a
good statement of problem.

C. Purpose and Description of the Project

 D. Objectives of the Study
The objectives of the study guide the researcher and the reader to know what the proponent
needs to do. These usually follow the chronological sequence of the statement of the problem
and its specific questions.
Objectives are written by either beginning with an action verb or an infinitive.
The importance of the project must contain explanations or discussions of any or all of the
following:
• The rationale, timeliness, and relevance of the study;
• Possible solutions to existing problems or improvements to unsatisfactory conditions;
• The beneficiaries and how they are going to be benefited;
• Possible contribution to the fund of knowledge (if any); and
• Possible implications

E. Scope and Limitation of the Study

The Scope and Delimitation of the Study should include a brief statement of the general purpose
of the study, the target users/beneficiaries of the study, the period of the study, and the features
of the proposed software.
The limitation of the study includes the weaknesses of the study beyond the control of the
researcher.
Chapter II – Review of Related Literature/Systems
A. Review of Related Literature
A literature review aims to show the reader what the researchers have read and had a good grasp
of the main published work concerning a particular topic or question in the particular field. This
work may be in any format, including online sources.
It is very important to note that the review should not be simply a description of what others have
published in the form of a set of summaries but should take the form of a critical discussion,
showing insight and an awareness of differing arguments, theories, and approaches. It should be
a synthesis Project and analysis of the relevant published work, linked at all times to your own
purpose and rationale.
Literature reviews should comprise the following elements:
 • An overview of the subject, issue, or theory under consideration, along with the objectives
of the literature review;
• Division of works under review into categories (e.g., those in support of a particular
position, those against, and those offering alternative theses entirely);
• Explanation of how each work is similar to and how it varies from the others;
• Conclusions as to which pieces are best considered in their argument are most convincing
of their opinions and make the greatest contribution to the understanding and
development of their area of research.

B. Related Studies and/or Systems

Published as well as unpublished research studies are sources of materials that may be included
in this section. The research studies may also be identified as foreign or local.
Existing systems that are closely related to the research/design are considered in this section and
may be identified as foreign or local.
Common Guidelines in Citing Related Literature and Studies:
1. The materials must be as recent as possible.
2. The materials must be objective and unbiased as possible.
3. The materials must be relevant to the study.
4. The materials must not be too few or too many.
5. After reading, the readers should gain an adequate understanding of the technical topic(s)
involved in the project.

C. Synthesis
This contains the conclusive summary of the Review of related literature/studies. In case that the
proposed project is a continuation of a previous work, this section should give emphasis or
justification why the proposed project is needed.
Chapter III – Technical Background
It includes an in-depth discussion of the relevant technical aspects of the project.
A. Overview of Current Technologies to be used in the System
This contains the discussions on the current trends and technologies to be used in developing and
implementing the proposed system.
B. Calendar of Activities
This contains the detailed sequence of activities that the proponents will undergo in completing
the project.
• Gantt Chart of Activities
This should contain a chart giving when each of the activities listed above is expected to
start and end. The time unit should be in terms of the week number (not actual dates)
from the start of the semester.
 C. Resources
• Hardware
This should list the specific hardware resources that the proponents expect to need in
completing the project.
• Software
This should list the specific software resources that the proponents expect to need in
completing the project.
Appendix
A. References
B. Resource Person/s
C. Personal Technical Vitae (one page per member)

Project Proposal Defense

1. The Project Coordinator schedules the Proposal Defense after the submission of the proposals.
Proposal Defense schedules are disseminated to the Project Groups. Note that only endorsed
project proposals shall be scheduled for proposal defense.
2. The Project Group defends their proposal. The Proposal Defense mechanics must be strictly
complied with during proposal defense.
3. The Defense Panel evaluates the Project Group’s proposal. In doing so, questions may be asked
of the Project Group and shall answer the questions as accurately and as correctly as possible.
Defense Panel must properly accomplish the required form/s (Project Proposal Defense
Evaluation Form) during the proposal defense.
4. The Project Adviser takes note of the revisions identified during the defense and discusses these
with his/her project advisees after the defense. The Project Adviser is required to attend the
defense to give moral support to the Project Group and to write down comments, suggestions,
recommendations, and clarifications from the panelists.
5. Defense Panelists deliberate and read the verdict to the Project Groups.
• In case of a redefense verdict, only the listed revisions in the Revisions List Form should be
raised.
• The same set of panelists shall serve as Defense Panel during redefense.
• Student(s) who failed the defense have to re-enroll the subject.

Grading System
1. Each member of the project group shall receive individual final grades. Hence, it is possible for
some members to pass while others fail.
2. The individual grades of students shall be submitted by the Project coordinator to the Registrar’s
Office. No INC grade shall be given for the Thesis course.
 3. The following are the required grading components:

1. Project Proposal Defense Grade* 50%

a. Project Proposal Documentation 60%
b. Oral Presentation 40%
2. Project Adviser’s Grade 50%
a. Project involvement 50%
b. Participation during consultations 30%
c. Attendance to consultations 20%
*Note that failure in the defense means failure in the course

Project Proposal Deliverables

Upon completion of the course, the project groups are required to submit the following ProjectProposal
Deliverables to the Dean of Informatics.

1. Proposal Grades
2. List of Groups and Topics