Chapter 3

Republic of the Philippines
MARINDUQUE STATE COLLEGE

P. Manguera Sr. Road, Tanza, Boac, Marinduque
SCHOOL OF TECHNOLOGY
CHAPTER III
Methodology
Requirements Analysis Procedure
In requirements analysis procedure, request letters were prepared and submitted to the
different organizations for interview to determine each major processes and different problems
currently facing regarding their information system. After the conducted interview, the gathered
data from the different organizations were analyzed and undergone the process of feasibility
analysis to identify which organization is more feasible to be a target of the project. After the
analysis, Provincial Environmental and Natural Resources (PENRO) was selected. In order to
know how the data are processed in the network monitoring system of Provincial Environmental
and Natural Resources (PENRO), the existing network monitoring system was analyzed. To
clearly understand the existing network monitoring system, Use Case has been used. Work
Breakdown Structure (WBS) (See Appendix A) is also used in this procedure used to identify all
the activities that are needed to be done from requirements determination up to implementation.
Activities are plotted using Gantt chart (See Appendix B) to identify the time and schedule
allotted for each activity.
System Analysis and Design Procedure
In this procedure, questionnaires were formulated and distributed to the target
respondents. Interviews were conducted to identify the problems encountered by the
organization, and to determine and analyze the possible solution system. Sample of important
documents and other report formats currently being used in organization were collected to
identify the relevance of each in the entire process in able to know whether it will be used or not
in the system. After identifying problems and determining the solution system, different data
models were formulated to present the flow of the determined solution system. To present the
logical aspects of the database of the proposed system, database schema was used (See Appendix
C). To identify the relationship of entity to every process, and the relationship of both entity,
Entity relationship diagram (ERD) (See Appendix D) was also used. Entity relationship diagram
(ERD) shows the conceptual aspects of the database, and to identify and organize system
requirements, use case was also used. Possible scenarios and series of interactions between users
and the proposed system were shown by the Use Case.
Feasibility Analysis Procedure
Feasibility analysis procedure was also conducted to easily determine whether the system
would be technically and operationally feasible. The operational feasibility was used to identify
whether the proposed system will be implemented and used by the organization. Series of
interviews were done with the In-charge IT Personnel of the org. Questionnaires were also
prepared and distributed. Included in it are the questions that identified the number of computers
they have in their network, the reports they make with their existing system was also ask. We are
pretty sure that they are computer literate because they are in the ICT Section. Moreover, for the
complete technical operation of the proposed system, existing IT (software and hardware)
specifications of ICT Section were collected.

In technical feasibility, in order to develop the proposed system, stable and proper
computer hardware and application software have been properly chosen. Latest and updated
computer hardware as well as application software will be utilized for the fastest and efficient
development of the system. SWOT analysis was used to assess the IT literacy of the proponents
and the capability to develop the system (See Appendix E). In SWOT analysis, strengths, and
weaknesses of the proponents were determined as well as the opportunities and threats in
developing the system.
Development and Testing Procedure
Systems Development Procedure
Prototyping will be chosen because this helps the developers acquire feedback from
users. In prototyping, users are actively involved in the development. It provides better system to
users, as users have natural tendency to change their mind in specifying requirements and this
method of developing systems supports this user tendency. Also, missing functionality can be
identified easily. C# will be used in encoding programming codes to provide a complete
environment to assist the developers in creating the software needed by the organization. This
will be also use to create an environment that can be easily understood by the users. MySQL
will also be used as the backend or the database of all the data inside the proposed system.
Furthermore, Adobe Photoshop CS6, will be used in editing images and any other objects to
embed in the proposed system. Web browser will be used for testing the system.
System Testing Procedure
After the development of the software, software testing will be done to know if the
software will function properly, and the system codes will be tested if there are still errors.
Software testing involves executing an implementation of the software with test data and
examining the outputs of the software and its operational behavior to check that is performing as
required. Testing also is dynamic technique of verification because it works with an executable
representation of the system.
To ensure that the system will properly function, unit testing will be done. Unit testing
performs error detection and debugging on the smallest unit of the software system. It involves
checking the internal of each module.
Any errors that will be found in the system will be corrected until the program has been
totally debugged. Program review will be done after the developers have removed all the errors
and performed tests on the program.
Alpha testing is carried out in this procedure to track all the bugs inside the system before
the presentation to the designated users for beta testing. Moreover, system testing will take place
for the users and developers to assure that the system meets all desired specifications and all
necessary features have been included, and beta testing for the designated users to know if the
system will satisfy them.

