Title Page

Executive Summary
Table of Contents
List of Figures, List of tables, List of Notations

Chapter 1 – Introduction
Project Context
- The proponent should introduce the problem by considering global, national and local environments. Make a
striking statement or a general knowledge about the topic. Include relevant data by citing statistics, journals,
research studies and etc. as a support to the identified problem.
Purpose and Description
- This section discusses the origin of the project (i.e. a. Current relevant institutional gaps b.
Improvements/enhancements to the current running systems c. Requests by users/clientele for systems
development initiative), the function and benefit of the project, and its uniqueness, innovative, and relevance.
Objectives
- Specify exactly what the proponent are going to do, where, and for what purpose. Use action verbs that are
specific enough to be evaluated (Examples of action verbs are: to determine, to provide, to verify, to calculate,
to describe, and to establish). Avoid the use of vague non-action verbs (Examples of non-action verbs: to
appreciate, to understand, or to study).
General Objective
o In a single sentence, what the group aims to achieve by the end of IT PROJECT must be stated here. It
should be very parallel to the project title.
Specific Objectives
o This section is the explosion of the general objective that will help realize the proposed study. It should
be SMART (i.e., S-pecific, M-easurable, A-ttainable, Realistic, and T-imebound) and should be
limited to 3-5 only.
o It may be stated in a single sentence, with the specific objectives in bullet form as shown in the
example below:

Specifically, the project aims to:

• specific objective 1;
• specific objective 2;
• specific objective 3;
• specific objective 4; and
• specific objective 5.
Scope and Limitation
- Scope
o Think the project scope as a box. High-level scope defines the sides of the box and separates what is
relevant to your project from what is irrelevant. It refers to the work that needs to be accomplished to
deliver the product, service or result with the specified features and functions. It gives an overview of
all the deliverables.
- Limitation
o It explains all that are NOT included in the project. It is the boundaries of the project (i.e. areas/things
that are out of scope)

Chapter 2 – Review of Related Literatures and Systems

- This portion of the proposal manuscript contains presentations and discussions of the following components:
o Related Concepts and Literature
 Contains evaluation of previous and current research, theories and design principles that are
relevant to the proposed capstone project that the proponent intends to use. Do not include
any unpublished new or original experimental work. Include the following:
a) An organizational pattern that combines both summary and synthesis to give new
interpretations of old material or combine new with old interpretations
b) A tracing of the intellectual progression of the field including major debates
c) An evaluation of the sources and an advise to the reader on which of the materials
cited are the most pertinent or relevant in the thesis or capstone project
 Start off with anchor theory followed with supporting theories to help elaborate anchor
theory. Observe correct endnoting and footnoting, fluidity and continuity. Cite at least 2 or 3
references from any local and foreign literature researches.
o Related Projects/Systems

IT CAPSTONE – IT PROJECT COLLEGE OF COMPUTER STUDIES

REVISED Date: January 8, 2018
  Contains overview and description of related and existing projects/systems that are relevant to
the proposed capstone project. Discussion of specific features of other systems that you intend
to replicate and improve will help define what is expected in your project
 Observe fluidity and continuity. Comparative matrix may be appropriate. Attach screenshots
of the related projects/systems. Cite 4 to 6 related projects/systems.

Chapter 3 –Technical Background

- In this section, discuss the overview of the current technologies (hardware/software/network) used in the current
system. Include the key features of the proposed design with brief explanation and rationale for each feature.
Discussions on the current trends and technologies to be used in developing and implementing the proposed
system (i.e. hardware, software, peopleware and network). It is important to describe how the tools and
technologies are being applied to the project. It should also include discussions on evaluations of alternate tools
and techniques, provide comparisons and state rationale for choosing the ones proponents used. Fluidity and
continuity should be observed
Chapter 4 – Methodology *** Each Diagram must have Title Below and Description (if not defined)
Requirement Analysis
Model (SDLC)
Requirements Modelling (Diagram)
• Input
• Process
• Output
• Performance
• Control
Team Organizational Structure
Requirements Documentation
Operational Feasibility
• Fishbone Diagram
• Functional Decomposition Diagram
Technical Feasibility
• Compatibility checking (hardware / software and other technologies) – discussion only
Schedule Feasibility
• WBS
• Gantt Chart
Economic Feasibility
• Cost and Benefit Analysis - table and discussion
• Cost Recovery Scheme - table and discussion
Design of Software, Systems, Products or processes
• Either of the following two (2) or combined, whichever are applicable:
o Data and Process Modelling
Data Design
• Entity Relationship Diagram
• Data Dictionary
Context Diagram
Data Flow Diagram
Program Flowchart (highlights only)
o Object Modelling
Use Case Diagram
Class Diagram
Sequence Diagram
Activity Diagram
Development and Testing (where applicable)
Programming Environment - discussion only
Front End
Back End
Test Plan
Test Case

Description of Prototype (where applicable)

Output and User-Interface Design
• Forms
• Reports
Implementation Plan (Infrastructure/ Deployment)
Network Architecture
IT CAPSTONE – IT PROJECT COLLEGE OF COMPUTER STUDIES
REVISED Date: January 8, 2018
 Network Model
Deployment Diagram (must observe the network model)
Lay out and module deployments must be shown
Implementation Results (must be implemented only before the final defense)
Evaluation Results ( discussion, diagrams, charts, tables)
Acceptance Testing

Chapter 5 – Recommendations
Content
1st Paragraph: Discussion of results and objectives
2nd paragraph: Panel Future recommendation (Future Features and improvements)
3rd paragraph: Team Final Recommendation (to the client and future used)

Appendices
Relevant Source Code
Evaluation Tool or Test Documents
Sample Inputs/ Outputs/ Reports
User Guide
Process/ Data/ Information Flow
Screen Lay-outs
Test Results
Picture Show casing the data gathering Phase, Investigation done (floor plan, lay-out, building, etc.)
Curriculum Vitae per team member

IT CAPSTONE – IT PROJECT COLLEGE OF COMPUTER STUDIES

REVISED Date: January 8, 2018
 Format

Line Spacing: Double

Font Style: Times New Roman
Font Size: 11
Margins: 1.5” Left, 1” The rest
Bold Chapter Header (e.g. Chapter 1, Chapter 2 . . . )
Center Chapter Titles (e. g. Introduction, Review of Related Literatures, Technical Background, Methodology, . . .)
Left Align Sub Header (Project Context, Objectives, Scope, . . . )
Figures and tables Italicize, (ex: Figure 1. Ishikawa Diagram or Table 1. Cost Benefit Analysis)
Diagrams and Images must have an Outline or place in a Box

IT CAPSTONE – IT PROJECT COLLEGE OF COMPUTER STUDIES

REVISED Date: January 8, 2018