Course Intended Learning Outcome (CILO)

At the end of this chapter, the student is expected to:

 Evaluate and use appropriate methodology including tools and techniques

significant to the research design of the chosen study and outline the
procedures in designing and developing it.

Introduction

Imagine life without procedures and methods. How would we able to

accomplish our goals if there will be no standard processes to do things in order? This
module will basically discuss the underlying rules and procedures when conducting a
research. Different tools and techniques will be introduced to give the developers a
wide variety of options on how to design a system, application or network. This section is
what they called, Methodology.

Methodology includes various procedures in designing IT researches. It starts from

planning, analyzing, designing, development up to Testing. It is obviously different from
other social researches and it varies depending on the kind of IT research is being
developed. System and Process models will also be discussed in this section as well as
Feasibility Analysis and other computing techniques.

1|P age
 ENGAGE
Measurement Materials Method

Absence of No clear
Not enough
Server method to use

Absence of Need to be
Less training
Network replaced

No Infra. To Not economic Less

test wise Maintainable

Absence of
Less efficient Less Reliable
Quality Tester

Low Quality Not policy

Low quality
Assurance friendly

Less updated
Poor Validation Unsecured
knowledge Problem
Statement
C lient feedback Obsolete Traditional
not addresses Materials C abling
Poor Signal and
Slow
transmission of
data
Inexperienced Materials of
Large Institution
Tehnician C onstruction

Separate Less Tech. Obsolete

Offices Support Hardware

Traditional
Too many users Poor Orientation
C able

Too many Not connected

Open Area
works system

Prone to Poor Netwrok

Lack of Training
rodents Infra.

High Risk when Unclear Job Many system to

raining Description connect

Absence of Absence of
Maintenance
Network Room Server

Environment Manpower Machine

The figure above depicts the main problem experienced by the Information and
Communication Technology Services Center (ISTSC) in Marinduque State College which
is Poor Signal and Slow Transmission of Data in all offices of the college. We could see in
the graph that in terms of Machine the main cause of the problem is the Materials for
Construction to be used in making the Network Infrastructure, in Manpower the main
cause is the Inexperienced technician, in Environment too large Institution, in Method is
the Traditional Cabling, while in Materials is the Obsolete set of materials being used like
old cables, hubs and even computer hardware and last is absence of server to
measure the real quality of the speed of connection and transmission of data.

From the above discussion, do you have any idea about the relevance of the
presented ISHIKAWA Diagram (Fishbone Diagram) in writing the Methodology?

Well it is definitely a YES! Methodology is where most of the tools that were used
in the research development are discussed. However, the diagrams are included in the
list of appendices and are just appended in the methodology.

2|P age
 EXPLORE
INSTRUCTIONS: The following are the commonly utilized tools when developing a
research. Select from the group the tools/technique you have used or will used in your
project.

Data Flow Diagram SWOT Analysis Test Cases

Gap Analysis Gantt Chart Survey
Entity Relationship Diagram WAMP Server Interview
Cost and Benefit Analysis Questionnaire Observation
Database Schema Waterfall Model HTML/Javascript
Use Case Diagram Flow Chart Sampling
Network Plan Navigation Structure Wireframe
Training Guide Storyboard Play Console
MS Visual Studio Modem Charts/Graphs

REQUIREMENT ANALYSIS

______________________ ______________________ ___________________

______________________ ______________________ __________________

FEASIBILITY ANALYSIS

______________________ ______________________ ___________________

______________________ ______________________ __________________

DEVELOPMENT AND TESTING

______________________ ______________________ ___________________

______________________ ______________________ __________________

IMPLEMENTATION PLAN

______________________ ______________________ ___________________

______________________ ______________________ __________________

3|P age
 EXPLAIN

I. THE METHODOLOGY
 The general research strategy that outlines the way in which a research project is
to be undertaken and among other things, identifies the methods to be used in
it.
 It encompasses concepts such as paradigm, theoretical model, phases and
quantitative or qualitative techniques.
 In writing the methodology, the students are expected to apply their
competencies gained in the “Application Development and Emerging
Technologies”, “Systems Analysis and Design”, etc.

II. PARTS OF THE METHODOLOGY

