Patuakhali Science and Technology University (PSTU)

Faculty of Computer Science and Engineering (CSE)

A Project Report On
Online Exam System

Project Type: Web Application

Course Code: CSE-420

Submitted by:
Suvronil Dey Niloy
1602071

Supervised By:

Assistant Prof. Md. Mahbubur Rahman

Department Of CSIT, PSTU

PROJECT SUBMITTED IN THE PARTIAL OF THE DEGREE OF BACHELOR OF SCIENCE IN

COMPUTER SCIENCE AND ENGINEERING
4th September, 2023.
 DECLARATION OF ORIGINAL WORK

We hereby declare that the project entitled “PSTU Electricity Billing System Web Application”,
submitted to the Faculty of Computer Science and Engineering, Patuakhali Science and Technology
University, for the fulfillment of the requirements for the Degree of Bachelor of Science in
Computer Science and Engineering, is our original work. We have not plagiarized or submitted the
same project for the award of any other degree.

.……………………………………
[Anik Saha, 1702062]

……………………………………..
[Mahedi hasan, 1702044]

LETTER OF APPROVAL

2|Page
This is to certify that the project titled "PSTU Electricity Billing System Web Application"
submitted by Anik Saha (ID No: 1702062) and Mahedi Hasan (ID No: 1702044) under the faculty of
computer science and engineering of Patuakhali Science and Technology University has been
accepted as satisfactory for the partial fulfillment of the requirements for the Degree of Bachelor in
Computer Science & Engineering.

Approval of the Supervisor

Dr. Md. Samsuzzaman

Professor
Department of Computer and Communication Engineering
Faculty of Computer Science and Engineering
Patuakhali Science and Technology University

Board of Examinee

3|Page
Signature : _______________________
Chairman of the ECC & Supervisor: Dr. Md. Samsuzzaman
Professor, Department of Computer and Communication Engineering

Signature : _______________________
Name of Internal Member : Golam Md. Muradul Bashir
Professor, Department of Computer and Communication Engineering

Signature : _______________________
Name of Internal Member : Sarna Majumder
Associate Professor, Department of Computer and Communication Engineering

Signature : _______________________
Name of Internal Member : Arpita Halder
Assistant Professor, Department of Computer and Communication Engineering

Signature : _______________________
Name of External Member : Chinmay Bepery
Professor, Department of Computer Science and Information Technology

4|Page
 ACKNOWLEDGEMENT

I extend my heartfelt gratitude to Prof. Dr. Md. Samsuzzaman, my esteemed supervisor, for his
invaluable guidance, unwavering support, and profound insights throughout the course of this
project. His exceptional expertise, patient mentorship, and constructive feedback have been
instrumental in shaping the trajectory of this endeavor. I am deeply appreciative of his dedication to
nurturing academic growth and his unwavering commitment to fostering an environment of
intellectual exploration. Prof. Dr. Md. Samsuzzaman's mentorship has been a beacon of inspiration,
guiding me through challenges and milestones, and his contributions have significantly enriched the
quality of this project.Finally, I would like to convey my gratitude to all the educators of the CSE
Faculty who have helped me along the way. I am truly grateful to have had you all as my guides.
May Allah bless and protect you all.

With Best Regards,

Anik Saha
Mahedi Hasan

5|Page
This Project is dedicated to our beloved Parents

6|Page
 ABSTRACT

This project presents a web application developed using the Flutter framework for the frontend and
PHP for the backend, aimed at revolutionizing the electricity billing system within Patuakhali
Science and Technology University (PSTU). The proposed web application provides a
comprehensive solution to the entire administrative section of electricity billing. Administrators are
empowered with tools to efficiently manage user accounts, houses, and bill calculations. The system
enables administrators to effortlessly add users, assign them to specific houses using unique meter
numbers and addresses, and establish associations between users and houses.The application
facilitates a dynamic bill calculation process that adapts to varying electricity consumption patterns.
Administrators have the flexibility to adjust the electricity bill rate for all units, ensuring accurate
billing according to current tariff regulations. The heart of the bill generation process lies in the
integration of real-time meter readings for the current month. By incorporating the latest meter
reading and retrieving historical data such as the previous month's meter reading, house details, and
user information from the database, the system generates precise and transparent electricity
bills.Furthermore, the web application streamlines communication through automated email
notifications. Administrators can effortlessly send billing notifications to all users, providing them
with detailed information about their consumption, charges, and payment due dates. This feature
enhances user awareness and transparency, reducing ambiguity in the billing process.The presented
web based intra-university electricity billing system represents a significant advancement in
administrative efficiency and user satisfaction at Patuakhali Science and Technology University
(PSTU). Through the fusion of Flutter and PHP, the project underscores the potential of seamless
cross-platform development and efficient backend data management. This innovation in the
educational context showcases the tangible benefits of embracing technology to enhance core
operational processes.

7|Page
 Table of Contents

