UNIVERSITY OF THE EAST

Manila Campus
COLLEGE OF ENGINEERING
DEPARTMENT OF COMPUTER ENGINEERING

SOFTWARE DEVELOPMENT CAPSTONE PROJECT

DEVELOPMENT PROPOSAL MANUSCRIPT FORMAT

Title Page
Approval Sheet
Turnitin Certificate
Certificate of Editing
Dedication
Acknowledgement
Table of Contents
List of Tables
List of Figures
CHAPTER I: PROJECT OVERVIEW

A. Background of the Study

This section must briefly discuss the sponsor if necessary; provide organizational
profile; what are the problems on the existing system; is there really a need for the
proposed system; and why and how the team decided to came-up with the
proposed system; give a short overview of the proposed system.

B. Project Objectives
What are the general and specific objective of your study?

C. Statement of Work
C.1 Scope of the Project
C.1.1 Functional Requirements

This section must discuss the different functional requirements of

the proposed system. The team may enumerate the different
modules or procedures that the proposed system will have. (The
official definition of ‘a functional requirement’ is that it
essentially specifies something the system should
do)

C.1.2 Limitations
This section must discuss the different boundaries or
functionalities that the proposed system will not be able to do.

Prepared by: Prof. Errol John M. Antonio, sgd.

 C.1.3 Non-Functional Requirements
This section must discuss the different non-functional
requirements of the proposed system. It includes technical non-
functional and non-technical non-functional requirements.

Some typical non-functional requirements are: Performance,

Scalability, Capacity, Availability, Reliability, Recoverability,
Maintainability, Serviceability, Security, Regulatory,
Manageability, Environmental, Data Integrity, Usability,
Interoperability. (Refer to ISO ISO/IEC 25010:2011 Systems
and Software Engineering -- Systems and software Quality
Requirements and Evaluation (SQuaRE))
C.2 List of Deliverables
• This section must enumerate and discuss the different
deliverables that team will provide after the development
(Includes but not limited to: URL, hosting credentials, user’s
manual, maintenance manual).

CHAPTER II: REVIEW AND ANALYSIS OF EXISTING SYSTEM

A. Review of Existing System

• This section must discuss the process of the existing system. Provide system
framework and Data Flow Diagram (DFD) of the existing system.
B. Review of Related Systems
• This section must discuss the team’s review on the related systems. At least
three (3) related system must be review. Provide screenshots.
C. Strength, Weakness, Opportunity, and Threat (SWOT) Analysis
• This section provides SWOT analysis for the existing system and related
systems. Use SWOT diagram if necessary.
D. Operational Definition of Terms
• In ascending order. No abbreviations or acronyms.

CHAPTER III: SOFTWARE DEVELOPMENT METHODLOGY

• Software Design and Development Approach
• This section provides the MOST APPROPRIATE software development model.
Discuss each stage.
• System Framework
• This section provides the system framework of the proposed system. ALL
processes must be included in the framework.
• Note. Use only thin arrow lines; horizontal and vertical flow only; no overlapping;
and use consistent images.
• System Wireframe
• This section must show the proposed system wireframe.
• System Mock-Up
• This section must show the proposed system mock-up.
• System Story Board
• This section must show the proposed system story board.
• Data Flow Diagram
• This section must illustrate dataflow diagram.
• Context Diagram, Level 1 and Level 2.
• If possible, fit each diagram in one page.

• Entity Relational Diagram

Prepared by: Prof. Errol John M. Antonio, sgd.

 • This section must illustrate ERD. Include all field, PK and FK. Show all
relationships. Use crow’s foot notation.
• Data Dictionary
• This section must present the data dictionary. Include all field, PK and FK.
Landscape as much as possible.
• Use the prescribed format.
• Use-Case Diagram
• Provides graphic depiction of the interactions among the elements of a
system.
• System Flowchart
• Illustrate the system flowchart.
• Observe proper use of symbols and connections.
• Modularize your flowchart
• Data Gathering Procedures
• Details of data collection procedure
• Includes time frame involved in data collection
• Who will do the data collection?
• Testing and Evaluation Procedures
• Details of how the proposed system be tested
• Includes time frame involved in testing
• Who will do the testing?
• Who will verify and certify your test results?
• Research Instrument
• Contains the criteria of measuring the effectivity and efficiency of the proposed
system.
• Instrument must be measurable by numerical values.
• Instrument may be provided by the instructor.
• Statistical Analysis of Data
• What statistic are to be used on the data and why?
• Should be in consonance with the objective.

NOTES

WORKING TITLE:
• Consist of not more than 20 major words
• Give a concise, accurate description of the design project
• Include key words in the title to make the design project more easily retrievable in electronic
listings
• Avoid using scientific formulas, Greek letters, symbols and abbreviations in titles - write them out
as words instead. Symbols often cannot be indexed in a library.
• Written in uppercase and in an inverted pyramid format.

TITLE PAGE:
• Use the prescribe format

APPROVAL SHEET, RECOMMENDATION SHEET, TURNITIN CERTIFCATE, CERTIFICATE OF

EDITING
• The department will be providing the said documents.

CHAPTER DESCRIPTION:
• Each chapter shall have an introductory description.

