[go: up one dir, main page]
Scribd
Upload
140 views3 pages

Sample Format of Meeting Minutes Example

This document outlines the required sections and content for a design project document. It includes sections for an abstract, table of contents, introduction/problem statement, literature review, methodology, performance analysis, conclusion, bibliography, and appendices. The methodology chapter must explain how the system is designed and put together, including functional requirements, component descriptions, and interactions. The performance analysis chapter provides experiments to prove the objectives were achieved and discusses results and observations.

Uploaded by

Paolo O. Lozada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
140 views3 pages

Sample Format of Meeting Minutes Example

This document outlines the required sections and content for a design project document. It includes sections for an abstract, table of contents, introduction/problem statement, literature review, methodology, performance analysis, conclusion, bibliography, and appendices. The methodology chapter must explain how the system is designed and put together, including functional requirements, component descriptions, and interactions. The performance analysis chapter provides experiments to prove the objectives were achieved and discusses results and observations.

Uploaded by

Paolo O. Lozada
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

OUTLINE OF THE DESIGN PROJECT DOCUMENT

(Title Page)
Approval Sheet
Biographical Data
Acknowledgement

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

Table of Contents
List of Tables
List of Figures
List of Appendixes

CHAPTER 1: PROBLEM AND ITS SETTING


1.1 Introduction
1.2 Statement of the Problem
1.2.1 General Problem
1.2.2 Specific Problem

1.3 Objectives of the Study


This should be taken from the corresponding sections of the approved thesis
proposal. The scope and limitations may be further elaborated but nothing must be
changed, added, nor removed without the written approval of the Thesis Coordinator.

1.3.1 General Objective


1.3.2 Specific Objectives

1.4 Scope and Limitations


1.5 Importance of the Study
1.6 Definition of Terms

CHAPTER 2: REVIEW OF RELATED LITERATURE


2.1 Local Literature
2.2 Foreign Literature
CHAPTER 3: METHODOLOGY
3.1 Materials and Method
3.2 System Design Specification
This should contain an explanation of how the system is put together. This
chapter may have several sections and subsections. This section may start by giving
an overview of the overall specifications and functional requirements of the system. It
shall discuss the functionalities and detailed description of the different components
of the system. Hardware and software components, as well as their interactions, may be
discussed graphically using design tools such as hierarchical charts, data flow diagrams
(DFD), entity relationship diagrams (ERD), and block diagrams. Normally, the general
diagram of the system is presented and explained here on a per block basis, including
the interrelation of each. The next section/s should describe the inner working of each
block/module in detail. Emphasis should be given on how the proposal attempts to solve
the specified problem.
:
:

3.n Summary

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 thesis 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 and Analysis


This should give an overview of the results from the experiments. 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.4 Summary

CHAPTER 5: CONCLUSION
The 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 thesis document. The
sequence may either be in the order of citing or in order of the first author’s surname.

APPENDICES
These should contain the raw data, program listing, and the technical and user’s
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 (possibly by circuit
block/section) and circuit board layout/s (if available). 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 user’s manual should
contain detailed procedures on how to set-up and use the system.

You might also like