Professional Documents
Culture Documents
Capstone Project Format
Capstone Project Format
Page
TITLE PAGE i
APPROVAL SHEET ii
ACKNOWLEDGMENT iii
EXECUTIVE SUMMARY iv
TABLE OF CONTENTS
LIST OF FIGURES
LIST OF NOTATIONS
LIST OF TABLES
CHAPTER
1 INTRODUCTION 1
Project Context 1
Purpose and Description
Objectives
Scope and Limitations
3 TECHNICAL BACKGROUND 15
4 METHODOLOGY 18
Project Planning 18
Gantt Chart
Project Analysis
Cost and Benefit Analysis
Cost Recovery Scheme (Payback Period)
Project Design
Use Case Diagram
Interface Designs
Class Diagram
System Flowchart
Program Flowchart (Highlights)
Project Development
Program Specification
Software Specification
Hardware Specification
Deployment Diagram
Project Evaluation
Software Testing
5 RESULTS AND DISCUSSION 35
REFERENCES 60
APPENDICES 62
A Relevant Source Code 62
B Transmittal Letter
D Sample input/output/Reports
C Users Guide
CURRICULUM VITAE
A Capstone Project
Presented to the
Faculty of the College of Engineering & Information Technology
Surigao State College of Technology
Surigao City
In Partial Fulfillment
of the Requirements for the Degree
Bachelor of Science in Information Technology
By
December 2018
LIST OF FIGURES
INTRODUCTION
Project Context
APPENDIX A
From 150 to 200 words of short, direct and complete sentences, the abstract should be
informative enough to serve as a substitute for reading the thesis itself. It states the rationale
and the objectives of the research. Do not put citations or quotes in this section. Avoid
beginning the abstract with “This paper/document/thesis/study/project/...”
A summary of all the essential proposal so a busy executive can read it quickly and decide what
parts of the plan to read in more depth.
Introduction
- Project Context
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. Discussion must not be too
technical or too detailed.
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 research objectives.
This section explains why research must be done in this area. It rationalizes the
objective of the research with that of the stated problem. Avoid including here
sentences such as “This research will be beneficial to the
proponent/department/college” as this is already an inherent requirement of all thesis
project. Focus on the research’s contribution to the Information technology field.
- Research Objectives
General Objectives
This section states the overall goal that must achieved to answer the
problem.
This section states the specific requirements that must be met by the system.
Specific Objectives
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, time-
bounded. Each specific objective may start with “to
design/survey/review/analyze...”
This section discusses the scope and limitations (i.e., the level of capability or
extent of power) of each major function. This means that operations, which
are beyond the identified limits, will simply be invalidated/ignored, and will
note cause the system to malfunction, but instead cause the system to respond
with error messages.
This section discusses the features, capabilities, and limitations of existing research,
algorithms, or software that are related/similar to the thesis. The reviewed works and
software must be arranged either in chronological order, or by (from general to
specific). Observe a consistent format when presenting each of the reviewed works.
Technical Background
- Include in-depth discussion on relevant technical aspects of the project
Methodology
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 Thesis Writing.
Examples of activities include inquiry, survey, research, brainstorming, canvassing,
consultation, review, interview, observe, experiment, design, test, document, etc. The
methodology also includes the following information:
Project Planning
Gantt Chart
This section discusses the hardware and software resources needed to
implement and to execute the system. If the system has a special set of target
users, this section also includes the user specification (e.g., educational level,
experience, and technical expertise). For certain uncommon resources, a
discussion of why such resources are necessary must also be included.
Project Analysis
Cost and Benefit Analysis
Cost Recovery Scheme (Payback Period)
Project Design
Use Case Diagram
Sequence Diagrams
Interface Designs
Class Diagram
System Flowchart
Program Flowchart (Highlights)
This section presents the initial internal design of the system, by discussing its
major components and their interactions. These components include the
software components (e.g., modules, database systems, etc.), as well as the
hardware components (e.g., processors, devices, etc.). The components and
their interactions are graphically represented using design tools, such as
hierarchical charts, structure charts or object models. Data flow diagrams may
also be included to show how information passes among processes. In addition,
discussions on why certain alternative and trade-offs were chosen must be
included (e.g., issues on software decomposition, cost of hardware).
This section discusses the design and implementation of the major data
structures and algorithms used in the software. It included a discussion on the
major issues and problems encountered, and the corresponding solutions and
alternatives employed by the proponent. Parts of the design tools in the
Technical Manual may be lifted as figures in this section.
Project Development
Program Specification
Software Specification
Hardware Specification
Deployment Diagram
Project Evaluation
Software Testing
- The type(s) of tests performed varies depending on the system developed. For instance,
commissioned software would require a detailed acceptance test and system response
time analysis, while software implementing an algorithm would require an analysis of
the performance of the algorithm on different machines or on different test data.
- This section discusses the features, capabilities, and limitations of existing research,
algorithms, or software that are related/similar to the thesis. 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.