1

Southern Christian College

United Church of Christ in the Philippines
Midsayap, North Cotabato

COLLEGE of COMPUTING and INFORMATION SCIENCES

CAPSTONE PROJECT COMPONENTS AND ITS ORGANIZATION

The components and organization of the capstone project shall be as presented below:

Front Matter
i. TITLE PAGE
ii. APPROVAL SHEET
iii. ACKNOWLEDGMENTS
iv. TABLE OF CONTENTS
v. LIST OF TABLES
vi. LIST OF FIGURES
vii. EXECUTIVE SUMMARY

Body of the Report

CHAPTER 1 INTRODUCTION
Project Context
Objectives
Scope and Limitations
Theoretical Framework
Conceptual Framework

CHAPTER 2 REVIEW OF RELATED LITERATURE

Title(s) of the Synthesized Literature, Study, and Work
Definition of Terms

CHAPTER 3 DESIGN AND METHODOLOGY

Project Methodology
● Standard Project Methodology or
● User-defined Project Methodology
Project Design
Requirement Analysis
✔ Data Flow Diagram
✔ Technical Feasibility
✔ Schedule Feasibility
 2

Design of Software, Systems, and Processes

✔ System Flow
✔ Use Case Diagram
✔ Use Case Specification
✔ System Sequence Diagram
✔ Design Class Diagram
✔ Entity Relationship Diagram
Development and Testing
Description of the Prototype

CHAPTER 4 RESULTS AND DISCUSSION

CHAPTER 5 SUMMARY AND RECOMMENDATIONS

Back Matter
Literature Cited
Appendices
Curriculum Vitae
 3

CAPSTONE PROJECT COMPONENTS AND ITS SPECIFICATIONS

Front Matter
TITLE PAGE

The title page includes the title of the research/project, the name of the author, the purpose
of the research and the month and year of completion (see Guide to Thesis Format and Style
Appendix 2). The unique name of the Information System and its intended purpose is stated. The
title should not exceed 21 words and must fully reflect the capstone project. The title appears in 3
lines. It is centered and printed in inverted pyramid form an inch from the edge of the paper. The
author’s name is printed below the title. For two or more authors, spaces between title and author
and type of paper must be equidistant. For group research, arrangement of the names of the authors
should be based on their contribution to the study.

APPROVAL SHEET

The approval page is provided by the Research Center (see Guide to Thesis Format and
Style Appendix 3). It contains the seal of the college and the names and signature of the guidance
committee members, the department chairperson (if any), the dean of the college and the research
director. The approval page is signed only after the 4 copies of the research reports are bound and
presented to the Research Center.

ACKNOWLEDGMENTS

The acknowledgments page is placed in the final manuscript. It bears the title
“ACKNOWLEDGMENTS.” People, institutions and organizations who have contributed to the
accomplishment of the research may be acknowledged. Minimum content includes the name of
Adviser, Client, and Research Committee. The acknowledgments page must not exceed one page.

TABLE OF CONTENTS

The table of contents is the fourth preliminary page. It bears the title “TABLE OF
CONTENTS.” The list includes the exact pages of the chapters and main headings (see Guide to
Thesis Format and Style Appendix 4).

LIST OF TABLES
 4

This page bears the title “LIST OF TABLES.” It contains three columns: the table number,
the title and the page where the table is located. The full title of the table is written without a period
and arranged according to number, starting from 1 (see Guide to Thesis Format and Style Appendix
5). For a research with only one table, the page bears the title “TABLE.”

LIST OF FIGURES

This page bears the title “LIST OF FIGURES.” This page contains three columns, for the
figure number, title and page. The full title of the figure is written without a period and arranged
according to number, starting from 1 (see Guide to Thesis Format and Style Appendix 6). Maps,
graphs and other diagrams are considered as figures. For a research with only one figure, the page
bears the title “FIGURE.”

EXECUTIVE SUMMARY

