Technical Website Documentation

BSCS FINAL PROJECT
Automated Complaint System [Revenue

Department]
Project Advisor: Prof. ------------------
Presented by:
------------------ ----------------------------------
----------------------
------------------- ---------------------
Faculty of Information Technology

National College of Business Administration & Economics
Gujrat
Automated Complaint System
[Revenue Department]
By
------------
----------------
------------------
Project submitted to
Faculty of Information Technology,
NCBA & E Gujrat
in partial fulfillment of the requirements for the degree of
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE
Project Advisor Manager Projects
Page ii
ABSTRACT
The food donation app is a digital platform designed to facilitate the process of donating surplus food from
individuals, restaurants, grocery stores, and other food establishments to those in need. With the rising concerns
about food waste and food insecurity, this app serves as a bridge to connect donors with organizations and
individuals who can redistribute food to communities facing hunger. The app provides an intuitive user interface for
donors to easily list available food items, specify pickup times, and choose recipient organizations or individuals.
Recipient organizations, such as shelters, food banks, and community centers, can register on the platform to
receive notifications about available donations and arrange pickups accordingly. Key features of the app include
real-time notifications, geolocation services for efficient pickup coordination, user profiles for tracking donation
history, and feedback mechanisms to ensure transparency and accountability in the donation process. Through the
implementation of this food donation app, we aim to reduce food waste, alleviate hunger, and foster community
engagement in addressing food insecurity issues. The app's user-friendly design and seamless functionality make it
accessible to a wide range of users, empowering individuals and businesses to make meaningful contributions to
their communities.
Page iii
DEDICATION
This project is dedicated to all those who believe in the power of compassion and solidarity in
addressing the pressing issues of food waste and hunger.
To the tireless volunteers, activists, and organizations working tirelessly to alleviate food
insecurity and promote food insecurity and promote sustainable solutions, your dedication inspires
us.
To the individuals and businesses who generously contribute their time, resources, and surplus
food to those in need, your kindness embodies the spirit of community and empathy.
May this food donation app serve as a catalyst for positive change, bringing us closer to a future
where no one goes hungry and where every meal shared is a symbol of hope and solidarity.
This project is dedicated to you, champions of compassion and advocates for a more equitable
world.
“Let's turn surplus into sustenance, waste into warmth, and hunger into hope. Together, through small acts of
generosity, we can create a world where no plate is empty and no heart is untouched. ”
------------------------
-------------
Page iv
ACKNOWLEDGEMENT
As we culminate the development of this food donation app as part of our university project, we
would like to extend our sincere gratitude to all those who have contributed to its success.
First and foremost, we express our appreciation to our academic advisors, professors, and mentors for their
guidance, encouragement, and unwavering support throughout the duration of this project. Your expertise
and insights have been invaluable in shaping the direction and scope of our work.
We also extend our heartfelt thanks to our fellow classmates and peers who provided feedback, suggestions,
and constructive criticism during various stages of development. Your perspectives and collaboration have
enriched the project and contributed to its overall quality.
We acknowledge the university administration and staff for providing resources, facilities, and technical
support that facilitated the implementation and execution of the project. Your commitment to fostering
innovation and academic excellence has been instrumental in our journey.
Furthermore, we are grateful to the broader community of stakeholders, including local organizations,
businesses, and individuals, who have supported our efforts to address food waste and hunger in our
university's vicinity. Your partnership and engagement have reinforced the importance of community-driven
initiatives in creating positive social impact.
Lastly, we extend our heartfelt thanks to our families, friends, and loved ones for their unwavering
encouragement, understanding, and patience throughout the challenges and triumphs of this project.
Together, through collaborative efforts and dedication, we have demonstrated the potential for technology to
address pressing societal issues and make a meaningful difference in people's lives.
Thank you to everyone who has been part of this journey.
----------------
---------------
Page v
Table of Contents
Dedication .....................................................................................................................................iv
Acknowledgement..........................................................................................................................v
Table of Contents .........................................................................................................................vi
List of Tables ...............................................................................................................................vii
List of Figures ...............................................................................................................................ix
CHAPTER 1: Introduction to the Problem.................................................................................1
1.1 Background of problem ............................................................................................................... 2
1.2 Problem........................................................................................................................................ 2
CHAPTER 2: Existing Solutions And Proposed
Solution .........................................................4
2.1 Existing Solutions ........................................................................................................................ 5
2.2 Proposed Solution ........................................................................................................................ 5
CHAPTER 3:
Analysis ..................................................................................................................6
Structured
Approach .....................................................................................................................7
3.1 Vision .......................................................................................................................................... 7
3.2 Supplementary Specification ....................................................................................................... 7
3.2.1 Functional Requiremnets ............................................................................................................................ 7
3.2.2 Non-Functional Requiremnets .................................................................................................................. 10
3.2.3 Design and Implementation Constraints ................................................................................................... 12
3.2.4 Glossary (Acronyms and Abreviations) ................................................................................................... 13
3.3 Software Architecture ................................................................................................................ 14
3.4 Screen Shots .............................................................................................................................. 15
3.5 Use Case Diagrams .................................................................................................................... 22
CHAPTER 4:
Design ...................................................................................................................57
4.1 Database Design ........................................................................................................................ 58
4.2 ERD ........................................................................................................................................... 59
4.3 Data Flow diagrams ................................................................................................................... 64
4.4 Activity Diagram ....................................................................................................................... 66
4.5 State Transition Diagrams ......................................................................................................... 68
4.6 System Sequence Diagrams ....................................................................................................... 69
CHAPTER 5:
Testing ................................................................................................................102
5.1 Introduction .............................................................................................................................
103
5.2 Test Plan .................................................................................................................................. 104
5.3 Test Case Specification ........................................................................................................... 109
5.4 Test Cases ................................................................................................................................ 110
5.5 Performance Testing ................................................................................................................ 144 5.6
Security Testing ....................................................................................................................... 144
5.7 Regression Testing .................................................................................................................. 145
CHAPTER 6: Tools
Used ..........................................................................................................146 a.
Languages ................................................................................................................................ 147
b. Applications ............................................................................................................................. 147
vi
c. Libraries ................................................................................................................................... 147
CHAPTER 7: Summary and
Conclusions ...............................................................................148
CHAPTER 8: User
Manual ......................................................................................................150 CHAPTER 9:
Lessons Learnt And Future Work ..................................................................169
Appendix A: Project Management
Documents .......................................................................171
a. Team Structure ........................................................................................................................ 172
b. Roles & Responsibilities ......................................................................................................... 172
c. WBS (Work Breakdown Structure) ......................................................................................... 173
d. PERT Diagram ........................................................................................................................ 174
e. Scope Statement ...................................................................................................................... 174
f. Project Charter ......................................................................................................................... 176
g. Meetings Summary .................................................................................................................. 177
Appendix B:
Bibliography/References .....................................................................................179 Appendix
C: Index .....................................................................................................................181
Page
List of Tables
Use Case Tables Related To Admin Side ..................................................................................
23
Table 1: Admin_Log_In ............................................................................................................................. 23
Table 2: Admin_Transfer_Complaints .......................................................................................................
24
Table 3: Admin_Register_User .................................................................................................................. 25
Table 4: Admin_Complete ..........................................................................................................................
26
Table 5: DC_Log_In ...................................................................................................................................
27
Table 6: DC_Update_Status ....................................................................................................................... 28
Table 7: DC_Complete ...............................................................................................................................
29
Table 8: AC_Log_In ...................................................................................................................................
30
Table 9: AC_Update_Status ....................................................................................................................... 31
Table 10: AC_Complete .............................................................................................................................
32
Table 11: Tehsildar_Log_In ....................................................................................................................... 33
Table 12: Tehsildar_Update_Status ............................................................................................................
34
Table 13: Tehsildar_Complete ....................................................................................................................
35
Table 14: Employee_Log_In ...................................................................................................................... 36
Table 15: Employee_Complete ...................................................................................................................
37
Use Case Tables Related To User Side………………………………………………………...38
Table 16: AC_Log_In .................................................................................................................................
38
Table 17: AC_Register_Complaints ...........................................................................................................
39
Page vii
Table 18: AC_Give_Feedback ....................................................................................................................
40
Table 19: AC_Complete .............................................................................................................................
41
Table 20: Tehsildar_Log_In ....................................................................................................................... 42
Table 21: Tehsildar_Register_Complaints ..................................................................................................
43
Table 22: Tehsildar_Give_Feedback ..........................................................................................................
44
Table 23: Tehsildar_Complete ....................................................................................................................
45
Table 24: Employee_Log_In ...................................................................................................................... 46
Table 25: Employee_Register_Complaints ................................................................................................ 47
Table 26: Employee_Give_Feedback .........................................................................................................
48
Table 27: Employee_Complete ...................................................................................................................
49
Table 28: Citizen_Sign_Up .........................................................................................................................
50
Table 29: Citizen_Log_In ...........................................................................................................................
51
Table 30: Citizen_Edit_Profile ...................................................................................................................
52
Table 31: Citizen_Change_Password .........................................................................................................
53
Table 32: Citizen_Register_Complaints .....................................................................................................
54
Table 33: Citizen_Give_Feedback ..............................................................................................................
55
Table 34: Citizen_Complete .......................................................................................................................
56
Table 35: Items to be tested…………...…………..……………..………………………...
…………....105
Table 36: Items not to be tested.…………..………………...………………………………….
……....105
Table 37: Features to be tested.…………..…………………..………………………………….
……...106
Table 38: Responsibilities .......................................................................................................................
108
Table 39: Test Case Identifiers….………..………….……..……………………………...…………...109
Test Cases for user side .......................................................................................................................... 110
Table 40: TC-1 ..........................................................................................................................................
110
Table 41: TC-2 ..........................................................................................................................................
111
Table 42: TC-3 ..........................................................................................................................................
111
Table 43: TC-4 ..........................................................................................................................................
112
Table 44: TC-5 ..........................................................................................................................................
113
Table 45: TC-6 ..........................................................................................................................................
113
Table 46: TC-7 ..........................................................................................................................................
114
viii
Table 47: TC-8 ..........................................................................................................................................
114
Table 48: TC-9 ..........................................................................................................................................
115
Table 49: TC-10 ........................................................................................................................................
116
Table 50: TC-11 ........................................................................................................................................
116
Table 51: TC-12 ........................................................................................................................................
117
Table 52: TC-13 ........................................................................................................................................
117
Table 53: TC-14 ........................................................................................................................................
118 Table 54: TC-
15 ........................................................................................................................................ 119 Table 55:
TC-16 ........................................................................................................................................ 119
Table 56: TC-17 ........................................................................................................................................
120
Table 57: TC-18 ........................................................................................................................................
121
Table 58: TC-19 ........................................................................................................................................
121 Table 59: TC-
20 ........................................................................................................................................ 122
Table 60: TC-21 ........................................................................................................................................
123
Table 61: TC-22 ........................................................................................................................................
123 Table 62: TC-
23 ........................................................................................................................................ 124
Test Cases For Admin Side .................................................................................................................... 125
Table 63: TC-24 ........................................................................................................................................
125
Table 64: TC-25 ........................................................................................................................................
125 Table 65: TC-
26 ........................................................................................................................................ 126
Test Cases for DC ....................................................................................................................................
127
Table 66: TC-27 ........................................................................................................................................
127 Table 67: TC-
28 ........................................................................................................................................ 128
Test Cases for AC ....................................................................................................................................
129
Table 68: TC-29 ........................................................................................................................................
129 Table 69: TC-
30 ........................................................................................................................................ 130
Test Cases for Tehsildar .........................................................................................................................
130
Table 70: TC-31 ........................................................................................................................................
130
Table 71: TC-32 ........................................................................................................................................
131
Table 72: TC-33 ........................................................................................................................................
132
Table 73: TC-34 ........................................................................................................................................
133
Page ix
Table 74: TC-35 ........................................................................................................................................
133 Table 75: TC-
36 ........................................................................................................................................ 134
Test Cases for Naib Tehsidar .................................................................................................................
135
Table 76: TC-37 ........................................................................................................................................
135
Table 77: TC-38 ........................................................................................................................................
136
Table 78: TC-39 ........................................................................................................................................
136 Table 79: TC-
40 ........................................................................................................................................ 137
Test Cases for Gadawar ......................................................................................................................... 138
Table 80: TC-41 ........................................................................................................................................
138
Table 81: TC-42 ........................................................................................................................................
139
Table 82: TC-43 ........................................................................................................................................
139 Table 83: TC-
44 ........................................................................................................................................ 140
Test Cases for Patwari ............................................................................................................................
141
Table 84: TC-45 ........................................................................................................................................
141
Table 85: TC-46 ........................................................................................................................................
142
Table 86: TC-47 ........................................................................................................................................
142 Table 87: TC-
48 ........................................................................................................................................ 143
Page
List of Figures
FIGURE-1: Software
Architecture ............................................................................................14
FIGURE: Screen
Shots ................................................................................................................15
User
Interface ...............................................................................................................................15
x
FIGURE-2:Home Page .........................................................................................................................
15
FIGURE-3:About Us Page .....................................................................................................................
16
FIGURE-4:Laws and Policies Page ......................................................................................................
17
FIGURE-5:Location Page ......................................................................................................................
18
FIGURE-6:Registration Page ............................................................................................................... 19
FIGURE-7:Login Page .......................................................................................................................... 20
FIGURE-8: Privacy Policy Page ............................................................................................................
21
FIGURE: Use Case Diagrams Related To Admin
Side ............................................................23
FIGURE: Use Case Diagram
(Admin) .......................................................................................23
FIGURE-9: Use Case (Admin Login).................................................................................................... 23
FIGURE-10: Use Case (Admin Transfer Complaints) ..........................................................................
24
FIGURE-11: Use Case (Admin Register Users) ....................................................................................
25
FIGURE-12: Complete Use Case (Admin) ............................................................................................
26
(DC) .............................................................................................27
FIGURE-13: Use Case (DC Login) .......................................................................................................
27
FIGURE-14: Use Case (DC Update Complainant Status) .....................................................................
28
FIGURE-15: Complete Use Case (DC) .................................................................................................
29
(AC) .............................................................................................30
FIGURE-16: Use Case (AC Login) .......................................................................................................
30
FIGURE-17: Use Case (AC Update Complainant Status) .....................................................................
31
FIGURE-18: Complete Use Case (AC) .................................................................................................
32
(Tehsildar) ..................................................................................33
FIGURE-19: Use Case (Tehsildar Login) ..............................................................................................
33
FIGURE-20: Use Case (Tehsildar Update Complainant Status) ...........................................................
34
FIGURE-21: Complete Use Case (Tehsildar) ........................................................................................
35
FIGURE: Use Case Diagram (Employee)..................................................................................36
FIGURE-22: Use Case (Employee Login) ............................................................................................ 36
FIGURE-23: Use Case (Employee Complete) ...................................................................................... 37
FIGURE: Use Case Diagram Related To
Complainants .........................................................38
(AC) .............................................................................................38
Page xi
FIGURE-24: Use Case (AC Login) .......................................................................................................
38
FIGURE-25: Use Case (AC Register Complaint) .................................................................................
39
FIGURE-26: Use Case (AC Give Feedback) .........................................................................................
40
FIGURE-27: Complete Use Case (AC) .................................................................................................
41
(Tehsildar) ..................................................................................42
FIGURE-28: Use Case (Tehsildar Login) ..............................................................................................
42
FIGURE-29: Use Case (Tehsildar Register Complaint) ........................................................................
43
FIGURE-30: Use Case (Tehsildar Give Feedback) ...............................................................................
44
FIGURE-31: Complete Use Case (Tehsildar) ........................................................................................
45
FIGURE: Use Case Diagram (Employee)..................................................................................46
FIGURE-32: Use Case (Employee Login) ............................................................................................ 46
FIGURE-33: Use Case (Employee Register Complaint) .......................................................................
47
FIGURE-34: Use Case (Employee Give Feedback) ..............................................................................
48
FIGURE-35: Complete Use Case (Employee) ...................................................................................... 49
(Citizen) ......................................................................................50
FIGURE-36: Use Case (Citizen Signup) ...............................................................................................
50
FIGURE-37: Use Case (Citizen Login) .................................................................................................
51
FIGURE-38: Use Case (Citizen Edit Profile) ........................................................................................
52
FIGURE-39: Use Case (Citizen Change Password) ..............................................................................
53
FIGURE-40: Use Case (Citizen Register Complaint) ...........................................................................
54
xii
FIGURE-41: Use Case (Citizen Give Feedback) ...................................................................................
55
FIGURE-42: Complete Use Case (Citizen) ...........................................................................................
56
FIGURE-43: Database
Design ....................................................................................................58
FIGURE-44: Entity Tables .........................................................................................................61
FIGURE-45: ER
Diagram ...........................................................................................................63
FIGURE-46: Data Flow Diagram...............................................................................................64
FIGURE-47: Activity
Diagram ...................................................................................................67
FIGURE-48: State Transition Diagram.....................................................................................68
FIGURE: Sequence Diagram Related To
Officers ...................................................................69 FIGURE: Sequence Diagram
(Admin) ......................................................................................69
FIGURE-49: Sequence Diagram (Admin: Login) .................................................................................
69
FIGURE-50: Sequence Diagram (Admin: Transfer Complaints) ..........................................................
70
FIGURE-51: Sequence Diagram (Admin: View Complaint Messages) ................................................
70
FIGURE-52: Sequence Diagram (Admin: Register Officer) .................................................................
71
FIGURE-53: Sequence Diagram (Admin: Logout) ...............................................................................
72
FIGURE: Sequence Diagram
(DC) ............................................................................................73
FIGURE-54: Sequence Diagram (DC: Login) .......................................................................................
73
FIGURE-55: Sequence Diagram (DC: View Complaint Messages) .....................................................
74
FIGURE-56: Sequence Diagram (DC: Update Complaint Status) ........................................................
74
FIGURE-57: Sequence Diagram (DC: Send Message) ......................................................................... 75
FIGURE-58: Sequence Diagram (DC: Logout) .....................................................................................
75
(AC) ............................................................................................76
FIGURE-59: Sequence Diagram (AC: Login) .......................................................................................
76
FIGURE-60: Sequence Diagram (AC: View Complaint Messages) .....................................................
77
FIGURE-61: Sequence Diagram (AC: Update Complaint Status) ........................................................
77
FIGURE-62: Sequence Diagram (AC: Send Message) ......................................................................... 78
FIGURE-63: Sequence Diagram (AC: Logout) .....................................................................................
78
FIGURE: Sequence Diagram (Tehsildar) .................................................................................79
FIGURE-64: Sequence Diagram (Tehsildar: Login) .............................................................................
79
Page xiii
FIGURE-65: Sequence Diagram (Tehsildar: View Complaint Messages) ............................................
80
FIGURE-66: Sequence Diagram (Tehsildar: Update Complaint Status) ...............................................
80
FIGURE-67: Sequence Diagram (Tehsildar: Send Message) ...............................................................
81
FIGURE-68: Sequence Diagram (Tehsildar: Logout) ...........................................................................
81
(Employee) .................................................................................82
FIGURE-69: Sequence Diagram (Employee: Login) ............................................................................
82
FIGURE-70: Sequence Diagram (Employee: View Messages) ............................................................ 83
FIGURE-71: Sequence Diagram (Employee: Logout) ..........................................................................
83
FIGURE: Sequence Diagram Related To
Complainants .........................................................84
(AC) ............................................................................................84
FIGURE-72: Sequence Diagram (AC: Login) .......................................................................................
84
FIGURE-73: Sequence Diagram (AC: Register Complaint) .................................................................
85
FIGURE-74: Sequence Diagram (AC: View Complaint Status) ...........................................................
86
FIGURE-75: Sequence Diagram (AC: Give Feedback) ........................................................................
86
FIGURE-76: Sequence Diagram (AC: View Messages) .......................................................................
87
FIGURE-77: Sequence Diagram (AC: Logout) .....................................................................................
87
FIGURE: Sequence Diagram (Tehsildar) .................................................................................88
FIGURE-78: Sequence Diagram (Tehsildar: Login) .............................................................................
88
FIGURE-79: Sequence Diagram (Tehsildar: Register Complaint) ........................................................
89
FIGURE-80: Sequence Diagram (Tehsildar: View Complaint Status) ................................................. 90
FIGURE-81: Sequence Diagram (Tehsildar: Give Feedback) ...............................................................
90
FIGURE-82 Sequence Diagram (Tehsildar: View Messages) ..............................................................
91
FIGURE-83: Sequence Diagram (Tehsildar: Logout) ...........................................................................
91
(Employee) .................................................................................92
FIGURE-84: Sequence Diagram (Employee: Login) ............................................................................
92
FIGURE-85: Sequence Diagram (Employee: Register Complaint) ...................................................... 93
FIGURE-86: Sequence Diagram (Employee: View Complaint Status) ................................................ 94
FIGURE-87: Sequence Diagram (Employee: Give Feedback) ..............................................................
94
FIGURE-88: Sequence Diagram (Employee: View Messages) ............................................................ 95
Page xiv
FIGURE-89: Sequence Diagram (Employee: Logout) ..........................................................................
95
(Citizen) ......................................................................................96
FIGURE-90: Sequence Diagram (Citizen: Login) .................................................................................
96
FIGURE-91: Sequence Diagram (Citizen: Manage Profile) ..................................................................
97
FIGURE-92: Sequence Diagram (Citizen: Change Password) ..............................................................
98
FIGURE-93: Sequence Diagram (Citizen: Register Complaint) ...........................................................
99
FIGURE-94: Sequence Diagram (Citizen: View Complaint Status) ...................................................
100
FIGURE-95: Sequence Diagram (Citizen: Give Feedback) ................................................................
100
FIGURE-96: Sequence Diagram (Citizen: View Messages) ...............................................................
101
FIGURE-97: Sequence Diagram (Citizen: Logout) .............................................................................
101
FIGURE: User Manual .............................................................................................................151
Admin
Dashboard ......................................................................................................................151
FIGURE-98:Admin Dashboard ........................................................................................................... 151
FIGURE-99:Admin Profile ..................................................................................................................
152
FIGURE-100:Admin View Notification ..............................................................................................
152
FIGURE-101:Admin Forward Complaints ..........................................................................................
153
FIGURE-102:Admin View User ......................................................................................................... 154
User
Dashboard ..........................................................................................................................155
FIGURE-103:User Dashboard .............................................................................................................
155
FIGURE-104:User Profile ................................................................................................................... 155
FIGURE-105:User Edit Profile ............................................................................................................
156
FIGURE-106:User Change Password ..................................................................................................
156
FIGURE-107:User Complaint Form ....................................................................................................
157
FIGURE-108:User Complaint Status ...................................................................................................
157
FIGURE-109:User Message Page ....................................................................................................... 158
FIGURE-110:User Feedback Page ...................................................................................................... 158
DC
Dashboard ............................................................................................................................160
FIGURE-111:DC Dashboard ...............................................................................................................
160
FIGURE-112:DC Profile ..................................................................................................................... 160
FIGURE-113:DC Incoming Complaints ..............................................................................................
161
Page xv
FIGURE-114:DC Send Message ......................................................................................................... 162
FIGURE-115:DC Complaints Page .....................................................................................................
162
AC
Dashboard ............................................................................................................................163
FIGURE-116:AC Dashboard ...............................................................................................................
163
FIGURE-117:AC Profile ..................................................................................................................... 163
FIGURE-118:AC Messages .................................................................................................................
164
Tehsildar
Dashboard .................................................................................................................164
FIGURE-119:Tehsildar Dashboard ..................................................................................................... 164
FIGURE-120:Tehsildar Profile ............................................................................................................
165
Naib Tehsildar
Dashboard ........................................................................................................165
FIGURE-121:Naib Tehsildar Dashboard .............................................................................................
165
FIGURE-122: Naib Tehsildar Profile ..................................................................................................
166
Gadawar
Dashboard ..................................................................................................................166
FIGURE-123:Gadawar Dashboard ......................................................................................................
166
FIGURE-124:Gadawar Profile ............................................................................................................ 167
Patwari
Dashboard ....................................................................................................................167
FIGURE-125:Patwari Dashboard ........................................................................................................ 167
FIGURE-126:Patwari Profile ...............................................................................................................
168
FIGURE-127: Team
Structure .................................................................................................172
FIGURE-128: WBS ...................................................................................................................173
FIGURE-129: PERT Diagram..................................................................................................174
Page xvi
CHAPTER 1
INTRODUCTION TO THE
PROBLEM
Page xvii
1. Introduction
1.1 Background of Problem