DECLARATION…………………………………………………………………………………………………………….2
LETTER OF APPROVAL.....................................................................................................................................................3
BOARD OF EXAMINEE......................................................................................................................................................4
ACKNOWLEDGEMENT......................................................................................................................................................5
DEDICATION........................................................................................................................................................................6
ABSTRACT...........................................................................................................................................................................7
CHAPTER-1.........................................................................................................................................................................11
1. INTRODUCTION.......................................................................................................................................................11
1.1 Introduction.........................................................................................................................................................11
1.2 Motivation...........................................................................................................................................................12
1.3 Existing System...................................................................................................................................................12
1.4 Updated system Feature......................................................................................................................................13
1.5 Objectives............................................................................................................................................................14
1.6 Organization of Project Reports………………………………………………………………………………..14
1.7 Summary……………………………………………………………………………………….………………14
2. LITERATURE REVIEW OF PROJECT....................................................................................................................15
2.1 Introduction.........................................................................................................................................................15
2.2 Existing System:.................................................................................................................................................15
2.3 Problems with Existing System…………………………………………………………………………………15
2.4 Comparisons with our System............................................................................................................................16
2.5 Summary.............................................................................................................................................................16
CHAPTER-3.........................................................................................................................................................................17
3. METHODOLOGY......................................................................................................................................................17
3.1 Introduction of Methodology..............................................................................................................................17
3.2 Facts finding techniques:....................................................................................................................................17
3.3 Software Development Life Cycle (SDLC):.......................................................................................................17
3.3.1 Software process model:............................................................................................................................18
3.3.2 Feasibility Study.........................................................................................................................................18
3.4 Summary.............................................................................................................................................................19
4. DATABASE DESIGN.................................................................................................................................................20
4.1 Database Design..................................................................................................................................................20
4.2 Entity Relationship .............................................................................................................................................20
4.2.1 PSTU ER-Diagram ...................................................................................................................................20
4.3 Symbols And Meaning Of ER :..........................................................................................................................21
4.3.1 ER Diagram......................................................................................................................................................22
4.4 Summary.............................................................................................................................................................23

CHAPTER-5 ………………………………………………………………………………………………………………24
8|Page
5. SOFTWARE DESIGN……………………………………………………………………………………………… 24
5.1 Introduction……………………………………………………………………………………………………. 24
5.2 Overall design…………………………………………………………………………………………………. 24
5.2.1 Activity diagram………………………………………………………………………………………… 24
5.3 Application Interfaces and Its Features……………………………………………………………………… 26
5.3.1 Bill Insert Tab…………………………………………………………………………………………… 26
5.3.2 Monthly record generation……………………………………………………………………………… 27
5.3.3 House view Tab………………………………………………………………...…………………………27
5.3.4 Unit Rate Tab………………………………………………………………..…………………….……...28
5.3.5 User Tab ………………………………………………………………..….……………………………..29
5.4 Work Plan and Timeline:............................................................................................................................................30
5.5 Implementation……………………………………………………………………………………………………. 31
5.6 Summary……………………………………………………………………………………………………… 31
6. TESTING & SECURITY………………………………………………………………………………………….. 32
6.1 Introduction………………………………………………………………………………………………….. 32
6.2 Testing Strategies …………………………………………………………………………………………….. 32
6.3 XP Practices:...................................................................................................................................................... 34
6.3.1 XP Testing……………………………………………………………………………………………………..34
6.4 Summary……………………………………………………………………………………………………… 35
CHAPTER-7……………………………………………………………………………………………………………… 36
7 CONCLUSION……………………………………………………………………………………………………… 36
7.1 Introduction…………………………………………………………………………………………………… 36
7.2 Project Outcomes:…………………………………………………………………………………………….. 36
7.3 Future Works………………………………………………………………………………………………….. 36
7.4 Summary………………………………………………………………………………………………………. 37
7.5 References…………………………………………………………………………………………………….. 38

9|Page
 LIST OF TABLES
TABLE 5.4.1 WORK PLAN AND TIMELINE…………………………………………………………………30
TABLE 5.4.2 WORK PLAN AND TIMELINE………………………………………………………………….31

LIST OF FIGURES
Figure 4.3.1: Symbols And Meaning of ERD…………………………………………………………………………… 21

Figure 4.3.2: ER Diagram ……………………………………………………………………………………………….. 22

Figure 5.2.1: Activity Diagram …………………………………………………………………………………………. 25

Figure 5.3.1: Bill Insert Tab……………………………………………………………………………………………… 26

Figure 5.3.2: Monthly Record Generation………………………………………………………………………………. 27

Figure 5.3.3: House Tab………………………………………………………………………………………………….. 28

Figure 5.3.4: Unit Rate Tab………………………………………………………………………………………………. 29

Figure 5.3.5: User Tab……………………………………………………………………………………………………. 29

10 | P a g e
 CHAPTER-1

1 INTRODUCTION

1.1 Introduction:

In an era marked by technological innovation, the seamless integration of advanced systems within
institutional processes is imperative to ensure efficiency and accuracy. This report introduces a
transformative project undertaken to modernize the electricity billing system at Patuakhali Science
and Technology University (PSTU) from conventional handwritten records and Microsoft Excel-
based methods to an intuitive and dynamic web-based solution. The transition from manual practices
to a comprehensive web application, developed using the Flutter framework for the frontend and
PHP for the backend, signifies a significant leap forward in enhancing administrative operations.

The erstwhile electricity billing system, reliant on manual entries and spreadsheet calculations, posed
inherent challenges in terms of data accuracy, timeliness, and resource utilization. Recognizing the
need for a streamlined and error-free approach, this project was conceived with the aim of not only
overcoming existing limitations but also revolutionizing the way electricity consumption records are
managed within the university.

