Professional Documents
Culture Documents
System Analysis and Design
System Analysis and Design
System Analysis and Design
By:
Basco, Bryan Zeos B.
Edres, Daniel Q..
Orate, Diana Marie S.
November 2020
Km. 54 National Highway, Makiling, Calamba, Laguna
I. Process Models
a. SDLC
c. Gant Chart
f. Multiple Constraints
g. Content Diagram
k. System Workflow
Km. 54 National Highway, Makiling, Calamba, Laguna
In this part, the researchers will discuss the set of procedures in system
Shown in the figure above is the method used by the researchers in developing
the system. The Waterfall Model is said to be the first model established and applied in
to its continuous and finite processes – one phase is required to be accomplished first
before starting another phase, therefore making the overlapping of phases inapplicable.
Waterfall model comprises the following stages: a) requirement gathering and analysis
– one that was already done by the developers in order to determine the expected
Km. 54 National Highway, Makiling, Calamba, Laguna
the “requirement specifications” are analyzed and where the system design is
constructed; c) implementation – this phase initially develops the system into small units
which will then be integrated on the next phase; d) integration and testing – integrates
the small units that are previously developed to a system after they are tested, includes
functional and non-functional testing; e) deployment – stage where the developers will
finally exhibit the system to the clients; and f) maintenance – releases patches and
updates versions in order to fix the issues raised on the client environment and also to
This project intended to use the Waterfall model based on the data gathering
done from interviewing the plausible clients. The clients requested to create a system
that the developers deemed would be used long-term and therefore require careful
planning and specific actions which the approaches in the Waterfall model can definitely
provide.
Km. 54 National Highway, Makiling, Calamba, Laguna
Requirement
System Design Development Testing Deployment Maintenance
Analysis
build system
Formuate title Initial execution login system system approval fix bug or issues
design
test payment
search technical water meter
make database with SMS backup data
background owner feedback
notification
develop project
print transactions
scope
modify water
pre-interview
owner meter info
In the figure shown above is the work breakdown structure of the system. It is
based on the SDLC used in the project. The SDLC used was Waterfall Model. The
Waterfall Model has 7 processes which includes Requirement Analysis, System Design,
Development, Testing, Deployment and Maintenance. Each process has its own sub-
processes. In order to achieve this structure, the researchers made sure that all
progress of the system project. The Gantt Chart is made in Microsoft Excel. There were
indicators so that the chart would be understand clearly. It includes the designated
tasks, the researchers assigned to, the progress bar of a specific task and the starting
and ending date of a task. The chart shows that requirements were not changing and
Village. The process starts by reading the water meter of each resident in order to
compute the amount to be shown in their water bill. After the reading, the homeowners
record the data on a log book with the resident’s name, month of the year, and the bill.
After recording the data, they will then distribute the printed water bill to the residents.
Km. 54 National Highway, Makiling, Calamba, Laguna
and MS Excel then repeat the process. Otherwise, they wait for the residents to pay.
water meter owner will receive a notification for its payment due date. He or she will pay
directly to the cashier. The cashier will record the payment in the system. The system
Km. 54 National Highway, Makiling, Calamba, Laguna
Multiple Constraints
Time Stakeholder
The allotted time for this As the target clients are not
project might be strained expertise of technological
under circumstance that the handling like this system,
developers have to work on their requirements might
other projects change over time.
Content Diagram
Km. 54 National Highway, Makiling, Calamba, Laguna
In the figure shown above is the content diagram of the project. The content
diagram consists of three entities such as the water meter owner, the admin and the
cashier. There are many data flowing through the system and entities.
In the figure shown above is the data flow diagram of the project. The data flow
diagram level 0 is the upgraded version of the content diagram. It is much specific and
clear on where is the data flowing and how the data is being used by the entities
Notification. The Admin and the Cashier have access into the system and can manage
transactions and modify water meter owner’s information. It means they can add, edit or
delete information while the cashier have limited access in the system, he or she cannot
add a user to the system. Both the admin and cashier have access in sending digital
receipt and payment notification thru SMS. And the water meter owner is the one
receiving the digital receipt and payment notification via SMS. They can view their
current and previous readings, actual water consumption, balances and monthly dues.
In the figure shown above is the entity relationship diagram of the project. It is
use for database design. There are three tables such as the bill, owners and user used
in the database with important columns (data needed) in the system. The bill consists all
of the transactions and reports made in the system. The owners represent the water
meter owners’ information. Lastly, the user(s) represent the authorized access control of
the system.
System Workflow
Km. 54 National Highway, Makiling, Calamba, Laguna
only. The system will ask username and password. After logging in successfully, the
admin can see the list of transaction options such as viewing of specific bill, paying bill,
managing transactions and customer information. If the admin or cashier wants to print
Km. 54 National Highway, Makiling, Calamba, Laguna
admin can add, edit, or delete customer information but not for the cashier.