Sunteți pe pagina 1din 9

CHAPTER IV

SOFTWARE PRODUCT DEVELOPMENT

Requirements Specification
Technical Feasibility
In the development of this system, the proponents defined a set of
hardware and software requirements that should be met accordingly. They
conducted a pre-assessment survey to the QMPD staff and gave a checklist
to Dr. Zandra Maningas to determine whether the QMPD has these
requirements available. She then made a phone call to Mr. Andrei V. Infante,
an IT Technical Officer of the Colegio and according to him, these hardware
and software prerequisites are accessible already.
The QMPDs Local Area network Connection is already in place which
will support the proposed system since it will rely on this type of connection
once the study reaches its testing and implementation phase. Table 1 shows
the hardware requirements that is needed in order to develop the system. As
depicted in the table, these requirements are already available for use.
Table 1. Hardware Requirements Checklist
Hardware Requirements

Existing

Computer Unit
Processor 1.5 gigahertz or higher

RAM 1 Gigabyte or higher

At least 10 gigabytes Hard Disk Free


Space
Network Interface Card

Table 2 on the other hand, shows the software requirements that is


needed to create the system. These requirements are also available
according to the QMPD.

Table 2. Software Requirements Checklist


Software Requirements

Propriet
ary

Existing

Mozilla Firefox or Google Chrome Web


browser

No

XAMPP Application Version 5.6.12 (32-bit)

No

Adobe PDF Reader

No

Notepad++

No

Operational Feasibility
The department of Makiling Center for Mountain Ecosystems helped
with the gathering of water level data. In gathering the water level data, a
device called Water Level Monitoring Station was used. For the maintenance
of the said device, it was done by the research team of the department. With
the proposed system, the director of the department was willing to support
it. He helped the researchers in providing the sample water level data, the
device, and creation of the map. Upon system completion, the client checked
it first prior full implementation for everyone to see.

Processing Requirements
Data and Processing Modeling
Figure 7 shows the context diagram for an early warning system. At the
center of the diagram is a single-named circle representing the system of
interest entitled Flash Flood Early Warning System for Makiling Center For

Mountain Ecosystems. The surrounding rectangles are the external entities


that the system interacts with. These are called terminators and can be
physical objects such as users and devices. The labelled arrows are the flows
which capture the interactions between the system and its terminators.

Figure 7. Context diagram


Figure 8 shows the data flow diagram. There are three external entities
in the diagram, one of which somehow enables an input for the database.
There are two data storage for the process: water level table and the
analysis table. The most important process of the system is matching the
water level data. After it has been interpreted for danger level, it will be
passed to the analysis table. If the matched data is in the yellow or red level,
it will then process the sending of SMS notification to the barangay officials
of the area. But if its only in green level, it will only send a notification to the
department director.

Figure 8. Data flow diagram


Data Design
Entity Relationship Diagram
Figure 20 shows the Entity Relationship Diagram of the proposed Client
Satisfaction System. The entities or tables which will be used in the system
together with its corresponding attributes are also shown. In addition, the
relationship of the entities to one another is also illustrated.

Figure 20. Entity Relationship Diagram

Data Dictionary
Table 5 shows the respondent table, which will be named as
tblrespondents, to be used in the system.

This table will serve as the

respondent data that will be obtained from the database server, where the
system sends the data to. The tblrespondents will consist of nine fields, with
client_ID as its primary key.
Table 5. Respondent Table
TABLE NAME
DESCRIPTION
FIELD NAME
client_ID

tblrespondents
Container for CSS Questions and Comments
TYPE
REMARKS
Int (10)
Client ID, Auto Generated,
Primary Key

client _Name
client _Type

Varchar (20)
Varchar (30)

Respondents name
Respondent Type(parent,
student,
staff,
alumni,
other) Required

Date

timestamp

Current date a survey is


answered

client _Cont

varchar(15)

Email

varchar

Clients
contact
number(landline or mobile
number)
Clients Email

Table 6 is the department being rated for CSS, named tbldepcss. The
primary key for this table is Department_ID. This table contains the
Department/service provider and type of service to be rated.
Table 6. tbldepcss Table
TABLE NAME
DESCRIPTION
FIELD NAME
Department_ID
client_Dept
dep_Serv_Prov
dep_serv_type

tbldepcss
Data represented by graphs and chart
TYPE
REMARKS
Int (10)
Primary Key
varchar (30)
Client
Department(In
which
department is
being rated), Not null
varchar (30)
Service Provider
varchar (10)
Type of Service

Table 7 is the account table for the administrator, named tbllogin. The
primary key for this table is named qmpd_ID. This table allows the
administrator to manage account from the database table.
Table 7. tbllogin Table
TABLE NAME
DESCRIPTION
FIELD NAME
qmpd_ID
qmpd_level
qmpd_uname

tbllogin
Data represented by graphs and chart
TYPE
REMARKS
Int (10)
Account ID, Primary Key
Int (1)
Foreign Key
varchar (25)
Admin/QMPD
Officer

qmpd_pword

varchar (25)

Username
Admin/QMPD Officer

Table 8 is the graph table, named tblanl. The primary key for this table
is Graph_ID. This table allows the administrator/officer to view the data
entered by CSS respondents.
Table 8. tblanl Table.
TABLE NAME
DESCRIPTION
FIELD NAME
Graph_ID
anl_graph2

tblanl
Data represented by graphs and chart
TYPE
REMARKS
Int (10)
Primary Key
Int(1000)
CSS
Result

per

anl_graph3
anl_mean
qmpd_ID

Int(1000)
Int(1000)
Int(1000)

Department
Respondent Count
Letran Ave. CSS result
Foreign key

Table 9 is the Survey Question table, named tblCSS. The primary key
for this table is Css_ID. This table allows the administrator to update the
existing survey questions from the database table.

Table 9. tblCSS Table


TABLE NAME
DESCRIPTION
FIELD NAME
css_ID
client_ID
Department_ID
css _Q1
css_qrate1
css _Q2
css_qrate2
css _Q3
css_qrate3
css _Q4
css_qrate4
css _Q5
css_qrate5
css _Q6
css_qrate6
css _Q7

tblCSS
Container for CSS Questions, CSS rating and
Comments
TYPE
Int (10)
Int (10)
Int (10)
varchar (255)
Int (1)
varchar (255)
Int (1)
varchar (255)
Int (1)
varchar (255)
Int (1)
varchar (255)
Int (1)
varchar (255)
Int (1)
varchar (255)

REMARKS
Primary Key
Foreign Key
Foreign Key
Question #1
Rating for Q#1
Question #2
Rating for Q#2
Question #3
Rating for Q#3
Question #4
Rating for Q#4
Question #5
Rating for Q#5
Question #6
Rating for Q#6
Question #7

css_qrate7
css _Q8
css_qrate8
Css_comm

Int (1)
varchar (255)
Int (1)
varchar (255)

Rating for Q#7


Question #8
Rating for Q#8
Comment/s