A. Requirement Analysis Procedure

The proponent must:

 Determine the requirements of the organization under study
 Need to know the details of the current system/process
o People involved
o Business activity
o Location
o Timing
o Current procedures
 Know and analyze why the business uses the current system

Important Pointers

 There may be good reasons why the organization is using the current methods,
and these should be considered when designing the proposed system.
 The programmer, system analyst, or software engineer, no matter how brilliant
they are cannot design the software solution to an organization unless they are
familiarized on the processes under study.

4|P age
 Methods/Technique Suggested Tools to Use
Data Gathering  Open-ended Questions
 Observation  Questionnaires
 Interview  Sloven’s Formula
 Sampling
 Survey *Please refer to the Module 2 for comprehensive explanations
Problem-Cause Analysis  Ishikawa Diagram – use to analyze problems and it
cause to design a definite solution
Project Scheduling  Work Breakdown Structure – decomposition of big
processes in to chunks (small processes)
 Gantt Chart – shows the project activities (WBS) and
schedule
Database Designing  Entity Relationship Diagram – use to show
( mostly for software relationship of all the entities involved in the project.
development and graphics
animation) It is use to logically design the system’s database
 Database Schema – the structure of the database
which is based on the Entity Relationship Diagram.
This is being illustrated to show how will the
proposed database will look like
Process Modelling  Flow Chart – shows the sequence of processes of an
organization. Usually use when there is less data to
be processed.
 Data Flow Diagram – illustrate the processes of the
organization which the main focus is to show how
the data is being processed, transformed and
stored.
 Use Case Diagram - use to illustrate how the users
interact to the system/process regardless of the
data involved
 Scripting and Storyboarding – also pertains to the
game play or how the game will be played
System Modelling  Prototyping Model
(Mostly for Software  Waterfall Model
Development and Graphics  Rapid Application Model
Animation)
 Scrum Methodology
 System Architecture to be more specific
Network Planning  Network Plan/Lay-out - illustration on how the
(for networking and data proposed network or security lay-out will look like
security)  Packet Tracer

5|P age
B. Feasibility Analysis Procedure

The proponent must:

 Collect information proving that the project is worth pursuing and feasible
 Assess the possibility of the project to be implemented
 Compute and determine the benefits that can be extracted from the project

Methods/Technique Suggested Tools to Use

Operational Feasibility  SWOT Analysis – stands for STRENGTH, WEAKNESS,
 This is done to assess OPPORTUNITY and THREAT.
the capability of the
organization to
support the project
Technical Feasibility  GAP Analysis – Comparative analysis between the
 This is done to assess existing technical resources of the developers and
the capability of the the required technical resources of the project as
developers to well as technical expertise.
create the project
Economic Feasibility  Cost and Benefit Analysis – use to compute the
 This is done to financial benefits of the project from the cost of the
determine the existing system, cost of the proposed system and
benefits or the return development cost.
of investment when
the project will be
developed
Market Feasibility  Survey Questionnaire – measures the marketability
 Performed when the of the project. This is used as replacement to the
project does not Economic Feasibility if the project has no existing
have an existing system.
system. For example,
a newly introduced
game.

C. Development and Testing Procedure

The proponent must:

 Develop the project based on the design of the created process model
 Select appropriate programming language, design necessary database and
materials to build the project
 Also refers to Coding of the program or game or execution of the network plan.
 Also includes testing and assessment of the quality of the final output.

6|P age
 for software development and graphics animation
Methods/Technique Suggested Tools to Use
Prototyping  Mockplus, Axure and other digital prototyping tool
Program Coding For web platforms:
 HTML/JavaScript/CSS - scripting and mark-up
languages often use in building the website and
defining its layout and styles
 PHP – use to manipulate data in the website
 Ajax, Python, JQuery etc.
 Laravel Framework – improves the security of the
PHP codes
 Notepad++, Sublime and other code editors
For mobile platforms:
 Java or C# Language
 Android Studio or Eclipse
For stand-alone system:
 Java or C# Language
 MS Visual Studio