Food waste and hunger are two interconnected challenges that persistently afflict communities worldwide.
Despite the abundance of food resources in many regions, a significant portion goes to waste while millions of
individuals struggle with food insecurity and hunger on a daily basis.
Food waste occurs at various stages of the food supply chain, including production, distribution, retail, and
consumption. In developed countries, a substantial amount of food is discarded by households, restaurants,
supermarkets, and other food establishments due to reasons such as overproduction, aesthetic standards,
and expiration dates. This wastage not only squanders valuable resources such as water, land, and energy
but also exacerbates environmental degradation and contributes to greenhouse gas emissions.
Conversely, food insecurity persists as a pressing social issue, affecting individuals and families across diverse
socioeconomic backgrounds. Factors such as poverty, unemployment, inadequate access to nutritious food,
and systemic inequalities contribute to food insecurity, leaving millions of people uncertain about their next
meal.
In response to these challenges, numerous initiatives, programs, and policies have been implemented to
address food waste and hunger. However, gaps in coordination, distribution inefficiencies, and logistical
barriers continue to hinder effective solutions.
Recognizing the urgency of addressing both food waste and hunger, this project aims to develop a digital
solution that leverages technology to facilitate the donation of surplus food from donors to individuals and
organizations in need. By harnessing the power of mobile applications and online platforms, the project
seeks to streamline the process of food donation, enhance transparency and accountability, and foster
community engagement in combating food insecurity.
Through collaborative efforts and innovative solutions, we aspire to create a more equitable and sustainable
food system where surplus food is redirected to those who need it most, thereby alleviating hunger, reducing
food waste, and promoting social cohesion and solidarity within our communities.
1.2 Problems
The existing system of food donation, although well-intentioned, is often characterized by inefficiencies, lack
of coordination, and limited accessibility, hindering its ability to effectively address the dual challenges of
food waste and hunger. Several key issues persist within the current framework:
• Lack of Visibility:
Many potential donors and recipients are unaware of opportunities for food donation or face challenges
in locating and connecting with suitable partners. This lack of visibility contributes to missed
opportunities for surplus food redistribution and leaves many individuals and organizations without
access to much-needed resources.
• Fragmented Coordination:
Page 18
The process of food donation is often fragmented, with multiple stakeholders operating
independently and utilizing disparate communication channels. This fragmentation leads to
inefficiencies, duplication of efforts, and difficulty in coordinating donation logistics, resulting in
inequalities in access to food resources, delays and missed opportunities for timely food distribution.
• Limited Accessibility:
Existing donation platforms may lack user-friendly interfaces or may not be accessible to
individuals and organizations with limited technological literacy or resources. As a result,
marginalized communities and smaller-scale donors may face barriers to participation in food
donation initiatives, exacerbating inequalities in access to food resources.
• Accountability and Transparency:

Transparency and accountability in the donation process are essential for building trust among donors,
recipients, and other stakeholders. However, the lack of standardized reporting mechanisms and
feedback loops in the existing system may compromise transparency and hinder efforts to track and
measure the impact of food donation initiatives.
• Resource Allocation Challenges:

Limited resources, including funding, personnel, and transportation infrastructure, pose significant
challenges to the efficient operation of food donation programs. Without adequate support and
coordination, organizations may struggle to manage donation logistics, handle perishable items, and
ensure equitable distribution of resources to those in need.
Addressing these challenges requires a comprehensive, integrated approach that leverages

technology to streamline donation processes, improve visibility and accessibility, enhance
accountability, and optimize resource allocation. By developing a user-centric food donation app,
we aim to bridge existing gaps in the system and empower individuals, organizations, and
communities to contribute effectively to the fight against food waste and hunger.
Page 19
CHAPTER 2
EXISTING SOLUTIONS AND
PROPOSED SOLUTION
2. Existing Solutions and the Proposed Solution

2.1 Existing Solutions
The existing solutions for food donation typically involve manual processes, phone calls, or in-
person coordination between donors and recipient organizations. Some communities may have
local food banks or charitable organizations that facilitate food redistribution, but these systems
often rely on outdated communication methods and face challenges in efficiently matching supply
with demand.
Page 20
2.2 Proposed Solution
The proposed solution is the development of a comprehensive food donation app that leverages
technology to streamline the donation process and enhance accessibility, transparency, and
accountability. The app will offer the following features:
1. User-friendly Interface: The app will feature an intuitive, user-friendly interface that allows
donors to easily list surplus food items for donation and specify pickup times and locations.
2. Geolocation Services: The app will utilize geolocation services to facilitate efficient pickup
coordination between donors and recipient organizations, reducing logistical challenges and
optimizing resource allocation.
3. Real-time Notifications: The app will provide real-time notifications to donors and recipient
organizations about available donations, pickup requests, and delivery status updates, enabling
timely response and coordination.
5. Feedback Mechanisms: The app will incorporate feedback mechanisms to promote transparency
and accountability in the donation process, allowing recipients to provide feedback on the quality
and suitability of donated items and donors to evaluate the effectiveness of recipient organizations
in distributing donations.
6. Community Engagement: The app will serve as a platform for community engagement,
providing opportunities for users to participate in volunteering, fundraising, and advocacy efforts
to address food insecurity and promote sustainable food systems.
4. Donation Tracking: Users will have access to personalized profiles where they can track their
donation history, view feedback from recipients, and monitor the impact of their contributions
over time.
By implementing this food donation app, we aim to create a more efficient, transparent, and inclusive
system for food redistribution, empowering individuals and organizations to make meaningful
contributions to their communities while reducing food waste and alleviating hunger.
CHAPTER 3
Page 21
ANALYSIS
3. Analysis
3.1 Vision
The vision of this project is to create a more equitable and sustainable food system where surplus
food is redirected to those in need, fostering a culture of generosity, compassion, and community
engagement.
We envision a world where every individual has access to nutritious food, regardless of
socioeconomic status or geographic location. Through the power of technology and collective
action, we aspire to:
Alleviate Hunger:
Our project aims to reduce food insecurity and hunger by facilitating the efficient redistribution of
surplus food to individuals and families facing nutritional challenges. By connecting donors with
recipient organizations and individuals in need, we seek to ensure that no one goes to bed hungry.
Minimize Food Waste:

We strive to minimize food waste by diverting surplus food from landfills and redirecting it to those
who can benefit from it. By promoting donations of excess food from restaurants, grocery stores,
events, and households, we aim to mitigate environmental impact and conserve valuable resources.
Empower Communities:
Through our food donation app, we aim to empower individuals, businesses, and organizations to
actively participate in addressing food insecurity and promoting social justice in their
communities. By providing a platform for collaboration, education, and advocacy, we seek to
cultivate a sense of shared responsibility and collective impact.
3.2 Supplementary Specification
3.2.1 Functional Requirements

The functional requirements of Food Donation App are following:
User Registration and Authentication:
• Users should be able to create accounts and authenticate themselves securely.
• Different user roles such as donors, recipient organizations, and administrators
should be defined.
Page 22
Donation Listing and Management:
• Donors should be able to list surplus food items for donation, including details such as quantity,
type, expiration date (if applicable), and pickup location.
• Donors should have the option to edit or delete donation listings as needed.
Search and Matching:
• Recipient organizations should be able to search for available donations based on criteria such as
location, food type, and quantity.
• The app should facilitate matching between donors and recipient organizations based on their
preferences and logistical constraints.
Pickup Coordination:
• The app should provide functionality for scheduling and coordinating pickup times and
locations between donors and recipient organizations.
• Automated notifications should be sent to both parties to confirm pickup arrangements and
provide real-time updates.
User Profiles and History:

• Users should have personalized profiles where they can view their donation history, track pending
pickups, and manage account settings.
• Donation history should include details such as donation dates, recipient organizations, and
feedback received.
Feedback and Ratings:

• Recipient organizations should have the ability to provide feedback and ratings on donated items
and donor interactions.
• Donors should have the opportunity to rate recipient organizations based on their satisfaction with
the donation process.
Administrative and Features:
• Administrators should have access to a dashboard for managing user accounts, donation listings,
and system settings.
• Administrators should be able to review and moderate user-generated content, resolve disputes,
and enforce community guidelines.
Reporting and Analytics:

• The app should provide reporting and analytics features to track key metrics such as donation
volume, impact metrics, and user engagement.
• Reports should be customizable and exportable for analysis and reporting purposes.
Accessibility and Localization:
Page 23
• The app should be accessible to users with diverse abilities and should comply with
accessibility standards.
• Localization support should be provided to accommodate users from different regions and
linguistic backgrounds.
Security and Privacy:
• The app should implement robust security measures to protect user data, including
encryption, secure authentication, and data access controls.
• Privacy policies should be clearly communicated to users, and consent should be obtained
for the collection and use of personal information.
By incorporating these functional requirements, the food donation app will provide a user-
friendly, secure, and efficient platform for connecting donors with recipient organizations
and individuals in need, thereby facilitating the redistribution of surplus food and
contributing to the alleviation of food insecurity.
3.2.2 Nonfunctional Requirements

1. Performance:
• The app should be responsive and performing, even under heavy user traffic and load.
• Response times for key actions such as donation listing, search, and pickup coordination
should be minimal.
2. Reliability:
• The app should be highly reliable, with minimal downtime and service interruptions.
• Robust error handling and recovery mechanisms should be in place to ensure graceful
degradation in case of failures.
3. Scalability:
• The app should be designed to scale horizontally to accommodate growing user base and
increasing transaction volumes.
• Scalability measures such as load balancing, caching, and sharing should be implemented
to distribute workload efficiently across servers.
4. Security:
• The app should adhere to industry best practices for security and data protection.
• Measures should be implemented to prevent unauthorized access, data breaches, and
malicious attacks such as SQL injection and cross-site scripting (XSS).
5. Usability:
• The app should have a clean and intuitive user interface that is easy to navigate and
understand.
• Usability testing should be conducted with representative user groups to identify and
address usability issues.
6. Compatibility:
• The app should be compatible with a wide range of devices, browsers, and operating
systems.
• Compatibility testing should be performed to ensure consistent performance and
functionality across different platforms.
Page 24
7. Accessibility:
• The app should comply with accessibility standards such as WCAG (Web Content
Accessibility Guidelines) to ensure accessibility for users with disabilities.
• Support for screen readers, keyboard navigation, and alternative input methods should be
provided.
8. Maintainability:
• The app should be designed with modularity, encapsulation, and code readability in mind
to facilitate ease of maintenance and future enhancements.
• Documentation should be comprehensive and up-to-date to aid in system understanding
and troubleshooting.
9. Compliance:
• The app should comply with relevant laws, regulations, and industry standards pertaining
to data privacy, security, and food safety.
• Compliance with standards such as GDPR (General Data Protection Regulation) and food
safety regulations should be ensured.
10. Performance Efficiency:
• The app should optimize resource utilization and minimize energy consumption to promote
environmental sustainability.
• Efficiency metrics such as CPU usage, memory footprint, and network bandwidth should
be monitored and optimized where possible.
By addressing these non-functional requirements, the food donation app will not only provide a
robust and secure platform for food redistribution but also deliver a positive user experience that
fosters trust, engagement, and satisfaction among users.
3.2.3 Design and Implementation Constraints
• The project budget and resources may be limited, constraining the scope of development and feature
implementation.
• Availability of skilled developers, designers, and testers may also pose constraints on the project
timeline and execution.
• Compliance with data privacy regulations such as GDPR and HIPAA (Health Insurance Portability and
Accountability Act) may impose constraints on data collection, storage, and processing.
• Implementation of robust security measures, including encryption, access controls, and secure
authentication, may introduce complexity and overhead to the development process.
• Integration with external systems such as payment gateways, mapping services, and notification APIs
may be subject to constraints imposed by third-party providers' terms of service and API limitations.
• Compatibility issues and version dependencies may arise when integrating with legacy systems or
proprietary software used by partner organizations.
• Operation system: the development environment will be Android.
• Android-Based: the system will be Android based application.
• Designing: The design must be in Flutter.
• Language: Dart must be used.
Page 25
3.2.4 Glossary (Acronyms & Abbreviation)
The acronyms and abbreviations used throughout the SRS are following:
1. Dart: The programming language used for developing Flutter apps.
2. UI: User Interface.
3. UX: User Experience.
4. API: Application Programming Interface.
5. HTTP: Hypertext Transfer Protocol.
6. HTTPS: Hypertext Transfer Protocol Secure.
7. SDK: Software Development Kit.
8. IDE: Integrated Development Environment.
9. JSON: JavaScript Object Notation.
10. XML: Extensible Markup Language.
11. SSL: Secure Sockets Layer.
12. TLS: Transport Layer Security.
13. HTTP: Hypertext Transfer Protocol.
14. HTTPS: Hypertext Transfer Protocol Secure.
15. URL: Uniform Resource Locator.
16. Firebase: Google's mobile platform that helps you quickly develop high-quality apps.
17. Stateless Widget: A widget in Flutter that does not require mutable state.
18. Stateful Widget: A widget in Flutter that maintains state.
19. HTTP Client: A package in Dart for making HTTP requests.
20. Material Design: A design language developed by Google that combines principles of good design with
innovations in technology and science.
21. Cupertino Design: Design language developed by Apple for iOS apps, supported in Flutter for iOS-specific
designs.
22. SDK: Software Development Kit.
23. APK: Android Application Package.
24. IPA: iOS App Store Package.
25. OEM: Original Equipment Manufacturer.
26. CPU: Central Processing Unit.
Page 26
27. GPU: Graphics Processing Unit.
28. RAM: Random Access Memory.
29. VCS: Version Control System.
30. CI/CD: Continuous Integration/Continuous Deployment.
3.3 Software Architecture

