Capstone Project Guidelines - 11

Chapter 1
RATIONALE
Capstone Project and Research is a six-unit (6.0) course required for
BS Information Technology students. A Capstone project is a terminal project
requirement that would not only demonstrate a student’s comprehensive
knowledge on his/her area of specialization and research methods used but
also allow them to apply the concepts and methods they have acquired (CMO
25 S. 2015). The primary aim of the Capstone project is to significantly
address an existing problem or need by introducing automated/computerized
systems.
Eastern Samar State University - College of Computer Studies (CCS)

ensures that quality projects are developed and that they conform to
international standards. The college also ensures that Capstone Projects are
in consonance with the priority thrusts under the College of Computer Studies
Research Agenda.
This document intends to guide students and faculty-advisers in

determining the allowable standards for a Capstone Project. This document
also contains the format of the manuscript that will be submitted once the
project has been successfully defended.
CCS Research Agenda
Thrust Key Result Area Objectives Research Areas
Education and Human Poverty Reduction Improve Interaction and Network Technology
Resource and Empowerment of Communication through the
Development the Poor & Vulnerable application of wired and
wireless network technologies
Enhance the teaching and

learning process through the Software Development
use information and
communication technology in
instruction
Establish flexible and distant

learning through the
development of e-learning
sites. Website Development
Agriculture, Fishery, Rapid, Inclusive and Integrate computerized Software Development
Forest and Natural Sustained Economic systems to agricultural
Resources Growth production activities
Integrity of the Support farming systems

Environment and innovation through modelling
Climate Change and simulations.
Adaptation and
Mitigation Use of digital arts in promoting
agricultural technologies
Thrust Key Result Area Objectives Research Areas
Engineering and Rapid, Inclusive and Promote low-cost computing Software/Hardware

Energy Sustained Economic through the development of Development
Growth improvised hardware and
software technology
Integrity of the
Environment and
Climate Change
Adaptation and
Mitigation
Livelihood and Rapid, Inclusive and Develop Information Systems Software/Hardware

Industry Sustained Economic and Strategic plans that will Development
Growth help improve production,
processing and operations
Health Care, Nutrition Poverty Reduction Develop Information Systems Software/Hardware

and Human Welfare and Empowerment of with usable common database Development
the Poor & Vulnerable for the University and its clients
Law, Legislation and Poverty Reduction Ensure that Intellectual Intellectual Property
Justice System and Empowerment of property rights are properly
the Poor & Vulnerable observed
Develop information systems

that will support justice
system.
Estehanon Culture Poverty Reduction Promote Estehanon culture Website Development
and Arts and Empowerment of and Arts through the
the Poor & Vulnerable development of software
applications and websites
Scope of the Project

BS Information Technology Students must complete a capstone project
in the form of an IT application, a Multimedia System or an Information
System Strategic Plan. Recommended infrastructure and its implications on
other systems should be reflected in the final report.
The Capstone Project Adviser should determine the appropriate

complexity level of the specific problem being addressed and the proposed
solution, considering the duration of the project, the composition of the team ,
and the resources available.
Suggested Areas of Study

The proposed project may fall in any of the following categories, but not
limited to:
Software Development
 Software Customization
 Information Systems Development for an actual client
(with pilot testing)
 Web Applications Development (with at least alpha
testing on live servers)
Multimedia Systems
 Game Development
 E-Learning Systems
 Interactive Systems
 Information Kiosks
Network Design & Implementation and Server Farm Configuration

and Management
IT Management
 IT Strategic Plan for sufficiency complex enterprises
 IT Strategic Analysis, Planning, and Implementation
Prerequisites
The prerequisite of the Capstone Project covers all the subjects from
first year to third year. However, exemption can be given to students with only
one subject remaining enrolled in that current semester.
Chapter 2
CAPSTONE PROJECT TEAM MEMBERS
The Capstone Project team is composed of at most five (5) members. The
following are the roles that the proponents/researchers should play:
Project Manager (PM) - The person with authority to manage a Research /

Capstone Project. This includes leading the planning and the development of
all Research / Capstone Project deliverables. The project manager is
responsible for the budget, work plan and all Project Management Procedures
(scope management, issues management, risk management, etc.).
Systems Analyst / Database Designer (SA/DD) – the person who ensures

that all parts of the system are coordinated. The person who makes sure that
the database design is complete and robust. He coordinates with the PM.
Network Designer / UI Designer (ND/UID) – The person who is responsible

for the system’s network design and prepares the User-Interface design
(Forms/ Screen Shots/ Storyboard). He coordinates with the SA/DD.
Software Engineer / Programmer (SE/P) - The person who designs, writes,

and tests computer programs. He coordinates with the ND/UID.
QA Tester/ Technical Writer (QA/TW) - The one who ensures the quality of
the software product and help find and eliminate any bugs. He determines the
functionality of every aspect of a particular application. A person who finalizes
the Research / Capstone Project study document, both the system and the
Research / Capstone Project manuscript. He coordinates well with the SE/P.
Duties and Responsibilities of Proponents/ Project Members

