Sie sind auf Seite 1von 9

CHAPTER III

RESEARCH METHODOLOGY AND DESIGN

3.1

METHODS OF RESEARCH USED


3.1.1 INTERNET METHOD
This method was used by the proponent in coming up with new
technology innovations that will ensure both the aesthetic value and the
functionality of the application. It was used to research for different topics
related to the study as it is filled with huge amount of information. The
proponent used the advantage of the Internet in order to save time and
money.

3.1.2 PROGNOSTIC METHOD


This is a method of prediction that correlates with something that is
about to happen in the future. Tools of the system analysis were done and
used to complete the study for better understanding and development of
the system.
Due to the very limited time, the proponent used this method in
order to avoid the delay of the application. The probability of failure was
estimated and actions were taken to prevent future failures.
3.1.3 LIBRARY METHOD
20

The proponent used this method in gathering information from


various resources and references such as books, magazines, news,
journals, and other printed related literatures and studies from different
libraries to gain more related information about the proposed application.
The proponent used AMA Computer College Pampanga Campus library
in gathering information related to its study.

3.1.4 CREATIVE METHOD


The proponent used this method to create new ideas and features
for the proposed application by using the imagination and creative mind of
the proponent. The researcher used his creativeness in conceptualizing
the plot, design, and mechanics of the proposed study guide application.

3.2

DATA GATHERING INSTRUMENTS


3.2.1 OBSERVATION
Before conducting the study, the proponent observed on what kinds
of problems need to be solved and what kind of technology is very popular
or mostly used today. The researcher found out that mobile application is
an effective way to increase the interest of the users when it comes to
learning.

21

There are several situations that the proponent had observed while
conducting the study and developing the application like observing the
behaviour of the application, the results of the experiments, and the
importance of the project in the society.

3.2.2 QUESTIONNAIRES
The way of gaining information about the study that consist of a set
of related questions, either in a survey form or printed papers that the
proponent used to come up with the problems brought by the existing
system, the questionnaires as a mean of data gathering information.
The proponent used this method in gathering ideas and information
that could help in the development of the application. This was also used
to determine if the proposed application will be suited or accessible to its
target beneficiaries. See Appendix D.

3.2.3 EVALUATION FORM


An evaluation form is a document that the supervisors use to
measure the proposed android applications performance and reliability
over the existing system. A critical appraisal or assessment; a judgment of
the value, worth, character, or effectiveness of something; measurement
of progress.
22

The purpose of the proponent in conducting system evaluation is to


determine whether outcome criteria have been met for the proposed
application might be improved. See Appendix E.

3.3

ANALYTICAL TOOLS
3.3.1 DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the flow
of data through an information system. It enables to represent the
processes of the proposed application from the viewpoint of data.
The proponent used the Data Flow Diagram to design informationprocessing of the mobile application in a detailed form but also as a way to
model of the whole system. See Appendix F.

3.3.2 FLOWCHART
A flowchart is a formalized graphic representation of a logic
sequence, work, manufacturing process, organization chart, or similar
formalized structure that proponent shows the step-by-step progression of
the proposed application through a procedure or system especially using
connecting lines and a set of conventional symbols.
The proponent used flowchart to provide users or other developers
with a common language or reference point dealing with the application
23

and its processes. It serves also as a blueprint for the proponent in all
internal logic process needed to take by the application throughout its
development. See Appendix G.

3.4

METHODS USED IN DEVELOPING THE SYSTEM


3.4.1 PLANNING PHASE
In the planning phase of the study, the proponent defined the
possible solutions in detail to the problem being studied. Answering the
questions What to create?, How to develop it?, When it will be
created?, What will be its features?, How effective it will be?, and How
it will meet the objectives of the study? were the topics in the planning
phase.
During this phase, the proponent need to plan carefully, particularly
in the early stages of the project, is required to coordinate activities and
manage the risk of their project effectively. It also includes the depth and
formality of project plans should be consistent with the characteristics and
risk of the given project.
This also covers the works to be done, back-up plans in case of
unexpected problems and researching for the necessary data needed to
build the project. These plans will be beneficial to avoid waste of time and
resources.

24

3.4.2 ANALYSIS PHASE


Analysis is the vital stage for the projects success. Every step must
be analyzed and the effects of every choice must be considered to avoid
mistakes. In the analysis phase, the proponent thoroughly analyzed the
concept of the whole project, determined all the requirements of the
proposed application, analyzed the data gathered and how to apply them
to the study. All of these are further analyzed, taking into consideration
technical requirements and more details are considered.

3.4.3 DESIGN PHASE


This

phase

shows

the

functional,

support,

and

training

requirements of a system are translated into a detailed design. The


proponent made decisions to address how the proposed application will
meet all the requirements. The technical specification and requirements
together with drawings are made in this phase. It emphasizes the features
of the application where the design will produce as a high-level guide.
The proponent used graphic designing software such as Adobe
Photoshop CS6 in creating the desired designs, such as the application
layouts, icons, and color schemes, that would be implemented in the
development of the application.

25

3.4.4 DEVELOPMENT PHASE


The development phase involves converting design specifications
into executable programs. At this state, the proponent will start to create or
develop the application from the scratch, wherein the proponent will go to
apply his plan to meet his goal to create a Cisco Pocket Study Guide for
android devices. The proponent starts coding the functionality of the
application; all the created graphics, layout, and texts were used and
included in Eclipse (an Android development software) and were
converted through XML layouts. Third parties components, such as the
SDK manager, was used so the developed application can be installed on
Android devices.

3.4.5 TESTING PHASE


In this phase, the proponent tested the proposed application for
possible errors. During this phase, the program was already finished and
the necessary adjustments were determined so that the system will
function properly. Each part was tested to see if it is functioning.

3.4.6 MAINTENANCE PHASE


This is a time in continuing or preserving something. The proposed
android application is flexible to accept changes that could happen
26

anytime. Every software will definitely undergo changes once it is


delivered and implemented to the beneficiaries, due to unexpected input
values, that could affect its operation. The proponents believed that the
system will be low-maintenance because the errors found in the system
during the testing phase were already corrected. Maintenance will
probably include modifications that will rely solely in the advancement of
technology and availability of newer information.

3.5

METHODS USED FOR PRODUCT EVALUATION


3.5.1 TECHNICAL FEASIBILITY
This method is used by the proponent to measure the application in
a way of gaining information on the availability of the hardware tools that
are needed for the development of the proposed system. However,
technical resources of the current system can be improved or add more
features that fulfill the request of the users. Adding features to the existing
system are expensive and not productive, because they must meet the
needs of the users efficiently.

3.5.2 OPERATIONAL FEASIBILITY


Suppose for a moment those technical and economic resources are
both adequate, the proponent must consider the operational feasibility of
27

the requested project. This is dependent on the human resources


available for the project and involves projecting whether the system will be
operational. These are the criteria that serve as a basis to test the
proposed application if it really works properly.
RELIABILITY refers to the ability to perform its intended functions
and operations in a systems environment without experiencing
failures.
EFFICIENCY describes the comparison of what is actually
produced or performed with what can be achieved with the same
consumption of resources which includes time, effort, or cost for the
intended purpose.
EFFECTIVENESS is the degree to which objectives are achieved
and the extent to which targeted problems are solved.
See Appendices E, N, O.

3.5.3 ECONOMIC FEASIBILITY


Economic feasibility is the analysis of a projects cost and revenue
in an effort to determine whether or not it is logical and possible to
complete. For instance, how to start the proposed study guide application
and make a plan for it. The proponent has estimated the requirements to
be needed in providing the proposed system. See Appendix I.
28