The significance of this project lies not only in its technical prowess but also in its potential to
redefine the efficiency and transparency of PSTU's administrative operations. With an intuitive user
interface, streamlined processes, and enhanced data accuracy, the web-based electricity billing
system is poised to alleviate the challenges associated with manual data management and offer a
superior experience to both administrators and end-users.

This report chronicles the journey from the conceptualization of the project to its development and
implementation. It outlines the technical architecture, design considerations, and features of the web
application, showcasing how the fusion of Flutter and PHP has contributed to the creation of a
powerful and user-centric solution [1]. The impact of this transformation on PSTU's operational
efficiency and user satisfaction is explored, underscoring the significance of embracing technology
to enhance core administrative processes.

1.2 Motivation:
11 | P a g e
In the pursuit of operational excellence, the motivation to transition from manual processes to a web-
based electricity billing system at Patuakhali Science and Technology University (PSTU) is
grounded in several key factors:

❑ Enhanced Precision and Speed: Manual record-keeping and spreadsheet calculations

are prone to errors and time-consuming. The project is driven by the desire to
eliminate errors and expedite processes by implementing an automated web-based
solution.

❑ Transparent User Experience: Traditional methods lack transparency and user-

centricity. The project aims to empower both administrators and end-users with
accurate, real-time billing data, fostering trust and satisfaction.

❑ Adaptability to Change: The evolving nature of administrative demands requires

agility. The project's motivation lies in providing an adaptable platform with features
like real-time meter readings and adjustable billing rates.

❑ Showcasing Technological Potential: By utilizing the Flutter framework and PHP, the

project demonstrates the potential of modern technology to streamline operations and

facilitate seamless data management.

In essence, the motivation behind this initiative is to leverage technology's transformative potential
to enhance efficiency, accuracy, and user experience, setting the stage for a more streamlined and
effective administrative environment at PSTU.

1.3 Existing System:

The existing electricity billing system at Patuakhali Science and Technology University (PSTU)
relied heavily on manual methods, primarily using Microsoft Word documents for record-keeping.
Billing information was communicated through handwritten receipts, a process that introduced a
range of challenges. In this system, the inherent risks of human error were prevalent, leading to
inaccuracies in calculations and data entry. Additionally, the manual nature of the process often
resulted in delays and inefficiencies, making it difficult to provide timely and accurate billing
information to users. Many users experienced difficulties in retrieving and retaining their billing
12 | P a g e
details, as the reliance on handwritten records and physical receipts made tracking and record-
keeping cumbersome. This system's limitations underscored the need for a more streamlined,
accurate, and user-friendly approach to electricity billing, prompting the pursuit of a web-based
solution that addresses these shortcomings effectively.

1.4 Updated system Features:

The updated system represents a significant leap forward from the traditional manual methods
previously employed at Patuakhali Science and Technology University (PSTU). It is a modern,
digitized intra-university electricity billing system designed to streamline administrative processes,
enhance user experiences, and improve overall efficiency. Key features of the updated system
include:

❑ Automation: The system automates billing calculations, reducing errors and saving

administrative time.

❑ User-Friendly Interfaces: It offers intuitive interfaces for both administrators and

users, enhancing accessibility and transparency.

❑ Real-Time Data Processing: Users benefit from real-time updates and accurate billing

information.

❑ Customizable Rate Structures: Administrators can adapt rates and charges to evolving

pricing policies.

❑ Electronic Billing: Billing notifications are electronically generated and sent to users,

eliminating the need for physical receipts.

❑ Secure Data Management: The system prioritizes data security, safeguarding sensitive

user information.

❑ Scalability: It can efficiently handle a growing number of users and data as the

university expands.

13 | P a g e
1.5 Objectives:
The main objectives to replace the existing system:
❑ To evaluate the current state of the existing system and identify areas that require
improvement.
❑ To propose an improved web-based electricity billing system ensuring future growth.

❑ To develop a web based electricity billing web app that automates calculations,
enhances user experience, and modernizes billing administration.
❑ To implement a web-based electricity billing system that significantly enhances the
efficiency and accuracy of billing processes.

1.6 Organization of Project Report:

Chapter 2 Shows the literature review of the project.

Chapter 3 Shows the Methodology of the Project.

Chapter 4 The design of the database described.

Chapter 5 Software Design Process Described.

Chapter 6 This chapter introduces the Conclusion and prospective future scopes.

1.7 Summary:
In response to the limitations of a manual electricity billing system at Patuakhali Science and
Technology University (PSTU), this project presents a transformative web-based solution.
Leveraging the capabilities of Flutter and PHP, the project offers a comprehensive approach to
managing electricity billing processes efficiently and accurately. The updated system replaces
handwritten records and Excel-based calculations with a dynamic web application that automates
house management, real-time bill calculations, billing rate adjustments, and user communication.
This innovation enhances administrative efficiency by eliminating errors, reducing delays, and
increasing transparency. Users benefit from a streamlined and personalized experience, receiving
accurate billing notifications and accessing their detailed records effortlessly. Overall, this project
contributes to advancing PSTU's administrative practices by embracing technology's potential to
revolutionize core processes and elevate user satisfaction.

14 | P a g e
CHAPTER-2

2 LITERATURE REVIEW OF PROJECT

2.1 Introduction:

The literature review serves as a foundational pillar in the journey of scholarly exploration, offering
a comprehensive overview of existing research, theories, and insights relevant to the subject at hand.
This critical examination of published works provides a contextual framework that informs and
refines the scope and direction of the present study. By delving into the collective knowledge
amassed by researchers, academics, and experts, the literature review not only identifies gaps and
trends but also establishes the project's academic significance. This introduction encapsulates the
essential role of the literature review in shaping the project's foundation, aligning it with current
discourse, and contributing to a deeper understanding of the subject matter.This literature review will
examine existing systems that share similarities with our project.

2.2 Existing System:

The existing system at Patuakhali Science and Technology University (PSTU) relies on manual and
paper-based methods for electricity billing, meter readings, and user communication. This traditional
approach involves handwritten records and physical receipts, which can be time-consuming and
prone to errors. The system lacks the efficiency, transparency, and scalability that modern web-
based solutions can offer.

2.3 Problems with Existing System

The existing system at Patuakhali Science and Technology University (PSTU) faces several key
challenges:

❑ Manual Data Entry: The reliance on manual data entry for electricity billing processes

introduces the risk of errors and inaccuracies in meter readings and calculations.

❑ Lack of Transparency: Users often lack transparency in understanding their billing

details, leading to disputes and confusion.

❑ Security Concerns: Manual records and paper-based communication may pose

security risks, especially when handling sensitive user information.

15 | P a g e
 ❑ Limited Scalability: The system may struggle to accommodate the growing number of

users and data as the university expands, potentially leading to administrative

challenges.

❑ Dependency on Physical Receipts: Users depend on physical receipts for billing

information, which can be misplaced or lost, further complicating the communication

process.

2.4 Comparisons with our System:

In comparison to the existing systems, our intra-university electricity billing system represents a
paradigm shift in efficiency, accuracy, and user experience. Unlike manual methods prone to errors
and delays, our project employs modern technologies like Flutter and PHP to automate billing
calculations, user management, and communication. This automation eliminates inaccuracies and
streamlines processes, saving time for both administrators and users. The introduction of user-
friendly interfaces enhances transparency and engagement, while real-time data processing ensures
up-to-date billing information. Our project's integration of dynamic billing tables, customizable rates,
and automated notifications not only modernizes the billing system but also drastically improves
accuracy, reduces administrative workload, and provides users with a seamless and convenient
experience.

2.5 Summary:

The literature review of the project critically analyzes and synthesizes existing research, theories,
and insights relevant to the intra-university web-based electricity billing system. It offers a
comprehensive overview of established knowledge, identifying gaps and trends that frame the
project's significance. By examining prior work, the literature review informs the project's direction,
validating its goals and methodologies within the broader academic landscape. This review serves as
a crucial foundation, guiding the project's approach and contributing to a deeper understanding of the
subject.

CHAPTER-3

16 | P a g e
 3 METHODOLOGY

3.1 Introduction of Methodology:

The methodology section of this report outlines the approach taken to conduct the research and
complete the project. It describes the research design, data collection methods, data analysis
techniques, and any limitations and ethical considerations. The methodology used in this project is
crucial in ensuring the reliability and validity of the findings and conclusions. This section provides a
clear understanding of the process followed to achieve the project objectives and helps to establish
the credibility of the research.

3.2 Facts finding techniques:

Fact-finding techniques are the methods used to gather information and data about a particular
system or problem in order to analyze and understand it better. For this project, the fact-finding
techniques used include interviews with stakeholders, surveys of users, observation of current
systems, and analysis of existing documents and reports. These techniques help to identify the
requirements, constraints, and opportunities associated with the system, and inform the design
and development process.

3.3 Software Development Life Cycle (SDLC):

Certainly, here's a concise Software Development Life Cycle (SDLC) for this project:

❑ Requirements Phase: Gather project requirements from stakeholders. Define scope

and functionalities of the billing system. Document requirements in detail.

❑ Design Phase: Create system architecture and component design. Design user

interface using Figma. Plan database schema for data storage.

❑ Development Phase: Develop frontend using Flutter. Implement backend using PHP

for APIs and endpoints. Build features: house management, real-time bill calculation,
user communication.

❑ Testing Phase: Perform unit testing for components. Conduct integration testing for

17 | P a g e
 system interaction.Validate the system through user acceptance testing.

❑ Deployment Phase: Deploy application on a suitable server. Configure security

measures and email notifications. User

❑ Training and Documentation: Prepare user guides and conduct training. Ensure

administrators are familiar with the system.

❑ Launch and Rollout: Gradually transition from the old system. Monitor the system

and address any issues.

❑ Maintenance and Updates: Continuously monitor performance and address bugs.

Provide regular updates and enhancements.

❑ Project Closure: Evaluate project against goals and outcomes.Archive documentation

and gather feedback.

3.3.1 Software process model:

The software development process for this project followed a structured approach, beginning with
requirements analysis and design. Utilizing Flutter and PHP, the team translated designs into a
functional system, implementing features like house management and real-time billing. Rigorous
testing ensured reliability, followed by deployment on a web server. User training and
documentation facilitated a seamless transition, and continuous monitoring post-launch ensured
system integrity. This methodical process culminated in a successful transformation from manual
billing to an efficient web-based solution [2].

3.3.2 Feasibility Study:

Before embarking on the development journey of the intra-university web-based electricity billing
system, a comprehensive feasibility study was conducted. This study assessed the project's potential
across various dimensions to determine its viability and potential impact.

