Title of Your Study

TITLE OF YOUR STUDY
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 System
by
<lastname, firstname, middle initial of proponents>

May 2019
TABLE OF CONTENTS
Pag
e
TITLE PAGE i
APPROVAL SHEET ii
ACKNOWLEDGMENT iii
ABSTRACT iv
TABLE OF CONTENTS vii
LIST OF FIGURES x
LIST OF NOTATIONS x
LIST OF TABLES x
CHAPTER
1 INTRODUCTION
Project Context 1
Purpose and Description
Objectives
Scope and Limitation of the Study
2 REVIEW OF RELATED LITERATURE/SYSTEMS
3 TECHNICAL BACKGROUND
4 METHODOLOGY
Planning Phase
Gantt Chart
Analysis Phase
Cost and Benefit Analysis
Project Design
Overview of the Proposed System
Use Case Diagram with Automation Boundary.
Interface Design
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
Include Interfaces of the running program, report
forms, tables of the result on the performance of
the system
6 CONCLUSIONS AND RECOMMENDATIONS
Conclusions
Recommendations
REFERENCES
APPENDICES
A Relevant Source Code
B Transmittal Letter
C Sample Input/ Output/ Reports
D Users Guide
CURRICULUM VITAE
Note:
Pls. use Arial font name, 12 font size, double
spacing Right margin=1.5”, Top, Left &
Bottom margin = 1” Pagination is top right, no
page within the chapter page

LIST OF TABLES
Table Pag
e
1 Use Case 1 -
2
3
4
5
LIST OF FIGURES
Figure Pag
e
1 Use Case Diagram of the Study
2 Sequence Diagrams
3
ABSTRACT
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 the entire essential proposal so as 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.
Purpose and Description
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.
Statement of Purpose and 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, and time-
bounded. 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 thesis and, therefore, must not be included
here.
It was the purpose of this study to evaluate the Cashiering and Inventory System
of Sescon Cycle Parts with the intention of coming up with a proposal for
computerization. Specifically, this seeks to achieve the following objectives.
1. To document the system in terms of its design and technical

specifications;
2. To develop the system, and
3. To test the system performance.
Scope and Limitations
• This section discusses the boundaries (with respect to the objectives) of

the research and the constraints within which the research will be develop.
• 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.
• Justifications for the identified limitations and assumptions must be

included here. Assumptions are the conditions that must be satisfied or things
that must be existing/available/followed in order for the system to function
properly. Ignoring such assumptions might result in system malfunction, which
will not be the responsibility of the proponent.
Review of Related Literature/Systems
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
 Include discussion on conceptual design/system architecture/block

diagrams and algorithms
 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:
?? 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
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
Define it….
Cost Recovery Scheme (Payback Period)
Project Design
Use Case Diagram
Sequence Diagrams
Interface Designs

Title of Your Study

Uploaded by

Copyright:

Available Formats

Title of Your Study

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Title of Your Study

Uploaded by

Copyright:

Available Formats

TITLE OF YOUR STUDY

A Capstone Project Presented to the

<lastname, firstname, middle initial of proponents>

spacing Right margin=1.5”, Top, Left &

Bottom margin = 1” Pagination is top right, no

page within the chapter page

A summary of the entire essential proposal so as busy executive can read it

Purpose and Description

This section explains why research must be done in this area. It

Statement of Purpose and Objectives

• This subsection is an elaboration of the general objective. It states the

1. To document the system in terms of its design and technical

Scope and Limitations

• This section discusses the boundaries (with respect to the objectives) of

• Justifications for the identified limitations and assumptions must be

This section discusses the features, capabilities, and limitations of existing

- Include in-depth discussion on relevant technical aspects of the project

 Include discussion on conceptual design/system architecture/block

?? who is responsible for the task

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.