User interface Designing You can use Adobe Photoshop or Illustrator to
enhance images and icon to improve the
appearance of the system or application
Database Creation  WAMP Server – Windows, Apache, MySQL and PHP.
Use to manipulate and design database of your
project.
Testing and Debugging  System Testing
o Browser Testing
o Integration Testing
o Unit testing
o Stress Testing
 Acceptance Testing
o Alpha Testing, Beta Testing
 Test Cases – sample scenario use to test the system
 ISO 9126 Evaluation Instrument
Note: Remember that the choice of tools still depends on the project and the capacity of the
developer to use it.

for networking and data security

Methods/Technique Suggested Tools to Use
Development of the  Networking tools that will be used
Proposed Network or Ex. Hub, UTP Cable, Switch, Modem, etc.
Security Infrastructure or
Application
Prototyping  Packet Tracer or any tool that can be used in
creating versions of the network layout/design.
Project Testing  Acceptance Testing
o Alpha Testing
o Beta Testing

7|P age
D. Implementation Plan

The proponent must:

 Devise a plan on how the project will be installed or implemented
 Consider the capability of the expected users
 Set schedule and place on where the dry-run of the project will be done

Methods/Technique Suggested Tools to Use

Installation of the  Web Hosting, Server, Filezilla Server, Google Play
Software or Game Console, etc.
Training/Seminar  Installation/Training schedule
 User Manual
 Flyers/Brochure
 Training Guide

ELABORATE

 Methodology pertains to the methods or

techniques to be performed in
conducting the project. You will discuss
how each activities will be performed.
 It involves various tools for each
procedure
 You must consider the type of your
project when selecting the tools to be
used
 When writing the methodology discuss
the tool using what, how and why questions.
o What tool or technique to be used?
o Why did you use that tool or technique?
o How are you going to use that tool or technique?
 Tools and analysis are place in the appendices, but discussed and appended in
 Be careful on the use of tenses, use present tense if the activities are not yet
done/performed otherwise use past tense.

8|P age
3. METHODOLOGY The Use Case (Appendix F) was drawn to show the

3.1 Requirement Analysis Procedure processes of the developed system and see how the

A series of interviews and observations was user interacts with it.

done to gather the organization's necessary The Entity-Relationship Diagram (Appendix

information and processes. The target organization is G) was used to show all the entities and their

an LGU or Local Government Unit of Boac, relationship in the system by determining all possible

Marinduque. Enable to conduct an interview, a tables that might be included in the system’s

sponsorship from the Municipality of Boac was database.

requested. A Letter of Interview (Appendix A) was The Database Schema (Appendix H) was

handed to the organization. A face-to-face interview used to represents the logical view of the entire

with the Market Supervisor using the prepared open- database. It also defines how the data is organized

ended questions (Appendix B) was performed. The into the system.

client's answers were written down and ahead of the

interview, as the developers asked for permission to 3.2 Feasibility Analysis Procedure
record the interview for future purposes. An A Feasibility Analysis was performed to
observation of the daily workflow was also determine whether the project is worthy to proceed
performed in the Boac Market Operation Office. further. A preliminary investigation was conducted at
After the interview and observation, the Boac Market Operation Office to analyze the existing
gathered data was analyzed to further understand the system. A formal letter (Appendix A) was sent to the
need of the organization. Also, unpublished thesis Municipal Hall of Boac for approval in conducting
and research related to the project were analyzed to the investigation that involves several interviews for
widen the knowledge about the developed study. secretary, chairman, treasury, and other staff of the
A Work Breakdown Structure (Appendix C) organization.
was prepared to know the project's scope based on The Operational Feasibility was used to
the order of the tasks that must be completed. It is a determine and ensure that the organization meets the
document guide for the developer to accomplish the development requirements. A series of interviews
written statement of work. with the organization's employees was conducted to
The Gantt Chart (Appendix D) was used to gain knowledge about the organization's business
identify the schedule of the project activities process. The open-ended questions (Appendix B)
developed that the development team should were asked to the employees. The interview cycles
accomplish. within the Market Supervisor, secretary, and collector
Data Flow Diagram (Appendix E) was used are the system's intended users. The data collected
to show the process of the existing system of the was analyzed to see if the operation of the
organization. It was drawn to show the interaction organization is feasible. Through SWOT Analysis
between the system and the external entities. It is a (Appendix I), the developers identified the
great tool to understand the existing process deeply. organization's strengths and weaknesses in adapting