1. Choose, with guidance of the Adviser and the approval of the Panel
Members, a Capstone Project.
2. Follow dutifully the guidelines set in the Capstone Project Writing
Manual.
3. Consult regularly with the adviser the progress of the project.
4. Keep track and follow the schedules given by the Over-all and
Capstone Adviser.
5. Religiously submit milestones, deliverables and other requirements.
6. Ensure that plagiarism is avoided and intellectual property rights are
observed.
7. Allow the inclusion of the Project Adviser to be one of the Projects’ co-
author for future presentations and publication
Duties and Responsibilities of the Subject Adviser
1. Announce Research / Capstone Project areas (at the start of the each
semester) to the students;
2. Conduct general meetings with the students to discuss the Capstone
Project Guidelines, Policies and Deliverables, and to allow the students
to raise and clarify issues;
3. Select a Proposal Hearing and Oral Defense panel for each team;
4. Schedule Research / Capstone Project activities, such as the deadlines
of deliverables and Proposal Hearing and Oral Defense sessions.
5. Post schedules, Proposal Hearing and Oral Defense guidelines,
requirements guidelines, and other announcements;
6. Furnish every member of the Proposal Hearing and Oral Defense
panel with all the necessary Capstone Project documents before the
Proposal Hearing or Oral Defense; File at least one copy of the
Proposal Hearing and Oral Defense panel's evaluation (including
revisions) and the Revised and Approved Deliverables at every stage
of the Research / Capstone Project.
7. Submit collated grades of students under his/her section for that term.
Duties and Responsibilities of Project adviser

1. Guide the Capstone project advisees in the formulation of a project
proposal, activities involving the writing of the documentation and
development of the software.
2. Meet the proponent at least once a week to:
a. Check the progress of the Project.
b. Identify areas of improvement and provide recommendations
as to how the documentation and the software project can be
improved.
3. Recommend the proponents for an Oral Defense by signing the
Request for Proposal Hearing form (Capstone form 5) after thoroughly
examining the readiness of the proponents and their respective
projects.
4. Clarify the points during Pre-oral and Final Defense, if necessary
argue the points being suggested,
5. Ensure that recommendations of the panel members are incorporated
into the team’s documentation and software project.
6. Keep informed of the schedule of Capstone Project Activities, required
deliverables and Deadlines.
7. Recommend to the Panel Members his/her deserving advisees for an
award.
The English Critic

The proponent should consult an English Editor every time they submit
for an Oral Defense to keep the grammar used in their manuscript in line and
correct. An English Editor should be a faculty of the Eastern Samar State
University and an English Major. The department shall coordinate with
languages department of the College of Arts and Sciences and the College of
Education in determining the roster of suitable editors.
The Statistician
The statistician is any individual that the proponent may consult
regarding the statistical aspects of their study, if the need arise. The
statistician should be a faculty of the Eastern Samar State University with
degree on Statistics or at least 3 years of experience in teaching statistics.
Panel Composition
The panel is composed of 1 Chairman and Panel Members identified by the

Dean/Program head. One of the panel members will concurrently act as the
censor, for the recording of the defense proceedings. Their duties and
responsibilities include the following, but not limited to:
Chairman:
1. Brief the Proponents/Researchers about the Proposal
Hearing or Oral Defense program during the actual
Proposal Hearing or Oral Defense, respectively.
2. Scrutinize the manuscript and the developed system of the
proponents.
3. Issue the verdict for the project. The verdict is a unanimous
decision among the four members of the Capstone Project
Defense panel. Once issued, it is final and irrevocable.
4. Nominate a Research / Capstone Project for the
Outstanding Research / Capstone Project Award.
Panel Members:
1. Scrutinize the manuscript and the developed system of the
proponents.
2. Evaluate the deliverables.
3. Recommend a verdict.
4. Equate the request of the adviser and/or the
Proponents/Researchers.
5. Nominate a Research / Capstone Project for the
Outstanding Research / Capstone Project Award.
Censor:
1. Record the proceedings of the Project Defense.
2. Provide a copy of the Team’s Recommendations to the
Subject Adviser.
Chapter 3
CAPSTONE PROJECT DURATION
The Capstone Project shall be completed within one semester and will
be divided into the following phases:
Pre-proposal Stage
1. Course Enrolment
2. Capstone Project Orientation
3. Short Listing of Possible Research / Capstone Projects
4. Title Critiquing and Patentability Check (Patent Searching) – via ITSO
5. Pre-Oral Defense
Documentation Stage
1. Writing of Chapters I, II, III, IV, V

2. Manuscript Submission
3. Manuscript Revisions
4. System/ Software Checking
5. System/Software Improvement
Final Defense
1. Submission of Final Manuscript