❑ Technical Feasibility: The study examined the technical aspects of implementing the

system using Flutter for the frontend and PHP for the backend. The availability of
suitable development tools, expertise, and resources was assessed to ensure the
project's technical feasibility [3].

18 | P a g e
 ❑ Operational Feasibility: The existing manual system's limitations were identified,

emphasizing the need for a more efficient solution. The new digital system's potential
to streamline house management, real-time billing calculations, and user
communication was evaluated for its operational feasibility [3].

❑ Financial Feasibility: The study weighed the project's costs against its benefits.

Investment in development, deployment, training, and maintenance was considered

against potential savings from reduced errors, improved efficiency, and user
satisfaction.

❑ Schedule Feasibility: The project timeline was analyzed to determine whether the

proposed development and implementation phases were achievable within the

allocated timeframe.

❑ User Acceptance: The feasibility study included gathering feedback from potential

users and administrators to gauge their interest and willingness to adopt the new
system.

3.4 Summary:

The methodology employed in this project to develop the intra-university web-based electricity
billing system was a comprehensive and systematic approach, blending modern technologies and
strategic planning. This methodology encompassed a detailed requirements analysis, followed by
architectural design using Flutter for the frontend and PHP for the backend. The development phase
translated designs into functional components, incorporating features such as house management,
real-time billing calculations, and user communication. Rigorous testing ensured system reliability,
and deployment on a web server facilitated accessibility. User training and thorough documentation
facilitated a seamless transition . Continuous monitoring post-launch ensured the system's efficiency
and adaptability [4, 5]. In summary, the methodology combined technical prowess, user-centric
design, and continuous improvement, resulting in the successful transformation of the university's
electricity billing operations.

19 | P a g e
CHAPTER-4

4 DATABASE DESIGN

4.1 Database Design:

The database architecture of this project embodies meticulous organization and tailored
functionalities across two databases: "biddutBill" and "monthlyBiddutBillTables." The latter
employs a dynamic structure, dedicating a new table for each month to optimize billing data. It
captures user-specific details, fostering transparency in billing calculations. The "biddutBill"
database comprises five tables, securing administrator credentials, managing charges, housing
details, billing rates, and user information. This design embodies streamlined data management,
ensuring accurate calculations, user awareness, and secure access, ultimately enhancing the project's
efficiency and user experience [6,7].

4.2 Entity Relationship :

biddutBill Database:

admin_auth: This entity includes fields like varsity_id, password, fullname, and email. It represents
administrator authentication credentials.

demand_and_vat_charge_table: This entity includes fields such as vat and demand_charge, capturing
the VAT and demand charges for billing calculations.

houses: This entity contains fields like building_name, house_no, meter_no, and assigned_user_id. It
represents housing details, meter assignments, and user associations.

unit_cost: This entity includes fields like starting_range, ending_range, and rate, defining billing
rates for different consumption ranges.

users: This entity contains fields like varsity_id, full_name, occupation, account_no, building_name,
house_number, and assigned_house. It captures user information and housing assignments.

monthlyBiddutBillTables Database:

Monthly Tables: A new table is added for each month, with fields like user_name, address,
previous_reading, current_reading, unit_cost, vat, demand_charge, account_no, and total_bill. Each
table holds billing details specific to that month.
20 | P a g e
Relationships:

The "houses" table in the "biddutBill" database is associated with the "users" table through the
assigned_user_id foreign key, establishing the user-house relationship.

The "users" table in the "biddutBill" database is connected to the "monthlyBiddutBillTables" tables,
allowing billing data to be associated with individual users in different months.

4.3 Symbols And Meaning Of ER

Fig 4.3.1 : SYMBOLS AND MEANING OF ERD

21 | P a g e
4.3.1 ER Diagram :

Figure 4.3.2 : ER Diagram

22 | P a g e
4.4 Summary:
At the core of the project's operational prowess lies a meticulous database design, comprising
"biddutBill" and "monthlyBiddutBillTables" databases. The former navigates administrative realms,
encompassing administrator authentication, charges, housing, rates, and user data. Meanwhile, the
latter employs a dynamic schema, materializing individualized billing tables for each month. This
arrangement optimizes data accuracy, transparency, and accessibility, ensuring a seamless transition
from manual methods to an agile web-based solution. Through this structured design, the project
attains operational efficiency, precision, and user-focused functionality, embodying a transformative
leap in electricity billing administration [8].

23 | P a g e
CHAPTER-5

5 SOFTWARE DESIGN

5.1 Introduction:

The software design of this project serves as the blueprint for transforming the vision of a web-based
electricity billing system into a functional and efficient reality. Rooted in a meticulous approach, the
software design encapsulates the architecture, structure, and components that will power the system's
capabilities. The software design document (SDD) is a crucial document used to specify the system
architecture and application design in the software-related project [9]. It will serve as a reference
guide for the software development team throughout the development process.

5.2 Overall design

5.2.1 Admin Activity diagram:

An admin activity diagram visually represents the sequential flow of actions and interactions an
administrator undertakes within a system. This diagram encapsulates the administrative journey,
illustrating tasks such as user management, bill calculation oversight, and system configuration.
Through clear symbols and arrows, the admin activity diagram provides an intuitive snapshot of the
steps an administrator takes, offering insights into the system's functionalities from an administrative
perspective.