9|P age
to the changes that the system may bring, and the the system could return the investment cost if it were
opportunities and threats that the organization may developed and implemented. In determining the
encounter when the system is implemented in the project benefit, the cost of the existing system was
organization were also indicated. The organization's subtracted from the cost of the developed system, and
available technical resources were inspected and on which year the organization will get the payback.
compared with the minimum technical specification
through Gap Analysis (Appendix J). 3.3 Development and Testing Procedure
Technical Feasibility was used to conclude The system development model used in this
if the developers have the technical resources needed project is the prototyping model. In this model, the
to develop the system. The developers assessed system was partially implemented, allowing the client
themselves if they have the capability of developing to see the product earlier. The initial prototype
the system. The SWOT analysis (Appendix I) was features only the basic functionality according to the
used to know the strengths and weaknesses of the client’s requirements. The process started in
developers. The opportunities and threats that the gathering data that was done by interviewing the
developers may face in developing the system were client, Municipal Market Supervisor, and observing
also indicated. The developers' available technical the workflow of the office. Then, the gathered data
resources were checked, which is the hardware and was analyzed, and it results in a requirements
the software needed in the development. The document. It is the basis of the initial prototype
specifications were inspected and compared to the developed by the developers and presented to the
minimum technical specifications through Gap client. It was tested and improved as per the client's
Analysis (Appendix L). feedback. The cycle continued until the user approves
Furthermore, the Economic Feasibility was the prototype and find it satisfactory. In creating the
used to know if the benefits of the project outweigh prototype design, Sublime and Photoshop were used.
the estimated cost (Appendix M). The list of the The system was developed with the help of
supplies and materials of the organization within a Use Case (Appendix F), as it was used as a guide of
year was requested. Having this information, the total the developer for the needed process and
amount of how much does the organization consumes functionality. The Entity-Relationship Diagram
in materials and supplies was calculated. The (ERD) (Appendix G) was illustrated and used to
estimated expenses of the organization for their define the relationship of the entities present in the
supplies increased by 10% every year were also process used in constructing the database schema.
calculated. The supplies and materials that the The Database Schema (Appendix H) was used in
organization still needs if the system is implemented creating the database structure. It includes the table,
were also computed. The materials lessen, as the fields, type, rules, and constraints. Then, it was
system intends to decrease the papers and other implemented using MySQL. The Sublime served as
unnecessary materials used in doing their the source code editor for coding and designing the
transactions. The addition of 10% every year was developed system. It was used as it supports
also calculated. It helped the developers identify if languages like Hypertext Markup Language (HTML),

10 | P a g e
which was used in creating the structure of the requirements needed by the organization. The
webpage of the website and the PHP Hypertext Software Quality Evaluation Based on the ISO 9126
Preprocessor (PHP) and Javascript were used in Software Product Quality Standard (Appendix O)
creating the dynamic web pages and functionality of was used by the Information Technology experts to
the developed system. The Cascading Style Sheet test and evaluate the developed system. It was used to
(CSS) and Bootstrap were used to define the measure the system quality base on the expert’s
website's style and layout. The XAMPP served as a feedback. The experts examined each function of the
server to manipulate and manage the database of the developed system and rated it based on the given
developed system. It also provided an Apache used to criteria. The result will be interpreted based on the
create a local webserver to access the developed Likert Scale Rating Basis (Appendix P ).
system.
After the development procedure, a series of 3.4 Implementation Plan
testing procedure was done. The system was After completing the development of the
examined to identify its possible issues/bugs. System system and performing a series of tests, it will be
Testing was performed. The functionality of the installed in the Boac Market Operation Office. An
system as a whole was tested to ensure that it is error- installation plan (Appendix Q) states how the system
free. Another purpose of this test is to evaluate the will be installed in the organization's system. First,
system’s compliance with the specified requirements. the developers will ensure to have the different
The testing followed the proper order of the processes technologies needed in the installation, such as the
based on its function and entered the desired inputs in hardware platform and software environment. Then,
required areas. The actual results were compared to they also need to purchase a domain name and
the expected result. The system was also tested in hosting to make the system online. The developers
different browsers to test its compatibility with all the also designed a Network Plan (Appendix R) to map
media browsers through Cross-Browser out the network structure in the organization's office
Compatibility Testing. It was run using different when the system is implemented.
browsers such as Google Chrome, Internet Explorer After the installation, the secretary and the
11, Mozilla Firefox, and Microsoft Edge. The collectors will be trained by the developers on how to
changes in the appearance and functions of the use it. The training will include an explanation about
developed system were observed and compared with the functionality of the developed system. Then, a
the expected results. Another test is User Acceptance step by step procedure on the process and functions
Testing. A User Acceptance Form (Appendix N) was of the system. The developers will use a laptop and a
given to the users as a tool to assess if the system's tablet to train the intended users. As a helpful tool,
functionalities are working, and if the users are the system will have a user manual in printed form.
satisfied with the developed system. The intended The manual is composed of functional and technical
users, secretary, and collectors tested the system by documentation of the system.
using it themselves to certify if it complies with the