In the following diagram, we can see the system’s organization/ architecture/ structure.
• Presentation, application and storage tier is being used for the system.
• Having one main database for all activities related to the complaint system (registration,
filing complaint, sending messages, setting statuses, giving feedback etc).
• The internet is being used as the source to use this web system. Without internet, system
cannot be accessed.
FIGURE 1: Software Architecture
3.4 Screen Shots
Page 27
User Interface Home
Page:
FIGURE-2: Home Page
About Us Page:
Page 28
FIGURE-3: About Us Page
Laws & Policies Page:
Page 29
FIGURE-4: Laws & Polices Page
Location Page:
Page 30
FIGURE-5: Location Page
Registration Page
Page 31
FIGURE-6: Registration Page
Login Page
Page 32
FIGURE-7: Login Page
Privacy Policy Page
Page 33
FIGURE-8: Privacy Policy Page
3.5 Use Case Diagrams
A use case is a list of actions or event steps typically defining the interactions between a role
(known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal.
The actor can be a human or other external system. The actors that are used in the use case of
automated complaint system are:
 Admin
Page 34
 Deputy Commissioner (DC)
 Assistant Commissioner (AC)
 Tehsildar
 Employees (Naib, Gadawar and Patwari).
 Citizens
 System
Where the officers of Revenue department: AC, Tehsildar and Employees can act as officers as
well as users (complainants) in different situations. That’s why the next portion describes the
diagrams related to admin and user sides. The tabular scenarios of all the use cases are also given
in this document.
Use Case Diagrams & Tables Related To Admin Side
3.5.1 Use Case 01_Admin_Log_in
Only authorize user can login to the system with authorize user name and password.
Page 35
FIGURE-9: Use case (Admin Login)
Identifier UC-1
Priority High
Purpose To access the admin panel.
Pre-conditions System Running Perfectly.
Post-conditions Successfully Login.
Typical Course of Action
S# Actor Action System Response
• System will check the CNIC, password
 Admin select role and enter and captcha.
1 login details. • System allows the user to login if the
entered data is valid.
Alternate Course of Action
 If the login details are  System will not allow the user to login and
1
invalid show the retry button.
Table 1: Admin_Log_In
Page 36
Use Case
3.5.2 02_Admin_Transfer_Complaints
Admin transfers complaints to the relevant authorities. If the complaint is against AC, it is
transferred to DC, if against Tehsildar then it is transferred to AC, if against employees
(Patwari, Gadawar or Naib/ Tehsildar) then it is transferred to the Tehsildar.
FIGURE-10: Use case (Admin Transfer Complaints)
Identifier UC-2
Purpose To Transfer Complaints to the related authority.
Priority High
Pre-conditions Admin must receive complaints before transfer.
Successfully Transfer Complaints to the associated
Post-conditions
authority.
• Admin Click on Transfer  System successfully transfers
complaint Option. complaints.
1 • Admin select authority from
category.
Table 2: Admin_Transfer_Complaints
Page 37
Use Case
3.5.3 03_Admin_Register_Users
FIGURE-11: Use case (Admin Register Users)
Identifier UC-3
Purpose To Register new government employees.
Priority Medium
Pre-conditions Admin must login to register a new user.
Post-conditions Successfully Register Users.
• Admin Click on Register User  System successfully register
Option. user.
1 • Admin enter the details related
to registration.
Table 3: Admin_Register_Users
Page 38
Use Case
3.5.4 04_Admin_Complete
FIGURE-12: Complete Use case (Admin)
Identifier UC-4
Purpose To Perform their tasks
Priority High
Pre-conditions Admin must login to perform different tasks.
Post-conditions Successfully perform activities.
• Admin can view complaints  System successfully transfers
from Notification. complaints to the related
1 • Admin can forward authority.
complaints.
 Admin can also view feedbacks  System would show feedback
received from the successfully.
2
Complainant after completion
of complaint.
 Admin can also manage other’s  System successfully saved
3
profile and then logout. changes
Table 4: Admin_Complete
Page 39
Use Case
3.5.5 05_DC_Log_in
FIGURE-13: Use case (DC Login)
Identifier UC-5
Purpose To Receive complaints and to perform further execution
Priority High
4 DC select role and and captcha.
1 enter login details.
• System allows the user to login if the
 System will not allow the user to login
 If the login details are
1 and
invalid
Shows the retry button.
Table 5: DC_Log_In
Page 40
Use Case
4.1.1 06_DC_Update_Status
FIGURE-14: Use Case (DC Update Complainant Status)
Identifier UC-6
Purpose To Update complainant status.
Priority High
Pre-conditions Must receive complaint before updating status
Post-conditions Successfully update status.
 User send message related to  System allows the user to
1 status
( on work or closed) send status.
Table 6: DC_Update_Status
Page 41
Use Case
4.1.2 07_DC_Complete
FIGURE-15: Complete Use Case (DC)
Identifier UC-7
Purpose To Perform duty.
Priority High
Pre-conditions User must login for processing.
Post-conditions Successfully operate tasks and Logout.
 DC Click notification option to  System shows complaint
1 view complaint messages and messages and sent messages.
send messages.
 DC clicks on update status option  System successfully updates
2 and then updates complainant complainant status
status.
Table 7: DC_Complete
Page 42
Use Case
4.1.3 08_AC_Log_in
FIGURE-16: Use case (AC Login)
Identifier UC-8
Priority High
 AC select role and • System will check the CNIC, password
enter login and captcha.
1
details. • System allows the user to login if the
 If the login details  System will not allow the user to login and
1
are invalid show the retry button.
Table 8: AC_Log_In
Page 43
Use Case
4.1.4 09_AC_Update_Status
FIGURE-17: Use Case (AC Update Complainant Status)
Identifier UC-9
Priority High
 User send message related  System allows the user to
1 to status
Table 9: AC_Update_Status
Page 44
Use Case
4.1.5 10_AC_Complete
FIGURE-18: Complete Use Case (AC)
Identifier UC-10
Purpose To Perform tasks.
Priority High
 AC Click inbox Option to view  System shows complaint
1 complaint messages and send messages and sent messages.
messages.
 AC clicks on update status option  System successfully updates
2 and then updates complainant complainant status
status.
Table 10: AC_Complete
Page 45
Use Case
4.1.6 11_Tehsildar_Log_in
FIGURE-19: Use Case (Tehsildar Login)
Identifier UC-11
Priority High
• System will check the CNIC,
 Tehsildar select role and enter password and captcha.
1 login details. • System allows the user to
login if the entered data is
valid.
5 System will not allow the user to
1  If the login details are invalid login and show the retry button
Table 11: Tehsildar_Log_In
Page 46
Use Case
5.1.1 12_Tehsildar_Update_Status
FIGURE-20: Use case (Tehsildar Update Status)
Identifier UC-12
Priority High
 User send message related to  System allows the user to
1 status
Table 12: Tehsildar_Update_Status
Page 47
Use Case
5.1.2 13_Tehsildar_Complete
FIGURE-21: Complete Use case (Tehsildar)
Identifier UC-13
Priority High
 Tehsildar Click inbox Option to  System shows complaint
1 view complaint messages and messages and sent
send messages. messages.
 Tehsildar clicks on update status  System successfully updates
2 option and then updates complainant status
complainant status.
Table 13: Tehsildar_Complete
Page 48
Use Case
5.1.3 14_Employee_Log_in
FIGURE-22: Use Case (Employee Login)

Identifier UC-14
Priority High
 Employee select role and enter password and captcha.
1 login details • System allows the user to
valid.
6 System will not allow the user
1  If the login details are invalid to login and show the retry
button
Table 14: Employee_Login
Page 49
Use Case
6.1.1 15_Employee_Complete
FIGURE-23: Complete Use case (Employee)
Identifier UC-15
Priority High
 Employee Click on notification  System shows complaint
1 Option to view complaint messages.
messages.
Table 15: Employee_Complete
Page 50
Use Case Diagrams & Tables Related To Complainants
6.1.2 Use Case 16_AC_Log_in
FIGURE-24: Use Case (AC Login)
Identifier UC-16
Priority High
password and captcha.
 AC enter login details • System allows the user to
1
valid.
7 System will not allow the user to
1  If the login details are invalid login and show the retry button
Table 16: AC_Log_In
Page 51
7.1.1 17_AC_Register_Complaints
FIGURE-25: Use Case (AC Register Complaint)
Identifier UC-17
Purpose To Register Complaints
Priority Medium
Pre-conditions AC must login to register Complaints
Post-conditions Successfully Register Complaint.

• AC Click on Register Complaint  System successfully
Option sent complaint.
1 • AC fill the form to register complaint
 AC enter textual data.
Table 17: AC_Register_Complaints
Page 52
Use Case
7.1.2 Use Case 18_AC_Give_Feedback
FIGURE-26: Use Case (AC Give Feedback)
Identifier UC-18
Purpose To Give feedback.
Priority Medium
Must login and processing related to complaints must be
Pre-conditions
closed.
Post-conditions Successfully Give Feedback.
 System successfully sent
 AC clicks on feedback option to give
1 feedback.
feedback.
Table 18: AC_Give_Feedback
Page 53
7.1.3 19_AC_Complete
FIGURE-27: Complete Use Case (AC)
Identifier UC-19
Purpose To file complaints.
Priority Medium
Pre-conditions AC must login to file complain.
Post-conditions Successfully Register complain
 AC Click on register complaint option  System successfully sent complains.
1
to file a complaint.
 AC can check status from status  System allow user to view all.
2 option and view messages from
messages option.
 AC can also give feedback after  System successfully saved changes.
3
complaint completion
Table 19: AC_Complete
Page 54
Use Case
7.1.4 20_Tehsildar_Log_in
FIGURE-28: Use Case (Tehsildar Login)
Identifier UC-20
Priority High
 Tehsildar select role • System will check the CNIC, password
and enter login and captcha.
1
details • System allows the user to login if the
 If the login details are 8 System will not allow the user to login
1
invalid and show the retry button
Table 20: Tehsildar_Log_In
Page 55
Use Case
8.1.1 21_Tehsildar_Register_Complaints
FIGURE-29: Use Case (Tehsildar Register Complaint)
Identifier UC-21
Priority Medium
Pre-conditions Tehsildar must login to register Complaints
Post-conditions Successfully Register Complaint.
• Tehsildar Click on Register Complaint  System successfully
Option sent complaint.
1 • Tehsildar fill the form to register
complaint
• Tehsildar enter textual data.
Table 21: Tehsildar_Register_Complaints
Page 56
Use Case
8.1.2 22_Tehsildar_Give_Feedback
FIGURE-30: Use Case (Tehsildar Give Feedback)
Identifier UC-22
Priority Low
Pre-conditions
closed.
 Tehsildar clicks on feedback option to
1 feedback.
give feedback.
Table 22: Tehsildar_Give_Feedback
Page 57
Use Case
8.1.3 23_Tehsildar_Complete
FIGURE-31: Complete Use Case (Tehsildar)
Identifier UC-23
Priority High
 Tehsildar Click on register  System successfully sent
1 complaint option to file a complains.
complaint.
 Tehsildar can check status  System allow user to view all.
2 from status option and view
messages.
Table 23: Tehsildar_Complete
Page 58
Use Case
8.1.4 24_Employee_Log_in
FIGURE-32: Use Case (Employee Login)
Identifier UC-24
To Receive complaints and to perform further
Purpose
execution
Priority High
 Employee select role • System will check the CNIC,
and enter login password and captcha.
1
details • System allows the user to login if the
 If the login details are 9 System will not allow the user to login
1 and show the retry button
invalid
Table 24: Employee_Log_In
Page 59
Use Case
9.1.1 25_Employee_Register_Complaints
FIGURE-33: Use Case (Employee Register Complaint)
Identifier UC-25
Priority Medium
Pre-conditions Employee must login to register Complaints
Post-conditions Successfully Registered Complaint.
• Employee Click on  System successfully
Register sent complaint.
Complaint Option
1
• Employee fill the form to register
complaint
• Employee enter textual data.
Table 25: Employee_Register_Complaints
Page 60
Use Case
9.1.2 26_Employee _Give_Feedback
FIGURE-34: Use Case (Employee Give Feedback)
Identifier UC-26
Priority Low
Pre-conditions
closed.
 Employee clicks on feedback
1 feedback.
option to give feedback.
Table 26: Employee_Give_Feedback
Page 61
Use Case
9.1.3 27_ Employee_Complete
FIGURE-35: Complete Use Case (Employee)
Identifier UC-27
Priority High
 Employee Click on register  System successfully sent
1 complaint option to file a complains.
complaint.
 Employee can check status  System allow user to view all.
from status option and view
2
messages from message
option.
Table 27: Employee_Complete
Page 62
Use Case
9.1.4 28_Citizen_Sign_Up
FIGURE-36: Use Case (Citizen Signup)
Identifier UC-28
Purpose For Registration.
Priority High
• System will check all details
 Citizen enter SignUp
1 • System allows the user to Sign-Up
details
if the entered data is valid.
 Citizen enter Sign-Up 10 System would not response.
1
details
Table 28: Citizen_Sign_Up
Page 63
Use Case
10.1.1 29_Citizen_Log_in
FIGURE-37: Use Case (Citizen Login)
Identifier UC-29
Purpose To access account.
Priority High
Pre-conditions Citizen must be Registered.
• Citizen select role and and captcha.
enter login details
• System allows the user to login if the
1 • If the login details are entered data is valid.
invalid
• System will not allow the user to login
and show the retry button
 If the login details are 11 System will not allow the user to login and
1 show the retry button
invalid
Table 29: Citizen_Log_In
Page 64
Use Case
11.1.1 30_Citizen_Edit_Profile
FIGURE-38: Use Case (Citizen Edit Profile)

Identifier UC-30
Purpose To Edit profile.
Priority Low
Pre-conditions Citizen must login to Managed Profile.
Post-conditions Successfully Save Changes.
• Citizen Click on Manage Profile  System successfully save
1 Option changes.
• Citizen Edit their information
Table 30: Citizen_Edit_Profile
Page 65
Use Case
11.1.2 31_Citizen_Change_Password
FIGURE-39: Use Case (Citizen Change Password)
Identifier UC-31
Purpose To Change Password.
Priority Low
Pre-conditions Citizen must enter current password to change password.
Post-conditions Successfully Save Changes.

• Citizen Click on Change  System successfully save
Password Option changes.
1
• Citizen type previous/ current
password to change password.
Table 31: Citizen_Change_Password
Page 66
Use Case
11.1.3 32_Citizen_Register_Complaint
FIGURE-40: Use Case (Citizen Register Complaint)
Identifier UC-32
Priority High
Pre-conditions Citizen must login to register Complaints
Post-conditions Successfully Registered Complaints.
• Citizen Click on Register Complaint  System successfully
Option send complaint.
1 • Citizen fill the form to register
complaint
• Citizen enter textual data.
Table 32: Citizen_Register_Complaints
Page 67
11.1.4 Use Case 32_Citizen_Give_Feedback
FIGURE-41: Use Case (Citizen Give Feedback)
Identifier UC-33
Must login and processing related to complaints must
Pre-conditions
be closed.
 Citizen clicks on feedback
1 feedback.
option to give feedback.
Table 33: Citizen_Give_Feedback
Page 68
11.1.5 Use Case 33_Citizen_Complete
FIGURE-42: Use Case (Citizen Complete)
Identifier UC-34
Purpose To file complaints and then perform further activities.
Pre-conditions Citizen must Sign-up or Login to file complain.
Post-conditions Successfully Register complain and perform other
activities.
 Citizen Click on register complaint  System allow the user to file
1 complain
option to file a complain
 Citizen can check status from status  System shows notification
2 option and view messages from option.
messages.
 System shows feedback
 Citizen can also give feedback after
3 option after the complaint
complaint completion
completion
 Citizen can also manage their profile  System successfully saved

4 changes.
and then logout.
Table 34: Citizen_Complete
Page 69
CHAPTER 4
DESIGN
4. Design
4.1 Database Diagram
A Schema is a pictorial representation of the relationship between the database tables in the
database that is created. A database schema is the blueprints of your database, it represents the
description of a database structure, data types, and the constraints on the database. And designing
database schemas is one of the very first and important steps to start developing any
software/website.
The database diagram of automated complaint system is as follows:
Database Diagram:
Page 70
FIGURE-43: Database Design
4.2 Entity Relationship Diagram (ERD)
Entity Tables:
Admin:
Page 71
Deputy Commissioner (DC):
Complaint Status:
Officers:
Tehsildar and Assistant Commissioner (AC) are called officers here as both have the same
attributes and same tasks.
Page 72
Employee:
Naib Tehsildar, Patwari and Gadawar are employees here. Who have the same attributes and same
tasks to perform using this system.
Citizen:
Complaint Message:
Page 73
Complaint:
Feedback:
FIGURE-44: Entity Tables
ER Diagram
An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical
representation of an information system that depicts the relationships among people, objects,
Page 74
places, concepts or events within that system. ER modeling helps you to analyze data
requirements systematically to produce a well-designed database. So, it is considered a best
practice to complete ER modeling before implementing your database. Entities can be thought
of as nouns. Examples: a computer, an employee, a song, a mathematical theorem, etc. A
relationship captures how entities are related to one another
ERDs model an organization’s data storage requirements with three main components: entities,
attributes, and relationships.
• Entities:
Entities which represent people, places, items, events, or concepts.
• Attributes:
Attributes which represent properties or descriptive qualities of an entity. These are also known as
data elements.
• Relationships:
Relationships which represent the link between different entities.
The ERD of proposed system consists of ten entities:
 Admin
 DC
 Officers
 Employee
 Citizen
 Complaint
 Verification Message
 Complaint Status
 Complaint Message
 Feedback
ERD:
Page 75
FIGURE-45: ER Diagram
4.3 Data Flow Diagram
DATA FLOW DIAGRAM

LEVEL 0
Page 76
FIGURE-46: Level-0
LEVEL 1
Page 77
FIGURE-47: Level-1
4.4 Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
Purpose of Activity Diagrams
Page 78
The purpose of an activity diagram can be described as − 
Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.
Page 79
FIGURE-48: Activity Diagram
Page 80
4.5 State Transition Diagram
A state [7] diagram is used to represent the condition of the system. It’s a behavioral diagram
and it represents the behavior using state transitions. State diagrams are also referred to as
State machines and State-chart Diagrams. These terms are often used interchangeably. So
simply, a state diagram is used to model the dynamic behavior of a class in response to time
and changing external stimuli. We prefer to model the states with three or more states.
Uses of state Transition diagram

• We use it to state the events responsible for change in state (we do not show what processes cause those
events).  We use it to model the dynamic behavior of the system.
FIGURE-49: State Transition Diagram
Page 81
4.6 Sequence diagram
A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system under development.
Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects
that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in
the order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.
Sequence Diagram Related to Admin Side
Sequence Diagram (Admin Login)
FIGURE-50: Sequence Diagram (Admin: Login)
Page 82
Sequence Diagram (Admin
View Complaints)
FIGURE-51: Sequence Diagram (Admin: View Complaints)
Sequence Diagram (Admin Forward Complaints)
FIGURE-52: Sequence Diagram (Admin: Forward Complaints)
Page 83
Register Users)
FIGURE-53: Sequence Diagram (Admin: Register Users)
Logout)
Page 84
FIGURE-54: Sequence Diagram (Admin: Logout)
Page 85
Page 86
Sequence Diagram (DC
Login)
FIGURE-55: Sequence Diagram (DC: Login)
View Complaints)
Page 87
FIGURE-56: Sequence Diagram (DC: View Complaints)
Sequence Diagram (DC Update Complaint Status)
FIGURE-57: Sequence Diagram (DC: Update Complaint Status)
Page 88
Send Messages)
FIGURE-58: Sequence Diagram (DC: Send Message)
Sequence Diagram (DC Logout)
FIGURE-59: Sequence Diagram (DC: Logout)
Page 89
Page 90
Sequence Diagram (AC
Login)
FIGURE-60: Sequence Diagram (AC: Login)
Page 91
View Complaints)
FIGURE-61: Sequence Diagram (AC: View Complaints)
Sequence Diagram (AC Update Complaints Status)
FIGURE-62: Sequence Diagram (AC: Update Complaints Status)
Page 92
Send Message)
FIGURE-63: Sequence Diagram (AC: Send Message)
Sequence Diagram (AC Logout)
Page 93
FIGURE-64: Sequence Diagram (AC: Logout)
Page 94
Sequence Diagram (Tehsildar
Login)
FIGURE-65: Sequence Diagram (Tehsildar: Login)
View Complaints)
Page 95
FIGURE-66: Sequence Diagram (Tehsildar: View Complaints)
Sequence Diagram (Tehsildar Update Complaint Status)
FIGURE-67: Sequence Diagram (Tehsildar: Update Complaint Status)
Send Messages)
Page 96
FIGURE-68: Sequence Diagram (Tehsildar: Send Message)
Sequence Diagram (Tehsildar Logout)
FIGURE-69: Sequence Diagram (Tehsildar: Logout)
Page 97
Page 98
Sequence Diagram
(Employee Login)
FIGURE-70: Sequence Diagram (Employee: Login)
Page 99
Sequence Diagram
(Employee View Complaints)
FIGURE-71: Sequence Diagram (Employee: View Complaints)
Sequence Diagram (Employee Logout)
FIGURE-72: Sequence Diagram (Employee:Logout)
Page 100
Sequence Diagram
Related To User Side
Sequence Diagram (AC Login)
FIGURE-73: Sequence Diagram (AC: Login)
Page 101
Sequence Diagram
Page 102
Register Complaints)
FIGURE-74: Sequence Diagram (AC: Register Complaint)
View Complaint Status)

Page 103
FIGURE-75: Sequence Diagram (AC: View Complaint Status)
Sequence Diagram (AC Give Feedback)
FIGURE-76: Sequence Diagram (AC: Give Feedback)
View Message)
Page 104
FIGURE-77: Sequence Diagram (AC: View Messages)
Sequence Diagram (AC Logout)
FIGURE-78: Sequence Diagram (AC: Logout)
Page 105
Login)
FIGURE-79: Sequence Diagram (Tehsildar: Login)
Register Complaints)
Page 106
FIGURE-80: Sequence Diagram (Tehsildar: Register Complaint)
View Complaint Status)
Page 107
FIGURE-81: Sequence Diagram (Tehsildar: View Complaint Status)
Sequence Diagram (Tehsildar Give Feedback)
FIGURE-82: Sequence Diagram (Tehsildar: Give Feedback)
View Message)
Page 108
FIGURE-83: Sequence Diagram (Tehsildar: View Messages)
Sequence Diagram (Tehsildar Logout)
FIGURE-84: Sequence Diagram (Tehsildar: Logout)
Page 109
Sequence Diagram
(Employee Login)
FIGURE-85: Sequence Diagram (Employee: Login)
Page 110
Sequence Diagram
(Employee Register Complaints)
FIGURE-86: Sequence Diagram (Employee: Register Complaint)
Page 111
Sequence Diagram (Employee View Complaint Status)
FIGURE-87: Sequence Diagram (Employee: View Complaint Status)
Sequence Diagram (Employee Give Feedback)
Page 112
Sequence Diagram
FIGURE-88: Sequence Diagram (Employee: Give Feedback)
(Employee View Message)
FIGURE-89: Sequence Diagram (Employee: View Messages)
Sequence Diagram (Employee Logout)
Page 113
FIGURE-90: Sequence Diagram (Employee: Logout)
Page 114
Sequence Diagram
(Citizen Login)
FIGURE-91: Sequence Diagram (Citizen: Login)
(Citizen Edit Profile)

