1
Grouping and Regrouping
Each Capstone Project Group must consist of three (3) or four (4) members who will
take on at least one of the following roles:
Hustler - Project Manager
The Hustler optimizes marketing strategies in promoting the product or output.
Hacker - System Analyst, Software Engineer, Software Tester
The hackers will be the one to build/develop the system or application.
Hipster - UX Designer, Technical Writer
The hipster is in-charge of the making sure that there is logical connection between the
design and user requirements.
Regrouping is allowed if less than three (3) members of the group remain. Should
this happen, the group may be disbanded and members of this affected group may join
other groups as long as the maximum number for each group is followed. However, if the
remaining member(s) decide(s) to continue with his/her/their project, regrouping may not
apply but with the consent both the Project and the Subject Advisers, and the Dean.
Revision of the scope may then be an option. The title/topic to be pursued will then be
decided among the team members, the Project and the Subject Advisers, and the Dean.
2
Manuscript Format
The Capstone Project Manuscript must follow the following format and technicalities:
Use standard short white bond paper (8.5” x 11”)
Use font Arial, Font size 12
Text computerized in double spacing
Pagination on upper right corner of page
Main title and subtitle should be in bold text; not underlined
Use College Design Letterhead
Margins (Top: 1” ; Bottom: 1” ; Left: 1.5 ; Right: 1”)
Use Fig for Figure. (Fig. 1 The Theoretical Framework of the Study) Note: No description
below.
For tables, table # then below is title of the table, center and bold, then the table
illustration below the title.
Manuscript Template
Pre-Proposal Statement Template (1 statement per title) – see Appendix A
Proposal Manuscript Format – see Appendix B
Final Oral Defense Manuscript Format – see Appendix C
Capstone Project Manuscript Details – see Appendix D
3
4
Pre-Proposal Statement Template
CAPSTONE PROJECT
PRE-PROPOSAL STATEMENT
Project Title:
Proponents: 1.
2.
3.
4.
Project Adviser:
Scope of the Study:
Limitations of the Study:
Project Design/Development Program Specification
Plan: (a technical specification for the programmer to
implement.)
Software Specification
(contains functional and nonfunctional requirements only)
Hardware Specification
5
Proposal Manuscript Format
Title Page
Table of Contents
List of Figures, List of Tables, List of Notations
The Problem and Its Scope
o Introduction
Rationale of the Project
Review of Related Systems/ Theoretical Background
o The Problem
Statement of the Problem/Objectives of the Project
Hypothesis/es (if statistic is applied)
Scope and Limitations of the Project
Significance of the Study and Project Highlights
Technical Background
Methodology
o Environment (optional for non org-specific problem)
o Requirements Specifications
o Analysis
o Design
o Development and Testing Methods
o Ethical Considerations
Presentation, Analysis and Interpretation of Data
o Questionnaire ( or how data is gathered, analyzed and interpreted )
o Cost Benefit Analysis (if applicable)
o Risk Assessment Management ( How, table 1 )
BIBLIOGRAPHY
APPENDICES (or ANNEXES)
GLOSSARY
6
Appendix C (Final Oral Defense Full Manuscript Format)
Preliminary Pages
Title Page (refer to Appendix E)
Approval Sheet (refer to Appendix K)
Acknowledgement (use third party nouns/pronouns)
Abstract
Table of Contents (use MS Word Table of Contents feature)
List of Figures, List of Tables, List of Notations
Chapter 1
THE PROBLEM AND ITS SCOPE INTRODUCTION
Rationale of the Project
Review of Related Systems /Technical Background THE
PROBLEM
Statement of the Problem/Objectives of the Project
Hypothesis/es (if there is data gathering, statistics)
Scope and Limitations of the Project
Significance of the Study and Project Highlights
Methodology
o Environment (optional for non-org specific project)
Locale
Population of the Study
Organizational Chart/Profile
o Requirements Specifications
Operational Feasibility
Fishbone Diagram
Functional Decomposition Diagram
Technical Feasibility
Schedule Feasibility
Gantt Chart
o Requirements Modeling
Input-Process-Output Diagram
Process
Control
Either of the following two (2), whichever is applicable:
Data and Process Modeling
o Context Diagram
o Data Flow Diagram
o System Flowchart
o Program Flowchart (highlights only)
Object Modeling
30
o Use Case Diagram
o Class Diagram
o Sequence Diagram
o Activity Diagram
o Analysis
Cost and Benefit Analysis (for projects that entails monetary costs)
Cost Recovery Scheme (for projects that entails monetary costs)
Risk Assessment/Analysis
o Design
Output and User-Interface Design
Forms
Reports
Data Design
Entity Relationship Diagram (use MS Access Relationships but
not preferable for implementation)
Data Dictionary
System Architecture
Network Model
Network Topology
Security
o Development
Software Specification
Hardware Specification
Program Specification
Programming Environment
Front End
Back End
Deployment Diagram
Test Plan
o Testing
Unit Testing
Integration Testing
System Testing
Acceptance Testing (must be done after the final oral defense)
DEFINITION OF TERMS/GLOSSARY
Chapter 2
PRESENTATION, ANALYSIS AND INTERPRETATION OF DATA
Questionnaire (How data is gathered, analyzed and interpreted)
Analysis (How, Tables only)
o Cost and Benefit Analysis (for projects that entails monetary costs)
o Cost Recovery Scheme (for projects that entails monetary costs)
o Risk Assessment/Analysis
Testing (How, Tables only)
30
o Unit Testing
o Integration Testing
31
o System Testing
o Acceptance Testing (must be done after the final oral defense)
Chapter 3
SUMMARY OF FINDINGS, CONCLUSION AND RECOMMENDATIONS
Summary of Findings
o Analysis (Results only)
o Cost and Benefit Analysis (for projects that entails monetary costs)
o Cost Recovery Scheme (for projects that entails monetary costs)
o Risk Assessment/Analysis
o Testing (Results only)
o Unit Testing
o Integration Testing
o System/Alpha Testing
o Acceptance/Beta Testing (must be done after the final oral defense)
Conclusions
Recommendations
Implementation Plan
BIBLIOGRAPHY
APPENDICES
o Relevant Source Code
o Evaluation Tool
o Sample Input/Output/Reports
o Users Guide
o Other Relevant Documents
o Project Working Title Form
o Signed Transmittal Letter
o Project Adviser Appointment Form
o Grammarian’s Certification (optional)
o Curriculum Vitae
32
Capstone Project Full Manuscript Details
Preliminary Pages
Title Page (refer to Appendix E)
Approval Sheet (refer to Appendix K)
Acknowledgement (use third party nouns/pronouns)
Abstract
Table of Contents (use MS Word Table of Contents feature)
List of Figures, List of Tables, List of Notations
Chapter 1
THE PROBLEM AND ITS SCOPE INTRODUCTION
Rationale of the Project
Review of Related Systems /Technical Background THE
PROBLEM
Statement of the Problem/Objectives of the Project
Hypothesis/es (if there is data gathering, statistics)
Scope and Limitations of the Project
Significance of the Study and Project Highlights
Methodology
o Environment (optional for non-org specific project)
Locale
Population of the Study
Organizational Chart/Profile
o Requirements Specifications
Operational Feasibility
Fishbone Diagram
Functional Decomposition Diagram
Technical Feasibility
Schedule Feasibility
Gantt Chart
o Requirements Modeling
Input-Process-Output Diagram
Process
Control
Either of the following two (2), whichever is applicable:
Data and Process Modeling
o Context Diagram
o Data Flow Diagram
o System Flowchart
o Program Flowchart (highlights only)
Object Modeling
o Use Case Diagram
33
o Class Diagram
o Sequence Diagram
o Activity Diagram
o Analysis
Cost and Benefit Analysis (for projects that entails monetary costs)
Cost Recovery Scheme (for projects that entails monetary costs)
Risk Assessment/Analysis
o Design
Output and User-Interface Design
Forms
Reports
Data Design
Entity Relationship Diagram (use MS Access Relationships but
not preferable for implementation)
Data Dictionary
System Architecture
Network Model
Network Topology
Security
o Development
Software Specification
Hardware Specification
Program Specification
Programming Environment
Front End
Back End
Deployment Diagram
Test Plan
o Testing
Unit Testing
Integration Testing
System/Alpha Testing
Acceptance Testing (must be done after the final oral defense)
DEFINITION OF TERMS/GLOSSARY
Chapter 2
PRESENTATION, ANALYSIS AND INTERPRETATION OF DATA
Questionnaire (How data is gathered, analyzed and interpreted)
Analysis (How, Tables only)
o Cost and Benefit Analysis (for projects that entails monetary costs)
o Cost Recovery Scheme (for projects that entails monetary costs)
o Risk Assessment/Analysis
Testing (How, Tables only)
34
o Unit Testing
o Integration Testing
o System Testing
35
o Acceptance Testing (must be done after the final oral defense)
Chapter 3
SUMMARY OF FINDINGS, CONCLUSION AND RECOMMENDATIONS
Summary of Findings
o Analysis (Results only)
o Cost and Benefit Analysis (for projects that entails monetary costs)
o Cost Recovery Scheme (for projects that entails monetary costs)
o Risk Assessment/Analysis
o Testing (Results only)
o Unit Testing
o Integration Testing
o System Testing
o Acceptance Testing (must be done after the final oral defense)
Conclusions
Recommendations
Implementation Plan
BIBLIOGRAPHY
APPENDICES
o Relevant Source Code
o Evaluation Tool
o Sample Input/Output/Reports
o Users Guide
o Other Relevant Documents
o Project Working Title Form
o Signed Transmittal Letter
o Project Adviser Appointment Form
o Grammarian’s Certification (optional)
o Curriculum Vitae
36
Title Page
ONLINE INFORMATION SYSTEM
(Must be inverted pyramid form, all caps)
A Capstone Project Presented to
Information Technology Department
Cebu Technological University - Argao Campus
In Partial Fulfillment of the Requirements
for the degree Bachelor of Science in Information Technology
By
Juan Dela Cruz
Pedro Reyes
May 2019
37