Implementation Plan
After the system development and testing process, implementation will be done. This
implementation plan will describe how the system will be deployed, installed and be used. First,
the researchers’ plan is to install the system on the organization site. Once installed, orientation
will be conducted in order to familiarize the users with the system functionalities and processes.
The system will require the organization to have technical resources: computer units and local
area network, which the organization already has. The IT Head of the organization will serve as
the technical support for the maintenance of the system because he has sufficient knowledge
about computers and system functions. Other application needed to be used in the system will be
installed during the implementation. A User manual will be created and be given to the
organization which will serve as guide of the admin as the system begin to be used, and for some
instance of encountering certain errors with the system. Moreover, the documentation will also
be included.
USE CASE OF EXISTING SYSTEM
PRTG Network Monitoring System
Get IP Address
Use Internet
Bandwidth
Monitoring
Uptime/Downtime User
Monitoring
Admin
Generate Report
Title: Get IP Address
Actor: Admin
Description: Describes the processes in getting the IP Addresses of the computers.
Pre-condition: The system gets IP Address.
Main Scenario:
1. The admin will get the IP addresses of the connected devices to the network.
2. The IP address will be used to monitor the activities of the connected devices to the
network.
Post condition: The network can now be monitored.
Title: Use Internet
Actor: User
Description: Describes the users’/employees’ use of internet.
Pre-condition: The users/employees use internet.
Main Scenario:
1. The employee/user will use a computer.
2. Browse internet
3. Browse applications or websites.

Post-condition: User/Employee’s internet usage and activity can now be monitored by the
Admin.
Title: Bandwidth Monitoring
Actor: Admin
Description: Describes the process in monitoring the bandwidth of the office’s internet
connection.
Pre-condition: The system monitors bandwidth of the network.
Main Scenario:
2. Browse internet
Post-condition: The system will monitor the changes in bandwidth of the network.
Title: Uptime/Downtime Monitoring
Actor: Admin
Description: Describes the process in monitoring the Uptime and Downtime of devices in the
network.
Pre-condition: The system monitors uptime and downtime of devices in the network.
Main Scenario:
1. Users/Employees will use computers.
3. The system will automatically detect the active devices in the network.
Post-condition: The system can now monitor when a computer became operational.
Title: Generate Reports
Actor: Admin
Description: Describes the process in generating reports.
Pre-condition: Admin generate reports.
Main Scenario:
1. The admin will go to the report features of the system.
2. The system will automatically display the needed information
3. The admin will print the report.
Post-condition: The admin can now pass the report to the main office.
USE CASE OF PROPOSED SYSTEM
Get IP Address
Use Internet
Bandwidth
Monitoring
User’s Activity
Monitoring
Anomaly
Admin Detection User
Uptime/Downtime
Monitoring
Set rules and

Manipulate PCs
Generate Reports
Maintenance
Title: Get IP Address
Actor: Admin
Description: Describes the processes used in getting the IP Addresses of the computers.
Pre-condition: The system gets IP Address.
Main Scenario:
1. The system will be installed
2. The system will get the IP addresses of the connected devices to the network.
3. The IP address will be used to monitor and manipulate the activities of the connected
devices to the network.
Post condition: The network can now be monitored and manipulated.
Title: Use Internet
Actor: User
Description: Describes the users’ internet usage.
Pre-condition: The user/employee use internet.
Main Scenario:
2. Browse internet
Post-condition: User/Employee’s internet usage and activity can now be monitored by the
system.
Title: Bandwidth & Bandwidth Monitoring
Actor: System
Description: Describes the process in monitoring the bandwidth and internet usage of the office’s
internet connection.
Pre-condition: The system monitors bandwidth and internet usage of the devices in the network.
Main Scenario:
2. Use internet
Post-condition: The system will monitor the changes in bandwidth and internet usage of the
connected devices in the network.