This page bears the title “EXECUTIVE SUMMARY.” The page has three components
(see Guide to Thesis Format and Style Appendix 9). The first component is comprised of the name
of the developers, year of completion, capstone project title, the capstone category, the College
where the developers belong, and the name and address of the school. It is single spaced and
flushed to the left. After two single spaces, the second component follows. It contains the name of
the adviser. The third component makes up the executive summary or synopsis of the project. It
contains summary of the problem statement, scope and significance, research findings,
methodology, design and the conclusions. It is single-spaced with one single space after each
paragraph. The executive summary is limited to 200-250 words.
 5

Body of the Report

CHAPTER 1

INTRODUCTION

Chapter 1 bears the title “INTRODUCTION.” The title is in uppercase and centered above
the text. This chapter includes a clear statement of the Project Context, Objectives, Scope and
Limitations, Theoretical Framework, and Conceptual Framework of the project.

Project Context

This contains the following:

(i.) introduction, business processes/ business rules;

(ii.) problem statement i.e., an account describing the circumstances, which suggested
research and/or project development;
(iii.) purpose and description i.e., (a.) a justification of the selection or choice of the
project, (b.) the elaboration of the importance and significance of the results of the
project, (c.) a statement of relevance to felt needs, policy implications, and other
possible uses for its results; and
(iv.) should be 2-3 pages.

Note: A business process refers to the event, task, or transaction done in an organization. A
business rule refers to the standard defined by an organization i.e., embedded in a specific
business process.

Objectives

This section includes:

(i.) one general or main objective;

(ii.) at least three (3) specific objectives; and
(iii.) written in one (1) page only.
 6

Scope and Limitations

This section includes:

(i.) the detailed description of the input, process, and output of the project;
(ii.) the locale of the study is indicated;
(iii.) the delimitations are defined; and
(iv.) there is a minimum of 1-2 pages.

Theoretical Framework

This section presents the theory from which the research problem was derived or to which
it is linked (Laviña, et. al., 2016). Hence, it notably serves as the basis of the study. And, it shapes
the justification of the research problem in order to provide the legal basis for defining its
parameters.

Moreover, it is a symbolic construction which uses abstract concepts, facts, laws, variables,
and their relations that explains and predicts how an observed phenomenon exists and operates.

Conceptual Framework

The concepts used from this level should be derived from the concepts used in the
theoretical framework (Laviña, et. al., 2016). This section presents the relationship between the
specific concepts that will be studied.

Moreover, the author indicates how concepts can be measured or judged; And,
operationalizes and defines the various concepts in the research question method and how he/she
will investigate the topic.

Finally, it is accompanied by a symbolic representation of a phenomenon or a diagram

usually given a schematic representation using arrows and boxes.
 7

CHAPTER 2

REVIEW OF RELATED LITERATURE

Chapter 2 bears the title “REVIEW OF RELATED LITERATURE”. The title is in

uppercase and centered above the text. This chapter consists of the specific title(s) of the
synthesized literature, study, and work. And, definition of terms is included in this chapter.

Title(s) of the Synthesized Literature, Study, and Work

This section contains the synthesized literature, study, and work from at least 15 published
and unpublished sources like theses manuscripts. A synthesized literature means that the
developers had done a comparison and contrast to different published and unpublished works as
part of their review, i.e., you draw and state a conclusion about the similarities and differences in
the studies you review.

Cited statement should be rephrased in layman’s terms based on the developers’

understanding, but should be appropriately anchored from the original text, meaning, it does not
lose the published work’s original meaning or concept.

Every topic is arranged thematically, chronologically, or by argument. And, proper in-text

citation should be strictly followed and observed.

Definition of Terms

This section defines the terms used in the project. Terms are defined operationally and
contextually. Meaning, how are these terms used in the context of the project.

It is noteworthy to point out that terms used as part of the technical background are included
here. Technical background terms are operationally and contextually defined. These could include
but are not limited to theorems, technologies, fundamental algorithms, mathematical
models/formula. And, its system requirements and compatibilities are included.