2. Completion of Software/ System
3. Final Oral Defense
Patent Process (via ITSO – optional)
1. Patent Drafting
2. Patent Application (if possible)
3. Technology Transfer
Chapter 4
GRADING SYSTEM
Group Grade
The group grade will be based on the following grading scheme:
Criteria for Evaluation Equivalent
Points
DOCUMENTATION (25%)
a. Completeness of Content 5
b. Substance, Format, Presentation & 5
Organization of Document
c. Diagrams
c.1 Data Flow Diagram 5
c.2 Entity Relationship Diagram 5
c.3 System Flowchart 5
PRESENTATION AND DECORUM (25%)
a. Appropriateness of attire 5
b. Articulation (Technical/Non-Technical) 10
c. Visual Presentation 5
d. Over-all organization of presentation 5
SOFTWARE (50%)
a. Ease in the use of chosen programming 5
language
b. Compliance to ISO standards in term s of:
b.1 Functionality 5
b.2 Reliability 5
b.3 Efficiency 5
b.4 Portability 5
b.5 Usability 5
b.6 Maintainability 5
c. Adequacy of Project Features 10
d. Congruency of the output to the Project 5
Objectives
Individual Grade
Individual grade will be given by each of the Project adviser. The grade
will be based on meeting deliverables on time, working attitude and technical
skills.
Final Individual Grade
The Final Individual Grade is the average of the Individual Grade and
the Group Grade.
Passing Score
Each Capstone member should be able to attain a minimum of 75% as

