<<TITLE>>

A Software Proposal
Presented to the
Basic Education Department- Senior High School
University of the East, Manila

In Partial Fulfillment
of the Requirements for Practical Research II

by
<< Team Members’ Name>>

<<Date>>
 TABLE OF CONTENTS
TITLE PAGE
Title Page ................................................................................... i
Approval Sheet............................................................................ ii
Dedication .................................................................................. iii
Acknowledgment ........................................................................ iv
Abstract ...................................................................................... v
Table of Contents ....................................................................... vi
List of Tables .............................................................................. vii
List of Figures ............................................................................. viii

CHAPTER
1 PROJECT OVERVIEW
Project Background.....................................................................
Objectives of the Project ............................................................
Statement of Work
Scope of the Project.........................................................
List of Deliverables...........................................................

2 ANALYSIS OF EXISTING AND RELATED SYSTEMS

Review of Existing Systems........................................................
Review of Related Systems........................................................
Operational Definition of Terms..................................................

3 SOFTWARE DEVELOPMENT METHODOLOGY

Software Design and Development Approach
Software Process Model .................................................
System Framework..........................................................
Process Flow (DFD) ........................................................
E-R Diagram and Table Normalization............................
Constraints and Assumptions.....................................................
 Risks and Minimization Measures..............................................
Project Schedule ........................................................................
Testing and Evaluation Procedure .............................................

4. RESULTS AND DISCUSSIONS

Developed (Implemented*) Project ....................................................
Testing and Evaluation Results .........................................................
Implementation Procedure
Systems Installation and Integration................................
User Training....................................................................

5 SUMMARY OF FINDINGS, CONCLUSIONS AND RECOMMENDATIONS

Summary of Results ...................................................................
Conclusions ................................................................................
Recommendations .....................................................................

Bibliography ..........................................................................................
Appendices ...........................................................................................
· Gathered Documents
· Transcript of Interview
· Sample Reports Generated by the System
· Students’ Curriculum Vitae
· User’s Manual
· Survey instrument
· Summary of Evaluation Results

· Certificate of Implementation
CHAPTER 1 – PROJECT OVERVIEW
Project Background
This section includes a short narrative background of the project. It gives the
reader an introduction on how the project came about and discusses the general
problems that it intends to concentrate on. This will give a short discussion on the
nature of the company being studied.

Objectives of the Project

General Objective
State the main goal of your project.
The general objective of your project is to provide a solution to the problems stated
in the Project Background. Logically, this should capture the title of the research.

Example:
The general objective of this project is to develop a preventive maintenance and
monitoring system that will facilitate better monitoring measures to ensure high-
quality services of all buses of Five Star Incorporated.

Specific Objectives
The specific objectives of the study
The specific objectives of the project are the following:
· To design a prototype that will . . . .
· To develop a system that will. . . .
· To test and evaluate the acceptability of the system in terms of
functionality, reliability, usability and so on by gathering feedback from
prospective users and technical experts.

Statement of Work

▪ Scope of the Project

The scope of the project means coming to a common understanding of its
major boundaries and the business functions it encompasses. Example: an
inventory system may INCLUDE raw materials and finished goods inventory,
 but to EXCLUDE cash flow. Or an enrollment system may or may not include
accounting system, student record management system, etc. It includes the
agreed activities that the team has to undertake and deals with how each
deliverable is prepared and presented. For example, your group is
commissioned to develop a Library System for Matalino University. The
University has existing student database; hence, the team might ask the client
whether will they utilize the existing database, or need to develop one. If the
client requires the group to use the existing database, then the development of
the new database is NOT covered in the scope of the project. Now, if the group
is required to develop an independent database, database development will be
part of the scope of the project plus the client’s database requirements and
specifications.

▪ List of Deliverables
List all expected outputs based on company’s requirement. The list should be
accompanied with a detailed description of the deliverables.

CHAPTER 2 – ANALYSIS OF EXISTING AND RELATED SYSTEMS

Review of Existing System

This section presents the existing or current system. This will allow them to
present the gaps/problems in the existing system in detail. It should contain the System
Description, Process Flow (DFD or Flowchart, depending on the type of the system),
and SWOT Analysis.

Review of Related Systems

After presenting the Review of Existing System, the team should also discuss
other systems that are related to their proposed system. This section should present the
features of the related systems that are beneficial for the proposed project. Related
systems are systems that are available in the market or systems that had been
implemented in a company.

Operational Definition of Terms

Define terminologies based on how they are used in the study. Terminologies
are alphabetically arranged. The definition of each term is presented in a paragraph
 format, with the first line of the definition, indented. (The different criteria in the
evaluation sheet should also be defined here.)

CHAPTER 3 – SOFTWARE DEVELOPMENT METHODOLOGY

Software Design and Development Approach
▪ Software process model discusses the activities/procedures necessary to
come up with the system. It shows and discusses the chosen software
process model. Examples of such models are: waterfall model, prototype,
RAD, Spiral model, etc. Steps in details should be discussed very well and
a justification on the choice of process model should be included.
▪ System Framework which may be a block diagram, representing the major
components of the system and their relationship with one another.
▪ Process flow (DFD) is the data flow diagram of system that includes the
context diagram and diagram 0. Child diagrams should be included if
processes defined in diagram 0 are quite general in context and
presentation.
▪ E-R Diagram and Table Normalization shows the relationships of entities
and the tables derived from the relationship. At least third level of
normalized table should be presented.

Constraints and Assumptions (5 M’s and T)