11 | P a g e
 1.0
Teachers Info. Add Mobile Teacher details
Mobile Teacher D1 Teacher folder
Teacher’s
Info.

2.0
Teaching specialization
Assign
Teaching assignment subject details D2
subject to Curriculum
Teacher
Teacher’s
assignment D3 Teaching load

3.0
Learner’s Info.
Learner Filled up PIS D4 PIS
Verify illiterate students
Learner’s
FLT Results Requirements List of BLP learners D5 Learner’s List

Qualified learners
D4
List of learners (E/S)

4.0
Learner’s additional Info. Record Learner’s details
Learner’s D6 Individual Profile
Info

5.0
Schedule of classes
Disseminate Subject/teacher D3
Schedule details
Schedule of classes D7 \Bulletin Board

6.0
Module
Mobile Teacher Subject handled D3
Provide
Learning
Learning Material
Materials D8 LM Box

7.0
Learner’s output Performance Results
Assess D6
Learners

12 | P a g e
13 | P a g e
 Record
Learner’s Info.

Recommend
Module

Classify extend Recommend

Learners
L. Strategy

Record
Pre-test

Mobile Teacher
Log E-learning extend Recommend
Activities
Module

Record
Post Test

Visualize
Reports

14 | P a g e
15 | P a g e
 Operational Feasibility – SWOT Analysis

Table 1. Result of SWOT Analysis for Operational Feasibility

Strengths Weaknesses

1. The organization has two computers, one 1. Lack of ICT maintenance personnel.
photocopier and one printer in making their 2. Poor Internet connection.
transaction and preparing reports. 3. System units are slow and tend to lag.
2. The organization has a provision in the
development of the developed system.
3. The organization has an Internet connection.
4. The employees are responsive, flexible and
cooperative.
5. The employees are capable to operate a
computer system.
Opportunities Threats

1. Customer satisfaction may increase through 1. Power interruption while operating the
the SMS notification feature. system.
2. Emergence use of technological device like 2. Weak internet connection or loss of internet
tablet which is used in recording payments. connection may occur
3. Innovative information recording 3. Unexpected occurrence of malware

Operational Feasibility – Gap Analysis

Table 2.1. Gap Analysis of the Available resources of the Boac Market Operation Office
Technical Specifications needed Technical Specification of the
Action Needed
for the Proposed System Available Resources
HARDWARE
Use the available processor of
Processor: 2GHz or faster 2.80 GHz
the organization.
Use the available RAM of the
RAM: Minimum of 2 GB DDR3 2.00 GB DDR3
organization.
Hard Disk Drive Capacity: Use the available Hard Disk
500 GB
Minimum of 500 GB Drive of the organization.
SOFTWARE
Operating System: Windows 7 or Use the available OS of the
Windows 7 Ultimate
higher organization.
Google Chrome (Version
Web Browser: Google Chrome, Use the available Web Browser
55.0.2883.8), Mozilla Firefox
Microsoft Edge, Mozilla of the organization.
(Version 50.1.0)

16 | P a g e
 Technical Feasibility – SWOT Analysis

Table 2.2. Result of SWOT Analysis for Technical Feasibility

Strengths Weaknesses

1. Developers have different tools and 1. Miscommunication with the client.