24 | P a g e
Figure 5.2.1: Activity Diagram

25 | P a g e
5.3 Application Interfaces and It’s Features:

5.3.1 Bill Insert Tab :

The "Bill Insert" tab within our web application acts as a central hub for recording and processing
electricity consumption data. Administrators utilize this feature to effortlessly input users' current
month meter readings, which triggers an automated billing calculation based on dynamic rate
structures, VAT charges, and demand charges. Beyond simplifying billing, this tab offers the
additional capability of seamlessly sending billing notifications to all users via email, eliminating
the inefficiencies of manual correspondence. In essence, the "Bill Insert" tab serves as the engine
that drives the project's mission to digital and optimize intra-university electricity billing
processes.

Figure 5.3.1: Bill Insert Tab

5.3.2 Monthly Record Generation:

The "Monthly Record in PDF" feature in our project is a pivotal functionality that transforms the
calculated billing records into easily accessible and shareable PDF documents. It encapsulates the
user-specific billing information, including consumption details, rates, VAT charges, and demand
26 | P a g e
charges, in a structured and visually appealing format. This PDF generation capability simplifies
the distribution of billing records, enabling administrators to effortlessly send detailed and
professional billing statements to each user. This user-friendly feature enhances transparency and
user satisfaction while promoting efficient record-keeping and digital documentation, aligning
perfectly with the project's mission to modernize intra-university electricity billing processes.

Figure 5.3.2: Monthly record Generation

5.3.3 House View Tab :

The "House View" tab in our project's web application provides a centralized platform for
administrators to efficiently manage housing data. It allows for quick searches, editing of house
details, deletion of records, modification of house information, as well as the assignment and
removal of users to and from their respective houses. This streamlined interface simplifies the
management of housing information, improving administrative efficiency and maintaining
accurate housing records.

27 | P a g e
 Figure 5.3.3 : House Tab

5.3.4 Unit rate Tab:

The "Unit Rate" tab is a core component of our web application, serving as the control center for
managing electricity billing rates. This feature empowers administrators to customize and adjust
rates for different usage ranges and categories, ensuring accurate billing calculations. It offers the
flexibility to modify rate details in response to evolving pricing structures or policies. The "Unit
Rate" tab plays a vital role in ensuring transparency and precision in the electricity billing system,
aligning it with the university's changing needs and billing policies..

28 | P a g e
 Figure 5.3.4: Unit Rate Tab

5.3.5 User Tab:

User Tab allows for the addition of users categorized by type (A, B, S), offers user search
capabilities, facilitates data modifications, and supports user deletions. Additionally,
administrators can effortlessly assign users to their respective houses, simplifying housing
allocation. This multifunctional module enhances administrative efficiency and data accuracy,
providing adaptable tools for managing user information within the university system.

Figure 5.3.5: User Tab

29 | P a g e
5.4 Work plan and Timeline
The "Work Plan and Timeline" is a structured roadmap presented in a table format, detailing weekly
tasks, durations, and responsibilities for various project sub-sections. This organized plan ensures
systematic progress, efficient resource management, and timely achievement of milestones, playing a
pivotal role in project success.

Weeks Work Plan

1 Research about the lacking of the existing system and Documentation

1 Feasibility Study

1 Design abstract system

1 Meeting with client and present abstract system

1 UI (Figma) design of Application

2 Admin Authentication System UI build

Backend Api build
Database build and data flow testing

2 House View Tab House view UI build

Edit , create , details house UI build

House model, Backend Api design for fetch houses, create

houses and update houses.
Build House table in database and data flow testing

2 Unit Ranges Rate Tab UI build for unit range rates , demand charge and vat

Ui build for Update unite range rates , vat

Create backend APIs

Build unite range rates and demand char and vat

percentage in database and data flow testing

Table 5.4.1 Work Plan and Timeline Tab

30 | P a g e
 Weeks Work Plan

3 Bill Insert Tab UI build

Email sending service add
Monthly record pdf generate

Model and API build for monthly record database

2 Admin Info Tab UI build

Edit and add Admin UI build

Model , API build and database connection

Table 5.4.2 Work Plan and Timeline Table

5.5 Implementation:

Implementation in your project refers to coding the entire web-based electricity billing system using
technologies like Flutter and PHP. This phase transforms design and plans into a functional
application, including user interfaces, backend logic, billing calculations, and more. Rigorous testing
is vital to ensure everything works as intended. The result is a fully operational system that
modernizes billing processes, streamlines administration, and offers an enhanced user experience.

5.6 Summary:

The software design phase crafts the blueprint for the project using technologies like Flutter and
PHP, merging user-friendly interfaces with robust backend functionalities. An admin activity
diagram visually maps administrative tasks, work plan tables outline project phases, and
implementation entails coding the entire system, rigorously tested to bring to life a modernized
solution simplifying administrative tasks and enhancing user experiences.

CHAPTER-6:
31 | P a g e
 TESTING & SECURITY

6.1 Introduction:

Project testing and security are two essential aspects of software development. Project testing
ensures that the software meets its requirements and functions as expected, while security testing
ensures that the software is protected from unauthorized access, use, modification, or disclosure. By
performing thorough testing, organizations can reduce the risk of security breaches and other
problems [10] . In addition to testing and security, it is also important to have a plan for ongoing
maintenance and support of the system to ensure that it remains functional and secure over time.