Page 115
Sequence Diagram
FIGURE-92: Sequence Diagram (Citizen:Edit Profile)
(Citizen Change Password)
Page 116
Sequence Diagram
FIGURE-93: Sequence Diagram (Citizen: Change Password)
Page 117
Sequence Diagram (Citizen Register Complaints)
FIGURE-94: Sequence Diagram (Citizen: Register Complaint)
Page 118
Sequence Diagram (Citizen View Complaint Status)
FIGURE-95: Sequence Diagram (Citizen: View Complaint Status)
Sequence Diagram (Citizen View Messages)
FIGURE-96: Sequence Diagram (Citizen: View Messages)
Sequence Diagram (Citizen Give Feedback)
Page 119
FIGURE-97: Sequence Diagram (Citizen: Give Feedback)
Sequence Diagram (Citizen Logout)
FIGURE-98: Sequence Diagram (Citizen: Logout)
Page 120
CHAPTER 5
TESTING
5. TESTING
5.1 Introduction
Web testing [9] is a software testing practice to test the websites or web applications for
potential bugs. It's a complete testing of web-based applications before making live. A web-
based system needs to be checked completely from end-to-end before it goes live for end users.
By performing website testing, an organization can make sure that the web-based system is
functioning properly and can be accepted by real-time users. We have been applied the
following different testing techniques on Automated Complaint System to ensure the quality and
efficiency of system.
Functionality Testing:
The below are some of the checks that are performed but not limited to the below list:
• Verify there is no invalid redirects.
• First check all the validations on each field.
• Wrong inputs to perform negative testing.
• Verify the workflow of the system.
• Verify the data integrity.
Usability testing:
To verify how the application is easy to use with.
• Test the navigation and controls.
• Content checking.
Page 121
• Check for user intuition.
Interface testing:
Performed to verify the interface and the dataflow from one system to other.
5.2 Test plan

The Test Plan describes the scope, approach, resources and schedule of intended test activities.
The test plan will keep track of possible tests that will be performed on ACS.
5.2.1 Purpose
To prescribe the scope, approach, resources, and schedule of the testing activities. To identify
the items being tested, the features to be tested, the testing tasks to be performed, and the risks
associated with this plan.
5.2.2 Outline
Structure of our test plan is as follows: a)
Test plan identifier
b) Introduction
c) Test items
d) Features to be tested
e) Approach
f) Item pass/fail criteria
g) Suspension criteria and resumption requirements
h) Environmental needs
i) Responsibilities
j) Staffing and training needs
k) Schedule
l) Risks and contingencies
m) Approvals
5.2.2.1 Test plan identifier

It uniquely identifies the test plan. Test plan identifier is basically the ID assign to each test
case.
Page 122
The test plan identifier for User Registration is TC-1.
5.2.2.2 Introduction
All modules of our system will be tested. All validation checks will be tested through STLC
(Software Testing Life Cycle).
5.2.2.3 Test items

It is a key section for defining the SCOPE of a Test Plan, here we will specify in outline the
items, which will be systems and subsystems, that are to be tested. It include reports and
documentation as well. Major test items are:
Items to be tested
Login Page
Registration Page
Edit Profile
Transfer Complaints
Register Complaint
Complaint Status
Messages
Feedback
Table 35- Items to be tested
Items not to be tested

About Us Page
Location Page
Privacy Polices Page
Laws and Polices Page
Table 36- Items not to be tested

Related Project Documentation:
This lists the project documentation which relates to ACS to be tested. These documents are
those which enable tests to be designed and run.
 Requirements Specification
 Design Documents
Page 123
5.2.2.4 Features to be tested
Here we will define which of the features of the ACS will be tested here. we need to identify
the functionality that are to be tested in each module or sub module as these are what delivers
value to the team.
Items being Tested Features being Tested

Registration  Valid data while registration
 Invalid data while registration
 Empty fields while registration
Login  Valid data while Login
 Invalid data while Login
 Empty fields while Login
 Attempt to login while not being

registered
 Edit User Profile

Edit Profile
 Change Password
 Accept complaint
Transfer Complaint
 Reject complaint
 Register a complaint
Register Complaint
 Update complaint status

Complaint Status
 View complaint status
 Send complaint message

Messages
 View complaint message
 Give feedback in the form of stars

Feedback
Table 37- Features to be tested

5.2.2.5 Approach
First of all, the Testing Engineer will take over the role of an end-user and will test the ACS to
identify any unexpected behavior or bug. Test Engineer will use test plans, test cases, or test
scenarios to test the system to ensure the completeness of testing.
Page 124
The technique we are going to adopt for testing are:
 Unit Testing
 Black Box Testing
The goal of unit testing is to isolate each part of the program and show that individual parts are
correct in terms of requirements and functionality. Black Box testing is defined as the testing of
combined parts of an application to determine if they function correctly. We applied these
testing techniques to check whether each module of ACS work properly when combine with
other module or not. Normally this type of testing will be performed by developers before the
setup is handed over to the test Engineer to formally execute the test cases.
5.2.2.6 Item pass/fail criteria

For each test in each category, the operational events should take place in the proper sequence
and each of the system entity should be left in the appropriate state following the operation.
Either pass or fail. If any test case will fail, we will write code to pass the test and again that
test case will be tested.
5.2.2.7 Suspension criteria and resumption requirements
If number or types of defects reach a point where the follow-on testing has no value, it will
make no sense to continue testing. In this case, system will be send for further reviews and
development.
In our case, we observe suspension 
Error in php code.
 Database Error.
Resumption Requirements:
Testing of the ACS will resume from the beginning when the reasons for suspension of testing
have been determined, have been corrected, and new versions of the System Entities have been
submitted to the testing group.
5.2.2.8 Environmental needs
The following elements are required to support the overall testing effort at all levels within the
project:
Page 125
Hardware Requirements
• System: Pentium 3 or higher
• Device: PC, Cell phone, Ipad, Laptop
• CPU: Must be 1 Ghz processor
• RAM: greater than 256 MB
• Internet: Required every time; should be > than 1MB.
• Hard Disk Space: 1 GB
• Input: Mouse and keyboard
• Output: Display screen
Software Requirements
• OS: Windows 7, windows 8.1 or windows 10
• Web Browser: Internet explorer, Google Chrome, Mozilla.
• Tool: Xampp Server
5.2.2.9 Responsibilities
The developing team of “Automated Complaint System” is responsible for managing,
designing, preparing, and executing the test cases.
Testing Module Performed By

Test Planning ABC, XYZ, LMN
Test Document ABC, XYZ
Test Writing ABC

Test Execution XYZ
Table 38- Responsibilities

Page 108
5.2.2.10 Staffing and training needs.
Testing was performed and executed by ABC. The other two members XYZ and LMN are
also part of the testing team in one way or another. As testing document and test plans were
done in their presence.
Technical assistance was also provided by our respected supervisor Prof. -------------.
5.2.2.11 Schedule
Testing was conducted at NCBA& E Gujrat Campus, July 5 2019.
5.2.2.12 Risks and contingencies
 The scope of the plan might be changed.
 The test schedule and development schedule might move out an appropriate number of
days.
 All stated features might not be tested.
 The system will be rejected by the end user if they found it less interactive and difficult to
use after adding new feature.
5.2.2.13 Approvals
This test plan is being approved by our respected supervisor Prof. --------.
__________________
Supervisor’s Signature
5.3 Test Case Specification 5.3.1 Purpose
To define a test case identified by a test plan.
5.3.2 Test case specification identifier
Following are the test case identifiers that will be used in our test:
Serial No. Testing Features Test Case Identifier
1 Valid data while TC-1
registration
2 Empty field in registration TC-2
form
3 Invalid data TC-3

while
registration
4 Valid data while login TC-4
5 Empty field in login form TC-5
Page 109
6 Invalid data while login TC-6
7 Attempt to login while not TC-7
being registered
8 File a complaint TC-8

9 Edit Profile TC-9
10 Change Password TC-10
11 View Complaint Status TC-11
12 Feedback TC-12
13 Admin transfer Complaints TC-13
14 Accepting complaint TC-14
criteria
15 Reject complaint criteria TC-15

16 Register new officer TC-16
17 Send message TC-17
18 Complainant view TC-18
messages
Table 39-Test case Identifiers
5.4 Test Cases [10]

5.4.1 Test cases for User side:
User registration
Identifier TC-1
Priority High priority
1. User must have internet access.
Related requirement(s) 2. System must be running successfully.
3. User must open ‘Register’ page.
Related use-case(s) Citizen_Sign_Up
Testing is applied on registration form fields to check when new
Short description user enters valid data in all form fields then user must be registered
successfully.
2. ACS (Automated Complaint System) must be running
Pre-condition(s) successfully.
3. Register page must be opened.
Page 128
Input data Correctly enter data in all fields of registration form by user.
1. User open UI successfully.
2. Navigate to Register page (new user is not register).
3. User enters valid Full Name, valid CNIC*, valid Email, valid
Detailed steps
Password* and valid Contact No* in registration form.
4. Click on REGISTER button.
Expected result(s) User must be registered.

Post-condition(s) User is registered successfully.
Table 40-TC-1
Identifier TC-2
Testing is applied on registration form fields to check if user does
Short description not fill “Full Name” form filed then which error message will be
shown to user by system.
User enters valid CNIC*, valid Email, valid Password* and valid
Input data
Contact No*.
2. Navigate to Register page (new user is not registered).
3. User enters valid CNIC*, valid Email, valid Password* and
Detailed steps
valid Contact No* in registration form fields.
Expected result(s) System must show a validation error.

Post-condition(s) System shows a validation message of “Please fill out this field”.
Table 41-TC-2
Identifier TC-3
Short description Testing is applied on registration form fields to check if user enters
Page 130
invalid CNIC number i.e. write CNIC with less than 13 numbers
then an error message must be shown to user to enter data that is
matched with the format.
User enters valid Full Name*, invalid CNIC*, valid Email, valid
Input data
3. User enters valid Full Name*, invalid CNIC*, valid Email,
Detailed steps
valid Password* and valid Contact No*.
Expected result(s) System must show some pop up or message to write valid data.
System shows a validation message of “Please match the requested
Post-condition(s)
Format”.
Table 42-TC-3
Identifier TC-4
Testing is applied on registration form fields to check if user enters
invalid CNIC number i.e. write CNIC with greater than 13
Short description
numbers then an error message must be shown to user to enter data
that is matched with the format.
User enters valid Full Name*, invalid CNIC*, valid Email, valid
Input data
3. User enters valid Full Name*, valid CNIC*, valid Email,
Detailed steps
valid Password* and valid Contact No*.

Post-condition(s)
Format”.
Page 131
Table 43-TC-4
Identifier TC-5
password that does not match with the given criteria (which is
Short description password should be At least one number, one small and capital
letter and should be 8 or more characters*) then what type of error
will be shown by system to user.
User enters valid Full Name*, valid CNIC*, valid Email, invalid
Input data
Password* and valid Contact No*.
3. User enters valid Full Name*, valid CNIC*, valid Email,
Detailed steps invalid Password* and valid Contact No* in registration form
fields.

Post-condition(s)
Format”.
Table 44-TC-5
Identifier TC-6
Short description phone number in “Contact No*” field with less than 11 numbers
then an error message must be shown by system to user.
Page 132
User enters valid Full Name*, valid CNIC*, valid Email, valid
Input data
Password* and invalid Contact No*.
Detailed steps 3. User enters valid Full Name*, valid CNIC*, valid Email, valid
Password* and invalid Contact No* in registration form fields.
Post-condition(s)
Format”.
Table 45-TC-6
Identifier TC-7
Short description phone number in “Contact No*” field with greater than 11
numbers then an error message must be shown by system to user.
Pre-condition(s) 1. User must have internet access.
Input data
Password* and invalid Contact No* in registration form.
Post-condition(s)
Format”.
Table 46-TC-7
Identifier TC-8
Related requirement(s) 1. User must have internet access.
2. System must be running successfully.
Page 133
Short description invalid email in “Email” field then an error message must be
shown by system to user.
Pre-condition(s) 1. User must have internet access.
successfully.
User enters valid Full Name*, valid CNIC*, invalid Email, valid
Input data
Password* and valid Contact No*.
3. User enters valid Full Name*, valid CNIC*, invalid Email,
Detailed steps
valid Password* and valid Contact No* in registration form
fields.
Post-condition(s)
Format”.
Table 47-TC-8
Identifier TC-9
Short description alphabets in Contact No* field then an error must be shown by
system to user.
Input data
Expected result(s) An error to enter valid Contact No occur.
Post-condition(s)
Format”.
Page 134
Table 48-TC-9
User login
Identifier TC-10
Related requirement(s)
3. User must be registered before login into system.
4. User must open User Login page.
Related use-case(s) Citizen_Log_In
Testing is applied on Login page to check when user leave both of
the fields of login form empty, no captcha is entered by user and
Short description
no role is selected then which error will be shown by system to
user.
3. User must be registered.
4. User Login page must be opened.
Input data Blank CNIC, password field, captcha and no role is selected.
Detailed steps 2. Navigate to User Login page (user must be registered before).
3. Click on SIGN IN button.
Post-condition(s) A validation message to “fill out this field” is shown.
Table 49-TC-10
Identifier TC-11
Testing is applied on Login page to check when user who is not
Short description
registered trying to login into system.
Page 135
Input data User enters invalid CNIC and invalid password.
2. Navigate to User Login page (user must be registered before).
Detailed steps
3. User write invalid CNIC and invalid password.
4. User select citizen role.
System shows an alert of “Incorrect password and please login
Post-condition(s)
again”.
Table 50-TC-11
Identifier TC-12
Related requirement(s) 3. User must be registered before login into system.
5. User must remember CNIC and Password for login.
Testing is applied on Login page to check when user enters valid
Short description CNIC, valid password and add correct captcha without selecting
‘citizen role’ then what state will be shown by system to user.
successfully.
Pre-condition(s) 2. User must be registered.
Input data User enters valid CNIC, valid password and correct captcha.
Detailed steps
3. User enters valid CNIC, valid password and correct captcha.
Post-condition(s) System redirected user to login page.
Table 51-TC-12
Identifier TC-13
Page 136
Related requirement(s) 3. User must be registered before login into system.
5. User must remember CNIC and Password for login.
CNIC, valid password , correct captcha and select ‘AC role’ rather
Short description
than citizen then which type of error will be shown by system to
user.
Pre-condition(s)
successfully.
User enters valid CNIC, valid password, correct captcha and select
Input data
AC role.
Detailed steps 3. User write valid CNIC, valid password, correct captcha and
select AC role.
Post-condition(s) System shows an alert of “Incorrect Password Please Login
again”.
Table 52-TC-13
Identifier TC-14
5. User must remember password.
6. User must select citizen role.
Testing is applied on Login page to check when user enters
Short description invalid CNIC, valid password and select citizen then what
response will be shown by system to user.
successfully.
User enters invalid CNIC, valid password, correct captcha and
Input data
select citizen role.
Page 137
Detailed steps 3. User write invalid CNIC, valid password, correct captcha and
again”.
Table 53-TC-1
Identifier TC-15
5. User must remember CNIC.
Short description CNIC, invalid password, correct captcha and select citizen role
then what response will be shown by system to user.
successfully.
User enters valid CNIC, invalid password, correct captcha and
Input data
Detailed steps 3. User write valid CNIC, invalid password, correct captcha and
again”.
Table 54-TC-15
Identifier TC-16
Page 138
7. User must remember CNIC and password.
Short description CNIC, valid password, correct captcha and select citizen role then
user must be logged in into user dashboard.
successfully.
User enters valid CNIC, valid password, correct captcha and select
Input data
citizen role.
Detailed steps 3. User write valid CNIC, valid password, correct captcha and
Expected result(s) User must login successfully.
Post-condition(s) System shows an alert of “Successfully Login”.
Table 55-TC-16
User register a Complaint

