Capstone Guidelines: Opol Community College
Capstone Guidelines: Opol Community College
CAPSTONE GUIDELINES
2
Table of Contents
I. Introduction ........................................................................................................................ 4
II. Research / Capstone Project Agenda ................................................................................. 5
III. Suggested Areas of Research / Capstone Project ............................................................... 5
Research / Capstone Project Categories ............................................................................ 5
Software Development ........................................................................................... 5
Multimedia Systems ............................................................................................... 5
Network Design and Implementation .................................................................... 5
IV. Pre-requisites ...................................................................................................................... 5
V. Research / Capstone Project Team ..................................................................................... 6
Duties and Responsibilities of the Proponents/Researchers ............................................. 6
Policy on Regrouping .......................................................................................................... 6
VI. Research / Capstone Project Adviser .................................................................................. 7
Duties and Responsibilities as the Subject Teacher ........................................................... 7
Duties and Responsibilities as the Adviser ......................................................................... 7
VII. Panel Composition .............................................................................................................. 8
Duties and Responsibilities of the Panel............................................................................. 8
Chairman ................................................................................................................. 8
Panel Members / Content Expert ........................................................................... 8
VIII. Research / Capstone Project Duration ............................................................................... 9
Pre-proposal Stage .............................................................................................................. 9
Proposal Stage .................................................................................................................... 9
Oral Defense Stage.............................................................................................................. 9
Public Presentation ............................................................................................................. 9
IX. Grading System ................................................................................................................... 9
Proposal Stage .................................................................................................................... 9
Verdicts ................................................................................................................. 11
System Oral Defense ......................................................................................................... 12
Verdicts ................................................................................................................. 12
X. Guidelines ......................................................................................................................... 12
Capstone 1 (Research Methods) ....................................................................................... 12
Capstone 2(Oral Presentation) ......................................................................................... 14
XI. List of Deliverables/Activities............................................................................................ 15
3
I. Introduction
This is a very special course in the BSIT program. Students do it in the final year of studies
and it is their opportunity to demonstrate that they can indeed meet the levels of performance
expected of an IT professional. The Capstone Project includes project proposal, feasibility studies,
intellectual property, teamwork, budget, schedule, management, professional communications
(i.e. reports, presentations), planning, design, implementation, deployment, and testing.
Students will be expected to do much more than “get something working”. They will be expected
to meet a number of strictly enforced milestones and to take considerable initiative in realizing
specific goals. Moreover, the Capstone Project is a way of determining whether students are
ready to graduate.
The Capstone Project has a number of educational objectives. Although each Research /
Capstone Project is different and the relative emphasis will vary, the subject will involve students
in:
• Bringing together and integrating knowledge and skills in the course as a whole;
• Reinforcing and developing competencies that have not been sufficiently emphasized in
the fundamental subjects;
• Defining a substantial engineering study or design task and carrying it to completion
within a specified time and to a professional standard;
• Completing a comprehensive written and bound report that places the Research /
Capstone Project in context, defines its objectives, and describes the work done with the
resulting conclusions or recommendations;
• Bridging the gap between the undergraduate studies and the professional future, and
demonstrating professional competencies and capabilities;
• Demonstrating initiative and creativity, taking pride in the achievement of a difficult task.
Through this course, students are prepared in their respective careers. The bulk of the work
(i.e., the Research / Capstone Project work itself) is to be done outside of the classroom.
5
Software Development
• Software Customization (most especially FOSS)
• IS Development (with at least Alpha Testing with Live Servers
• Web Applications Development
• Multimedia Systems
• Game Development
• E-learning Systems
• Interactive Systems
• Information Kiosks
The Capstone Project team is composed of at most five (5) members. The following are
the four roles that the proponents/researchers should play:
• Project Manager - 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 – the person who checks that all parts of the system are coordinated.
• Programmers - The persons who design, write, and test computer programs.
• QA Staff / Tester - A person 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.
• Documenter /Technical Writer - A person who writes the Research / Capstone Project
study document, both the system and the Research / Capstone Project manuscript.
Policy on Regrouping
Regrouping is allowed if less than 3 members of the group remain from ITE 307 to ITE 404.
Should this happen, the group may be disbanded and members of these affected groups may join
in other groups for as long as the maximum number for each group is followed. However, if the
remaining member(s) decide(s) to continue with his/their Research / Capstone Project,
7
regrouping may not apply but with consent of the Adviser 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 and the Dean.
believes that the Proponents/Researchers are not yet ready for Proposal Hearing and Oral
Defense, respectively. Thus, if the Proponents/Researchers fail in the Proposal Hearing or
Oral Defense, it is partially the adviser's fault.
7) Clarifies points during the Proposal Hearing and Oral Defense.
8) Ensures that all required revisions are incorporated into the appropriate documents
and/or software.
9) Keeps informed of the schedule of Research / Capstone Project activities, required
deliverables and deadlines.
10) Recommends to the Proposal Hearing and Oral Defense panel the nomination of his/her
Research / Capstone Project for an award.
11) As a special adviser, he/she is responsible to be:
a. A provider
b. An encourager
c. A dictator
d. A pushy boss
e. A connector
f. An employment agency
Pre-proposal Stage
• Course Enrolment
• Capstone Project Orientation
• Short Listing of Possible Research / Capstone Projects
• Title Critiquing and Patentability Check (Patent Searching) – via ITSO
• Pre-Proposal Statement Preparation
• Pre-Proposal Hearing
Proposal Stage
• Practical Examination of the chosen Programming Language (by team) - optional
• Writing of Chapters I, II, III, and IV (planning and design only)
• Proposal Manuscript Submission
• Proposal Hearing
• Proposal Manuscript Revisions
Public Presentation
(As recommended by the Philippine Society of IT Educators (PSITE) – Research Committee)
• Public Presentation
• Public presentation is required. It should be a school-based presentation open for public
which may include the Poster category
• Other Options
o Regional Student Congress
▪ Presentations to Philippine Computing Science Congress of CSP, National
Conference on IT Education of PSITE
X. Grading System
Proposal Stage -CAPSTONE 1
The rating of each proponent per panel member shall be based on the following rubric
for objective evaluation purposes:
5
Chapter 3
• There should be comprehensive discussions on the technologies
(hardware/software) involved in the Research / Capstone Project and
its related Research / Capstone Projects in the past
Chapter 4 10
• Methodology strictly follows the SDLC (esp. for Software
Development)
• Methodology includes project management techniques appropriate
for the chosen Research / Capstone Project.
• Requirements Specification is more or less complete and answers the
objectives
• Design Tools used are relevant and appropriate which should be
based on requirements
• Development Plan is concrete and should be consistent with the
Design
11
Verdicts
There will be four possible verdicts after the Proposal Hearing. The verdict is a unanimous
decision among the three members of the Capstone Project Oral Defense panel. Once issued, it
is final and irrevocable.
APPROVED. Minor revisions are necessary but they do not have to be presented in
front of and checked by all panelists. 86 – 100
APPROVED WITH REVISIONS. Major revisions shall be incorporated in the final copy
of the revised Project Proposal summary. These must be checked by the panelists. 70
– 85
DISAPPROVED. The Proponents/Researchers failed to propose a researchable or
scholarly Research / Capstone Project. Below 70
12
Verdicts
ACCEPTED WITH REVISIONS. Revisions are necessary but they do not have to be
presented in front and checked by all panelists. 70 to 100
REORAL DEFENSE. Another Oral Defense session, in which all panelists must be
present, is necessary to further clarify the objectives and scope of the capstone
project. Student must re-apply for another Hearing Notice Form from the Center for
Research if the Oral Defense is scheduled after the semester ends. 65 to 69 and upon
the panel’s unanimous decision
NOT ACCEPTED. The proponent failed to achieve the objectives of the research
established in the proposal. The panelists’ numeric grades are not anymore needed.
Below 65
XI. Guidelines
CAPSTONE 1
1) The students shall form a team of3-4 member. They then decide who plays the following
roles - Project Manager, Systems Analyst, Programmer, QA Staff/Tester, and
Documenter/Technical Writer. The team then submits Project Team Assignments Form
(Deliverable D1- Please refers to Appendix A. Project Team Assignments Form) with
signatures, to the Subject Teachers or the Dean’s Office.
2) The Proponents/Researchers of the Research / Capstone Project shall prepare 10
different possible topics/titles, and present/consult these topics to any of the CICS
teachers or any expert of the field. The Team shall ensure the novelty or patentability of
13
the Research / Capstone Project through the help of using patent libraries online. The
project manager would then select 3 - 5 out of the 10 possible titles.
3) The Proponents/Researchers shall make the Pre-Proposal Statements (Deliverable D2-
Please refers to Appendix B. Pre-Proposal Statement Template) of each of the selected
topics/titles.
4) The Pre-Proposal Hearing will be scheduled upon the completion of the Pre-Proposal
Statements. During this hearing, the team members, subject teachers and the Program
Head shall convene and select only one of the 3 - 5 topics/titles presented. Only the
approved Research / Capstone Project topics should proceed to the research proposal
stage. After a topic/title is finally chosen, the team then accomplishes (in triplicate) a
Project Working Title Form (Deliverable D3 - refer to Appendix C. Project Working Title
Form) which will then indicate the name of the appropriate adviser as decided by the
team of advisers together with the proponents.
5) The team shall prepare all the parts of the proposal manuscript on time with the
set/agreed dates. The team always seeks approval from the adviser all the required
deliverables, by letting him sign/conform with the submitted documents. By conforming,
it means that the deliverable had been checked /corrected diligently.
6) The researchers will ensure that the proposal is refined. Please refer to the Research /
Capstone Project Study Manuscript Outline in Appendix D. Research / Project Manuscript
Outline.
7) The researchers will prepare 4 copies of the Complete Proposal Manuscript (Deliverable
D4) for the Proposal Hearing. The Proposal Hearing Notice Form (Deliverable D5 - refer
to Appendix E. Research / Capstone Project Hearing Notice Form) from the Dean's Office
should be filled out and complied. This notice and the 4 copies of complete proposal
manuscript must be submitted to the Adviser. Use Times New Roman, font size 12, 1.5
line spacing. Use standard 8.5" x 11" white bond paper and all margins must be 1 inch.
8) The Adviser forwards the Proposal Hearing Notice and the Complete Proposal
Manuscripts to the Dean's Office
9) The Office will then arrange the date and time of the proposal hearing and distribute the
manuscripts to the identified members of the proposal hearing panel.
The Dean assigns qualified and competent faculty members who will constitute
the proposal hearing panel. The proposal hearing panel shall be composed of the
following:
▪ 1 Chairman - preferably the Dean or a faculty with at least a master's
degree.
▪ 2 Members (one may be a content expert)
10) At the end of the proposal hearing, the chair makes a synthesis and announces the panel’s
verdict.
11) The chairman and the adviser shall ensure that all recommendations for improvement by
the proposal hearing panel are incorporated in the Proposal Manuscript. This may include
grammar, accuracy of language, adequacy of data, interpretation of results, etc.
12) The team shall prepare and provide for the honoraria of the panel of examiners through
the college secretary immediately after the proceedings.
14
13) The proposal is revised based on the recommendation of the panel members during the
proposal hearing.
14) The adviser shall guide the student researchers throughout the conduct of the approved
project proposal. The adviser is responsible for monitoring the students and ensuring that
the approved project design and methodology are followed; appropriate data are
gathered, analyzed and interpreted.
15) One copy of the Revised Proposal Manuscript (Deliverable D6) together with the
Grammarians Certificate (Deliverable D7 – refer to Appendix F. Grammarian’s Certificate
Template) shall be routed to the Adviser, Panel members, and Chairman for the
confirmation of revisions. Approval Sheet (Deliverable D8 - refer to Appendix G. Approval
Sheet) may be routed too for their signatures if already amenable.
16) The hardbound copy containing the Approval Sheet and the Final Proposal Manuscript
(Deliverable D9) with the Proposal CD (Deliverable D10) in a CD Jacket at the inlet portion
of the back cover should be submitted to the Dean’s Office. The color of the hardbound
is black with gold/yellow text. The Proposal CD shall contain the following:
a. Final Proposal Manuscript (word copy) – filename: Research / Capstone Project
Alias
b. Final Proposal Manuscript (puff copy) – filename: Research / Capstone Project
Alias
c. Other pertinent files
7) During the Oral Defense, the adviser shall be the moderator who clarifies and mediates
over issues raised.
8) A designated recorder is tasked to record all the suggestions and recommendations of the
panel during the Oral Defense.
9) At the end of the Oral Defense, the chair makes a synthesis and announces the verdict.
10) The Oral Defense panel chair and the adviser shall ensure that all recommendations for
improvement by the Oral Defense panel are incorporated in the final copies. This may
include grammar, accuracy of language, adequacy of data, interpretation of results, etc.
11) The team shall prepare and provide for the honoraria of the panel of examiners through
the college secretary immediately after the proceedings.
12) Approval Sheet (Deliverable D17), this time for the ITE 404, is necessary prior to the final
submission of the manuscript and other research transcripts.
13) The researchers must submit the 2 copies of Oral Defense CD’s (Deliverable D18). Each of
the Oral Defense CD’s should contain the following:
• complete documentation
i. Final Oral Defense Manuscript (word file)
ii. Final Oral Defense Manuscript (pdf file)
iii. Final Journal-Formatted Manuscript (word file)
iv. Final Journal-Formatted Manuscript (pdf file)
• Developed system.
i. Installation or Setup Files/Folders
ii. Installation and/or Users’ Guide
Team
Alias
NOTE: 1 for each of the 3 to 5 titles chosen by the adviser (strictly word-processed)
Project Title:
Proponents/Researchers: 1.
2.
3.
4.
5.
Scope of the Study:
• Software Specification
• Hardware Specification
19
Proponents/Researchers:
1)
2)
3)
4)
5)
____________________________________ _____________________________________
_____ ___
(Signature of Project Manager over printed name) (Signature of Adviser over printed name)
____________________________________ _____________________________________
_____ _____
(Signature of Patent Searcher over printed name) (Signature of the Dean over printed name)
***Accomplish in 3 copies
20
▪ Schedule Feasibility
• Gantt Chart
▪ Economic Feasibility
• Cost and Benefit Analysis
• Cost Recovery Scheme
▪ Requirements Modeling
• Input
• Process
• Output
• Performance
• Control
• Data and Process Modeling
▪ Context Diagram
▪ Data Flow Diagram
▪ System Flowchart
▪ Program Flowchart (highlights only)
• Object Modeling
▪ Use Case Diagram
▪ Class Diagram
▪ Sequence Diagram
▪ Activity Diagram
▪ Risk Assessment/Analysis
o Design
▪ Output and User-Interface Design
• Forms
• Reports
▪ Data Design
• Entity Relationship Diagram
• Data Dictionary
▪ System Architecture
• Network Model
• Network Topology
• Security
o Development
▪ Software Specification
▪ Hardware Specification
▪ Program Specification
▪ Programming Environment
• Front End
22
• Back End
▪ Deployment Diagram
▪ Test Plan
o Testing and Evaluation
▪ Unit Testing
▪ Integration Testing
• Compatibility Testing
• Performance Testing
• Stress Testing
• Load Testing
▪ System Testing
▪ Acceptance Testing (must be done after the Oral Defense)
▪ Conclusions
▪ Recommendations)
▪ Implementation Plan
o Project Implementation Checklist
o Implementation Contingency
o Infrastructure/Deployment
▪ BIBLIOGRAPHY
▪ APPENDICES
o Relevant Source Code
o Evaluation Tool
o Sample Input / Output / Reports
o Users Guide
o Other Relevant Documents
o Working Title Form
o Grammarian’s Certification
o Curriculum Vitae
23
_____________________________________________________________________________________
_____________________________________________________________________________________
Proponent/s:
__________________________ ___________________________ ___________________________
CERTIFICATION
The undersigned members comprising the panel for oral examination hereby agree to the schedule of hearing for
the above research. [Please PRINT NAME and SIGN]
_____________________________
RESEARCH ADVISER
___________________________________________ ___________________________________________
PANEL MEMBER 1 PANEL MEMBER 2
__________________________________________
PANEL CHAIR
APPROVED:
_______________________________________
Program Head, Information Technology
24
[Date Read]
G R A M M A R I A N’ S C E R T I F I C A T E
This is to certify that the undersigned has reviewed and went through all the pages of the proposed project
study / research entitled “TITLE OF THE CAPSTONE” as against the set of structural rules that govern the
Signed:
Conforme:
APPROVAL SHEET
The Research / Capstone Project Study entitled [TITLE OF THE PAPER IN CAPITAL LETTERS AND IN BOLD
FORMAT] prepared and submitted by [Name of the Team Members separated by comma] has been
examined and is recommended for approval and acceptance.
RECOMMENDED:
[ADVISER NAME]
Adviser
=====================================================================
APPROVED by the Committee on Oral Examination with a grade of PASSED on [Date].
___________________________________
Chairman
___________________________________ ___________________________________
Member Member
=====================================================================
ACCEPTED and APPROVED in partial fulfillment of the requirements in Bachelor of Science in Information
Technology.
Date: _______________
26
A Proposal
presented to the Faculty of the
Information Technology Department
Southern Philippines College
Cagayan de Oro City
By
[Student 1]
[Student 2]
[Student 3]
[Student 4]
[Student 5]
March, 2012
(the batch month and year)
27
By
[Student 1]
[Student 2]
[Student 3]
[Student 4]
[Student 5]
June, 2XXX
(the batch month and year)
28
address is needed, center all address text. For address to obtain the report within your citation)
two addresses, use two centered tabs, and so and may be obtained by any reader. Proprietary
on. For more than three authors, you may have information may not be cited. Private
to improvise.1 communications should be acknowledged, not
First Page Copyright Notice referenced (e.g., “[Robertson, personal
Please leave 3.81 cm (1.5") of blank text box at the communication]”).
bottom of the left column of the first page for the Page Numbering, Headers and Footers
copyright notice. Do not include headers, footers or page numbers in
Subsequent Pages your submission. These will be added when the
For pages other than the first page, start at the top of publications are assembled.
the page, and continue in double-column format. The FIGURES/CAPTIONS
two columns on the last page should be as close to Place Tables/Figures/Images in text as close to
equal length as possible. the reference as possible (see Figure 1). It may
extend across both columns to a maximum
Table 1. Table captions should be placed above the width of 17.78 cm (7”).
table
Captions should be Times New Roman 9-point
Graphics Top In-between Bottom bold. They should be numbered (e.g., “Table 1”
Tables End Last First or “Figure 2”), please note that the word for
Figures Good Similar Very well Table and Figure are spelled out. Figure’s
References and Citations captions should be centered beneath the image
Footnotes should be Times New Roman 9-point, or picture, and Table captions should be
and justified to the full width of the column. centered above the table body.
Use the “ACM Reference format” for references SECTIONS
– that is, a numbered list at the end of the The heading of a section should be in Times New
article, ordered alphabetically and formatted Roman 12-point bold in all-capitals flush left with an
accordingly. See examples of some typical additional 6-points of white space above the section
reference types, in the new “ACM Reference head. Sections and subsequent sub- sections should
be numbered and flush left. For a section head and a
format”, at the end of this document. Within this
subsection head together (such as Section 3 and
template, use the style named references for the subsection 3.1), use no additional space above the
text. Acceptable abbreviations, for journal subsection head.
names, can be found here:
Subsections
http://library.caltech.edu/reference/abbreviatio
ns/ The heading of subsections should be in Times
New Roman 12-point bold with only the initial
letters capitalized. (Note: For subsections and
The references are also in 9 pt., but that section sub subsections, a word like the or a is not
(see Section 7) is ragged right. References should capitalized unless it is the first word of the
be published materials accessible to the public. header.)
Internal technical reports may be cited only if
Sub subsections
they are easily accessible (i.e. you can give the
The heading for sub subsections should be in Times [4] Tavel, P. 2007 Modeling and Simulation Design.
New Roman 11-point italic with initial letters AK Peters Ltd.
capitalized and 6-points of white space above the sub [5] Sannella, M. J. 1994 Constraint Satisfaction and
subsection head. Debugging for Interactive User Interfaces.
Sub subsections Doctoral Thesis. UMI Order Number: UMI Order
The heading for sub subsections should be in Times No. GAX95-09398., University of Washington.
New Roman 11-point italic with initial letters [6] Forman, G. 2003. An extensive empirical study of
capitalized. feature selection metrics for text classification. J.
Mach. Learn. Res. 3 (Mar. 2003), 1289-1305.
Sub subsections
The heading for sub subsections should be in Times [7] Brown, L. D., Hua, H., and Gao, C. 2003. A widget
New Roman 11-point italic with initial letters framework for augmented interaction in SCAPE.
capitalized. In Proceedings of the 16th Annual ACM
Symposium on User interface Software and
ACKNOWLEDGMENTS
Technology (Vancouver, Canada, November 02 -
Our thanks to ACM SIGCHI for allowing us to 05, 2003). UIST '03. ACM Press, New York, NY, 1-
modify templates they had developed. 10. DOI=
REFERENCES http://doi.acm.org/10.1145/964696.964697
[1] Bowman, M., Debray, S. K., and Peterson, L. [8] Y.T. Yu, M.F. Lau, "A comparison of MC/DC,
L. 1993. Reasoning about naming systems. MUMCUT and several other coverage criteria for
logical decisions", Journal of Systems and
ACM Trans. Program. Lang. Syst. 15, 5 (Nov.
Software, 2005, in press.
1993), 795-825. DOI=
http://doi.acm.org/10.1145/161468.161471. [9] Spector, A. Z. 1989. Achieving application
requirements. In Distributed Systems, S.
Mullender, Ed. Acm Press Frontier Series. ACM
Press, New York, NY, 19-33. DOI=
http://doi.acm.org/10.1145/90417.90738