their final grade to pass in Capstone Project.
Verdict
There will be four (4) possible verdicts after the Final Oral Defense.
The verdict is a unanimous decision among the four members of the
Capstone Project Defense panel. Once issued, it is final and irrevocable.
1. Accepted with no revisions
2. Accepted with minor revisions
3. Accepted with major revisions (group may undergo redefense
upon the recommendation of the panel members.)
4. Not accepted (group is advised to undergo a redefense but non-
compliance to the recommendations of the panel means the group
will undergo the whole process of capstone project again.
Chapter 5
THE COMPONENTS OF THE MANUSCRIPT
As approved by the Capstone Project Committee, the Capstone Project

manuscript should contain the given format:
Chapter 1 – Introduction
Background and Rationale
Objectives
Development
Scope
Program Specification
Significance
Input Descriptions
Definition of Terms
Output Descriptions
Chapter 2 – Related Systems
Data Structure Descriptions
Chapter 3 – Methodology
Program Descriptions
Planning
Programming Environment
Software Development Model
Evaluation
Requirement Analysis
Research Design
Operational Requirements
Locale
Technical Requirements
Instrumentation
Gantt chart
Data Analysis
Design
System Testing (Alpha Test)
Output and User Interface
Acceptance Testing (Beta Test)
Process Design
Implementation
Data Flow Diagram
Chapter 4 Results and Discussion
System Flowchart
Chapter 5 Conclusion and Recommendation
Data Design
Bibliography
Entity Relationship Diagram
Appendices
Data Dictionary
System Architecture
Figure 2. Parts of the Capstone Project Manuscript

Chapter 6
THE MANUSCRIPT FORMAT
i. General Document Format

This section covers the fundamental construction of the document.
a. Margins
Top: 1.0 inch
Bottom: 1.0 inch
Right: 1.0 inch
Left: 1.5 inches
ii. Font
The font type of all the text is Arial size 11 unless otherwise specified, and
with 1.5 line spacing.
iii. Pagination
1. Pages containing chapter number and its title, should have no page
numbers appearing on them, but should be included in the numbering.
2. Pages excluded in item c.1 should contain the page number written on the
lower right corner, half inch from the bottom, one inch from the
right.
3. Pages before Chapter 1 i.e. the title page, approval sheet,
acknowledgement, dedication, table of contents, list of figures, list of table
and abstract should have page numbers written in roman numerals and
should appear on the lower right corner, half inch from the bottom,
one inch from the right.
NOTE: There should be no page number appearing on the title page.
iv. Figures
The figure label should appear below the figure, emboldened and centered
relative to the figure. The figures should be numbered accordingly from the
first to last figure in the manuscript.
Example: Figure 2. System Flowchart
v. Tables
The table label should appear above the table, emboldened and left justified
relative to the table. The tables should also be numbered accordingly from the
first to last table in the manuscript.
Example: Table 4. Data Dictionary
ii. Documentation
This section covers the actual contents of the documentation. It discusses all of
parts that are included in the documentation as contained in chapter 3 of this
manual.
a. The title page

The title page is located in the very start of the document. It should not
contain a page number, but is included in the counting of the pages.
TITLE of the STUDY

(centered, Arial, size 16, bold font style, ALL CAPS)
10-single spaces from the Title; space before: 0 pt; space after: 0 pt; Arial, 12
An Undergraduate Capstone Project

(centered, Arial, size 12, bold font style)
5-single spaces; space before: 0 pt; space after: 0 pt; Arial, 12
Presented to the Faculty of the
DEPARTMENT OF INFORMATION TECHNOLOGY

(centered, Arial, size 12,ALL CAPS, Bold)
College of Computer Studies
Eastern Samar State University
Borongan City, Eastern Samar

(centered, Arial, size 12,1.5 spacing)
In Partial Fulfilment of the Course Requirement for the Degree
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

(centered, Arial, size 12,ALL CAPS, Bold)

ii. Approval Sheet
The approval sheet should be fully signed and will only be included during the
final submission of the documents. If decided, the members of the panel may
include all core faculty members of the department.
ii
(right aligned, Arial, size 12)
APPROVAL SHEET
The Capstone Project attached hereto entitled Title of the Study was prepared and
submitted by the proponents Names of the Proponents, in partial fulfillment of the requirements
for the degree of Bachelor of Science in Information Technology has been defended orally and is
hereby recommended for approval.
(One Tab indent, justified, 1.5 space, Arial, size 12, regular font style except for the name of the student and
the title of the study)
Name of English Editor NAME OF ADVISER
English Editor Capstone Project Adviser

(Name of Adviser: right aligned, Arial,
(Name of English: left aligned, Arial,
Size 12, underlined, bold font style
Size 12, underlined, bold
Project Adviser: centered from the
NAME OF ADVISER, Arial, Size 12 )
…………………………………………………………………………………………………
Capstone Project Committee

COMMITTEE MEMBER COMMITTEE MEMBER

Member Member
COMMITTEE MEMBER
Member
…………………………………………………………………………………………………
iii. Acknowledgement
The acknowledgement should only include persons and/or entities that helped
in the technical aspect of the research (documentation and software) only.
iii
(right aligned, Arial, size 12)
ACKNOWLEDGEMENT
The Acknowledgement should contain acknowledgements to anyone and

everyone.
(One Tab indent, justified, 1.5 space, Arial, size 12)
iv. Dedication
The dedication is the only section the documentation where no formatting will
apply. It can contain dedications to and/or thank you to anyone and everyone
the authors wishes to include, unlike in the acknowledgement the authors can
now include persons and/or entities who has contributed in the non-technical
aspect of the project, it may include parents, relatives etc. The dedication
should only be one page.
iv
(page number will depend on
the number of page of
the preceding page
right aligned, Arial, size 12)
DEDICATION
v. Table of Contents
The table of contents should contain an index with page numbers of all the
contents of the documentation. It is highly recommended that the authors
should use the automated feature of a word processor to produce the table.
v
(page number will depend on the number of page of
the preceding pageright aligned, Arial, size 12)
TABLE OF CONTENTS
PAGE
Title page i
Approval Sheet ii
Acknowledgement iii
Dedication v
Table of contents vi
List of Figures viii
List of Tables ix
vi. List of Figures/Tables

The list should include all figures/tables included within the documentation; it
may include figures/tables from a citation. The list should be in three columns
containing table, description and page respectively.
vi
the preceding page
LIST OF FIGURES / TABLES

Table Description Page

vii. Abstract
The abstract gives the reader an overview of the study, based on information
from the other sections of the documentation. The information given in the
abstract is usually the basis of many readers as to whether they will read the
entire report or not. The abstract should contain maximum of 200 words.
The typical information elements included in an abstract are as follows:

1. Some background or general information on the study
2. The main topic (or purpose) of the study and its scope
3. Some information on how the study was conducted (or the methodology
used in the study)
4. The most important findings of the study
5. A statement of conclusion (justified based on the data presented).
NOTE: Abstract will only be written when the study is completed.
viii. Chapter I - Introduction

ix
(page number will depend onthe number of page of
the preceding page right aligned, Arial, size 12)
ABSTRACT
Title : Aradman: Eastern Samar State University Online Classrooms
Proponent : Casillano, Niel Francis B.
Adviser : Engr. John Glenn Ocaña
Contents of the Introduction are divided into five sections, as follows:

i. Background and Rationale
ii. Objectives
iii. Scope
iv. Significance of the Study
v. Definition of Terms
The page number will only appear after the heading page (the page
containing the Chapter title).
i. Content of the Background and Rationale

The Background and Rationale gives an overview of the project, giving
the reader a background or basis of the problem to be reported. It can
be divided into five parts, as follows:
1. The setting or context or frame of reference

This part gives general statement(s) about a field of research to
provide the reader with a preview of the problem to be reported.
2. The review of previous research

This part continues the contextual setting or frame of reference
given in Part 1 by including more statements about the general
aspects of the problem already investigated by other
researchers.
3. The gap or missing information

This part refers to the statement(s) that indicate the need for the
study or the need for more investigation.
4. The statement of purpose

This part gives very specific statement(s) pertaining to the
objective(s) of the study.
5. The statement of value

This part refers to statement(s) that give the significance of
carrying out the study.
NOTE: The Background and Rationale is written continuously

paragraph by paragraph.
ii. Content of the Statement of the Problem
The statement of the problem enumerates the statements that are to
be satisfied by the study.
This section should contain the following:

1. Introductory statements
2. General problem statement
3. Enumeration of statements in a form of a question or plain
statement.
NOTE: The Statement of the Problem is written in an enumerated
form using numberings ex. 1, 2, 3,...
iii. Content of the Scope and limitation of the Study

The scope and limitation of the study enumerates the domain / area at
which the study focuses. It provides information such as the location of
the study, the main processes involved.
This section should contain the following:
1. Introductory statements
2. General scope and limitation statements
3. Enumeration of the scope
4. Enumeration of the limitation
This section should be supported by a complete list of processes
certified by the head of the department, manager or any person of
authority by the organization or company and additional scope and
limitation determined by the panel.
iv. Content of the Significance of Study

The significance of the study enumerates why the study has been
conducted and its significance. It may enumerate the significance to
the following sectors:
a. Institution
b. College / Department
c. Proponent
d. Etc.
NOTE: The Significance of the study is written in a continuous
paragraph, each paragraph is hinted by the sector being
discussed.
v. Content of the Definition of Terms

The definition of terms shall contain ALL TECHNICAL TERMS,
including all abbreviations and acronyms used in the study and its
definitions in its simplest form. The terms must be alphabetically
arranged. Correct citation from where the definition has been taken
should never be forgotten.
NOTE: The Term is written in an enumerated form but without

numberings nor bullets.
Definition of Terms
Agile Manifesto - also called the Manifesto for Agile Software Development, is a
formal proclamation of four key values and 12 principles to guide
an iterative and people-centric approach to software development.
User Acceptance
Testing (UAT) - also called beta testing, application testing, and end user
testing - is a phase of software development in which the software
is tested in the "real world" by the intended audience.
Below is how the chapter page should appear. It should contain no page number.
The sections, if present should be written in upper case and emboldened. Start
the discussion of a section immediately following the section title. As indicated
with the example, the start of the discussion should the indented with two tabs
from the left, the paragraph body with one tab from the left. The basic setup of
this chapter page is the same all throughout the document.
Chapter I
(Capitalized the first letter only, bold font style, center page)
CHAPTER TITLE
(All Caps, bold font style, center page)
SECTION TITLE
(Left Aligned, Arial, size 12, All Caps, bold)
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum sed orci tellus. Cras
vitae quam nisl, vel malesuada sapien. Proin eu metus sed lorem laoreet eleifend at ac risus.
Donec bibendum imperdiet risus, nec imperdiet leo faucibus eu. Sed porttitor consequat odio in
scelerisque. Curabitur posuere mi lectus.
ix. Chapter II – Review of Related Systems/Review of Related

Literature
i. Literature Review
The literature review is basically an evaluated, organized, and
synthesized collection of citations to other literatures / studies (NOT a
MERE listing of previous studies), which are related or somewhat
related to your own specific research problem. It serves three
important functions.
1. It continues the process started in the introduction of giving the

readers background information needed to understand your
study.
2. It assures the readers that you are knowledgeable about the
significant research that has been done in your area of
investigation.
3. It establishes your study as one link in a chain of research that
is developing and enlarging knowledge in your field of research
interest.
The role of literature review is as follows:

1. It will increase your confidence in your topic as a result of the
time, effort, and resources you invested in studying your
research problem.
2. It can give you new ideas and approaches that may not have
occurred to you.
3. It can inform you about other researchers doing work in the
same area of studyindividuals whom you may choose to
contact for advice or feedback.
4. It can show you how others have tackled methodological and
design issues in studies similar to your own.
5. It can lead you to sources of data that you may not have known
existed.
6. It can orient you to measurement tools that other researchers
have developed and used effectively.
7. It can reveal methods dealing with problem situations that may
be similar to difficulties you are having.
8. It can help you get meaning out of your data or make sense of
your findings and, eventually, help you tie your results to the
work of previous researchers.
The difference of a literature from a study:

 Literatures - refers to texts, books, pieces of writing; written works.
 Studies - refers to research, analysis and/or experimentation
regarding a subject, and may refer to written work that regards such
studies.
Ways to cite references in review of related literature:

All references must be stated in the review of literature / studies; no
report will be accepted without the proper acknowledgement to the
authors referred to in the literature review. Please refer to the citation
section of this manual.
The composition of the literature review
The number needed for a complete Literature Review is at least ten
(10). The composition of the ten (10) citations shall either be literature or
related study. The citation maybe local, national or international in nature
as long as it completes the ten (10) that is needed. There will be no
distinct sections between a literature or related study.
Sources of literatures
A published book is the safest source of literature. If available
books are not sufficient to compose the needed number of citations the
proponent may utilize internet sources. Internet sources, though abundant,
should be taken with caution in citing literatures as some of the sources
are not reputable. Below are the sources that should NOT BE INCLUDED:
1. Wikipedia
2. Articles without authors
3. Any wiki site
Chapter II
REVIEW OF RELATED SYSTEMS

(All Caps, bold font style, center page)
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum sed orci tellus. Cras vitae
quam nisl, vel malesuada sapien. Proin eu metus sed lorem laoreet eleifend at ac risus. Donec
bibendum imperdiet risus, nec imperdiet leo faucibus eu. Sed porttitor consequat odio in scelerisque.
Curabitur posuere mi lectus. Nulla cursus feugiat felis. Nunc non nunc et neque vulputate suscipit.
Aliquam tincidunt sollicitudin volutpat.
ii. Theoretical Framework
Chapter two will also contain the theoretical framework. The

Theoretical framework is the framework from which the study revolves
around, the sort of essence / driving force of the study. The theoretical
framework is stated in pictorial form; however the figure should be
discussed. The discussion should contain:
1. The description of the figure
2. The significance / connection of the selected framework to the
study.
The researcher may select from any models in connection to the study
but it is strongly suggested that the researcher should select from
known process models discussed under the course software
engineering. Examples are:
1. Waterfall model
2. V model
3. Prototyping model
4. Etc.
Although the researchers are encouraged to use known process
models they are not, however, restricted from inventing or including
other frameworks that proves valuable and relevant to the study. The
inclusion of such should be defended in the discussion of the figures.
NOTE:
x. Planning, Design and Specification

Chapter III contains the tools, methods and techniques that were used
in the study; the chapter is divided into 6 sections:
i. Gantt Chart
ii. System Design Specification
a. Data Flow Diagram
b. Entity Relationship Diagram
c. Data Dictionary
d. System Flowchart
e. Requirements
iii. Hardware Specifications
iv. Software Specifications
a. Operating System
b. Application Software
v. System Development
vi. System Deployment
NOTE:
1. Before the actual discussion of the sections and subsections an
introductory paragraph should be provided. This should be placed
immediately after the chapter title.
2. The discussions of the above sections and subsections should be
complete. Each section and subsection above should discuss the
actual figure generated by the study and the figure that is generated
must be attached not on the appendices but contained in the
sections and subsections, respectively.
i. Gantt Chart section

The main purpose of this section is to track the progress of the
development of the project corresponding to the framework the
researcher has chosen to follow.
This section should include the following:
 A discussion on what is a Gantt chart, its components and its

use. Please refer sample format provided below.
 A discussion on specific activities included in the study and its
time allotment. These activities are the activities mentioned in
the theoretical framework.
 The chart itself with its proper label, meaning it will appear
within this section and not as an appendix. The label refers to
the vertical and horizontal axis. Refer to the sample page
provided.
ii. System Design Specification Section

The System Design Specification Section is a portion of the
documentation devoted to capture the predevelopment phase of the
project, which is the specification of the software or information system
or website.
The researcher should include a preliminary or introductory discussion

before any subsection is discussed.
a. Data Flow Diagram

This subsection should include the following:
 A discussion on what is a Data Flow Diagram (DFD)

including the difference, in context, between an existing
DFD from a proposed DFD, its figure components and its
use. Please refer sample format provided below.
 A discussion of the whole data flow diagram, i.) Context
Free Diagram, ii.) Context Level Diagrams and iii.) Child
Diagrams, but separated into two existing and proposed,
during the discussion the researcher should not forget to
use the figure numbers and / or page numbers.
Additional notes
 The proposed DFD should include an indicator (broken

line box) where the automation will happen.
 If the two DFDs, existing and proposed, has no difference
