Outline of the Thesis Document

(Title Page)
Advisers Recommendation Sheet
Panels Approval Sheet
Thesis Coordinators Acceptance Sheet
Table of Contents
List of Tables (optional)
List of Figures (optional)
Acknowledgement

Abstract
This should contain a brief summary of the project. It is composed of a single paragraph of at most 300
words and should include the overview of the problem, the project design, and the results of the project

Preface
This should contain a brief statement of the problem, the significance of the study, the proposed system, and
an overview of the structure of the project document.


CHAPTER 1
INTRODUCTION

1.1 Background of the Problem
This should contain a discussion on the general problem to be addressed by the project work.

1.2 Current State of the Technology
This should include the state of the current technology and the different solutions proposed so far (based on a
literature survey). It contains discussion on the specific problems faced by or that still in a specific technology or
field (e.g., limitations of existing systems, software, or algorithms). The discussion should include only enough
detail to show the rationale behind and the problems in each leading to the specific need for the proposed
system

1.3 Statement of the problem
This should introduce the general problem that the proposed system addresses, and the need to find a solution
to the problem. It states the rationale and significance of finding a solution to the problem.

1.2.1. Major Statement
1.2.2. Minor Statements

1.4 Objectives
This should be taken from the corresponding sections of the approved project proposal. The scope and
limitations may be further elaborate but nothing must be changed, added, nor removed without the written
approval of the Project Coordinator or Adviser.

1.4.1. General Objective
This should contain a single paragraph describing the general objective of the project.

1.4.2. Specific Objectives
This should contain a list of the specific work that the proponents expect to address to arrive
at the accomplishment of the general objective.







1.5 Scope and Delimitations
This should contain the basic assumptions within which the project should work the solution to the problem.
Consequently, this should also contain the extent of the prototype to be developed and the means by which the
proposed system is to be evaluated on its capability of solving the problem.

The limitations are those conditions beyond the control of the proponents that may place restrictions on the
conclusions of the study and their application to other situations.


CHAPTER 2
<NAME OF THE PROJECT>

2.1. Introduction
This should introduce how the proposed system solves the problem cited in Statement of the Problem.
This should also give the interrelation between the different sections of the chapter.

2.2. System Design Specification
This should contain an explanation of how the system is put together. This section may start by giving an
overview of the overall specification and functional requirement of the system. It shall discuss the
functionalities and detailed description of the different components of the system.

2.3. Resources
Specify hardware and software components, as well as their interactions may be discussed graphically.

2.3.1. Hardware
This should list the specific hardware resources that are needed in the project

2.3.2. Software
This should list the specific software resources that are needed in the project

2.4. User Manual
This should capture each form of the system and put description, direction, and function details to guide
users of the system.

CHAPTER 3
METHODOLOGY

3.1. Introduction
This should contain the specific approaches that may be employed by the proponents in arriving at the
realization of a solution to the problem.

3.2. System Development Life Cycle
3.3. Data Flow Diagram
3.4. Conceptual Database Design
3.5. Logical Database Design
3.6. Physical Database Design

CHAPTER 4
PERFORMANCE ANALYSIS

This chapter provides a list of experiments conducted by the group, as well as the discussion of the results and
observations done on the system. In this section, the proponents must prove that the objectives of the project
have been achieved.

4.1. Introduction
This should give the major objectives of the experiments conducted. (The minor / specific objectives of each
experiment should be included in the Experimental section.) There should be a description of the
parameters to be measured. All assumptions made in the analysis should be explained in detail.






4.2. Experimental
This section should describe the experiments conducted in analyzing the behavior / performance of the
proposed system. This should include how the required parameters were quantified, i.e., what measurable
parameters were used to give an indication of the desired parameters if these are not directly measurable.
This should also include the basis for such assumptions. The information given should be enough that the
reader can repeat the experiments for evaluation and verification.

4.3. Results, Analysis, and Interpretation
This should an overview of the results from the experiments and research. Sample raw data shall be
included to explain how these are presented and analyzed. The full set of data shall be included as an
appendix. This shall also contain a discussion of the information derived from the results, with sample raw
data to support each conclusion.

4.3.1. Presentation of Data / Result
Present findings of the study and experiment in the order of the specific problem as stated in the
statement of the problem. Present data in tabular and graphical data presentation.

4.3.2. Analysis of Data / Result
Data must be analyzed quantitatively or qualitatively depending in the level if measurement and the
number of dimensions and variables of the study. Analyze in depth to give meaning to the data
presented in the data presented in the table. Statistical description in declarative sentence is
recommended.

4.3.3. Interpretation of Data / Result
Establish interconnection between and among data. Link the present findings with the previous current
state of technologies and draw out implications.

4.4. Summary


CHAPTER 5
CONCLUSION

This conclusion shall be a one-section chapter. This should contain a summary of the problem, the proposed
system, the major results of the performance analysis, and the recommendations for further work/s.

BIBLIOGRAPHY
This should contain the references cited throughout the project document. The sequence may either be in the
order of citing or in order of the first authors surname.

APPENDICES
These should contain the raw data, program listing, and the technical and users manuals. The program listing
must be unformatted and in a fixed width font (e.g., Courier). The technical manual for hardware systems shall
include the list of parts/components used, the detailed schematic diagram/s and circuit board layout/s. The
technical manual for software systems shall contain a description of the main program structure. This should also
include a short description of each user-defined functions/procedures that contain what each does, what
parameters are passed, how the parameters are used, which routines call them, and which routines they call.
The users manual should contain detailed procedures on how the set-up and use the system.

Physical Format:

Use 8.5 x 11 bond paper with 1 inch margin on each side.
Has 1.5 spacing, Times New Roman, 12pt
The pages shall be numbered at the bottom right. All pages from the table of contents page to preface shall
use lower-case Roman numerals while Arabic numerals shall be used from Chapter 1.
Each chapter should start on a new page.




GRADING SYSTEM:

Thesis Coordinator (10%)
Attendance (20%)
Submission of Requirements (80%)
Thesis Adviser (20%)
Attendance (15%)
Participation in the discussion (25%)
Project Involvement (60%)
Final Defense Grade (70%)
Functionality (50%)
Knowledge and Answering Skills (20%)
Presentation Performance (15%)
Factuality (15%)