Identifier TC-17
Related requirement(s) 3. User must be login successfully.
4. User must open ‘File a Complaint’ page from ‘Complaint’
option from sidebar of user dashboard.
Related use-case(s) Citizen Register Complaint
Testing is applied on Complaint form to check when user enters
Short description valid information in all form fields then complaint will be
registered.
successfully.
Pre-condition(s) 2. User must log in successfully.
3. ‘File a Complaint’ page must be opened.
Page 139
Input data User enters valid data in all fields.
3. Enter valid CNIC, valid password, correct captcha and select
citizen role for login into dashboard.
Detailed steps 4. Click on Complaint option from sidebar.
5. Select ‘File a Complaint’ option from dropdown menu of
‘Complaint’.
6. Fill all complaint fields with valid information.
7. Click on ‘submit’ button.
Expected result(s) Complaint must be registered.
Post-condition(s) System shows an alert of “Successfully Registered”.
Table 56-TC-17
Identifier TC-18
Related requirement(s) 3. User must be login successfully.
4. User must open ‘File a Complaint’ page from ‘Complaint’
Related use-case(s) Citizen Register Complaint
Testing is applied on Complaint form to check when user left
Short description Address and Complaine Text field empty then what validation
error will be shown by system to user.
successfully.
All other fields are filled except Address and Complaine Text
Input data
fields.
4. Click on Complaint option from sidebar.
Detailed steps
‘Complaint’.
6. Fill all complaint fields except Address and Complaine Text
fields.
Expected result(s) System must show a validation error to fill out field.
Page 140
Table 57-TC-18
Edit User Profile
Identifier TC-19
Priority Low priority
2. User must be login successfully.
3. User must open ‘Edit Profile’ page from ‘User Options’ option
from sidebar of user dashboard.
Related use-case(s) Citizen Manage Profile
Testing is applied to check whether user successfully edit personal
Short description
information or not.
2. User must log in successfully.
3. Dashboard must be opened.
4. Edit Profile page must be opened.
Input data User change Name from Edit Your Info form.
4. Click on User Options from sidebar.
Detailed steps
5. Select ‘Edit Profile’ option from dropdown menu of ‘Users
Options’.
6. Replace name with new name, Email with new Email id and
add new Contact.
7. Click on submit button.
Expected result(s) Information must be edited.
Post-condition(s) User personal information updated.
Table 58-TC-19 View
Complaint Status
Identifier TC-20
3. User must open ‘Complaint Status’ page from ‘Complaint’
Related use-case(s) User working
User has registered a complaint and want to see complaint status
Short description so we applied testing to check whether user can successfully view
complaint status or not.
Page 141
successfully.
Pre-condition(s) 2. User must login successfully.
User click on ‘Complaint Status’ Option from drop down menu of
Input data
‘Complaint’.
Detailed steps citizen role for login into dashboard.
5. Select ‘Complaint Status’ option from dropdown menu of
‘Complaint’.
Expected result(s) Status must be viewed to user.
Status “PENDING CLEARENCE FROM Admin.....” has been
Post-condition(s)
shown to user.
Table 59-TC-20
Change Password
Identifier TC-21
3. User must open ‘Change Password’ page from ‘User Options’
Testing is applied to check whether user can successfully change
Short description
password or not.
successfully.
4. Change Password page must be opened.
Input data User enters new password in change password field.
Detailed steps 5. Select ‘Change Password’ option from dropdown menu of
‘Users Options’.
6. Write old password in old password field.
7. Write new password in New password and Confirm password
fields.
Page 142
Expected result(s) Password must be edited.
Post-condition(s) User’s password is updated.
Table 60-TC-21
Identifier TC-22
3. User must open ‘Change Password’ page from ‘User Options’
Testing is applied to check when user enter wrong new password
Short description in “Confirm password” field then either its password will be
updated or system will show an error.
Pre-condition(s)
successfully.
2. User must log in successfully.
4. Change Password page must be opened.
User enters correct old password, valid new password but wrong
Input data
new password in confirm password field.
Detailed steps
5. Select ‘Change Password’ option from dropdown menu of
‘Users Options’.
6. User enters correct old password, valid new password but
wrong new password in confirm password field.
Expected result(s) Error must be shown to user.
Error of “Old Pass didn't matched or please type correct in retype
Post-condition(s) password!” is shown to user.
Table 61-TC-22
User’s Feedback
Identifier TC-23
Page 143
3. Complaint must be closed by relevant authority.
Related use-case(s) Citizen Feedback
User registered a complaint and when complaint’s processing has
been done and status is closed then user can give feedback in the
Short description
form of stars. Now we applied testing to check whether user can
easily give feedback or not.
successfully.
3. Messages option must be opened.
Input data User click on feedback button in messages page.
Detailed steps
4. Click on Feedback button.
5. Give feedback in the form of selecting stars from Rating.
Expected result(s) Feedback must be submitted.
Post-condition(s) Feedback has been submitted in the form of stars.
Table 62-TC-23
5.4.2 Test cases for Admin side:
Admin forward citizen complaint to relevant authority
Identifier TC-24
1. Admin must have internet access.
Related requirement(s) 3. Admin must be login successfully.
4. Notifications page must be opened.
5. Complaints must be stored in Notifications.
Related use-case(s) Admin transfer Complaints
User registered a complaint (against AC) and it has been viewed
to admin first. Now admin has authority to forward that complaint
Short description to relevant authority (DC) or to reject it on the basis of complaint
text. Here we applied testing to check when admin click on
forward button then either complaint is transferred to DC or not.
successfully.
Pre-condition(s) 2. Admin must be login.
Input data Admin click on top right Notifications button.
Page 144
1. Admin open UI successfully.
2. Navigate to User Login page.
Detailed steps Admin role for successfully login.
4. Click on Notifications button.
5. Click on View button.
6. Click on forward button.
Expected result(s) Complaint must be transferred to relevant authority.
Post-condition(s) System shows a message of “Forwarded to authorities”.
Table 63-TC-24
Admin reject a complaint
Identifier TC-25
Related requirement(s) 3. Admin must be login successfully.
Related use-case(s) Admin transfer Complaints
User registered a complaint (against AC) and it has been viewed to
Short description
admin first. Now admin has authority to forward that complaint to
relevant authority (DC) or to reject it on the basis of complaint
text. Here we applied testing to check when admin click on reject
button then either complaint is rejected or not.
successfully.
Input data Admin click on top right Notifications button.
Detailed steps Admin role for successfully login.
4. Click on Notifications button.
5. Click on View button.
6. Click on reject button.
Expected result(s) Complaint must be deleted.
Post-condition(s) System shows a message of “Deleted Successfully!”.
Table 64-TC-25
Admin Register new officer
Identifier TC-26
Page 145
3. Admin must be login successfully.
Related use-case(s) Admin
Whenever new officer has been appointed (DC, AC, Tehsildar,
Naib Tehsildar, Gadawar, Patwari), a login must be given to new
Short description officer so that he/she can manage profile and handle incoming
complaints. We applied testing to check whether admin
successfully register new officer or not.
successfully.
3. Admin options must be opened.
Admin first click on ‘Admin Options’ and then select ‘Register
Input data
Officer’ option from dropdown menu.
Admin role for successfully login .
Detailed steps
4. Admin first click on ‘Admin Options’ and then select ‘Register
Officer’ option from dropdown menu.
5. Registration form is opened and admin enters correct officer
details in form fields.
6. Click on register button.
Expected result(s) Officer must be registered.
Post-condition(s) Message of “Successfully Registered” is shown.
Table 65-TC-26
5.4.3 Test cases for DC (Deputy Commissioner):

DC send informational message to complainant
Identifier TC-27
1. DC must have internet access.
Related use-case(s) DC Working
Short description All complaints are shown to DC that are against to AC (Assistant
Commissioner) and DC then accept complaints and send
complaint message (complaint message is in the form of date) to
citizen who file complaint. We applied testing to check after
accepting complaint whether message is shown to complainant or
Page 146
not.
1. DC first click on Notifications button and then Accept button
below complaint text box.
Input data
2. Write date on Dated box to send informational message to
user.
1. DC open UI successfully.
3. DC enters valid CNIC, valid password, correct captcha and
select Dc role for login .
Detailed steps 4. Click on SIGN IN button.
5. Click on Notifications button and then Accept button below
complaint text box.
6. Writes suitable date on Dated box.
7. Click on send button.
Expected result(s) Message must be shown to user.
Post-condition(s) Message has been sent to user.
Table 66-TC-27
DC close complaint status

Identifier TC-28
1. DC must have internet access.
3. “Active complaints” page must be opened.
Related use-case(s) DC Working
After complete processing of complaint DC can close status so that
Short description user can give feedback. We applied testing to ensure the working
of close status module when DC actually close it.
Input data DC click on Active Complaints option from side bar.
Page 147
1. DC open UI successfully.
3. DC enters valid CNIC, valid password, correct captcha and
Detailed steps select Dc role for login .
5. Click on Active Complaints option from side bar.
6. Click on close button.
Expected result(s) Status of complaint must be closed.
User is able to give feedback which shows status of particular
Post-condition(s)
complaint is closed.
Table 67-TC-28
5.4.4 Test case for AC (Assistant Commissioner):
AC send informational message to complainant
Identifier TC-29
1. There should an internet access.
Related requirement(s) 3. AC must be login successfully.
4. “Check incoming complaints” page must be opened.
Related use-case(s) AC Working
All complaints are shown to AC that are against to Tehsildar and
AC then accept complaints and send complaint message
Short description (complaint message is in the form of date) to user who file
complaint. We applied testing to check when AC accept a
complaint and write message then whether it is send to user or not.
Page 148
1. AC click on complaint’s accept button.
Input data 2. Write date on Dated box to send informational message to
user.
1. AC open UI successfully.
3. AC enters valid CNIC, valid password, correct captcha and
select Ac role.
Detailed steps
5. Click on ‘Complaints’ option and then click on “Check
incoming complaints”.
6. Click on accept button.
Table 68-TC-29
AC close complaint status

Identifier TC-30
1. AC must have internet access.
Related use-case(s) AC Working
After complete processing of complaint AC can close status of
complaint that is against Tehsildar so that user can give feedback.
Short description
We applied testing to ensure the working of close status module
when AC actually close it.
Input data AC click on Active Complaints option from side bar.
Page 149
1. AC open UI successfully.
3. AC enters valid CNIC, valid password, correct captcha and
Detailed steps select Ac role for login .
Post-condition(s)
Table 69-TC-30
5.4.5 Test cases for Tehsildar:
5.4.5.1 Test case when Tehsildar act as an officer
Tehsildar send informational message to complainant

Identifier TC-31
Related requirement(s) 3. Tehsildar must be login successfully.
Related use-case(s) Tehsildar Working
All complaints are shown to Tehsildar that are against to Naib
Short description Tehsildar, Gadawar and Patwari and Tehsildar then accept
complaints and send complaint message (complaint message is in
the form of date) to user who file complaint. We applied testing to
check when Tehsildar accept a complaint and write message then
whether it is send to user or not.
1. Tehsildar click on complaint’s accept button.
Input data 2. Write date on Dated box to send informational message to
user.
Page 150
1. Tehsildar open UI successfully.
3. Tehsildar enters valid CNIC, valid password, correct captcha
and select Tehsil role.
Detailed steps
5. Click on ‘Complaints’ option and then click on “Check
incoming complaints”.
6. Click on accept button.
Table 70-TC-31
Tehsildar close complaint status
Identifier TC-32
1. Tehsildar must have internet access.
After complete processing of complaint Tehsildar can close status
of complaint that is against to Naib Tehsildar, Gadawar and
Short description Patwari so that user can give feedback. We applied testing to
ensure the working of close status module when Tehsildar actually
close it.
Input data AC click on Active Complaints option from side bar.
3. Tehsildar enters valid CNIC, valid password, correct captcha
Detailed steps and select Tehsildar role for login .
Post-condition(s)
Table 71-TC-32
5.4.5.2 Test case when Tehsildar act as a complainant

Page 151
Register a Complaint
Identifier TC-33
4. Tehsildar must open ‘File a Complaint’ page from ‘Complaint’
option.
Related use-case(s) Tehsildar Register Complaint
Testing is applied on Complaint form to check when Tehsildar
Short description enter valid information in all form fields then complaint will be
registered.
successfully.
Pre-condition(s) 2. Tehsildar must be login successfully.
Input data Tehsildar enter correct data in all fields.
Tehsildar role for login.
‘Complaint’.
Table 72-TC-33
Identifier TC-34
Related requirement(s) 3. Tehsildar must login successfully.
4. Tehsildar must open ‘File a Complaint’ page from ‘Complaint’
Page 152
Related use-case(s) Tehsildar Register Complaint
Testing is applied on Complaint form to check when Tehsildar
Short description leave Address and Complaine Text field empty then what
validation error will be shown by system to Tehsildar.
successfully.
Pre-condition(s) 2. Tehsildar must log in successfully.
Input data
fields.
Tehsildar role for login into dashboard.
Detailed steps
‘Complaint’.
fields.
Table 73-TC-34
Receive Informational Message
Identifier TC-35
4. “Messages” page must be opened.
Tehsildar can also file complaint against other AC so whenever
Tehsildar file complaint, complaint message and complaint status
Short description
has been send to Tehsildar. We applied testing to check whether
Tehsildar receives message or not.
successfully.
Input data Click on ‘Messages’.
Page 153
3. Write valid CNIC, valid password, correct captcha and select
Detailed steps Tehsildar role.
5. Click on ‘Messages’ option.
Expected result(s) Complaint message must be shown to Tehsildar.