the author would no longer need to include the child
diagrams, only the Context Free and Context Level
Diagrams with the indicator should be present for the
proposed DFD.
 No more than one diagram should be found on a single
page.
 The researcher will use Gane-Sarson notation.
b. Entity Relationship Diagram (ERD)

This section should include the following:
 A discussion on what is an Entity Relationship Diagram
with proper document citations.
 Complete Figure Definition, not a portion of the set figure
of figures.
 A discussion on the whole ERD focusing on the
relationships.
 The researcher shall use Crow's Foot notation without
the listing of fields which will be included in the next
subsection.
c. Data Dictionary
This subsection, though maybe differently defined in authored
books, should include a tabular representation of the fields in
the entities included in the ERD and also included here those
that are not represented in the ERD like temporary tables etc.
The tabular representation should include the following

columns:
i. Field Name
ii. Data Type Name
iii. Size
iv. Attribute Type
v. Description
 The tables generated from the subsection should follow
the standard table naming convention
 Following the table a discussion should be provided
examining what the table is, its use and purpose.
d. System Flowchart
The System Flowchart as the subsection title implies should
include presentation and discussion of the overall flow of the
system presented graphically using flowcharting figures.
Thereby it should follow that the subsection should include the
following:
 A definition of what is a Flowchart with proper document