Prepared by: Prof. Errol John M. Antonio, sgd.

FONT STYLE:

• Must be appropriate for an academic paper and must use the same font primarily throughout the
manuscript (dedication page excepted)

Headings: Times new Roman /Arial, 12, Bold

Contents: Times new Roman /Arial, 12
*Observe proper italicization

RUNNING HEADERS AND FOOTERS:

• It is not necessary to have running headers or footers in your manuscript, other than for page
numbers. If you wish, you can use one with page titles (for the preliminary pages), chapter titles
(and chapter numbers, if applicable).
• But you must be consistent throughout the manuscript. Information other than this is not
acceptable in a header or footer. The running header must be placed top center or top right-
justified.

OUTLINE AND SPACING:

• Double spacing, with 1.0 inch invisible margin from top, bottom and right edges, and 1.5 inches in
left edge of 8.5” x 11” of 70-80 Grams per Square Meter paper.
• The margin requirements apply to all photocopies, photographs, charts, maps, and other items,
which might be included in the appendices.
• Adopt the “descending” outline of the MLA (Modern Language Association) format.
• Spaced quotations of more than one line can be single-spaced; Acknowledgements, footnotes,
table, figure and illustration captions and the bibliography can be single-spaced, provided that
individual entries are separated by a full space
• Dedication page and Abstract page are single spaced. All other pages are double spaced.

INDENTION:
• Do not indent:
The first line of Dedication Page, any line on the Abstract Page, subheadings in the
body of the paper
• Indent:
Subheadings in the Table of Contents, paragraphs in the body of the paper
• Centering:
All titles should be centered (examples: Abstract, Dedication, Table of
Contents, Chapter I, Chapter II, Appendices, etc.). Subheadings should be
justified, not centered.

TABLES AND FIGURES:

• Tables, figures and illustrations must be identified with the word "Table", "Figure", or other
appropriate descriptor, and include a title and/or caption.
• You must use a consistent format for titles and captions of tables, figures and illustrations
throughout the manuscript
• Lettering in tables and figures should be at least 2 mm high to ensure that the information is easy
to read
• Tables and figures must have titles or captions, and must be numbered.
• Headings must be repeated on the second and subsequent pages of tables that split over two
pages or more
• Tables should be split at an appropriate place, e.g. just before a new subheading
• The format for titles and captions of tables, figures and illustrations must be consistent throughout
the manuscript.

Prepared by: Prof. Errol John M. Antonio, sgd.

TABLE AND FIGURES (NUMBERING):

• Tables, figures, illustrations and other such items must be numbered consecutively in order of
appearance within the manuscript.
• There are two methods for numbering Tables, Figures and other items:
sequentially throughout the manuscript, e.g. 1, 2, 3…

1. Sequentially throughout the manuscript, e.g. Recommended.

Figure 1, Figure 2, Figure 3…, Figure n
2. Chapter number first, then numbered sequentially within
each chapter, e.g.:
Tables in Chapter 1: Table 1.1, 1.2, 1.3…
Figures in Chapter 3: Figure 3.1, 3.2, 3.3…
• Whichever method you choose, the numbering style must be the same for both Tables and
Figures; for example: Table 1.1 and Figure 1.3, or Table 1 and Figure 3, not Table 1 and Figure
1.3.

TABLES AND FIGURES (LOCATION):

• There are three acceptable locations for tables and figures: Recommended.
1. Within the chapter immediately following first reference to them
2. Grouped at the end of the relevant chapter
3. Grouped at the end of the manuscript before the bibliography
• Whichever method you choose, you must be consistent.
• If your table and figures are grouped at the end of the manuscript, you must include an entry in
the table of contents that directs the reader to their location.

PAGE NUMBERS:

• PRELIMINARY PAGES
Must be numbered in lower case Roman numerals (ii, iii, iv, etc.) the title page is "i" but this
number must not appear on the page numbering begins at "ii" on the first page of the abstract

• BODY OF MANUSCRIPT:
Must be numbered in Arabic numerals (1, 2, 3, etc.) the first page of the text is "1“ subsequent
pages are numbered continuously throughout, including pages with tables and figures,
bibliographies, appendices, and index.

• WHOLE MANUSCRIPT
Every page except the title page must have a number on it there must be no blank pages in the
manuscript, page number sequence and completeness will be checked at final submission

• LANDSCAPE PAGES
Landscape pages must be orientated in your PDF so that they are readable without rotation. You
do not need to change the location or orientation of the page number.

• FACING PAGES
Facing pages are not acceptable. If the caption for a figure, table, etc., cannot appear on the
same page as its accompanying illustration, place the illustration on a separate page after the
caption.

APPENDICES:

• To be cited in the body

• Includes data sheets, tables, and figures

Prepared by: Prof. Errol John M. Antonio, sgd.

BIBLIOGRAPHY:

• It can be a bibliography that contains webliography or references or end notes

• Use American Psychological Association (APA) format
• If you use in-line citation, do not arrange in aphetically order.

UPON COMPLETION OF THE RESEACH PROPOSAL STAGE

Submit the following:
1. Edited Software Development Proposal Manuscript
2. IEEE Journal Format (maximum of 10 pages)

Prepared by: Prof. Errol John M. Antonio, sgd.