· Constraints are limits or boundaries within which you must
work. These restrain the performance of the group. For
example: 1) Budget (is the company willing to buy the
technology?) 2) Time (What will be the effects of delayed
shipment/non-availability in the schedule of the project?) 3)
Technology (Is the technology needed available?) 4) Skill (Do
we have the skill to apply the technology?) etc.
· Assumptions are positive statements that the aforementioned
constraints will/can be attended. For example, you are
developing a Payroll System with the use of Iris Scanner. The
scanner will be ordered from abroad. Hence, your
assumptions are: 1) the company is willing to buy the
technology, 2) it is available (not out-of-stock), 3) if available, it
will be delivered on time, 4) if delivered on time, it is not
defective, and 5) the team is capable of using the technology.
 Risks and Minimization Measures
· Risks are the threats of unsolved constraints and unmet
assumptions. List the effects of unsolved constraints and
unmet assumptions. Minimization measures try to lessen the
effects of risks.

NOTE: Constraints, Assumptions, Risks, and Minimization Measures can be

presented in tabular format. For example:

Minimization
Constraints Assumptions Risks
Measures
The technology is The company is If the company will · Look for an
expensive. willing to fund the not fund the alternative
technology. technology, the technology.
proposal will be · Look for other
rejected. company that is
willing to fund the
proposal.

Project Schedule
This section should present the Gantt chart (with assigned person on each
activity) and PERT.

Testing and Evaluation Procedure

After developing the system, the next step is to test and evaluate its acceptability.
This section discusses how testing and evaluation is done. This may include the
following:
· Steps in conducting the testing
State the steps that encompass the testing and evaluation procedure. It should
include the instructions given to the respondents on what and how to explore
the system in order to test it.
· The client should test the system.
· Evaluation Instrument
Discuss the evaluation instrument to be used in order to know the acceptability
of the system. Discuss on how did you arrive with your evaluation instrument.
 Discuss your bases in the development of the instrument. For your
convenience, the most usual rating scale being utilized is given in Table 1.

Table 1.
Rating, Range and Its Verbal Interpretation
Rating Range Verbal Interpretation
5 4.51 – 5.00 Highly Acceptable
4 3.51 – 4.50 Acceptable
3 2.51 – 3.50 Moderately Acceptable
2 1.51 – 2.50 Slightly Acceptable
1 1.00 – 1.50 Not Acceptable

· Statistical Treatment of Data

This section explains the statistical tool(s) used in computing the rating of the
respondents. If the statistical formula used is widely known (such as mean),
there is no need to show the formula.

The system can be tested and evaluated depending on the nature of the system.
First, if there is only one system user, the system has to be tested with at least 40
dummy data. The result will be compared with the actual data. Second, if there are
multiple users (at least 30), these users will evaluate the system.

For CMR111/MERIT, Chapters 1 – 3 are initially written in either present or future verb
tense. In CPP111/Capstone A, the remaining Chapters (4 and 5) should be finished
after the development stages of your system. Final document verb tense should be
changed appropriately to past tense since the project is already done and has been
defended to a group of evaluators. Necessary appendices should already be included
for CMR 111/MERIT, and should be updated during CPP 111/Capstone A.

CHAPTER 4 – RESULTS AND DISCUSSIONS

 Developed (Implemented*) Project
· Description
· Features and Capabilities
a. Enumerate and discuss the features of the system. What can it do? What
are its advantages?
b. Modular presentation through explanation of screen shots.
c. Discuss the result of the project in accordance with the objectives of the
project. Screen shots of outputs with accompanying explanations are
recommended.
*NOTE
▪ The word “Developed” will be changed to “Implemented” once the system is
deployed in the company.
▪ The Company will issue a Certificate of Completion to ensure that the system
is employed.
▪ If the system was implemented and yet it is not acceptable in the company,
the group grades will be withheld.

Testing and Evaluation Results (initial)+

It discusses in detail the result of the evaluation procedure. Data may be
presented in a table format with accompanying interpretation. This section should
answer the following:
· Who evaluated the system?
· What is the numerical score with the equivalent descriptive rating given by each
respondent in each criterion?
· What was the overall acceptability rate of your respondents and how would you
rationalize it with respect to the overall quality of the system.

Implementation Procedure+
This section is composed of Systems Installation and Integration, and User
Training. The team has to present how the system should be installed and be integrated
in the company. They should also provide a user-training plan so that the company can
fully adopt the system. This section should only be written after the actual testing of the
software.
▪ Systems installation and integration
▪ User-Training

+
Initially, technical experts and 30 users (who are not the actual client of the system)
will test the system. After the actual testing, this section should be revised accordingly.

CHAPTER 5 – SUMMARY OF FINDINGS, CONCLUSIONS AND

RECOMMENDATIONS
Summary of Findings
Summarize the result the software development process and evaluation.

Conclusions
Discuss the interpretation of your evaluation results in relationship with your initial
objectives? Were you able to achieve these objectives? What does the result of the
evaluation procedure say about your project? How acceptable is your project?

Recommendations
What modifications/improvements can you give to future teams in reference to
the weaknesses/limitations of system and of the whole project?

BIBLIOGRAPHY
This section should identify the different sources of information utilized in the
accomplishment of the project. All sources mentioned in the document should be
reflected here. Sources are categorized according to type (books, journal, theses, etc.)
and should be written alphabetically according to the Author’s Surname. Use the
appropriate APA format for proper bibliographical entries.

APPENDICES
 This section allows the group to include the documents related in their topic. This
may include sample documents, sample screen outputs, interviews, survey instruments,
etc.