System shows a message of “You have been summoned in
Post-condition(s)
court…”.
Table 74-TC-35
Give Feedback
Identifier TC-36
3. Tehsildar must login successfully.
Related use-case(s) Tehsildar Feedback
Tehsildar registered a complaint and when complaint’s processing
Short description has been done then Tehsildar can give feedback. Now we applied
testing to check whether Tehsildar can easily give feedback or not.
successfully.
3. Messages option must be opened.
Input data Tehsildar click on feedback button in messages page.
Detailed steps
Tehsildar role for login into dashboard.
Table 75-TC-36
5.4.6 Test cases for Naib Tehsildar:
File a Complaint
Page 154
Identifier TC-37
1.Naib Tehsildar must have internet access.
2.System must be running successfully.
Related requirement(s) 3.Naib Tehsildar must be login successfully.
4.Naib Tehsildar must open ‘File a Complaint’ page from
‘Complaint’ option.
Related use-case(s) Employee Register Complaint
Testing is applied on Complaint form to check when Naib
Short description Tehsildar enter valid information in all form fields then complaint
will be registered.
successfully.
Pre-condition(s) 2. Naib Tehsildar must be login successfully.
Input data Naib Tehsildar enter correct data in all fields.
1. Naib Tehsildar open UI successfully.
Naib Tehsildar role for login.
‘Complaint’.
Table 76-TC-37
Identifier TC-38
Related requirement(s) 1. Naib Tehsildar must have internet access.
Page 155
3. Naib Tehsildar must login successfully.
4. Naib Tehsildar must open ‘File a Complaint’ page from
‘Complaint’ option from sidebar of user dashboard.
Testing is applied on Complaint form to check when Naib
Short description Tehsildar leave Address and Complaine Text field empty then
what validation error will be shown by system to Naib Tehsildar.
successfully.
Pre-condition(s) 2. Naib Tehsildar must log in successfully.
Input data
fields.
Naib Tehsildar role for login into dashboard.
Detailed steps
‘Complaint’.
fields.
Table 77-TC-38
Receive Complaint Message
Identifier TC-39
Related requirement(s) 3. Naib Tehsildar must be login successfully.
Related use-case(s) Employee Working
Naib Tehsildar can also file complaint against other officers so
whenever Naib Tehsildar file complaint, complaint message and
Short description
complaint status has been send to Naib Tehsildar. We applied
testing to check whether Naib Tehsildar receives message or not.
Pre-condition(s)
successfully.
Page 156
Input data Click on ‘“Messages” Option.
3. Naib Tehsildar enters valid CNIC, valid password, correct
Detailed steps captcha and select Naib Tehsildar role.
5. Click on ‘“Messages”’ option.
Expected result(s) Complaint message must be shown to Naib Tehsildar.

Post-condition(s) Message has been displayed.
Table 78-TC-39 Give
Feedback
Identifier TC-40
1. Naib Tehsildar must have internet access.
Related use-case(s) Employee Feedback
Naib Tehsildar registered a complaint and when complaint’s
processing has been done then Naib Tehsildar can give feedback.
Short description
Now we applied testing to check whether Naib Tehsildar can
easily give feedback or not.
successfully.
Pre-condition(s) 2. Naib Tehsildar must log in successfully.
3. Messages page must be opened.
Input data Naib Tehsildar click on feedback button in messages page.
Detailed steps
Naib Tehsildar role for login into dashboard.
Table 79-TC-40
5.4.7 Test cases for Gadawar:
Page 157
File a Complaint
Identifier TC-41
1.Gadawar must have internet access.
Related requirement(s) 3.Gadawar must be login successfully.
4.Gadawar must open ‘File a Complaint’ page from ‘Complaint’
option.
Testing is applied on Complaint form to check when Gadawar
Short description enter valid information in all form fields then complaint will be
registered.
successfully.
Pre-condition(s) 2. Gadawar must be login successfully.
Input data Gadawar enter valid data in all fields.
1. Gadawar open UI successfully.
3. Enters valid CNIC, valid password, correct captcha and select
Gadawar role for login.
‘Complaint’.
Table 80-TC-41
Identifier TC-42
Page 158
1.Gadawar must have internet access.
Related requirement(s) 3.Gadawar must login successfully.
4.Gadawar must open ‘File a Complaint’ page from ‘Complaint’
Testing is applied on Complaint form to check when Gadawar
Short description leave Address and Complaine Text field empty then what
validation error will be shown by system to Gadawar.
successfully.
Pre-condition(s) 2. Gadawar must log in successfully.
Input data
fields.
Gadawar role for login into dashboard.
Detailed steps
‘Complaint’.
fields.
Table 81-TC-42
Receive Informational Message
Identifier TC-43
Related requirement(s) 3. Gadawar must be login successfully.
Gadawar can also file complaint against other officers so whenever
Gadawar file complaint, complaint message has been send to
Short description
Gadawar. We applied testing to check whether Gadawar receives
message or not.
Pre-condition(s)
successfully.
2. Gadawar must login successfully.
Page 159
Input data Click on “Messages” Option.
3. Write valid CNIC, valid password, correct captcha and select
Detailed steps Gadawar role.
5. Click on “Messages” option.
Expected result(s) Complaint message must be shown to Gadawar.

Table 82-TC-43 Give
Feedback
Identifier TC-44
1. Gadawar must have internet access.
3. Gadawar must login successfully.
Gadawar registered a complaint and when complaint’s processing
has been done then Gadawar can give feedback. Now we applied
Short description
testing to check whether Gadawar can easily give feedback and it
is submitted or not.
successfully.
Pre-condition(s) 2. Gadawar must log in successfully.
Input data Messages page must be opened.
Detailed steps
Gadawar role for login.
Table 83-TC-44
Page 160
5.4.8 Test cases for Patwari:
File a Complaint
Identifier TC-45
1.Patwari must have internet access.
Related requirement(s) 3.Patwari must be login successfully.
4.Patwari must open ‘File a Complaint’ page from ‘Complaint’
option.
Testing is applied on Complaint form to check when Patwari enter
Short description valid information in all form fields then complaint will be
registered.
successfully.
Pre-condition(s) 2. Patwari must be login successfully.
Input data Patwari enter valid data in all fields.
1. Patwari open UI successfully.
Patwari role for login.
‘Complaint’.
Table 84-TC-45
Page 161
Identifier TC-46
1.Patwari must have internet access.
Related requirement(s) 3.Patwari must login successfully.
4.Patwari must open ‘File a Complaint’ page from ‘Complaint’
Testing is applied on Complaint form to check when Patwari leave
Short description Address and Complaine Text field empty then what validation
error will be shown by system to Patwari.
successfully.
Pre-condition(s) 2. Patwari must log in successfully.
Input data
fields.
Patwari role for login.
Detailed steps
‘Complaint’.
fields.
Table 85-TC-46
Receive Complaint Message
Identifier TC-47
Related requirement(s) 3. Patwari must be login successfully.
Patwari can also file complaint against other officers except DC so
whenever Gadawar file complaint, complaint message has been
Short description
send to Patwari. We applied testing to check whether Patwari
receives message or not.
Page 162
Pre-condition(s)
successfully.
2. Patwari must login successfully.
Input data Click on ‘“Messages” Option.
3. Enters valid CNIC, valid password, correct captcha and select
Detailed steps Patwari role.
5. Click on “Messages” option.
Expected result(s) Complaint message must be shown to Patwari.

Table 86-TC-47
Give Feedback
Identifier TC-1
1. Patwari must have internet access.
3. Patwari must login successfully.
Patwari registered a complaint and when complaint’s processing
Short description has been done then Patwari can give feedback. Now we applied
testing to check whether Patwari can easily give feedback or not.
successfully.
Pre-condition(s) 2. Patwari must log in successfully.
Input data Messages page must be opened.
Detailed steps 3. Enters valid CNIC, valid password, correct captcha and select
Patwari role for login into dashboard.
Table 87-TC-48
Page 163
5.5 Performance testing
Performance testing is a type of testing for determining the speed of a computer, network or
device. It checks the performance of the components of a system by passing different
parameters in different load scenarios. Keeping in view the performance requirements,
performance testing has been applied to Automated Complaint System to check response
time, load that ACS can handle and also apply stress testing to ensure the quality of system.
Performance testing is applied on the basis of following testing:

• Load Testing
Load testing is the process that simulates actual user load on any application or website.
It checks how the application behaves during normal and high loads. This type of
testing is applied when a development project nears to its completion. Automated
Complaint System is design to accept maximum number of complaints. It shall be able
to handle at least 100 transactions/inquiries per second. For checking this performance
requirement we apply load testing by registering complaints from citizen, officer and
employees at the same time and then check either each of them receive immediate
response in the form of complaint status or not. And ACS pass this load test as every
user can see his complaint status and informational message too just after filing a
complaint
• Stress Testing
Stress Testing verifies the stability & reliability of the system. This test mainly
determines the system on its robustness and error handling under load conditions. So in
case of ACS when we apply load testing on system by registering complaints from
different logins the reliability of system does not effect as it shows proper validations
error and also navigate user from one page to another without taking much delay.
5.6 Security testing

It is performed to verify if the application is secured on web or not. The system must have
protection from unauthorized users. The system should display the error message if any
unauthorized person try to use this app. In ACS all the administrative, officers and
employees of Revenue Department have unique logins so system can understand who is
login in to the system right now.
Page 164
Nobody can change record and valuable data except the admin. Sessions are used to
prevent the unauthentic use of any user’s personal information and complaint record. Also
user’s web browser not displaying a user’s password. It is always be echoed with special
characters representing typed characters.
5.7 Regression testing
Regression Testing is basically a full or partial selection of already executed test cases
which are re-executed to ensure existing functionalities work fine. This testing is done to
make sure that new code changes should not have side effects on the existing
functionalities. It ensures that the old code still works once the new code changes are done.
ACS also pass this test as we made test cases three times whenever we modify the code of
system. In all test cases Login, Registration and Complaint module is not effected by
addition of any other module.
Page 165
CHAPTER 6
TOOLS USED
6. Tools Used
a. Language/ Technologies
• PHP
• HTML
• CSS
• JavaScript
• JQuery
b. Applications
• Brackets Editor
• Xampp Server
c. Libraries
• Bootstrap library
Page 166
• Datatables.net
• Fontawesome library
Page 167
CHAPTER 7
SUMMARY & CONCLUSION
7. Summary and Conclusion
This section describes that the web-system runs successfully on the given system like laptops. The
web-system runs successfully and covers it’s all the modules in the system. It will be helpful in
registering all sorts of complaints against the officers of Revenue department, Punjab and related to
all the land related issues. The citizens will just have to sign up to start registering complaints
online. All the manual work would be eliminated. In future, we will enhance its features and make
this websystem more efficient for the use of citizens. It will be installed and made for all other
districts as well so no any district remain un-computerized for registering complaints for Revenue
Department. The Automated Complaint System allows people to register complaints in a more
convenient way, by using available resources which could facilitate the complainers during filing
complaints. Its main purpose is to convert the Revenue Department free from negative aspects
such as bribery and corruption. The integration of the system to the Revenue System will provide
an efficient way to do their all tasks, free of fraud, free of corruption and bribery and to make the
system more trustable, fair and fast. The use of CNIC deepens the process of ensuring – one man,
one login portal – is fully enforced. The project will provide immense benefit to Sialkot as it
protects and secures the integrity of the complaints registration, reduces administrative work, and
improves the creditability rating which subsequently strengthens internal democracy and trust
among the complainers.
Page 168
CHAPTER 8
USER MANUALS
8. User Manual
Admin Dashboard
Page 169
FIGURE-99: Admin Dashboard
Admin Profile
FIGURE-100: Admin Profile
Page 170
Admin
View Notification
FIGURE-101: Admin View Notification
Page 171
Admin
Forward Complaints
FIGURE-102: Admin Forward Complaints
Page 172
Admin
View User
FIGURE-103: Admin View User
Page 173
User Dashboard
User Dashboard
FIGURE-104: User Dashboard

User Profile
FIGURE-105: User Profile
User Edit Profile

Page 174
FIGURE-106: User Edit Profile
User Change Password
FIGURE-107: User Change Password
User Complaint Form
Page 175
FIGURE-108: User Register Complaint User
Complaint Status
FIGURE-109: User Complaint Status
User Message Page
Page 176
FIGURE-110: User Message Page
User Feedback Page
Page 177
FIGURE-111: User Feedback Page
DC Dashboard
FIGURE-112: DC Dashboard
DC Profile Page
Page 178
FIGURE-113: DC Profile
Incoming Complaints Page
Page 179
FIGURE-114: DC Incoming Complaint Page
Send Information Message Page
Page 180
FIGURE-115: DC Send Message
AC Dashboard
Page 181
FIGURE-116: AC Dashboard
AC Profile Page
FIGURE-117: AC Profile
Messages Page
Page 182
FIGURE-118: AC Received Message
Tehsildar Dashboard
FIGURE-119: Tehsildar dashboard

Tehsildar Profile Page
Page 183
FIGURE-120: Tehsildar Profile
Naib Tehsildar Dashboard
FIGURE-121: Naib tehsildar Dashboard

Naib Tehsildar Profile Page
Page 184
FIGURE-122: Naib Tehsildar Profile
Patwari Dashboard
FIGURE-123: Patwari dashboard
Patwari Profile Page
Page 185
FIGURE-124: Patwari Profile
Page 186
CHAPTER 9 LESSONS
LEARNT AND
FUTURE WORK
9. Lessons Learnt and Future Work
Lessons Learnt:
As every aspect of life teaches some lessons during the passage of time. Similarly this project did
too. During this project development, we learnt so many things and experienced a lot of stuff.
Lessons which we learnt were about:
• Time Management
• New Technologies/Languages
• Team coordination
• Many new software engineering concepts
• Decision Making
• Meeting deadlines etc
Future Work:
In Future a lot of improvements can be made to this project, to enhance the usability and
functionality of automated complaint system.
In future, it will be helpful in registering all sorts of complaints against/to the officers of Revenue
department, Punjab and related to all the land related issues. The citizens will just have to sign up
to start registering complaints online. All the manual work would have been eliminated. In future,
we will enhance its features and make this web-system more efficient for the use of citizens. It
will be installed and made available for all other districts as well so no any district remain
uncomputerized for registering complaints for Revenue Department. Also, the modules of
divisional based officers and members of Revenue Department will also be added in the system so
that the copies of result could be transferred to them.
Page 187
APPENDIX A
PROJECT MANAGEMENT
DOCUMENTS
Page 188
Appendix A: Project Management Documents
a. Team Structure
XXXXXXX
XXXX X XXXXXXXXXX XXXXXXXXX
XXXXXXXXX XXXXXXXX XXXXXXXX
FIGURE 125: Team Structure

b. Roles & Responsibilities
ABC. XYZ and LMN have managed and operated all activities of
this project. Requirement Analysis
----------
 ---------
 -----------
Managing and Documenting
 ----------- Developer
 -------
 ---------- Testing
 ---------
 -------
Project Supervisor
 Prof. _______
c. WBS (Work Breakdown Structure)
Page 189
Following is the Work Breakdown Structure that we used to organize our work into manageable
sections.
FIGURE 129: WBS
d. PERT Diagram
Following is the Program Evaluation Review Technique Chart which we used to schedule, organize,
and coordinate tasks within our project.
Page 190
FIGURE 130: PERT Diagram
e. Scope Statement
Project Scope Statement
Project Name Automated Complaint System [Revenue
Department]
Project Supervisor Prof. ----------------
Date Of Project Approval 05-Dec-2018
Scope Description This is Automated complaint system for Revenue
Department that provides the facility to the public to
register complaints about various issues in their areas
regarding land taxation, land revenue etc. People can
just log in and register a complaint online. Provide
information about issue, check the status of
complaints and give the feedback regarding it. This
web system is Tehsil based system that gets
complaints from citizens of a specific Tehsil
(Currently we are dealing with Sialkot Tehsil only).
Page 191
Constraints  GUI is only in English
 this system is working for single server.
 The computers must be equipped with
web browsers to use the system.
 The system shall run on Windows

Operating System.
 The development environment will be
windows 7 or higher.
 The system will be web

based application.
 Server must have greater than 500 MB

storage space and Hard disk greater than 1
GB.
 The design must be in html.

 Php must be used.
Assumptions[5]  There will be a risk that people who
don’t have any knowledge about online
registration might not use our system
especially the people of rural areas of
Punjab.
 No other government institution can
implement this system as the
hierarchy of Revenue Department is
totally change from other
departments.
 A complaint’s status must be closed