A minimum of five (5) terms is required.

 8

CHAPTER 3

DESIGN AND METHODOLOGY

Chapter 3 bears the title “DESIGN AND METHODOLOGY.” The title is in uppercase
and centered above the text. Minimum of 3 pages.

Project Methodology

This level 2 heading has two options. First, developers may follow standard project
methodology like RAD, Agile Scrum, XP, DSDM, AUP, RUP, and the like. Second, developers
may define their project methodology which they deem appropriate to their project development.

qqdvv

Standard Project Methodology

Developers choose to follow the standard project methodology like Agile Scrum, XP,
DSDM, AUP, RUP, and the like.

User-defined Project Methodology

Developers define their own project methodology as deemed appropriate to their project
development.

Project Design

This level 2 heading contains the (i.) Requirement Analysis, (ii.) Design of Software,
Systems, and Processes, (iii.) Development and Testing, (iv.) Description of the Prototype, (v.)
Implementation Plan (for proposal), and (vi.) Implementation Results (for final).

Requirement Analysis

This section contains the visual presentation of the client’s existing business processes and
rules thru Data Flow Diagram using Gane and Sarson Notation. Also, Technical Feasibility and
Schedule Feasibility are written here.
 9

(v.) Data Flow Diagram. It illustrates the existing business processes and rules of the
client. It follows the Gane and Sarson Notation.

(vi.) Technical Feasibility. It is an assessment based on an outline design of system

requirements, to measure the practicality of a specific technical solution & the availability of
technical resources & expertise to implement and maintain it. It refers to the technical resources
needed to develop, purchase, install, or operate the system. When assessing technical feasibility,
the team specifically the system’s analyst must consider the following points:

1. Does the company have the necessary hardware, software, and network resources? If
not, can those resources be acquired without difficulty?
2. Does the company have the needed technical expertise? If not, can it be acquired?
3. Does the proposed platform have sufficient capacity for future needs? If not, can it be
expanded?
4. Will a prototype be required?
5. Will the hardware and software environment be reliable? Will it integrate with other
company information systems, both now and in the future? Will it interface properly
with external systems operated by customers and suppliers?
6. Will the combination of hardware and software supply adequate performance?
7. Do clear expectations and performance specifications exist?
8. Will the system be able to handle future transaction volume and company growth?

(vii.) Schedule Feasibility. It is a measure of how reasonable the project timetable is. A
project will fail if it takes too long to be completed before it is useful. Typically, this means
estimating how long the system will take to develop, and if it can be completed in a given time
period. It means that a project can be implemented in an acceptable timeframe. When assessing
schedule feasibility, a system’s analyst must consider the interaction between time and costs. For
example, speeding up a project schedule might make a project feasible, but much more expensive.
Other issues that relate to schedule feasibility include the following:

1. Can the company or the IT team control the factors that affect schedule feasibility?
2. Has management established a firm timetable for the project?
3. What conditions must be satisfied during the development of the system?
4. Will an accelerated schedule pose any risks? If so, are the risks acceptable?
5. Will project management techniques be available to coordinate and control the
project?
6. Will a project manager be appointed?

Note: A Gantt Chart or other project scheduling tool can be used to present the schedule
feasibility.
 10

Design of Software, Systems, and Processes

This section contains the System Flow, Use Case Diagram, Use Case Specification,
System Sequence Diagram, Design Class Diagram, and Entity Relationship Diagram.

(viii.) System Flow. It describes how data flow in the systems and how decisions
are made to control an event.

(ix.) Use Case Diagram. This illustrates the interaction of the

external entities to the information system. It follows the Unified Modeling
Language 2.0 standard when drawing diagram.

(x.) Use Case Specification. This outlines the narrative or