6.2 Testing Strategies:

In our project, we have implemented various testing strategies such as unit testing, integration
testing, and system testing to ensure the quality of the software. We have also prioritized security by
implementing various security measures such as encryption, user authentication, and authorization
to ensure the confidentiality, integrity, and availability of the system's data [11].

❑ Unit Testing:

House Management: Unit tests validate the creation, modification, and deletion of
houses, ensuring accurate storage and retrieval of associated details such as building
name, house number, and meter number.

Billing Calculation: Testing verifies the precise execution of billing calculations

based on real-time meter readings, unit costs, VAT rates, and demand charges,
ensuring accurate bill generation.

❑ Integration Testing:

Frontend-Backend Integration: Integration tests validate seamless data flow between

the Flutter frontend and PHP backend, confirming the successful transmission of user
inputs, house details, and billing data.

Billing Components: Comprehensive integration tests assess the seamless interaction

between different billing components, including user data, billing rates, VAT, and
demand charges, guaranteeing accurate and comprehensive bill calculation.

32 | P a g e
❑ User Acceptance Testing (UAT):

User Experience: Real users engage in UAT to evaluate the system's ease of use,
testing interactions like entering meter readings, viewing bills, and updating personal
information, ensuring an intuitive user experience.

Email Notifications: UAT validates that users receive timely and accurate email
notifications containing their billing details, ensuring effective communication.

❑ Security Testing:

Authentication: Security testing ensures the effectiveness of authentication

mechanisms, such as username-password combinations, multi-factor authentication,
or other secure login methods, preventing unauthorized access.

Data Encryption: This testing verifies the encryption of sensitive data during
transmission and storage, safeguarding user information against unauthorized access
or breaches.

Access Control: Security tests validate that user roles and permissions are enforced,
ensuring that users can only access the functionalities they are authorized to use.

❑ Performance Testing:

Scalability: Scalability testing assesses the system's performance under varying user
loads, ensuring that it remains responsive and efficient as the number of users
increases.

Response Time: Performance tests measure the system's response time during critical
operations, such as bill calculation and data retrieval, ensuring acceptable levels of
speed and efficiency.

❑ Penetration Testing:

Vulnerability Scanning: Automated tools scan the system for vulnerabilities, such as
outdated software, unsecured APIs, or potential security gaps, providing insights for
remediation.

Ethical Hacking: Ethical hackers simulate real-world attacks to identify potential

vulnerabilities and weaknesses, helping to fortify the system's security measures.

❑ User Data Privacy Testing:

33 | P a g e
 Data Anonymization: Testing ensures that personal user data is anonymized or
pseudonymized when stored or used for testing purposes, protecting user privacy and
complying with data protection regulations.

Data Retention: This testing confirms that the system adheres to data retention
policies, deleting or archiving user data as required by applicable laws and
regulations.

❑ Backup and Recovery Testing:

Data Recovery: Backup and recovery tests validate the system's ability to restore data
in case of data loss or system failure, ensuring data integrity and minimizing
downtime.

Backup Frequency: Testing ensures the regularity and reliability of data backup
processes, reducing the risk of data loss and enabling swift recovery.

❑ Compatibility Testing:

Cross-Browser Compatibility: This testing ensures that the system functions

correctly and maintains its appearance across different web browsers, catering to a
wide range of user preferences.

Device Compatibility: Compatibility tests assess the system's responsiveness and

usability across various devices, screen sizes, and orientations, ensuring a consistent
experience for all users.

6.3 XP Practices:

Extreme Programming (XP) is an agile software development methodology that emphasizes

collaboration, flexibility, and customer satisfaction. In order to increase productivity while
maintaining quality, XP proposes a set of software development practices that can be grouped into
three key areas: customer satisfaction, software quality, and development process organization.
These practices include a total of 12 practices that aim to improve the overall software development.

6.3.1 XP Testing:

34 | P a g e
XP testing is an integral part of the Extreme Programming (XP) methodology, which emphasizes
the need for frequent and automated testing throughout the development cycle. XP testing involves
continuous integration and regression testing, with the goal of catching defects early and ensuring
that software is delivered on time with high quality. It also involves customer involvement in testing
to ensure that the software meets their needs and expectations

Types of Testing:
❑ White box testing.

❑ Black box testing.

White Box Testing: In the realm of white box testing, the project's focus rests on delving into the
intricate details of the system's architecture and code. This approach involves scrutinizing the internal
logic of functions, such as house management and billing calculations. White box testing ensures that
these functions execute seamlessly, accurately storing, modifying, and deleting house details, as well
as precisely computing billing amounts based on real-time data inputs. Additionally, white box
security testing evaluates authentication mechanisms, encryption processes, and access control to
fortify the system's resilience against unauthorized access. This meticulous examination of the
system's inner workings contributes to its reliability, security, and overall robustness.

Black Box Testing: In the domain of black box testing, the project shifts its focus to the system's
external behaviors and user interactions. With a holistic approach, black box testing validates the
integration between the Flutter frontend and PHP backend, ensuring smooth communication without
requiring insight into the internal code structure. Through user acceptance testing (UAT), the project
ascertains the system's user-friendliness and functionality from an end-user perspective, validating
tasks like entering meter readings and receiving accurate email notifications [12]. Security testing
from a black box perspective aims to identify vulnerabilities and potential breaches, simulating
external attacks to bolster the system's defenses. This encompassing methodology evaluates the
system's performance, security, and user experience as a comprehensive whole.