technology for the development of the 2. Low communication and social skills.
developed project. 3. Leadership ability
2. Developers have enough time to complete
the developed project.
3. Developers are knowledgeable in using
different programming languages.
4. The developers possess a resourceful
characteristic.
Opportunities Threats

1. Utilize and enhance knowledge of the 1. Power shortage while developing the
devopers about the programming languages system
that will be used in developing the system 2. Development tools failure
2. Sudden changes on the requirements and 3. Bugdet shortage
other recommendations may help the 4. Weak internet connection
developers to have better analyzation and
problem solving skills.

Technical Feasibility – Gap Analysis

Table 2.3. Gap Analysis of the Available resources of the Developers

Technical Specification needed for Technical Specification of the
Action Needed
the Development Available Resources
HARDWARE
Use the available processor
Processor: 2GHz or faster 2.67GHz ~2.7 GHz
of the developers.
Use the available RAM of
RAM: Minimum of 2 GB DDR3 4.00 GB DDR3
the developers.
Hard Disk Drive Capacity: Use the available Hard Disk
500 GB
Minimum of 250 GB Drive of the developers.
SOFTWARE
Operating System: Windows 7, Use the available OS of the
Windows 10 Pro
Windows 8, Widows 10 developers.
Google Chrome (Version
Web Browser: Google Chrome, 80.0.3987.163), Microsoft Edge Use the available Web
Microsoft Edge, Mozilla (Version 44.17763.831.0), Mozilla Browser of the developers.
(Version 75.0)

17 | P a g e
Table 3. Breakdown Representative of the Total Cost of Existing System
Particulars Unit Cost Quantity Unit Total Cost
Bond Paper (short) ₱155.65 25 Reams ₱3,891.25
Bond Paper (long) 175.56 25 Reams 4,389.00
Pencil 20.79 4 Boxes 83.16
Sign Pen (black) 34.61 30 Pieces 1,038.30
Sign Pen (colored) 34.61 4 Pieces 138.44
Folder(long) 279.00 2 Boxes 558.00
Paper Clip 14.04 4 Boxes 56.16
Stapler 54.65 4 Pieces 218.60
Cartridge(black) 290.00 5 Cartridges 1,450.00
Cartridge(colored) 290.00 15 Cartridges 4,350.00
Brown Envelop(long) 507.40 2 Boxes 1,014.80
Staple Remover 23.35 4 Pieces 93.40
Staple Wire 39.52 4 Boxes 158.08
Glue 49.40 3 Jars 148.20
Clip 30.54 4 Boxes 122.16
Correction Tape 14.02 10 Pieces 140.20
Data File Box 169.00 12 Pieces 2,028.00
Fastener 83.67 4 Boxes 334.68
Signature Stamp 79.50 4 Pieces 318.00
Scissor 15.60 4 Pieces 62.40
Stamp pad ink 26.26 6 Bottles 157.56
Stamp pad 29.10 2 Pieces 58.20
White Board 212.40 1 Pieces 212.40
Marker(fluorescent) 37.23 4 Sets 148.92
Marker(permanent) 8.98 6 Pieces 53.88
Marker(whiteboard) 10.28 4 Pieces 41.12
Record Book(300pages) 70.72 4 Books 282.88
Record Book(500pages) 101.92 4 Books 407.68

Ruler 17.68 6 Pieces 106.08

Tape(masking) 106.60 6 Rolls 639.60
Tape(packaging) 18.20 8 Rolls 145.60
Tape(transparent, 24mm) 9.10 10 Rolls 91.00
Tape(transparent,48mm) 18.20 3 Rolls 54.60
Xerox machine 6,000.00 1 Piece 6,000.00
Printer 7,450.00 1 Piece 7,450.00
External Hard Drive 5,000.00 2 Pieces 10,000.00
Flash Drive ₱212.16 2 Pieces ₱424.32
Total ₱46,866.67

