Scribd
Upload
10 views3 pages

Water Usage Billing System Analysis

Chapter Three provides a comprehensive system analysis for the Water Usage and Billing System for Kebele Residents, detailing functional and non-functional requirements, user and security specifications, and system constraints. It includes requirement modeling through context diagrams, data flow diagrams, and an entity relationship diagram. Additionally, it compares the current manual system with the proposed digital system, highlighting improvements in data storage, bill calculation, report generation, access control, data backup, and retrieval efficiency.

Uploaded by

tashegirma888
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views3 pages

Water Usage Billing System Analysis

Chapter Three provides a comprehensive system analysis for the Water Usage and Billing System for Kebele Residents, detailing functional and non-functional requirements, user and security specifications, and system constraints. It includes requirement modeling through context diagrams, data flow diagrams, and an entity relationship diagram. Additionally, it compares the current manual system with the proposed digital system, highlighting improvements in data storage, bill calculation, report generation, access control, data backup, and retrieval efficiency.

Uploaded by

tashegirma888
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Chapter Three – System Analysis

3.1 Introduction
This chapter outlines the detailed system analysis for the Water Usage and Billing System
for Kebele Residents. It includes the specification of system requirements, system modeling
using diagrams, and a comparison between the current and proposed systems.

3.2 System Requirement Specifications

Functional Requirements
- Admin can add, update, and delete resident records.
- Staff can input monthly water usage.
- The system calculates water bills automatically.
- Admin can generate and print reports.
- Users have role-based access (admin vs. staff).

Non-Functional Requirements
- System must respond within 2 seconds.
- All user data must be stored securely.
- Weekly data backup is required.
- The system interface must be simple and usable by kebele staff.

User Requirements
- Admin can manage residents, billing, and payments.
- Staff can only enter usage and view reports.
- Secure login credentials for all users.

Security Requirements
- Role-based access control (RBAC)
- Password-protected access with session timeout
- Encrypted database communication

System Constraints
- Platform: Windows 7 or above
- Database: MySQL
- Programming Language: PHP
- Offline-first, local deployment

3.3 Requirement Modeling

Context Diagram
Describes how Admin and Staff interact with the system. Shows external entities and major
data flows.
Data Flow Diagrams (DFD)
Level 0 DFD – High-level system overview.
Level 1 DFD – Details key sub-processes:
1. Manage Resident Information
2. Record Monthly Usage
3. Generate Bill
4. Record Payment
5. Generate Reports

Use Case Diagram


Actors:
- Admin
- Staff
Use Cases:
- Login
- Manage Residents
- Record Usage
- Generate Bill
- View Reports

3.4 Entity Relationship Diagram (ERD)

Entities and Attributes


- Resident (ResidentID, Name, HouseNo, Phone)
- WaterUsage (UsageID, ResidentID, Month, CubicMeters)
- Bill (BillID, UsageID, Amount, Status)
- Payment (PaymentID, BillID, AmountPaid, Date, Method)
- User (UserID, Username, Password, Role)

Relationships
- One Resident → Many WaterUsage
- One WaterUsage → One Bill
- One Bill → Many Payments
- One User → Many Transactions

3.5 Current vs Proposed System Comparison


Feature Current Manual System Proposed Digital System

Data Storage Paper-based MySQL Database

Bill Calculation Manual and error-prone Auto-calculated

Report Generation Manual using forms Digital, instant reports

Access Control None Role-based secured login


Data Backup Not available Weekly automated backups

Data Retrieval Time-consuming Instant and searchable

You might also like