citations.
 A complete set of figure components and its definition.
 A thorough discussion of the generated flowcharts.
During the discussion the researcher should not forget to
include the figure numbers and page numbers.
e. Requirements
In this section, the researcher will try to consolidate what has
been discovered during the gathering of facts from the
institution, office or company. Following the guide questions
found on a Software Engineering book by Shari Lawrence
Pfleeger the researcher should unfailingly answer all questions
thoroughly. Answer every question provide.
The questions are divided into several groups which are:
o Physical Environment
o Interfaces
o Users and Human Factors
o Functionality
o Documentation
o Data
o Resources
o Security
 If the question is answerable by yes or no the researcher is
obliged to discuss why the proponent has arrived to the
answer.
 Especially on item Functionality, the researcher should
consult an adviser as to what functions are to be included in
the study. The section in chapter 1, scope and limitation can
provide adequate listing of functionality.
iii. Hardware Specifications section

The Hardware Specifications section discusses the minimal
requirements needed by the system; it is divided in two parts:
 Development
 Implementation
A discussion should be provided in each part examining its purpose.
iv. Software Specification section

This section is divided further into two subsections:
 Operating System
o Development
o Implementation
 Application Software
o Development
o Implementation
A discussion should be provided in each part examining its purpose.
Note:
 When discussing operating system particularly on