18 | P a g e
Table 3.1 Operational Cost of the Existing System
Description Year 1 Year 2 Year 3 Year 4 Year 5
Electrical Consumption ₱22,000.00 ₱24,200.00 ₱26,620.00 ₱29,282.00 ₱32,210.20
Bond Paper (short) 3,891.25 4,280.38 4,708.41 5,179.25 5,697.18
Bond Paper (long) 4,389.00 4,827.90 5,310.69 5,841.76 6,425.93
Pencil 83.16 91.48 100.62 110.69 121.75
Ballpen (black) 1,038.30 1,142.13 1,256.34 1,381.98 1,520.18
Ballpen (colored) 138.44 152.28 167.51 184.26 202.69
Folder(long) 558.00 613.80 675.18 742.70 816.97
Paper Clip 56.16 61.78 67.95 74.75 82.22
Stapler 218.60 240.46 264.51 290.96 320.05
Cartridge(black) 1,450.00 1,595.00 1,754.50 1,929.95 2,122.95
Cartridge(colored) 4,350.00 4,785.00 5,263.50 5,789.85 6,368.84
Brown Envelop(long) 1,014.80 1,116.28 1,227.91 1,350.70 1,485.77
Staple Remover 93.40 102.74 113.01 124.32 136.75
Staple Wire 158.08 173.89 191.28 210.40 231.44
Glue 148.20 163.02 179.32 197.25 216.98
Clip 122.16 134.38 147.81 162.59 178.85
Correction Fluid 140.20 154.22 169.64 186.61 205.27
Data File Box 2,028.00 - - - -
Fastener 334.68 368.15 404.96 445.46 490.00
Signature Stamp 318.00 349.80 384.78 423.26 465.58
Scissor 62.40 68.64 75.50 83.05 91.36
Stamp pad ink 157.56 173.32 190.65 209.71 230.68
Stamp pad 58.20 64.02 70.42 77.46 85.21
White Board 212.40 233.64 257.00 282.70 310.97
Marker(fluorescent) 148.92 163.81 180.19 198.21 218.03
Marker(permanent) 53.88 59.27 65.19 71.71 78.89
Marker(whiteboard) 41.12 45.23 49.76 54.73 60.20
Record Book(300pages) 282.88 311.17 342.28 376.51 414.16
Record Book(500pages) 407.68 448.45 493.29 542.62 596.88
Ruler 106.08 116.69 128.36 141.19 155.31
Tape(masking) 639.60 703.56 773.92 851.31 936.44
Tape(packaging) 145.60 160.16 176.18 193.79 213.17
Tape(transparent,
91.00 100.10 110.11 121.12 133.23
24mm)
Tape(transparent,48mm) 54.60 60.06 66.07 72.67 79.94
Xerox machine 6,000.00 6,600.00 7,260.00 7,986.00 8,784.60
Printer 7,450.00 - - - -
External Hard Drive 10,000.00 - - - -
Flash Drive ₱424.32 ₱466.75 ₱513.43 ₱564.77 ₱621.25
Total ₱68,866.67 ₱54,327.54 ₱59,760.29 ₱65,736.32 ₱72,309.95

19 | P a g e
Table 3.1 shows the list of supplies and materials of existing system increased 10% in a year.

Table 3.2 Breakdown Representative of Supplies and Materials of the Developed System.
Particular Unit Cost Quantity Unit Total Cost
Bond paper (short) ₱155.65 10 Reams ₱1,556.50
Bond paper (long) 175.56 10 Reams 1,755.60
Sign pen 34.61 10 Pieces 346.10
Folder (long) 279.00 0.5 Box 139.50
Paper clip 14.04 1 Box 14.04
Correction fluid 14.02 2 Pieces 28.04
Stapler 54.65 1 Piece 54.65
Cartridge (black) 290.00 2 Cartridges 580.00
Cartridge (colored) 290.00 8 Cartridges 2,320.00
Stapler 54.65 1 Piece 54.65
Brown envelop (long) 507.40 1 Box 507.40
Tablet ₱2,500.00 2 Pieces ₱5,000.00
Total ₱12,356.48
Table 3.2 shows the breakdown representation of supplies and materials procurred using the developed system.

Table 3.3 Operational Cost of the Developed System