Title: User’s Activity Monitoring
Actors: Admin and User
Description: Describes the process of monitoring the activities of users/employees.
Pre-condition: The admin monitors the activities of the users.
Main Scenario:
1. The users/employees will log-in to the system.
2. The system will have access to the device once they log-in
3. System will show the activities/data usage of each computer.
Post-condition: The admin can now monitor the activities of the connected devices to the
network.
Title: Anomaly Detection
Actor: Admin
Description: Describes the process of anomaly detections of the network.
Pre-condition: The system detects anomalies in the network.
Main Scenario:
1. The system gathers all the connected devices to the network.

2. The system will detect errors in the network.
3. The system will automatically notify the admin about the error.
Post-condition: The admin can now easily know and troubleshoot the problems in the network.
Title: Uptime/Downtime Monitoring
Actor: Admin
Description: Describes the process in monitoring the Uptime and Downtime of devices in the
network.
Pre-condition: The system monitors uptime and downtime of devices in the network.
Main Scenario:
1. Users/Employees will use computers.
3. The system will automatically detect the active devices in the network.
Post-condition: The system can now monitor when a computer became operational/not
operational.
Title: Set Rules and Manipulate
Actor: Admin
Description: Describes the process of setting rules and manipulating the connected devices to the
network.
Pre-condition: The administrator sets rules and manipulates devices.
Main Scenario:
1. The admin will log-in in the system as Administrator.
2. Monitor the activities/changes of the devices connected to the network.
3. He will set rules like setting maximum data usage and block sites
Post-condition: The admin has now overall control with the network.
Title: Generate Reports
Actor: Admin
Description: Describes the process in generating reports.
Pre-condition: Admin generate reports.
Main Scenario:
1. The admin will go to the report features of the system.
2. The system will automatically display the needed information
3. The admin will print the report.
Post-condition: The admin will submit the report to the main office.
Title: Maintenance
Actor: Admin
Description: Describes the maintenance of the system.
Pre-condition: The admin maintenances the system.
Main Scenario:
1. The admin will be oriented of the functionalities of the system during installation.
2. Use “help” feature or refer to the manual if he has questions about the system.
3. Contact the developers if there are crashes and anomalies encountered.
Post-condition: The system will be fixed by the developers if problems occurred.

Chapter 3

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 3

Uploaded by

Copyright:

Available Formats

Republic of the Philippines

MARINDUQUE STATE COLLEGE

Requirements Analysis Procedure

allotted for each activity.

System Analysis and Design Procedure

In this procedure, questionnaires were formulated and distributed to the target

respondents. Interviews were conducted to identify the problems encountered by the

and the proposed system were shown by the Use Case.

Feasibility Analysis Procedure

specifications of ICT Section were collected.

developing the system.

Development and Testing Procedure

Systems Development Procedure

identified easily. C# will be used in encoding programming codes to provide a complete

System Testing Procedure

representation of the system.

checking the internal of each module.

and performed tests on the program.

system will satisfy them.

USE CASE OF EXISTING SYSTEM

PRTG Network Monitoring System

Title: Get IP Address

Description: Describes the processes in getting the IP Addresses of the computers.

Pre-condition: The system gets IP Address.

Post condition: The network can now be monitored.

Title: Use Internet

Description: Describes the users’/employees’ use of internet.

Pre-condition: The users/employees use internet.

1. The employee/user will use a computer.

3. Browse applications or websites.

Title: Bandwidth Monitoring

Pre-condition: The system monitors bandwidth of the network.

1. The employee/user will use a computer.

3. Browse applications or websites.

Title: Uptime/Downtime Monitoring

1. Users/Employees will use computers.

2. Browse applications or websites.

Title: Generate Reports

Description: Describes the process in generating reports.

Pre-condition: Admin generate reports.

1. The admin will go to the report features of the system.

2. The system will automatically display the needed information

3. The admin will print the report.

USE CASE OF PROPOSED SYSTEM

Set rules and

Title: Get IP Address

Pre-condition: The system gets IP Address.

1. The system will be installed

devices to the network.

Post condition: The network can now be monitored and manipulated.

Title: Use Internet

Description: Describes the users’ internet usage.

Pre-condition: The user/employee use internet.

1. The employee/user will use a computer.

3. Browse applications or websites.

Title: Bandwidth & Bandwidth Monitoring

1. The employee/user will use a computer.

3. Browse applications or websites.

connected devices in the network.

Title: User’s Activity Monitoring

Actors: Admin and User

Description: Describes the process of monitoring the activities of users/employees.