MANUSCRIPT CONTENTS

PRELIMINARY PAGES
Title Page
Approval Sheet
Dedication (free form) Acknowledgement Executive Summary
Table of Contents (You may use MS Word Table of Contents feature)
List of Figures List of Tables
List of Notations (optional)

CHAPTER I: INTRODUCTION

Project Context
(Should be at least 2 pages of presentation and discussion) What will the
researcher do?
1. The researcher must describe its prevailing issues based on his
experience when introducing the research problem.
2. Project context gives a strong justification for choosing such research
problem based on his/her capacity.
3. Finally, in the project context, provide a statement that shows the
relationship among the rationale of the study to the proposed
research problem.

Purpose and Description

1. This section gives the reader an overview of the specific technology
or field in the international or local setting. The information regarding
the technology or field should be contemporary and not based on
outdated sources.
2. Discussion must not be too technical or too detailed.
3. This section ends with a discussion on the problems faced by or that
still exist in the specific technology or field (e.g., limitations of existing
software or algorithms). The problem statement would lead to the
project objectives.

General Objective
This section states the over-all goal that must be achieved to answer
the problem.

Specific Objectives
1. This subsection is an elaboration of the general objective. It states
the specific steps that must be undertaken to accomplish the general
objective. These objectives must be specific, measurable, attainable,
realistic, and time-bounded.
2. Each specific objective may start with “to
design/survey/review/analyze…” Studying a particular programming
language or development tool (e.g., to study Windows/Object-
Oriented/Graphics/C++ programming) to accomplish the general
objective is inherent in all project paper and, therefore, must not be
included here.

Scope and Limitations

This section discusses the boundaries (with respect to the
objectives) of the project and the constraints within which the project
will be developed.
The scope explains the nature, coverage and time frame of the study.
The limitation, on the other hand, explains all that are NOT included
in your project.
 Significance of the Project
1. This section explains why project must be done in this area. It
rationalizes the objective of the project with that of the stated
problem.
2. Avoid including here sentences such as “This project will be
beneficial to the proponent/department/college” as this is
already an inherent requirement of all projects. Focus on the
project’s contribution to the field of Information Technology.

CHAPTER II: REVIEW OF RELATED LITERATURE/SYSTEMS

1. This section discusses the features, capabilities, and limitations of existing
work, algorithms, or software that are related/similar to the project.
2. The reviewed works and software must be arranged either in chronological
order, or by area (from general to specific). Observe a consistent format
when presenting each of the reviewed works.

CHAPTER III: TECHNICAL BACKGROUND

1. This section discusses and presents different sets of diagrams and charts
pertaining to the software project that is being develop by the proponents.
2. How the project will work Theoretical/Conceptual Framework
3. This section discusses the theories and concepts to be used in the course
of designing or developing the project. Include only those concepts that you
feel will be needed. Do not copy the whole source material. Use the topics
stated in the Project Paper Proposal Objectives as a guide in determining
the contents of this section.

CHAPTER IV: METHODOLOGY, RESULTS AND DESCRIPTIONS

1. This section lists and discusses the specific steps and activities that will be
performed by the proponent to accomplish the project. The discussion
covers the activities from pre- proposal to Final Project Paper Writing. This
section also includes an initial discussion on the theoretical framework to be
followed.
2. Examples of activities include inquiry, survey, brainstorming, canvassing,
consultation, review, interview, observe, experiment, design, test,
document, etc. The methodology also includes the following information:
• who is responsible for the task the resource person to be contacted
• what will be done
• when and how long will the activity be done
• where will it be done
• why should be activity be done

(choose only the parts that are applicable)

Environment
Population of the Study (Respondents)
Research Instrument
Organizational Chart/Profile/map or picture

Requirements Analysis and Specifications

Gantt chart

A Gantt chart showing the schedule of the activities should be included as a table. For
example:
ACTIVITY JAN FEB MAR APR …
Data Gathering **** **
Software Requirements **** **** ****
 Analysis
Initial Architectural Design **

Requirements Modeling
Input
Process
Output
Feedback

Data Design
Entity Relationship Diagram

Data and Process Modeling

1. Context Diagram Data Flow
2. Diagram System Flowchart
3. Program Flowchart (highlights only)
Object Modeling (choose any applicable)
1. Use Case Diagram – Web-based and app
2. Class Diagram Sequence
3. Diagram Activity Diagram - pure app

Requirements Documentation
1. User-Interface Design and Reports

System Architecture
1. Network Topology
2. Network
3. Model Security

Development, Testing and compatibility

1. Software Specification
2. Hardware Specification
Server
Client
Mobile Phone (for app if applicable)

Programming Environment
1. Front End Back End
2. Deployment Diagram

Implementation Results
Verification, Validation and Testing (Implementation and Evaluation)
1. Unit Testing
2. Integration Testing
3. Compatibility Testing
4. Performance Testing
5. Load Testing System
6. Testing Acceptance Testing (must be done after the Oral Defense)

Results and Observations

1. This section presents the analysis, interpretation and implications of the
summarized test results, as well as observations on the limits of the
system‟s capabilities. It also discusses the type(s) of testing performed on
the system, the test data used, and the results of the tests.
 2. The type(s) of tests performed varies depending on the system developed.
For instance, a commissioned software would require a detailed acceptance
test and system response time analysis, while a software implementing an
algorithm would require an analysis of the performance of the algorithm on
different machines or on different test data.

CHAPTER V: FINDINGS, CONCLUSION AND RECOMENDATION

1. This chapter gives an assessment of what happened in this project. It
presents explanations and justifications on how the objectives of the project
were met, to what extent and why some objectives were not met.
2. This chapter also includes a discussion of possible improvements that can
be made on the software, as well as future directions of the project in
general. This serves as a springboard for projects that may be done by
future project proponent.

SUPPLEMENTARY PAGES
References
Appendices (may include the following)
1. Transmittal Letters
2. Evaluation Tool or Test Documents
3. Sample input/output/Reports
4. Users Guide
5. Process/Data/Information Flow
6. Screen layouts
7. Test Results
8. Sample Generated Outputs
9. Pictures showcasing the data gathering, investigation done (e.g. floor plan,
layout, building, etc.)
10. One-Page Curriculum Vitae per team member
ii