Particular Year 1 Year 2 Year 3 Year 4 Year 5
Web Hosting ₱2,083.00 ₱2,291.30 ₱2,520.43 ₱2,772.47 ₱3,049.72
Electric Consumption 12,000.00 13,200.00 14,520.00 15,972.00 17,569.20
Bond paper (short) 1,556.50 1,712.15 1,883.37 2,071.70 2,278.87
Bond paper (long) 1,755.60 1,931.16 2,124.28 2,336.70 2,570.37
Sign pen 346.10 380.71 418.78 460.66 506.73
Folder (long) 139.50 153.45 168.80 185.67 204.24
Paper clip 14.04 15.44 16.99 18.69 20.56
Correction fluid 28.04 30.84 33.93 37.32 41.05
Stapler 54.65 60.12 66.13 72.74 80.01
Cartridge (black) 580.00 638.00 701.80 771.98 849.18
Cartridge (colored) 2,320.00 2,552.00 2,807.20 3,087.92 3,396.71
Stapler 54.65 60.12 66.13 72.74 80.01
Brown envelop
507.40 558.14 613.95 675.35 742.88
(long)
Tablet ₱5,000.00 - - - -
Total ₱26,439.48 ₱23,583.43 ₱25,941.77 ₱28,535.95 ₱31,389.54
Table 3.3 shows the expenses in the developed system. There is an assumption use in the estimation where supplies
and materials increased by 10% every year.

20 | P a g e
Table 3.4 Total Development Cost
Description Year 0
Domain Name ₱450.00
Programmer 40,000.00
Supplies 12,356.48
Internet Fee 9,000.00
Electric Consumption ₱5,000.00
Total Cost ₱66,806.48
Table 3.4 shows the total development cost of the developed system.

Table 3.5 Cost and Benefit Analysis

Year 0 Year 1 Year 2 Year 3 Year 4 Year 5
Operational
Cost of
₱68,866.67 ₱54,327.54 ₱59,760.29 ₱65,736.32 ₱72,309.95
Existing
System
Operational
Cost of
26,439.48 23,583.43 25,941.77 28,535.95 31,389.54
Developed
System
Total
Development
Cost (₱66,806.48)
Cost Project
42,427.19 30,744.11 33,818.52 37,200.37 40,920.41
Benefit
Cumulative
(₱24,379.29) 6,364.82 40,183.34 77,383.71 118,304.12
Benefit (₱66,806.48)
Break Even
0.79
Ratio
Break Even
Year 2
Year
Break Even
2.79 2 years and 9 months
Point
Table 3.5 shows the result of the cost benefit analysis. It presents that after the implementation of the developed
system, the organization will benefit within 2 years.

Break Even Year = 2

Break Even Ratio = Project Benefit – Cumulative Benefit

Projec Benefit

Break Even Ratio = ₱42,427.19– ₱24,379.29

₱ 42,427.19
= 0.79
Break Even Point = Breakeven year + Breakeven ratio
= 2 + 0.79
= 2.79 or 2 years and 9 months

21 | P a g e
 Database Schema of the Developed System
Table 1. Admin Table

Admin
Field Type Rules and Constraints
admin_id bigint(20) Primary key
Name varchar(255) not null
Email varchar(255) not null
Address varchar(255) not null
Contact varchar(255) not null
Gender varchar(255) not null
email_verified_at Timestamp not null
Password varchar(255) not null
remember_token varchar(100) not null
created_at Timestamp not null
updated_at Timestamp not null
Table 1 shows information about the admin.

Table 1.1 Advance Deposit Table

advance_deposit
Field Type Rules and Constraints
adddep_id bigint(20) Primary key
stallholder_id bigint(20) Foreign key
Amount varchar(255) not null
Date varchar(255) not null
created_at Timestamp not null
updated_at Timestamp not null

Table 1.1 shows information about the advance deposit of the stallholder.

22 | P a g e
 EVALUATE

WORKSHOP 8
WRITING THE METHODOLOGY

INSTRUCTIONS:

1. Write the Methodology of your research project including:

I. Requirement Analysis Procedure

II. Feasibility Analysis Procedure

III. Development and Testing Procedure

IV. Implementation Plan

*Note:

1. Include tools which you think best to be used in your project.

2. You are not required to use all the tools discussed in this module.

3. You can use tools that are not discussed in this module which do you think can help
you achieve all the necessary research activities for your project.

23 | P a g e