implementation the researcher should provide evidence
(screenshots) that the system can actually run on the mentioned
OS. The screenshot should include proper naming convention.
v. System Development section
In paragraph form the researcher will try to discuss all and everything
that had happened during development of the software mentioning
along the applications including operating systems that was used in the
development and testing. The researcher may also include a
discussion problems met related to the application and operating
system.
vi. System Deployment section

The System Deployment Section will discuss how the system will be
deployed it should include what installers are needed, how they are
installed, the proponent should occasionally refer to the user manual
and some parts of the requirements section for reference, training
plans should also be included.
Sample format of Figure Definition

Data flow diagram or DFD is a graphical representation of the flow of data through an
information system.
- Flow of Data. The arrow shows the movement of data from one
input point to another, with the head of the arrow pointing
towards the data’s destination. Arrow also represents data about
a person, place or thing, so it should describe with a noun.
- A rectangle with rounded corners is the Process. It is used to
show the occurrence of transforming process. A process is
always denotes a change in or transformation of data.
- An open-ended rectangle represents the Data store. A

depository for data that allows addition and retrieval of data. The
two parallel lines are drawn only wide enough to allow identifying
lettering and so on to identify its level.
Chapter III
METHODOLOGY
(All caps, bold font style, center page)
Section Title
(Left Aligned, Arial, size 12, bold)
NOTE: The format of this chapter that will be followed is similar to
the format specified in chapter 1 including the format specified for
the sections. The difference is the format specification of the
subsection, where all of the subsections are indented including the
discussion.
xi. Testing and Results

The chapter IV is divided into three sections:
 Acceptance Testing – System User

 Screen Shots
 System Reports
The page number will only appear after the heading page (the page
containing the Chapter title).
Acceptance Testing – System User:

Screen Shots section:
 Main features
 Addition features
This section shall contain all possible screen shots, discussing each screen shot
for its use. Each screen shot will be discussed thoroughly after its presentation,
the discussion should contain:
 What particular objective the screen shot is associated with
 The features what the screen shot depicts
 And all other details about the screen shot
For Screen Shot label it this way:
Figure 4.1 Main form of the Proposed ESSU Automated Beauty Pageant
Tabulation System
NOTE: The format of this chapter that will be followed is similar to the
format specified in chapter 1 including the format specified for the
sections.
Chapter IV
RESULTS AND DISCUSSION

System Development Results

(Left Aligned, Arial, size 12, bold)
xii. Summary, Conclusion, and Recommendation
The chapter V is divided into three sections:
 Summary
 Conclusion
 Recommendation
The page number will only appear after the heading page (the page containing the Chapter
title).
Content of the Summary section

This section discusses the summary of the whole study, discussing briefly
the major points of the study, i.e.
 Summary of the whole chapter one (1) the introduction but giving
emphasis on the statement of the problem.
 A relevant citation from chapter two (2) and briefly including the theoretical
framework.
 A summary of tools used, enumerated from chapter III
 A quick discussion of the results
Content of the Conclusion section
This section discusses the conclusion/s that has been derived from the
study. It shall discuss only to the bounds of what has been found in the
analysis of the data. The conclusion shall be listed in enumerated format
answering the problems proposed in chapter one (1).
Content of the Recommendation section
According to the conclusion/s that has been derived the researcher shall make
the recommendations about the system.
Chapter V
CONCLUSIONS AND RECOMMENDATIONS

SUMMARY
The following sections
xiii. Bibliography
The bibliography is a listing of all references used in the study; it should
include all of references lifted from the internet. The listing should appear sorted
alphabetically. The bibliography is divided into 3 sections, they are:
 Published Books
 Unpublished Books
 Websites
Rules about using internet text are discussed in the citation section of the
manual.
the preceding page
Bibliography
A. Published Books
Downie, N.M. Basic Statistical Methods. New York. Harper and Row Publishers, 1984
Dy, Josanna Maribeth W. et. Al. Computer Fundamentals. Technology and Livelihood
Recourse Center, Urban II Bldg. Sen. Gil J. Puyat Ave., Makati, Metro Manila,
Philippines. 1990
B. Unpublished Books
Apelado, Joan B. et.al. A Payroll System of National Irrigation
Administration. Eastern Samar State University. Borongan City,
Eastern Samar. 2003
Bebita, Ferdinand et al. ESSU-CSD Knowledge Base System. Eastern Samar State
University. Borongan City, Eastern Samar.2007
C. Websites
Anonymous. Developing Entity Relationship Diagrams.
http://www.infocom.cqu.edu.au/Courses/spr2000/95169/Extra_Examples/
ERD.htm Retrieved last August 17, 2008.
xiv. Appendices
1. The word Appendices is all capitalized, bold font style, center of page,
included in the numbering.
2. Name each appendix as A, B, C, etc.
3. Write the title of the appendix below the appendix label.
 The list of appendices are as follow:

1. Communication Letter
2. Student-Adviser Agreement
3. Software Evaluation Questionnaire
4. User Manual
5. Pictorials
6. Curriculum Vitae
The curriculum vitae is the document listing the research’s author
Page number
the preceding page
CURRICULUM VITAE
ID picture here 2x2
School uniform
Name: Josephus Argus Mikhail D. Afable

Pseudo Name: JamJam
E-mail Address: j.argus.m@ygmail.com
Contact Number: (055) 560-XXXX/0927755XXXX
Birth date: May XX, XXXX
Address: Brgy. Songco, Borongan City, Eastern Samar
Parents:
Father’s Name: Kenneth Rey C. Afable
Mother’s Name: Maria Fatima D. Afable
Preliminary Education
Elementary: UP Integrated School
Diliman, Quezon City
Year Graduated: 2022
Secondary: UP Integrated School
Diliman, Quezon City
College: Eastern Samar State University
Brgy. Maypangdan, Borongan City, Eastern Samar
Course: Bachelor of Science in Information t=Technology
xv. Honorariums
As provided by the University Research Manual the honorariums shall be:
a. Adviser: 500.00
b. English Editor: 200.00
c. Member of the Project Defense Panel: 300.00
Single Payment per Semester.
xvi. Post Defense actions
Once the group receives a “Accepted” final verdict, the group should:
1. Accomplish all Capstone Defense Panel suggestions

2. Have all the Panel sign the draft copy of the Manuscript, for final
production of manuscript.
3. Create a softcopy of the packaged Software, including its supporting
installers.
4. Create a softcopy of the Documents both in .docx and .pdf format.
5. Develop a journal version of the study based on the format that will be
given by the subject adviser.
6. The outer cover of the Manuscript will be Green
7. The side of the book should have the following text:
SURNAMEs Title of the Paper ESSU BSIT Year

Color of print not gold
References
CHED Memorandum Order 25 Series of 2015
University of Cebu Capstone Guidelines Compiled by Dr. Sheryl Satorre
Mapua Institute of Technology Capstone Guidelines Compiled by Prof. Ariel Kelly Balan
Far Eastern University Capstone Guidelines Compiled by Prof. Erwin Globio, MBA, MSIT

Capstone Project Guidelines - 11

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

Capstone Project Guidelines - 11

Uploaded by

Copyright:

Available Formats

Chapter 1

Eastern Samar State University - College of Computer Studies (CCS)

This document intends to guide students and faculty-advisers in

CCS Research Agenda

Thrust Key Result Area Objectives Research Areas

Enhance the teaching and

Establish flexible and distant

Integrity of the Support farming systems

Engineering and Rapid, Inclusive and Promote low-cost computing Software/Hardware

Livelihood and Rapid, Inclusive and Develop Information Systems Software/Hardware

Health Care, Nutrition Poverty Reduction Develop Information Systems Software/Hardware

Develop information systems

Scope of the Project

The Capstone Project Adviser should determine the appropriate

Suggested Areas of Study

Network Design & Implementation and Server Farm Configuration

Project Manager (PM) - The person with authority to manage a Research /

Systems Analyst / Database Designer (SA/DD) – the person who ensures

Network Designer / UI Designer (ND/UID) – The person who is responsible

Software Engineer / Programmer (SE/P) - The person who designs, writes,

Duties and Responsibilities of Proponents/ Project Members

Duties and Responsibilities of the Subject Adviser

Duties and Responsibilities of Project adviser

The English Critic

The panel is composed of 1 Chairman and Panel Members identified by the

1. Writing of Chapters I, II, III, IV, V

1. Submission of Final Manuscript

Patent Process (via ITSO – optional)

Final Individual Grade

Each Capstone member should be able to attain a minimum of 75% as

As approved by the Capstone Project Committee, the Capstone Project

Figure 2. Parts of the Capstone Project Manuscript

i. General Document Format

a. The title page

TITLE of the STUDY

An Undergraduate Capstone Project

5-single spaces; space before: 0 pt; space after: 0 pt; Arial, 12

Presented to the Faculty of the

DEPARTMENT OF INFORMATION TECHNOLOGY

College of Computer Studies

Eastern Samar State University

Borongan City, Eastern Samar

5-single spaces; space before: 0 pt; space after: 0 pt; Arial, 12

In Partial Fulfilment of the Course Requirement for the Degree

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

10-single spaces; space before: 0 pt; space after: 0 pt; Arial, 12

Name of English Editor NAME OF ADVISER

English Editor Capstone Project Adviser

NAME OF ADVISER, Arial, Size 12 )

Capstone Project Committee

COMMITTEE MEMBER COMMITTEE MEMBER

The Acknowledgement should contain acknowledgements to anyone and

the number of page of

the preceding page

right aligned, Arial, size 12)

the preceding pageright aligned, Arial, size 12)

List of Figures viii

vi. List of Figures/Tables

the number of page of

the preceding page

right aligned, Arial, size 12)

LIST OF FIGURES / TABLES

Table Description Page