Capstone Documentation Check List

No Status Description Reference

General Format Guideline
SPACING PLMar
1.  Double-space throughout the paper, except entries in the appendixes. Thesis
Manual
 Entries in tables may be single or double-spaced; prime consideration is and Style
2. Guide
readability.
 Spacing between subsections or subheadings within a chapter should at Handouts
3. least be double-spaced, but may be triple- or quadruple-spaced for (2018)
added clarity. Pg. 10
 For added clarity put two spaces between sentences.
4.
FONT
5.  Use 12-size Times New Roman font throughout the paper, including
entries in tables
MARGINS
6.  Use a 1.25-inch margin for the left side; 1-inch for all other sides of the
page
ALIGNMENT
7.
 Left-aligned throughout the paper
INDENTION
8.  Paragraph indentation should be 5-7 spaces or the normal tab (0.5”)
default
RUNNING HEAD
 The running head is an abbreviated title, maximum of 50 characters,
including spaces. Placed at the upper left hand corner, ALL CAPS. Should
9.
only appear on the pages after a new chapter and includes references
and appendices. Running head should never appear on title pages and
other front materials.
PAGINATION
10.  ALL page numbers are placed at the upper right hand corner of each
page
11.  Page 1 begins in Chapter I (Introduction) but is not numbered.
12.  The first page of a new chapter is not numbered but is still counted
 Lower-case Roman numerals are used for the front material,
o Page numbers first appear with the Executive Summary (or page
13. iv), Acknowledgments (v), Table of Contents (vi, vii, etc),
Appendices (v..), List of Tables (v..) and List of Figures (v..)
o The title page (i), approval sheet (ii)
HEADING & SUBHEADINGS
PLMar
 Level 1 heading: Chapter titles are printed in boldface, title case [upper-
Thesis
and lower case], and centered on top of the page.
Manual
 Level 2 heading: Bold, flushed to the left, title case [upper-and lower
14. and Style
case]. Text follows in the next paragraph, indented (5 spaces from the
Guide
left margin or the normal "0.5 tab")
Handouts
 Level 3 heading: Bold, 5 spaces from the left margin *normal “0.5” tab+,
(2018)

1 of 6
Capstone Documentation Check List

lower case except for the first letter, should end with a period, text Pg. 11
should follow immediately this heading
 Level 4 and succeeding subsection/subheadings: Italicized, 5 spaces
from the left margin*normal “0.5” tab+, lower case except for the first
letter, should end with a period, text should follow immediately.
SAMPLE PAGES OF THE FRONT MATERIALS
 The title should be in inverted triangle form (refer to title page) PLMar
 The List of Tables and the List of Figures are placed in their own Thesis
separate pages and are never combined. In other words, start a new Manual
page when listing down List of Figures even if it can still fit the bottom of and Style
the List of Tables. Guide
 The arrangement of Front Materials is as follows: Handouts
o Title page (no small roman numeral for page number but is (2018)
counted as i) Pg. 12
o Approval Sheet (no small roman numeral for page number but is
counted as ii)
o Executive Summary (small roman numeral first appears for page
number. Use "iv")
15.
o Acknowledgements (use small roman numeral "v" for page
number)
o Table of Contents (use small roman numeral accordingly)
o List Tables (use small roman numeral accordingly)
o List of Figures (use small roman numeral accordingly)
 Chapter I, page 1, immediately follows after the List of Figures. However,
page number only appears on the next page after the start of each
chapter page. The chapter page is still counted.
 The title page is the same template used in the cover page of the
hardbound final capstone copy (the font is gold and the color of the
hardbound is maroon).

PLMar
Thesis
Manual
and Style
16. APPROVAL SHEET Format
Guide
Handouts
(2018)
Pg. 14
Chapter 1 (Introduction)
Project Context Outcomes-
 Presentation of the importance of the system software, algorithms, Based
processes or an enterprise resource plan to be designed and/or Practical
developed Guide to
17.
 Research Locale Thesis and
 The existence of an unsatisfactory conditions Capstone
 A desire to find a better way of doing something or improving the Project
present condition Writing in

2 of 6
Capstone Documentation Check List

Computing
Pg. 16-18
Outcomes-
Based
Practical
Guide to
Purpose and Description
Thesis and
18.  The features and capabilities should be written in such a way that it
Capstone
would highlight the significance of the project.
Project
Writing in
Computing
Pg. 27-29
Outcomes-
Based
Practical
Objectives
Guide to
 The objectives of the study will guide the researcher and the reader to