description of the Use Case Diagram in a table format which has five (5)
columns containing information for (i.) Use Case, (ii.) Brief Description,
(iii.) Pre-condition, (iv.) Flow of Events, and (v.) Post-condition.

(xi.) System Sequence Diagram. This illustrates the interaction

of the actor to the system in respect to the order or sequence of
event/transaction in the system. It may be visualized per module.

(xii.) Design Class Diagram. This illustrates the classes used in

the information system and its multiplicity among other classes.
Importantly, it presents the stereotypes of classes following guillemet <<>>
notation. Also, the class methods, visibility, parameters, and data types are
presented here. Note that this diagram is optional for multimedia projects.

(xiii.) Entity Relationship Diagram. This presents the cardinality

of tables in a database(s). It should be normalized to its 3rd Normal Form
(3NF). It follows the Crow’s Foot Notation. Note that this diagram is
optional for multimedia projects.

Development and Testing

This section includes standards to be used and tradeoffs involved in the design choices
discussed in synopsis only (Laviña, et. al, 2016). The evaluation and assessment tools are discussed
here in synopsis only.

For example, “In designing, developing, and evaluating the proposed Scheduling Expert
System, the proponents shall be using the ISO 9126-1 software quality model. ISO 9126 is an
international standard for the evaluation of software. It identifies six (6) main quality
characteristics, namely (i.) Functionality, (ii.) Reliability, (iii.) Usability, (iv.) Efficiency, (v.)
Maintainability, and (vi.) Portability” (Laviña, et. al, 2016).
 11

Description of the Prototype

This section contains the Graphical User Interface (GUI) of the information system with
appropriate figure label and description.
 12

CHAPTER 4

RESULTS AND DISCUSSION

Chapter 4 bears the title “RESULTS AND DISCUSSION.” The title is in uppercase and
centered above the text.

Note that all specific objectives under Chapter 1 should be answered and the results should be
discussed to a great extent which may be supported with tables, graphs, figures, algorithms, or
relevant source code. Moreover, it should be able to relate to literatures and studies reviewed to
reinforce or debunk the findings (Laviña, et. al).
 13

CHAPTER 5

SUMMARY AND RECOMMENDATIONS

Chapter 5 bears the title “SUMMARY AND RECOMMENDATIONS.” The title is in

uppercase and centered above the text.

Summary

This section summarizes the results based on Chapter 4. If there are only three (3) specific
questions stated in the statement of the problem or three (3) specific objectives (Chapter 1) and
answered in the results and discussions (Chapter 4), there are only three results summarized in this
section and no presentation of tables.

And, the result(s) or finding(s) of the evaluation or assessment of the project is revealed
here in a brief and concise manner.

Recommendations

This section includes further research of the project and/or enhancement of the developed
system. Also, it contains a direction on how to use the software product in order to achieve its
maximum benefits.
 14

Back Matter
LITERATURE CITED

This section comprises the bibliography or the list of works cited in the project. It contains a list of
all references such as books, journals, monographs, periodicals, conference proceedings, web pages and
other similar works. The listing follows the APA style. All entries are categorized according to type of
reference, and in alphabetical order based on the last name of the author.

APPENDICES

This section contains the following:

Statement of Work

This section contains the signed Statement of Work by the development team and the client.

Relevant Source Codes

This section contains the figure and its description for significant source codes used in the project.

Evaluation Tool

This section contains the standard or user-defined survey questionnaire or other assessment
tool(s) used in the project development.

Sample Input/Output/Reports

This presents the sample inputs/outputs/reports generated in the information system.

User’s Guide

This may not be included in the document but this document should be provided to the client i.e.,
either in printed form or in a video format.

Test Results
This section includes the answered USE and Feasibility Surveys.

CURRICULUM VITAE

This section contains information about the developer(s).

 15

Prepared by:

GLENDA J. JERUELA, LPT

Research Coordinator
College of Computing and Information Sciences

Noted by:

SHEILA T. MEJOS, MIT

Dean
College of Computing and Information Sciences