6.4 Summary:
Security and testing converge as sentinels guarding the web-based electricity billing system.
Testing, executed through meticulous white box and black box approaches, scrutinizes both internal
logic and user experiences. White box testing delves into intricate code structures, ensuring precise
house management and billing calculations, while also fortifying authentication and encryption
35 | P a g e
mechanisms. In contrast, black box testing encompasses external behaviors, affirming seamless
frontend-backend integration and user-friendly interactions. Security measures encompass both
penetration and data privacy testing, reinforcing defenses against potential threats. This unified
security and testing strategy stands as the project's bulwark, assuring an impregnable, reliable, and
user-centric digital landscape .

36 | P a g e
CHAPTER-7

7 CONCLUSION

7.1 Introduction:

The conclusion section summarizes the findings and outcomes of the study, and provides
recommendations for future work. It is an important section as it helps to tie all the pieces of the
research together and highlight the key points that have been made throughout the study.

7.2 Project Outcomes:

The project's outcomes reflect a transformative shift in the electricity billing system at Patuakhali
Science and Technology University. By embracing technology, the system has evolved from manual
processes to a dynamic web-based solution. The project's key accomplishments include streamlined
house management, real-time billing calculations, personalized user communication, and adaptable
billing rate adjustments. These outcomes converge to enhance administrative efficiency, eliminate
errors, and elevate user satisfaction. The system's deployment facilitates transparent billing, reduces
delays, and offers a user-friendly experience. Ultimately, the project's outcomes showcase the
successful integration of technology to revolutionize university administrative practices, setting a
new standard for accuracy and convenience in electricity billing operations..

7.3 Future Works:

Some of the future works of the project are the following:

❑ User Section. There will be-

• User login section

• See their current month bill in Detail
• User all past bill history
• Complain system for their bill
• Electricity uses graph

37 | P a g e
 7.4 Summary:

This project epitomizes innovation's impact on administrative practices, transforming Patuakhali

Science and Technology University's electricity billing system. Leveraging Flutter and PHP, the
system transitions from manual methods to a digital paradigm. Key features—house management,
real-time billing calculations, user communication, and adaptable rates—usher in operational
efficiency and accuracy. The project elevates user experience through transparency and personalized
interactions. Administrator authentication, charges, housing, rates, and user data are meticulously
organized. The system's dynamic billing tables and secure access ensure precision and reliability. In
culmination, this project advances university operations by embracing technology's transformative
potential, underscoring accuracy, efficiency, and user-centricity in the new digital era of electricity
billing.

38 | P a g e
References :

1. Eugenio MC, Miguel CL. Web Service for Monitoring Electricity Billing at a University
Campus. In2018 IEEE 38th Central America and Panama Convention (CONCAPAN XXXVIII)
2018 Nov 7 (pp. 1-6). IEEE.

2. Jazayeri M. Some trends in web application development. InFuture of Software Engineering

(FOSE'07) 2007 May 23 (pp. 199-213). IEEE.

3. Prokhorenko V, Choo KK, Ashman H. Web application protection techniques: A taxonomy.

Journal of Network and Computer Applications. 2016 Jan 1;60:95-112.

4. Conallen J. Modeling web application architectures with UML. Communications of the ACM.
1999 Oct 1;42(10):63-70.

5. Di Lucca GA, Fasolino AR, Faralli F, De Carlini U. Testing web applications. InInternational
Conference on Software Maintenance, 2002. Proceedings. 2002 Oct 3 (pp. 310-319). IEEE.

6. Ongo G, Kusuma GP. Hybrid database system of MySQL and MongoDB in web application
development. In2018 international conference on information management and technology
(ICIMTech) 2018 Sep 3 (pp. 256-260). IEEE.

7. Jaimez-González C, Martínez-Samora J. DiagrammER: A Web Application to Support the

Teaching-Learning Process of Database Courses Through the Creation of ER Diagrams.
International Journal of Emerging Technologies in Learning (iJET). 2020 Oct 5;15(19):4-21.

8. Al-Fedaghi S. Developing web applications. International journal of software engineering and

its applications. 2011 Apr 2;5(2):57-68.

9. Littlewood B, Popov P, Strigini L. Modeling software design diversity: a review. ACM

Computing Surveys (CSUR). 2001 Jun 1;33(2):177-208.

10. Huang HC, Zhang ZK, Cheng HW, Shieh SW. Web application security: Threats,
countermeasures, and pitfalls. Computer. 2017 Jun 9;50(6):81-5.

11. Huang YW, Huang SK, Lin TP, Tsai CH. Web application security assessment by fault
injection and behavior monitoring. InProceedings of the 12th international conference on World
Wide Web 2003 May 20 (pp. 148-159).

12. AL-atraqchi OM. A Proposed Model for Build a Secure Restful API to Connect between Server
Side and Mobile Application Using Laravel Framework with Flutter Toolkits. Cihan
University-Erbil Scientific Journal. 2022 Aug 20;6(2):28-35.

39 | P a g e
Websites:

1. For design UI : https://www.figma.com/

2. For ER diagram and Flowchart design : https://www.lucidchart.com/

3. Flutter packages : https://pub.dev/

40 | P a g e