Thesis and
19. know what the proponent(s) need to do.
Capstone
o Objectives are written by either beginning with an action verb or
Project
an infinitive
Writing in
Computing
Pg. 21-22
Outcomes-
Based
Scope and Limitations
Practical
 The scope and Delimitation of the Study should include a brief statement
Guide to
of the general purpose of the study, the target users/beneficiaries of the
Thesis and
20. study, the period of the study and the features of the proposed
Capstone
software.
Project
 The limitation of the study includes the weaknesses of the study beyond
Writing in
the control of the researcher.
Computing
Pg. 29-31
Chapter 2 (Related of Related Literature/Systems)
 The aim of a literature review is to show the reader what the researchers Outcomes-
have read, and have a good grasp of, the main published work Based
concerning a particular topic or question in the particular field. Practical
Guide to
Elements of Literature Review Thesis and
o An overview of the subject, issues or theory under consideration, Capstone
along with the objectives of the literature review; Project
21.
o Division of works under review into categories (e.g. those in Writing in
support of a particular position, those against, and those offering Computing
alternative theses entirely:; Pg. 47-57
o Explanation of how work is similar to and how it varies from the
others;
o Conclusions as to which pieces are best considered in their
arguments, are most convincing of their opinions, and make the

3 of 6
Capstone Documentation Check List

greatest contribution to the understanding and development of

their area of research.
Citations
Plagiarism
Chapter 3 (Technical Background)
Outcomes-
Based
 Provides and discuss the requirements upon development and
Practical
deployment of the proposed system
Guide to
o Platform to be used
Thesis and
22. o Hardware specifications
Capstone
o Software specifications
Project
o Network specifications (if applicable)
Writing in
o Peopleware (if applicable upon deployment)
Computing
Pg. 46-47
Definition of Terms
 Terminology/words that is being used of the researcher/proponents
23. during development.
o This should be provided to avoid misunderstanding and adds
enlightenment to the reader.
Chapter 4 (Methodologies)
Requirement Analysis
24.  Discussion of the chosen SDLC Model
 Fishbone Diagram (figure)
o Illustrate the unsatisfactory condition that is address by the
25.
researchers/proponents
o Provide all possible causes that contribute to the issues.
 Data Flow Diagram of Current system
o Level 0 or Context Diagram
o Level 1 or illustration of Main Process
o Level 2 or illustration of sub-process of each Main Process (if
applicable)
26.
Note: Objects that will be used:
Rectangle = Entity
Arrow with label= flow
Rectangle with vertical line = storage/database
Rectangle with horizontal line = process
Requirements Documentation
Outcomes-
Based
Practical
Guide to
27.  Provide the name of the module and the functionality. Thesis and
Capstone
Project
Writing in
Computing

4 of 6
Capstone Documentation Check List

Pg. 69-70
Functional Decomposition (figure)
28.
 Illustrate the system module and function that will be design.
Design of Software, Systems, Product, and/or Processes
Outcomes-
Based
Practical
Guide to
Under this part of documentation, adviser or panelist may require the
Thesis and
29. proponents to include in this Chapter, among others, conceptual design, data
Capstone
model, system architecture, and block diagrams.
Project
Writing in
Computing
Pg. 70-72
Testing
30.  List the type of testing that will be used to validate the functionality of
the system.
31. Description of the Prototype (figure)
Outcomes-
Based
Practical
Guide to
Thesis and
32. Implementation Plan (table)
Capstone
Project
Writing in
Computing
Pg. 76-77
33. Implementation Result (if applicable)
Chapter 5 (Recommendations)
Outcomes-
Based
Practical
Guide to
 Provides the client all the necessary requirements and recommendation Thesis and
34. to maximize the developed system/application. Capstone
 It will include a recommendation for future development. Project
Writing in
Computing
Pg. 127-
128
Appendices
35. Transcript of Interview signed by the authorized representative
36. Photos of Current documentations/ current process
Photos shows data gathering, investigation done. (Floor plan/layout,
37.
building, environment.
38. DFD or Flowchart of the proposed system

5 of 6
Capstone Documentation Check List

39. Final screen layouts

40. Sample screen input and output and reports
41. Testing Results
User Guide/Manual
42.  Documentation for the user.
o Must be a user centric design
43. Relevant Source Code
ONE PAGE CURRICULUM VITAE PER TEAM MEMBER WITH FORMAL 2X 2
44.
PICTURE and legitimate contact information.

Crisanto S. Sarmiento

6 of 6