in order to give feedback about it.
 Any user of the system must check
the roll in login form for login to the
system.
 Project will follow waterfall
methodology throughout execution.
Acceptance Criteria The project will be determined successful if it works
correctly. And second, if the system implements in
real.
Page 192
Project Deliverables It will provide a platform to public to register their
complaints online instead of registering manually.
Complainant’s feedback will provide information to

the district’s authority about whether citizens are
satisfied with the working of officers or not. The
complainant will easily be able to check the status of
his/her complaint. The citizens will able to register a
complaint at any time and at any place.
f. Project Charter
Project Charter
Project Name “AUTOMATED COMPLAINT SYSTEM”
[Revenue Department, Punjab]
Project Description The automated complaint system(ACS) provides way to solve public’s
land related problems and issues easily, on district level, by registering
online complaints, tracking the status of the complaint and giving the
feedback related to the solved issues and complaints. This system acts
as an interface between the public and Deputy Commissioner (DC).
The Intention for creating ACS is to simplify the process of registering
complaints and making it quicker and cheaper.
Project Supervisor Prof. ------------- Date Approved 05-Dec-2018
Signature
Risk and Constraints Expected Goals
• There will be a ris k that people who don’t • The goal of ACS is to provide a platform
have any kno wledge about online to public to register their complaints online
registration might not use our system instead of registering manually.
especially the pe ople of rural areas of • System’s goal is to provide public a
Punjab. friendly user-interface and a secured
• One of the obstacl e will be the training of platform for recording complaints.
the employees of the department as they • Goal is to save the time of citizens so they
are not well trained computer users and don’t have to visit the complaint cell
the cost of computer systems and internet personally.
devices would incr ease govt.’s budget. • Major goal is to abolish corruption.
• Employee resistan ce can also be a risk.
• GUI is only in Eng lish.
• The computers mu st be equipped with
web browsers to use the system.
• The system sha ll run on Windows
Operating System.
• Server must have greater than 500 MB
storage space and Hard disk greater than 1
GB.
Team Members Milestones
Name Role Activities Weeks
Page 193
Requirement Elicitation 1 Weeks
Page 194
UML Diagrams 2 Week
Interface Design 1 Week
ABC Group Member Testing 3 Week
Requirement Analysis 2 Week
Managing and Documentation 5 Week
XYZ Group Member
Coding 6 Weeks
Database Design 2 Weeks
UML Diagrams 2 Weeks
Coding 6 Weeks
LMN Group Member
Database Design 2 Weeks
Testing 3 Weeks
g. Meetings Summary
Page 176
Page 196
APPENDIX B
Page 197
BIBLIOGRAPHY /
REFRENCES
Appendix B: Bibliography / References

• [1]L. Espy, "How to Create a Project Assumptions List: Examples and Template Included - Project
Bliss", Project Bliss, 2019. [Online]. Available: https://projectbliss.net/projectassumptions-list/.
• [2]"Developing Website Requirements-(Functional vs. Non-Functional)-
New2HTML", New2HTML,2019.[Online].Available:http://www.new2html.com/website/develo
ping-website-requirements-functional-vs-non-functional/.
• [3]"FastVal Functional Requirements Template | Ofni Systems", Ofni Systems, 2019. [Online].
Available: http://www.ofnisystems.com/products/fastval/details/fastval-functional-
requirementstemplate/.
• [4]w. What is the definition of user classes and S. Bailey, "What is the definition of user classes, with
respect to software use?", Software Engineering Stack Exchange, 2019. [Online]. Available:
https://softwareengineering.stackexchange.com/questions/62965/what-is-the-definition-of-
userclasses-with-respect-to-software-use/63000.
• [5]L. Espy, "How to Create a Project Assumptions List: Examples and Template Included - Project
Bliss", Project Bliss, 2019. [Online]. Available: https://projectbliss.net/projectassumptions-list/.
• [6]PHP 6 and MySQL 5 for Dynamic Web Sites: Visual QuickPro Guide, 1st ed. Peachpit Press,
2007, p. 648.
• [7]"Unified Modeling Language (UML) | State Diagrams - GeeksforGeeks", GeeksforGeeks, 2019.

[Online]. Available: https://www.geeksforgeeks.org/unified-modeling-language-umlstate-diagrams/.
[Accessed: 04- Jun- 2019].
• [8]"UML State chart Diagram with solved Example(HINDI) || IGNOU || MCS-032", YouTube,
2019. [Online]. Available: https://www.youtube.com/watch?v=OSr0T7ErhRE. [Accessed: 04- Jun-
2019]
• [9]"Test Case", www.tutorialspoint.com, 2019. [Online]. Available:
https://www.tutorialspoint.com/software_testing_dictionary/test_case. [Accessed: 04- July- 2019].
• [10]"Web Application Testing", www.tutorialspoint.com, 2019. [Online]. Available:
https://www.tutorialspoint.com/software_testing_dictionary/web_application_testing.
Page 198
APPENDIX C INDEX
Page 199
Index 182, 187, 188 complaints, iii, 2, 3, 5, 6, 7,
10, 11, 26, 28, 29,
32, 35, 38, 40, 42, 43, 44, 46, 47, 48, 50, 51,
57, 58, 134, 135, 136, 137, 138, 139, 154,
159, 182, 187, 188
A Constraints, vi, 13, 187, 188
AC, vii, viii, ix, x, xi, 8, 9, 10, 14, 24, 26, 32, Corruption, 7
33, 34, 40, 41, 42, 43, 62, 78, 79, 80, 81, 87, D Data
88, 89, 90, 91, 124, 132, 133, 134, 136, 137, Flow diagrams, vi
138, 139, 142, 175, 176 Database, vi, x, 14, 60, 112, 188
Activity Diagram, vi, x, 68, 69 DC, vii, viii, ix, x, xi, 5, 8, 10, 14, 24, 26, 29,
Admin, vii, viii, ix, x, xi, 7, 10, 24, 25, 26, 27, 30, 31, 32, 61, 64, 75, 76, 77, 78, 132, 133,
28, 29, 61, 64, 71, 72, 73, 74, 115, 129, 132, 134, 135, 136, 152, 172, 173, 174, 188
133, 134, 161, 162, 163, 164, 165 authority,
iii, 2, 5, 10, 14, 26, 28, 131, 132, 133, 187 Deputy Commissioner, 5, 8, 14, 24, 61, 134,
Automated, i, ii, iii, 7, 11, 13, 14, 108, 113, 188
116, 117, 118, 119, 121, 122, 123, 124, 125, Design, vi, x, 13, 60, 110, 188
126, 127, 128, 129, 130, 131, 132, 133, 134, E
135, 137, 138, 139, 140, 141, 142, 143, 144,
145, 146, 147, 148, 149, 150, 151, 152, 153, ERD, vi, 61, 64, 65 experience,
154, 159, 186, 187 7
Automated Complaint System, i, ii, iii, 7, 11, F
13, 14, 108, 113, 116, 117, 118, 119, 121, feedback, iii, 3, 6, 7, 10, 15, 28, 42, 43, 46, 50,
122, 123, 124, 125, 126, 127, 128, 129, 130,
57, 58, 111, 131, 132, 135, 136, 138, 139,
131, 132, 133, 134, 135, 137, 138, 139, 140,
140, 143, 146, 149, 150, 153, 187, 188
141, 142, 143, 144, 145, 146, 147, 148, 149,
Feedback, vii, ix, x, xi, 3, 7, 8, 9, 42, 46, 50,
150, 151, 152, 153, 154, 159, 186
57, 63, 64, 89, 90, 94, 95, 98, 99, 105, 106,
B 110, 111, 115, 131, 132, 142, 143, 146, 149,
Bibliography, vi, 193 150, 153, 170, 171
Functional, vi, 7, 193
C
citizens, iii, 3, 6, 7, 159, 182, 187, 188 closed, G
6, 7, 10, 31, 33, 36, 42, 46, 50, 57, 131, 136, Gadawar, iii, viii, xii, 8, 9, 10, 14, 24, 26, 62,
138, 140, 187 134, 138, 139, 147, 148, 149, 150, 152, 178,
CNIC, 9, 10, 14, 25, 29, 32, 35, 38, 40, 44, 48, 179
53, 116, 117, 118, 119, 120, 121, 122, 123,
124, 125, 126, 127, 128, 129, 130, 131, 132, I
133, 134, 135, 136, 137, 138, 139, 140, 141, Introduction, vi, 2, 108, 109
142, 143, 144, 145, 146, 147, 148, 149, 150,
151, 152, 153, 159 complainant, 3, 5, 6, 10, L
11, 30, 31, 33, 34, 36, land, iii, 2, 7, 14, 159, 182, 187, 188
37, 134, 135, 136, 138, 140, 187 Languages, vi, 182 Lessons,
complainants, iii, 24 Complainer, 7 vi, 182
complaint, iii, 2, 3, 5, 6, 7, 10, 11, 12, 13, 14, login, iii, 6, 9, 10, 11, 12, 25, 27, 28, 29, 31, 32,
15, 24, 26, 28, 30, 31, 33, 34, 36, 37, 39, 41, 34, 35, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46,
43, 45, 47, 49, 51, 56, 58, 60, 111, 115, 116, 47, 48, 49, 50, 51, 53, 54, 56, 57, 111, 115,
127, 128, 129, 131, 132, 133, 134, 135, 136, 122, 123, 124, 125, 126, 127, 128, 129, 130,
137, 138, 139, 140, 141, 142, 143, 144, 145, 131, 132, 133, 134, 135, 136, 138, 140, 141,
146, 147, 148, 149, 150, 151,152, 153, 154, 142, 143, 144, 145, 146, 147, 148, 149, 150,
151, 152, 153, 154, 159, 187 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99,
M 100, 101, 102, 103, 104, 105, 106 sign up, iii,
10, 159, 182 Software, vi, ix, 12, 14, 15, 109,
manually, iii, 5, 187, 188 113, 193 status, iii, 3, 6, 7, 10, 30, 31, 32, 33,
Meetings Summary, vi, 189 34, 36, 37,
N Non- 43, 47, 51, 58, 111, 129, 131, 135, 136, 137,
Functional, 193 138, 139, 140, 142, 145, 154, 187, 188
system, iii, 2, 5, 6, 7, 10, 11, 12, 13, 14, 15, 24,
O 25, 60, 62, 64, 68, 70, 71, 108, 109, 112,
office, 5, 12 114, 117, 119, 120, 121, 122, 123, 124, 125,
officers, iii, 12, 24, 62, 145, 149, 152, 154, 159, 126, 127, 130, 141, 145, 148, 151, 153, 154,
182, 187 online, iii, 5, 6, 159, 155, 159, 182, 187, 188
182, 187, 188 T
P tehsil, iii
password, 9, 10, 12, 25, 29, 32, 35, 38, 40, 44, Tehsil, 5, 7, 14, 139, 187
48, 53, 55, 118, 122, 123, 124, 125, 126, Tehsildar, iii, vii, viii, ix, x, xi, xii, 8, 9, 14, 24,
127, 128, 129, 130, 131, 132, 133, 134, 135, 26, 35, 36, 37, 44, 45, 46, 47, 62, 81, 82, 83,
136, 137, 138, 139, 140, 141, 142, 143, 144, 84, 85, 91, 92, 93, 94, 95, 96, 134, 136, 138,
145, 146, 147, 148, 149, 150, 151, 152, 153, 139, 140, 141, 142, 143, 144, 145, 146, 176,
155 177, 178
Patwari, iii, viii, xii, 8, 9, 10, 14, 24, 26, 62, Test Cases, vi, vii, viii, 116
134, 138, 139, 150, 151, 152, 153, 179, 180 Testing, vi, 108, 109, 112, 113, 114, 115, 116,
people, 5, 6, 64, 159, 187, 188 117, 118, 119, 120, 121, 122, 123, 124, 125,
PHP, 13, 14, 157, 193 126, 127, 128, 130, 140, 141, 143, 144, 147,
Problem, vi, 2 148, 150, 151, 154, 155, 184, 188, 193
Tools, vi, 157
R
U
References, vi, 193
register, iii, 2, 3, 5, 6, 7, 10, 11, 13, 27, 41, 43, Use Case, vi, vii, ix, x, 24, 25, 26, 27, 28, 29,
45, 47, 49, 51, 56, 58, 116, 126, 134, 159, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41,
187, 188 relevant authority, 5, 10, 132, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53,
133 Revenue, i, ii, iii, 2, 5, 6, 7, 12, 14, 24, 54, 55, 56, 57, 58
154, User Manual, vi, xi, 161
159, 182, 186, 187, 188
V
S Vice Tehsildar, iii
Security, vi, 12, 154
Sequence Diagram, x, xi, 71, 72, 73, 74, 75, 76, W
77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, WBS, vi, xii, 185 web-system,
iii, 159
Page 201

Technical Website Documentation

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

Technical Website Documentation

Uploaded by

Copyright:

Available Formats

BSCS FINAL PROJECT

Automated Complaint System [Revenue

Project Advisor: Prof. ------------------

Faculty of Information Technology

Faculty of Information Technology,

NCBA & E Gujrat

in partial fulfillment of the requirements for the degree of

Project Advisor Manager Projects

Thank you to everyone who has been part of this journey.

1.1 Background of Problem

• Accountability and Transparency:

• Resource Allocation Challenges:

Addressing these challenges requires a comprehensive, integrated approach that leverages

2. Existing Solutions and the Proposed Solution

Minimize Food Waste:

3.2 Supplementary Specification

3.2.1 Functional Requirements

User Profiles and History:

Feedback and Ratings:

Reporting and Analytics:

3.2.2 Nonfunctional Requirements

3.2.3 Design and Implementation Constraints

1. Dart: The programming language used for developing Flutter apps.

2. UI: User Interface.

3. UX: User Experience.

4. API: Application Programming Interface.

5. HTTP: Hypertext Transfer Protocol.

6. HTTPS: Hypertext Transfer Protocol Secure.

7. SDK: Software Development Kit.

8. IDE: Integrated Development Environment.

9. JSON: JavaScript Object Notation.

10. XML: Extensible Markup Language.

11. SSL: Secure Sockets Layer.

12. TLS: Transport Layer Security.

13. HTTP: Hypertext Transfer Protocol.

14. HTTPS: Hypertext Transfer Protocol Secure.

15. URL: Uniform Resource Locator.

18. Stateful Widget: A widget in Flutter that maintains state.

19. HTTP Client: A package in Dart for making HTTP requests.

22. SDK: Software Development Kit.

23. APK: Android Application Package.

24. IPA: iOS App Store Package.

25. OEM: Original Equipment Manufacturer.

26. CPU: Central Processing Unit.

28. RAM: Random Access Memory.

29. VCS: Version Control System.

30. CI/CD: Continuous Integration/Continuous Deployment.

3.3 Software Architecture

FIGURE 1: Software Architecture

3.4 Screen Shots

FIGURE-2: Home Page

Laws & Policies Page:

Privacy Policy Page

3.5 Use Case Diagrams

Use Case Diagrams & Tables Related To Admin Side

3.5.1 Use Case 01_Admin_Log_in

FIGURE-10: Use case (Admin Transfer Complaints)

FIGURE-11: Use case (Admin Register Users)

FIGURE-12: Complete Use case (Admin)

FIGURE-13: Use case (DC Login)

FIGURE-14: Use Case (DC Update Complainant Status)

FIGURE-15: Complete Use Case (DC)