PROJECT REPORT

CIVICAI

ARUNRAJ R (REG NO: 32023803013)

KARTHIK S (REG NO:32023803025)
PRATHEESH S (REG NO: 32023803039)

COLLEGE OF APPLIED SCIENCE, MAVELIKARA

(Affiliated to University of Kerala)

Managed by

INSTITUTE OF HUMAN RESOURCE DEVELOPMENT

(Established by Govt. of Kerala)

SUBMITTED IN PARTIAL FULFILLMENT OF THE

REQUIREMENTS FOR THE AWARD OF
BSC COMPUTER SCIENCE
UNIVERSITY OF KERALA

2023-2026
 COLLEGE OF APPLIED SCIENCE, MAVELIKARA
(Affiliated to University of Kerala)

Managed by
INSTITUTE OF HUMAN RESOURCE DEVELOPMENT

(Established by Govt. of Kerala)

Certificate
Certified that this report titled “CIVICAI” is bonafide record of the project work one by
ARUNRAJ R (REG NO: 32023803013), KARTHIK S ( REG NO: 32023803025), PRATHEESH
S ( REG NO: 32023803039) under our supervision and guidance, towards partial fulfillment of the
Requirements for the award of the degree of BSC COMPUTER SCIENCE of the “University of
Kerala”.

Mrs. Anjali S Kumar [Link] Mr. Sajith S

Asst Prof in Computer Science HOD, Computer Science PRINCIPAL

External Examiners:
1:

2:
 DECLARATION
We, hereby declare that, this project report entitled “CIVICAI” is the bonafide work of ours carried out
under the supervision of our project guide Mrs. Anjali S Kumar ([Link] in Computer Science),
College of Applied Science, Mavelikara and declared further that to the best of our knowledge, the
work reported here in does not form part of any other project report or dissertation on the basis of which
a degree or award was conferred on an earlier occasion to any other candidate. The content of this report
is not being presented by any other student to this or any other University for the award of a degree.

Signature:

ARUNRAJ R (REG NO: 32023803013)

KARTHIK S (REG NO:32023803025)
PRATHEESH S (REG NO:32023803039)

Countersigned:

Head, Department of Computer Science

College of Applied science, Mavelikara

 ACKNOWLEDGEMENT

First and foremost, I thank the almighty God who gave me the knowledge and strength to complete this
project successfully.

I express my deep sense of gratitude to Principal Mr. Sajith S for providing me with all the necessary
facilities, which helped me, a lot in the successful completion of this project.

It is a great pleasure for me to acknowledge the assistance of [Link] (Head of the

Department, Computer Science) and my project guide Mrs. Anjali S Kumar ( Asst Prof in
Computer Science) for her valuable advice and kind support during the period of this project.

I am extremely grateful to my external guide for her valuable guidance, advice and support for the
completion of this project.

ARUNRAJ R
KARTHIK S
PRATHEESH S
 ABSTRACT

The CivicAI web application is developed to address the growing need for efficient, automated, and
intelligent civic complaint management. By digitizing citizen grievance reporting and integrating
artificial intelligence, CivicAI eliminates manual complaint handling, reduces administrative
overhead, and significantly enhances the responsiveness of public services. It creates a centralized
digital environment where citizens, government departments, and administrative staff can interact
seamlessly, making civic issue resolution more organized, transparent, and accountable.

The platform supports distinct user roles such as Administrators, Citizens, and Department Staff.
Each user type benefits from tailored functionalities—administrators can oversee complaint
assignments, track resolution metrics, and manage department operations; citizens can quickly
submit complaints, track status updates, and provide feedback on resolved issues; and staff can
monitor their assigned complaints and update resolution progress. A key innovation of the system
is its integrated AI Analytics engine, which automates complaint categorization through machine
learning, predicts complaint priority using sentiment analysis, detects duplicate complaints, and
provides intelligent department routing, ensuring proactive rather than reactive civic management.

Developed using the Django (Python) framework for robust backend logic, machine learning
libraries (Scikit-Learn, NLTK, Pandas) for predictive analytics and natural language processing,
SQLite/PostgreSQL for secure data storage, and responsive web technologies for the frontend,
CivicAI is designed to be scalable, secure, and highly intuitive. Future enhancements may include
real-time geospatial mapping of complaints, automated SMS/email notifications, AI-powered
chatbot assistants for citizen support, and cross-platform mobile accessibility, evolving it into a fully
intelligent and citizen-driven governance solution.
 TABLE OF CONTENTS
Slno Title Page Number

1 INTRODUCTION 1
1.1 INTRODUCTION 2
1.2 SCOPE 2
1.3 OVERVIEW 2

2 SYSTEM ANALYSIS 3
2.1 EXISTING SYSTEM 4
2.1.1 LIMITATIONS OF EXISTING SYSTEM 4
2.2 PROPOSED SYTEM 4
2.2.1 ADVANTAGES OF PROPOSED SYSTEM 4
2.3 FEASIBILITY STUDY 5
2.3.1 TECHNICAL FEASIBILITY 5
2.3.2 OPERATIONAL FEASIBILITY 5
2.3.3 ECONOMICAL FEASIBILITY 5
2.3.4 LEGAL FEASIBILITY 6
2.4 MODULE DESCRIPTION 6

3 SYSTEM SPECIFICATION 8
3.1 SYSTEM SPECIFICATIONS 8
3.1.1 HARDWARE SPECIFICATIONS 8
3.1.2 SOFTWARE SPECIFICATIONS 8
3.2 SOFTWARE TECHNOLGY OVERVIEW 9
3.2.1 PYTHON 9
3.2.2 MYSQL 11
4 SYSTEM DESIGN AND DEVELOPMENT 13
4.1 INTRODUCTION 13
4.2 INPUT DESIGN 14
4.3 OUTPUT DESIGN 15
4.3.1 FORM DESIGN 16
4.4 DATA FLOW DIAGRAM 19
4.4.1 LEVEL 0 DFD 20
4.4.2 LEVEL 1 ADMIN 21

4.4.3 LEVEL 1 CITIZEN 22

4.4.4 LEVEL 1 STAFF 23

4.5 ANALYSIS TOOLS 24

4.5.1 USE CASE DIAGRAM ADMIN 25

4.5.2 USE CASE DIAGRAM USER 25

26
4.5.3 USE CASE DIAGRAM SELLER
4.6 DATABASE DESIGN 27
4.7 E R DIAGRAM 31

5 SYSTEM TESTING 34
5.1 INTRODUCTION
34
5.1.1 TYPES OF TESTING 35
5.1.2 WHITEBOX TESTING 35
5.1.3 BLACKBOX TESTING 35
5.1.4 UNIT TESTING 35
5.1.5 INTEGRATION TESTING 35
5.1.6 VALIDATION TESTING 35
5.1.7 OUTPUT TESTING 36

5.2 TESTCASES 36
6 SYSTEM IMPLEMENTATION 37
6.1 INTRODUCTION 37

6.2 IMPLEMENTATION PROCEDURE 38

6.2.1 EQUIPMENT ACQUISITION 39
39
6.2.2 TRAINING
39
6.2.3 EVALUATION
39
6.2.4 ORGANIZATIONAL IMPACT
40
6.2.5 USER MANAGEMENT ASSESSMENT
40
6.2.6 DEVELOPMENT PERFORMANCE
40
6.2.7 DOCUMENTATION

7 SOFTWARE MAINTENANCE 41
7.1 CORRECTIVE MAINTENANCE 41

7.2 ADAPTIVE MAINTENANCE 41

7.3 PERFECTIVE MAINTENANCE 41
7.4 PREVENTIVE MAINTENANCE 41

8 CONCLUSION 42

9 FUTURE ENHANCEMENTS 43
10 APPENDIX
10.1 SCREENSHOTS 44
10.2 SOURCE CODE 47
10.3 GANTT CHART 53

11 REFERENCE 54
 1

CHAPTER 1
INTRODUCTION
1.1 INTRODUCTION

In an era where urban governance and civic services demand seamless administration,
yet traditional complaint management relies on outdated and manual processes, CivicAI emerges as a
smart, intelligent solution—where citizen grievance reporting meets automated technology. At the
heart of our vision lies a deep belief in organized digital environments, proactive issue resolution, and
community-driven access to responsive public services.

In today's fast-paced civic environments, the need for efficient, transparent, and
hassle-free complaint management is greater than ever. This is where CivicAI steps in—not just as a
platform for logging grievances, but as an artificially intelligent ecosystem that connects citizens,
government departments, and administrative staff under one unified system of mutual benefit and
operational harmony.

For citizens, CivicAI offers a gateway to convenience—allowing them to easily

submit complaints, track resolution status, and provide feedback on resolved issues. This model
empowers citizens with a voice, using AI-driven sentiment analysis to ensure that urgent or highly
critical grievances are automatically prioritized and rapidly addressed without getting lost in a
bureaucratic paper trail.

For the department staff, CivicAI acts as a structured digital workplace. Whether it
is tracking assigned complaints, updating resolution progress, or managing workload distribution, the
staff maintains clarity over their responsibilities and performance, fostering a motivated and
accountable workforce
For administration, CivicAI is more than just a record-keeping application—it is a
tool for proactive management. From utilizing predictive analytics to forecast complaint trends and
identify systemic issues before they escalate, to monitoring department performance and resolution
metrics, administrators enjoy unprecedented control, transparency, and data-driven insights.

College of Applied Science, Mavelikara

 2
At its core, CivicAI values efficiency and accessibility. Whether you are a citizen
reporting a road issue, a staff member resolving water supply complaints, or an administrator
overseeing municipal operations, the platform adapts to diverse needs with ease. With intuitive
interfaces and role-specific dashboards, users can navigate the system effortlessly—ensuring that
technology serves the entire community, not just the administration

.Beyond the immediate utility of complaint management, CivicAI fosters a standard of

civic responsibility and governance. Every resolved complaint and optimized resource contributes to
reducing institutional friction, lowering operational costs, and making public services more
responsive. It is not just about addressing issues—it is about how we manage civic infrastructure,
together. With CivicAI, we envision a future of smarter, more transparent, and more connected citizen
governance

1.2 SCOPE

The scope of CivicAI encompasses the development of a comprehensive, AI-integrated

web platform that facilitates intelligent civic complaint management by connecting citizens,
government departments, and administrative staff. The system supports dynamic user registration,
intelligent complaint categorization and routing, an automated complaint resolution ticketing system,
and secure feedback collection with sentiment analysis. Enhanced by machine learning capabilities,
the system provides advanced features like AI-powered complaint classification, priority prediction
based on sentiment analysis, duplicate complaint detection, and departmental performance analytics.
Designed to operate in municipal corporations, local government bodies, and public service
departments, CivicAI eliminates manual administrative overhead, maximizes resource utilization, and
promotes a highly responsive civic environment. The platform is scalable and adaptable, paving the
way for future integrations such as real-time geospatial complaint mapping, automated SMS/email
notification systems, AI-powered chatbot assistants for citizen support, and cross-platform mobile
accessibility.

College of Applied Science, Mavelikara

 3
1.3 OVERVIEW OF THE PROJECT

CivicAI is an innovative digital platform designed to revolutionize the way civic

complaints and public grievances are managed. By seamlessly integrating complaint submission, AI-
driven categorization, departmental routing, and resolution tracking into a unified system, CivicAI
addresses key challenges like delayed responses, misrouted complaints, and inefficient resource
allocation. The platform enables users to interact through dedicated interfaces as citizens, staff, or
administrators, utilizing intuitive workflows that ensure convenience, transparency, and
accountability. With a focus on proactive management and citizen satisfaction, CivicAI is not just an
administrative tool—it is a smarter, more predictive, and highly inclusive approach to modern civic
governance.

College of Applied Science, Mavelikara

 4

CHAPTER 2
SYSTEM ANALYSIS
System analysis is a logical process; it is an important activity that takes place when
a new system is being built. The objective of this phase is not actually to solve the problem but to
determine what must be done to solve the problem. It is the central intact of system development and
it includes gathering and interpreting facts, diagnosing and using this information to recommend
improvements to the system. System analysis gives the structure and functioning of the system and
it specifies what the system should do. It is helpful to understand the problem and emphasize what
is needed from the system.

Before designing an application which will help its users, it is important that the way
it currently operates should be clearly identified. The process of system investigation includes several
methods of gathering the required information. It is important that the approach is appropriate to the
application under consideration and the user of the system. System analysis should be creative and
imaginative in producing new solutions to meet the user requirements. In short the system is analyzed
by gathering various information such as system functionality, problems encountered, requirement
by the proposed system, users, their tasks and responsibilities. Here in the system analysis phase,
system is viewed as a whole and inputs to the system are in defined, and also the output from the
system is traced through the various data collected.

A detailed study of these processes must be made by the various techniques like
interviews, questionnaires, etc. The data collected by these sources must be scrutinized to arrive to
a conclusion. The conclusion is an understanding of how the system functions. This system is called
the existing system. Now, the existing system is subject to close study and the problem areas are
identified. The designer now functions on a problem solver and tires to sort out the difficulties that
weighed with the existing faces. The solutions a given on a proposal. The proposal is then weighed
with the existing system analytically and the best one is selected. The proposal is presented to the
user for any endorsement by the user. The proposal is reviewed on user request and suitable changes
that made. This is a loop that ends as soon as the user in satisfied with the proposal.

College of Applied Science, Mavelikara

 5

2.1 EXISTING SYSTEM

 Lack of centralized platform: There is no unified system that connects citizens, government
departments, and administrative staff for efficient coordination of complaint submission, routing, and
resolution tracking.
 Manual or fragmented handling: Manual tools like paper forms, phone calls, email chains, and
messaging apps create disorganized complaint management with no systematic tracking.
 No verification or tracking: Current manual systems lack AI-driven insights for prioritizing
urgent citizen complaints, predicting service bottlenecks, or tracking department performance reliably.

2.1.1 Limitations of Existing System

 Unverified Complaints and Poor Prioritization:

 Inefficient Resource Utilization: Manual assignment of complaints to departments and staff is prone
to human error, resulting in misrouted grievances, uneven workload distribution, and compromised service
quality.

2.2 PROPOSED SYSTEM

The proposed CivicAI system is an intelligent, web-based platform that connects

citizens, government departments, and administrative staff in a seamless and secure environment. It
provides role-specific features such as AI-powered complaint categorization, intelligent department
routing, automated complaint tracking via sentiment analysis, duplicate complaint detection, and
integrated feedback collection with sentiment scoring.

By offering a unified dashboard and workflow for each user type, the system ensures
efficient coordination, real-time updates, and data-driven decision-making. This digital solution not
only improves administrative efficiency but also promotes a more responsive, transparent, and
accountable civic governance environment.

College of Applied Science, Mavelikara

 6
2.2.1 ADVANTAGES OF PROPOSED SYSTEM

The proposed system for early education offers several advantages over existing system:

⬛ Enhanced Security and Verification: All users, including citizens and staff, undergo
authentication and role-based approval, ensuring safety and trust in every complaint
submission and resolution.
⬛ Optimized Use of Resources: AI-powered categorization and routing ensures complaints
reach the right departments efficiently, while predictive analytics helps identify systemic issues
before they escalate, maximizing service effectiveness
⬛ Convenient, Role-Based Access: Each user interacts through a tailored interface that supports
their specific needs—be it submitting complaints, resolving grievances, or monitoring department
performance.

2.1 FEASIBILITY STUDY

An initial investigation culminates in a proposal that determine whether an ultimate

system is feasible. When a proposed system is made and approved, it initiates a feasibility study. The
purpose of feasibility study is to identify various candidate systems and evaluates whether they are
feasible by considering technical, economical, operational and legal feasibility and to recommend
the best candidate system.

Feasibility study is conducted to test whether the system is beneficial to the

organization.

Feasibility study of this project includes the following.

2.2.2 Technical Feasibility

Technical feasibility study deals with the hardware as well as the software
requirements. The scope was whether the work for the project is done with the current equipment
and the existing software technology. The outcome was found to be positive.
The system “CIVIC AI” is said to be technically feasible because the software and
hardware required to develop this system is already available. For this system we use HTML,CSS,JS
as the front end, and PYTHON as the back end and database is MySQL.
College of Applied Science, Mavelikara
 7
2.2.3 Operational Feasibility

The proposed project would be beneficial to organization satisfying the objectives

when developed and installed. One of the main problems faced during the development of a new
system is getting the acceptance from the user. There is support from the management of organization
towards the development of the project. All the operational aspects are considered carefully. This the
project is operationally feasible.

2.2.4 Economic Feasibility

The developing system must be justified by cost and benefit a criterion to ensure that
effort taken on the project gives the best return at the earliest. One of the factors, which affect the
development of a new system, is the cost it would require. Since the system developed is a part of a
project work, there is no manual cost to spend for the proposed system. Also, all the resources are
already available, giving an indication that the system is economically possible for development.
The system “CIVIC AI” is said to be economically feasible because the hardware a n d
software required to develop the system is already available. No additional requirements are needed,
so there is no need to purchase any tools from outside. So it is a cost effective system. Its maintenance
cost is also very cheap. This project is done as part of our course. Hence this is economically feasible.

2.2.5 Legal Feasibility

Legal feasibility is the determination of any infringement, violation, or liability that

could result from the development of the system. Legal feasibility environment passes abroad range
of concerns that include contract and liability. The proposed project is also a legally feasible one.

2.3 MODULE DESCRIPTION

The system has the following users: Admin, Citizen, and Staff..
[Link]
Duties:
 Approve or reject user registrations (citizens, staff).
 Manage departments, staff assignments, and overall service inventory.
 View AI-generated insights (complaint trends, priority analytics, sentiment scores of feedback).
 Oversee complaint resolution metrics, department performance, and generate analytical reports

College of Applied Science, Mavelikara

 8

2. Citizen
Duties:
 Register and submit complaints with location, images, and detailed descriptions.
 Track complaint status and view resolution timeline
 Provide feedback and ratings on resolved complaints
 View notification updates and manage profile information.

3. Staff
Duties:
 Register and view assigned complaints or daily workload.
 Update complaint statuses (e.g., mark a complaint as "In Progress" or "Resolved")
 Add resolution notes and communicate with citizens regarding complaint progress.
 View performance metrics and manage availability status.

College of Applied Science, Mavelikara

 9

CHAPTER 3
SYSTEM SPECIFICATION

3.1.1 HARDWARE SPECIFICATIONS

The selection of hardware configuration is a very important task related to software

development. Insufficient random-access memory may affect adversely on speed and efficiency of
the entire system. The process should be powerful to handle the entire operations.

The hard disk should have sufficient capacity to store the file and application.

 Processor : 2.0 GHz i5 Processor or above 

 Hard Disk : 550 GB or above

 RAM : 4.00 GB or above

 Input Device : Standard Mouse and Keyboard

 Output Device : High Resolution Monitor

3.1.2 SOFTWARE SPECIFICATIONS

 Operating System  : Windows 10 or above / Linux

 Web Server : ASGI / WSGI Web Server (e.g., Gunicorn

Or Daphne)

 Web Brower : MicrosoftEdg/

Mozilla
Firefox /
Google
Chrome

 Front End : HTML,CSS,JS

College of Applied Science, Mavelikara

 10

 Back End : Python(3.10 or above)

 Framework : Django (6.0)

 Database : MySQL

 ML Libraries : Scikit-Learn, Pandas, NLTK,

TextBlob, NumPy

3.2 SOFTWARE TECHNOLOGY OVERVIEW

3.2.1 PYTHON

Python is a widely-used, open-source, high-level programming language designed

specifically for general-purpose programming and web development. It is executed on the server,
making it ideal for creating dynamic, data-driven, and interactive websites. Python is especially
popular for developing intelligent web-based applications due to its simplicity, compatibility with
databases (like MySQL), and unparalleled support for artificial intelligence and machine learning.

Python's syntax is easy to learn for beginners, yet powerful enough to build complex
architectural solutions. It supports object-oriented programming, dynamic typing, and has a vast
ecosystem of frameworks (like Django and Flask). Python continues to evolve, with newer versions
offering improved performance, better security, and modern asynchronous development features.

Advantages of PYTHON

 Open-source and free to use.

 Easy to learn,read, and write with extremely clear syntax.
 Extensive support for Machine Learning and Data Science libraries (Pandas, Scikit-Learn, NLTK).
 Large community support and extensive documentation.
 Highly versatile and cross-platform capable..

College of Applied Science, Mavelikara

 11
Disadvantages of PYTHON

 Slower execution time compared to compiled languages like C++ or Java.

 High memory consumption due to the flexibility of the data types.
 Design restrictions due to dynamic typing can sometimes introduce runtime errors.

Features of PYTHON
 Server-side scripting and rapid application development.
 Cross-platform compatibility (Windows, Linux, macOS).
 Built-in support for multiple database connectors.
 Seamless integration with C/C++ modules for performance-critical logic.
 Supports both procedural and object-oriented programming paradigms..

Django Framework

Django is a high-level Python web framework that encourages rapid development and
clean, pragmatic design. Built by experienced developers, it takes care of much of the hassle of web
development, allowing developers to focus on writing the app without reinventing the wheel. It follows
the Model-View-Template (MVT) architectural pattern.
One of Django’s key strengths is its "batteries-included" feature set, which provides built-
in admin panels, secure authentication, and an Object-Relational Mapper (ORM) right out of the box.
Its high security prevents common vulnerabilities like SQL injection and cross-site scripting natively.
Django is widely adopted for its scalability, high productivity, and robust structure for complex
projects like Civic AI.

Hyper Text Mark Up Language

An HTML file is a text file containing small mark-up tags. These tags tell the web browser
how to display the page. An HTML file must have an htm or html file extension. An HTML file can be
created by using a simple text editor. HTML documents are text files made up of HTML elements e.g.:
<html>, <body>. HTML elements are defined using HTML tags.
HTML tags are used to mark-up HTML elements. The two characters surround HTML
tags <and>. The surrounding characters are called angle brackets. HTML tags normally come in pairs
like <b> and </b>. The first tag in a pair is the start tag: the second tag is the end tag. The text between
the start and the end tag is the element content. HTML tags are not case sensitive; <b> means the same
as <B>.
College of Applied Science, Mavelikara
 12
3.2.2 MySQL

MySQL is an open-source relational database management system (RDBMS).Its

name is a combination of "My", the name of co-founder Michael Widenius's daughter My and
"SQL", the acronym for Structured Query Language. A relational database organizes data into one
or more data tables in which data may be related to each other; these relations help structure the data.
SQL is a language programmers use to create, modify and extract data from the relational database,
as well as control user access to the database.

In addition to relational databases and SQL, an RDBMS like MySQL works with an
operating system to implement a relational database in a computer's storage system, manages users,
allows for network access and facilitates testing database integrity and creation of backups.
MySQL is the world's most popular open source database software, with over 100
million copies of its software downloaded or distributed throughout its history. With its superior
speed, reliability, and ease of use, MySQL has become the preferred choice for Web, Web 2.0,
SaaS, ISV, Telecom companies and forward-thinking corporate IT Managers because it eliminates
the major problems associated with downtime, maintenance and administration for modern, online
applications.
Many of the world's largest and fastest-growing organizations use MySQL to save
time and money powering their high-volume systems, and packaged software – including industry
leaders such as Yahoo Alcatel-Lucent, Google, Nokia, YouTube, Wikipedia, and [Link].
The flagship MySQL offering is MySQL Enterprise, a comprehensive set of production-tested
software, proactive monitoring tools, and premium support services available in an affordable
annual subscription.
MySQL is a key part of LAMP (Linux, Apache, MySQL, PHP Perl / Python), the
fast-growing open source enterprise software stack. More a companies are using LAMP as an
alternative to expensive proprietary software stacks because of its lower cost and freedom from
platform lock-in.
The MySQL database is owned, developed and supported by Sun Microsystems, one
of the world's largest contributors to open-source software.

MySQL was originally founded and developed in Sweden by two Swedes and a Finn
David Axmark, Allan Larsson and Michael "Monty" Widenius, who had worked together since the
1980's. The best and the most-used database in the world for online applications

College of Applied Science, Mavelikara

 13
• Available and affordable for all

• Easy to use

• Continuously improved while remaining fast, secure and reliable

• Fun to use and improve Free from bugs

Python Web Application Servers (WSGI/ASGI)

While traditional applications use Apache, modern Python web applications utilize Web
Server Gateway Interface (WSGI) or Asynchronous Server Gateway Interface (ASGI) servers like
Gunicorn or Daphne. These servers natively translate the HTTP requests into Python code that Django
can understand, acting as the robust bridge between the external web traffic and the internal application,
providing a full range of reliable server features, security, and extensibility.

College of Applied Science, Mavelikara

 14

CHAPTER 4
SYSTEM DESIGN & DEVELOPMENT

4.1 INTRODUCTION
System design provides a clear understanding of the procedures and technical details
required for implementing the proposed system. It is one of the most important phases in the software
development life cycle because the quality of the design directly influences coding, testing,
deployment, and maintenance. In CivicAI, the design phase transforms the requirements gathered
during analysis into a working civic complaint management platform that supports citizens,
department staff, and administrators.

CivicAI is designed as a web-based civic complaint management system developed

using Django. The system automates user registration, OTP-based account verification, complaint
submission, AI-powered categorization, department routing, complaint tracking, resolution
management, feedback collection, sentiment analysis, duplicate detection, and AI-assisted analytics.
The design also supports operational monitoring through dashboards for admin, staff, and citizens.

During this phase, the system was divided into functional modules and database
entities. Input forms, output screens, business rules, workflows, and data storage structures were
carefully planned so that the system becomes easy to use, secure, maintainable, and scalable. The
design of CivicAI focuses on solving civic complaint management problems logically while ensuring
smooth user [Link] design the analyst.

 Models for users, complaints, departments, feedback, and notifications were identified.
 Input methods for registration, complaint submission, status updates, and feedback were designed.
 Output screens such as dashboards, reports, notifications, and confirmation receipts were planned.
 Database tables and relationships were defined based on project requirements.
 Security controls such as OTP verification, role-based access, and approval status were specified.
 Software components such as Django modules, templates, static files, and AI analytics utilities were
organized.
The physical design of CivicAI includes modules for account management, hostel
operations, complaint tracking, payment handling, and AI analytics. These modules interact with a
centralized MySQL database and provide a structured workflow for complaint management.
College of Applied Science, Mavelikara
 15

4.2 INPUT DESIGN

Input design refers to the process of converting user-oriented data into a format that
can be processed by the computer system. The objective of input design in CivicAI is to make data
entry simple, accurate, consistent, and user friendly. Each form is designed with proper labels,
validation rules, and clear submission actions so that users can complete tasks without confusion.

During this phase, the analyst schedules design activities, works with the user to
determine the various data inputs to the system, plans how data willow though the system, designs
required outputs and writes program specifications. Again the analyst's activities focus on solving a
user's problem in logical terms.

During this second step, analysts employ s variety of tools such as data flow diagrams,
entity- relationship diagrams, data dictionaries and Gantt chart. The system's design converts the
theoretical solution introduced by the feasibility study into a logical reality

In CivicAI, input is collected through web forms for the following major activities:

 User login
 Citizen registration
 Staff registration
 OTP verification
 Profile update
 Complaint status update
 Resolution notes submission
 Feedback submission
 Department management
 Staff assignment
 Complaint reassignment
 Analytics query

The proposed system satisfies the following input design objectives:

 A cost effective method of data entry

 High level of accuracy and validation

College of Applied Science, Mavelikara

 16
 Ease of understanding for citizens, staff, and administrators
 Faster processing with reduced manual work
 Role-based input flow to avoid irrelevant fields

Input objectives are:

i. Controlling the amount of input: The system reduces manual effort by using dropdowns, radio
buttons, date pickers, and predefined options. Examples include complaint category, priority level,
status options, department selection, role assignment, and feedback rating. This reduces typing effort
and improves consistency.

ii. Avoiding Delay: Input screens are role-based, reducing unnecessary navigation. OTP verification
supports quick account confirmation, and dashboard-based routing allows users to access required
modules faster. Admin, citizen, and staff tasks are separated into dedicated pages.

iii. Avoiding Data: Validation is used at both form level and model level. Email format, OTP length,
phone number, required fields, selection choices, location details, and complaint descriptions are
checked before data is saved. This improves reliability of records stored in the database.

iv. Avoiding Extra steps: The citizen registration flow combines profile details and contact information
in a single process. Staff members are assigned to departments during registration. Complaints are
automatically categorized and routed to appropriate departments using AI, thereby reducing manual
assignment steps.

v. Keeping the process Simple : The forms are designed with clear labels and logical grouping of

personal data, complaint details, and operational requests. Error messages are displayed in
understandable form so that users can correct invalid entries without difficulty.

College of Applied Science, Mavelikara

 17

4.3 OUTPUT DESIGN

Output design is concerned with how the processed information is presented to the
users. In CivicAI, outputs are designed to be clear, accurate, timely, and role-specific. The outputs of
the system include dashboards, status updates, notifications, complaint details, feedback summaries,
resolution timelines, and AI analytics reports.

The major objective of output design in CivicAI is to provide meaningful information

to the user in a form that supports decision making and smooth civic complaint management
operations. Different users of the system require different outputs, so the system generates role-based
screens and reports.

 External Outputs: These include email verification messages, account approval mails, complaint
submission confirmations, status update notifications, and feedback reminders.

 Internal Outputs: These include admin dashboards, staff task lists, citizen complaint history,
department performance reports, complaint status summaries, and feedback analytics

 Interactive Outputs: These include notifications, complaint status tracking, feedback prompts,
resolution progress updates, AI category predictions, priority alerts, and analytics charts

The outputs are designed with the following objectives:



 Accuracy of displayed data
 Neat and readable screen layout
 Proper role-based access to information
 Quick understanding of platform operations
 Support for analytics and monitoring

College of Applied Science, Mavelikara

 18

4.3.1 FORM DESIGN

LOGIN FORM

EMAIL ADDRESS

PASSWORD

LOGIN

USER REGISTRATION

FIRST NAME

LAST NAME

EMAIL ADDRESS

GENDER

PHONE NUMBER

PASSWORD

CONFIRM PASSWORD

PROFILE PHOTO

REGISTER

College of Applied Science, Mavelikara

 19

4.4 DATA FLOW DIAGRAM

A DFD, also known as a "bubble chart" has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system design. A
DFD consists of a series of bubbles joined by lines. The bubbles represent data transformations and the
lines represent data flow in the system.
A data flow diagram may be used to represent a system or software at any level of
abstraction DFD's can be partitioned into levels that represent increasing information flow and functional
details. A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that
change or transform data throughout a system. It is a structured analysis and design tool that can be used
for flowcharting in place of or in association with, information oriented and process oriented system
flowcharts.
When analysts prepare the DFD, they specify the user needs at a level of detail that
virtually determines the information flow into and out of the system and the required data resources. This
network is constructed by using a set of symbols that do not imply a physical implementation. The DFD
reviews the current physical system, prepares input and output specification, specifies the implementation
plan etc.

Basic data flow diagram symbols are:

 A “Rectangle” defines a source or destination.

 An “Arrow” identifies data flow. It is a pipeline

through which information flows.

 A “Circle” represents a process that transforms

incoming data flow(s) into outgoing data flow(s).

 An “Open Rectangle” is a data store

College of Applied Science, Mavelikara

 20

Steps to Construct Data Flow Diagrams:

Three steps are commonly used to construct a DFD.

 Process should be named and numbered for easy reference each name should be
representative of the process.
 The direction of flow is from top to bottom and from left to right.
 When a process is exploded in to lower level details they are numbered.

LEVEL 0 DFD (CONTEXT DIAGRAM)

Fig: 4.4.1 Context Diagram

College of Applied Science, Mavelikara

 21

Level 1 Admin

Fig: 4.4.2 Level 1 Admin

College of Applied Science, Mavelikara

 22

Level 1 Citizen

Fig: 4.4.3 Level 1 Citizen

College of Applied Science, Mavelikara

 23

Level 1 Staff

Fig: 4.4.4 Level 1 Staff

College of Applied Science, Mavelikara

 24
4.5 ANALYSIS TOOLS

System analysis is the process of collecting and interpreting facts, understanding

problems and using this information to suggest improvements in the system. This will helps to
understand the existing system and determine how computers make their operations more effective.

In software engineering, a use case diagram in the Unified Modeling Language (UML)
is a type of behavioral diagram defined by and created from a Use-Case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors, their goals,
and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are
performed for which actor. Roles of the actors in the system can be depicted. The use case diagram
shows the position or context of the use case among other use cases. As an organizing mechanism, a
set of consistent, coherent use cases promotes a useful picture of system behavior, a common
understanding between the customer/ owner/ user and the development team.

Use Case is a technique for capturing functional requirements of systems and systems-
of-systems. Each use case provides one or more scenarios that convey how the system should interact
with the users called actors to achieve a specific business goal or function. Use case actors may be end
users or other systems. Use cases typically avoid technical jargon, preferring instead the language of
the end user.

The UML standard describes graphical notation for relationships. Use cases are
represented by ovals and the actors are represented by stick figures. The use case diagram of this
application is given below.

College of Applied Science, Mavelikara

 25

Fig: 4.5.1 Admin

Fig: 4.5.2 Citizen

College of Applied Science, Mavelikara

 26

Fig: 4.5.3 Staff

College of Applied Science, Mavelikara

 27

4.6 Database Design

After designing the input and output activities, the designer moves to concentrate on
database design. How data are organized depends on the data and response requirements that
determine hardware configurations. The database is organized to ensure that the system resources
are not wasted. The objective of the database design is to provide the effective auxiliary storage
and contribute to the overall efficiency to the computer program components of the proposed
system. The database design translates the data models that were developed for the system users
during the definition phase into the data structures supported by the chosen database technology.
The goals of database design are as follows:

1. A database should provide for the efficient storage, update and retrieval of data.

2. A database should be reliable; the stored data should have high priority to promote user trust in
that data.

3. A database should be adaptable and scalable to new and unforeseen requirements and
applications.

The techniques used to improve a data model in preparation for database design is called
data analysis. Data analysis is a process that prepares a data model for implementation as a simple,
non-redundant and adaptable database. The specific technique is called Normalization.
Normalization is a technique that organizes the data attributes such that they are grouped to form
stable, flexible and adaptive entities. The table involved in inspection process along with attributes,
data types, constraints and brief description about the fields are stated in the below mentioned
table.

Normalization

Normalization is the process of decomposing the attributes in an application, which results

in a set of tables with very simple structure. The purpose of normalization is to make tables as simple
as possible. Normalization is carried out in this application for the following reasons.

o To structure the data so that there is no operation of data, this helps in saving space.

o To permit simple retrieval of data in response to query and report request.

College of Applied Science, Mavelikara
 28

o To simplify the maintenance of the data through updates, insertions and deletions.

o To reduce the need to restructures or recognize data which new application requirements arise.

Primary key is assigned for this purpose. The primary key fields in the tables help to ease the search
and improve efficiency. The proposed system is using second normal form as it is found most suitable.
In second normal form each row must contain associated field that describes an attribute of the entry
that the table describes.

Table 4.6.1 accounts_user

Column Type Null Description

id int(11) No Primary key
password varchar(128) No Encrypted password
last_login datetime Yes Last login time

varchar(254) No User email

email

full_name varchar(105) No Full name

phone varchar(10) Yes Phone number
role varchar(10) No User role
profile_photo varchar(100) No Profile photo path
is_active tinyint(1) No Active status
is_staff_member tinyint(1) No Staff member flag
is_verified tinyint(1) No Verification status
date_joined datetime No Account creation time
otp varchar(6) Yes OTP code
otp_created_at datetime Yes OTP generation time
employee_id varchar(20) Yes Employee identifier
is_available tinyint(1) No Availability status
department_id int(11) Yes FK → department

Table 4.6.2 complaints_complaintstatuslog

Column Type Null Description

id int(11) No Primary key
complaint_id int(11) No FK → complaint
old_status varchar(20) No Previous status
new_status varchar(20) No Updated status
changed_by_id int(11) Yes User who changed status
note text Yes Additional notes
changed_at datetime No Change timestamp

College of Applied Science, Mavelikara

 29
Table 4.6.3 complaints_complaint

Column Type Null Description

id int(11) No Primary key
complaint_id varchar(20) No Unique complaint ID
title varchar(200) No Complaint title
description text No Complaint description
category varchar(20) Yes Complaint category
priority varchar(10) No Priority level

status varchar(20) No Complaint status

citizen_id int(11) No FK → user (citizen)
department_id int(11) Yes FK → department
assigned_staff_id int(11) Yes Assigned staff ID
location text No Complaint location
phone varchar(10) No Contact phone
latitude decimal(9,6) Yes Latitude
longitude decimal(9,6) Yes Longitude
image varchar(100) Yes Image path
ai_category varchar(20) Yes AI predicted category
ai_priority varchar(10) Yes AI predicted priority
ai_confidence double No AI confidence score
submitted_at datetime No Submission time
assigned_at datetime Yes Assigned time
in_progress_at datetime Yes Work started time
resolved_at datetime Yes Resolution time
updated_at datetime No Last updated time
admin_notes text Yes Admin remarks
resolution_notes text Yes Resolution details
is_duplicate tinyint(1) No Duplicate flag
duplicate_of_id int(11) Yes Original complaint reference
feedback_submitted tinyint(1) No Feedback submitted flag

Table 4.6.4 departments_department

Column Type Null Description

id int(11) No Primary key
name varchar(100) No Department name
code varchar(20) No Department code
description text Yes Department description
email varchar(254) Yes Department email
phone varchar(15) Yes
Contact number
head_name varchar(100) Yes Department head
is_active tinyint(1) No Active status
created_at datetime No Created time
updated_at datetime No Updated time

College of Applied Science, Mavelikara

 30

Table 4.6.5 t feedback_feedback

Column Type Null Description

id int(11) No Primary key
complaint_id int(11) No FK → complaint
citizen_id int(11) No FK → user
emoji_rating varchar(10) No Emoji rating
text_comment text Yes Feedback comment
attachment varchar(100) Yes Attachment file
sentiment varchar(10) Yes Sentiment label
sentiment_score double No Sentiment score
submitted_at datetime No Submission time
updated_at datetime No Last updated time
is_edited tinyint(1) No Edited flag

Table 4.6.6 notifications_notification

Column Type Null Description

id int(11) No Primary key
recipient_id int(11) No FK → user
notification_type varchar(30) No Notification type
title varchar(200) No Notification title
message text No Notification message
is_read tinyint(1) No Read status
created_at datetime No Created time
complaint_id varchar(20) Yes Related complaint ID
link varchar(200) Yes Redirect link

College of Applied Science, Mavelikara

 31
4.6 E-R DIAGRAM

An entity-relationship (ER) diagram is specialized graphic that illustrates the

interrelationship between entities in a database Boxes are commonly used to represent entity Diamonds
are normally used to represent relationships and ovals are used to represent attributes.

An entity is piece of data is shared between entities.

 Classifying Relationships

Relationships are classifieds by their degree, connectivity, cardinality, direction, type and existence.

 Degree of Relationships

The degree of a relationship is the number of entities associated with the relationship. The n- array
relationship is there general from for degree n. Special cases are binary, ternary where the degree is 2
and 3 respectively.

 Connectivity and Cardinality

The connectivity of a relationship describes the mapping of associated entity instances in the relationship.
The values of connectivity are "one" or "many" The cardinality of a relationship is the actual number of
related occurrences for each of the two entities. The basic types of connectivity of relations are: One-to-
one, one-to- many, many-to-many.

A one-to-one (1:1) is when at most one instance of an entity A is associated with one instance of entity
B.

0-to-many (1: N) Is when for an instance of a entity A, there are zero, one or many instances of entity B,
but for instance of the entity B, there is only one instance of the entity A.

A many-to-many (M: N) relationship, sometimes called non-specific, is when for one instance of entity
A, there are zero, one or more instances of entity B and for one instance of entity B there are zero, one
or many instances of entity A.

College of Applied Science, Mavelikara

 32

The symbols used ER Diagram is

Entity

Attributes

Relationships

Lines

College of Applied Science, Mavelikara

 33

FIG: 4.7 ER Diagram

College of Applied Science, Mavelikara

 34

CHAPTER 5
SYSTEM TESTING
5.1 INTRODUCTION

System testing is actually a series of different testes whose primary purpose is to fully
exercise the computer based system. Although each test has a different purpose, all work together to
verify that the system elements have been properly integrated and perform all functions clearly.
System testing makes logical assumptions that if all parts of the system are correct, the
goal will be successfully achieved. Testing is the process of executing the program with the intent of
finding errors. Testing cannot show the absence of defects, it can only show that software errors are
present.
Testing on this project can be done in many ways, such as module testing, where every
single program module is examined thoroughly, this project is also divided into many modules such
service, user interface, viewing schedules and deleting schedules etc. Also, the whole unit will be tested
as every data entered and searched will also be tested; all the runtime errors can be detected and corrected
accordingly. There are also other types of testing such as integration testing; validation testing etc. the
whole project is integrated so it has to be tested at each and every point.
Testing is a process of checking whether the developed system is working according to
the original objectives and requirements. A test case is one that has a possibility of finding as yet
undiscovered error. A successful test is one that uncovers as yet undiscovered error. The developed
system is tested whether it works efficiently and whether it satisfies all the user requirements by taking
a series of test cases.

5.1.1. Types of Testing

The software, which has been developed, has to be tested to prove its validity. Testing is
considered to be least creative phase of the whole cycle of the system design. In the real sense it is the
phase, which helps to bring out the creativity of the phases. No system design is ever perfect. Errors
occur due to communication problems, programmer’s negligence or time constraints. All these must be
eliminated before the system is ready for user acceptance testing.
Different levels of testing are employed during different stages of the system development.

College of Applied Science, Mavelikara

 35

[Link] White Box Testing

By using this technique, it was tested that all the individual logical paths were executed
at least once as logical decisions were tested on both their true and false sides. All the loops were tested
with data in between the ranges and especially at the boundary values.
[Link] Black Box Testing

By the use of this technique, the missing functions were identified and placed in their
positions. The errors in the interfaces were identified and corrected. This technique was used to identify
the initialization and termination errors and correct them.
[Link] Unit Testing

In the lines of this strategy, all the individual functions and modules were put to the test
independently. By following this strategy, all the errors in coding were identified and corrected. This
method was applied in combination with the White Box and Black Box testing techniques to find the
errors in each module.
[Link] Integration Testing

This testing strategy has two different approaches namely the top down approach, in
which the integrations are carried out from the top level module to the bottom and bottom up approach
in which the integration is carried out from the low level module to the top. The modules were tested
using the bottom up approaches by introducing stubs for the top-level functions. This test was used to
identify the errors in the interfaces, the errors in passing the parameters between the functions and to
correct them.

[Link] Validation Testing

Validation testing can be defined in many ways, but a simple definition that validation
succeeds when the software in a manner that is reasonably expected by the customer. Software validation
is achieved through a series of black box test that demonstrate conformability with requirements. After
validation test have conducted, one of the two possible conditions exists.

• The function or performance characterized confirm the specification and are accepted.

• Deviation from specification is found and a deficiency list is created.

College of Applied Science, Mavelikara

 36

[Link] Output Testing

After performing the validation testing, the next step is output testing of the proposed
system since no system could be useful if it does not produce the required output in a specific format.
Asking the users about the format required by them tests the outputs generated or displayed by the system
under consideration.
The output format of a screen is found to be correct as the format was designed in the
system design phase according to the user needs. For the hard copy also, output comes out as the specified
requirements by the user. Hence output testing does not result in any correction in the system.

5.2 TEST CASES

A specific set of steps and data along with expected results for a particular test objective.
A test case should only test one limited subset of a feature of functionality. Test case documents for each
functionality/ testing areas will be written, reviewed and maintained separately in Excel sheets.
In system testing, test data should cover the possible values of each parameter based on
the requirements. Since testing every value is impractical, a few values should be chosen from each
equivalence class. An equivalence class is a set of values that should all be treated the same. Ideally, test
cases that check error conditions are written separately from the functional test cases and should have
steps to verify the error message s and logs. Realistically, if error test cases are not yet written, it is OK
for testers to check for error conditions when performing normal functional test cases. It should be clear
which test data, if any, is expected to trigger errors.

College of Applied Science, Mavelikara

 37

CHAPTER 6
SYSTEM IMPLEMENTATION
6.1 INTRODUCTION

Implementation is the stage of project when the theoretical design is turned into a working
system. At this stage, the main workload, the greatest upheaval and the major impact on existing practices
shift to the user department. If the implementation stage is not carefully planned and controlled, it can
cause chaos. The implementation stage is a system project in its own right. It involves careful planning,
investigation of the current system and its constraints on implementation, design of methods to achieve
the changeover, training of staff in the changeover procedure and evaluation of changeover methods.
The implementation is the final and important phase. It involves user training system
testing in order to ensure successful running of the proposed system. Once the system design phase is
over, the next stage is to implement and monitors the operation of the system to ensure that it continues
the work effectively and efficiently.
The three main phases in implementation take place in series. These are the initial
installation, the test of the system as a whole and evaluation maintenance and control of the system. The
implementation plan and action to implement should be bound closely together. The implementation
plan is a function of line management at least as far as key decision or alternative plans are concerned.
The implementation plan was to convert the existing clerical files to the computer. The implementation
plan listed all sub tasks so that individuals in the organization may be assigned specific responsibilities.
The installation of the new system that is bound to replace the current one may require a
major revision of computer facilities as well as completely new after space. Space planning took into
account the space occupied by the people, space by equipment and the movement of people and
equipment in the working investment. After conduction the initial testing the system is loaded on the
client office's computer. Some of the user employees in this case are selected. These users are trained
first and they run the system. A detailed documentation is prepared to this set of employees. There may
be slight modifications to meet the organization.

After all modifications specified by the users in the documentation are made, the computer
system is run along with manual system. Even though this kind of parallel run make extra burden to the

College of Applied Science, Mavelikara

 38

employees and management, the system is run in parallel for the sake of checking reliability and
efficiency.
After this document which compares the result of the manual system with those of the
computerized is prepared. In the case of management many of whom participated in the development of
the system short seminars were given. Particular attention was paid to the training of end users. The
training sessions were aimed at giving the user staff the specific skills required in their new jobs.
Education involved creating the right atmosphere and motivation of user staff. It explained the need for
changes and helped to overcome the resentment caused by the feeling that computers took away the
responsibility from individual departments.

Various measures have been taken by department officials in order to find suitable solutions by the
following issues

 About the skill to be acquired.

 Reduction of man power in department.

 About the new form having all required option.

6.2 IMPLEMENTATION PROCEDURE

Implementation is the stage of the project where the theoretical design is turned into a
working system. At this stage, the main work load, the greatest upheaval and the major impact on the
existing system shifts to the department. If the implementation is not carefully planned and controlled,
it can cause confusion. Implementation includes all those activities that take place to convert from the
old system to the new one. Proper implementation is essential to provide a reliable system to meet the
organizational requirements.

Successful implementation may guarantee improvement in the organization using the new
system, but improper installation will prevent it. The process of putting the developed system into the
actual use is called system implementation. This includes all those activities that take place to convert
from the old system to the new system. The system can be implemented only after through testing is done
and if it is found to be working according to the specification of the system.

College of Applied Science, Mavelikara

 39

The most crucial stage is achieving a new successful system and giving confidence on the
new system for the user that it will work efficiently. It involves careful planning, investigation of the
current system and is constraints on implementation, design of methods to achieve the changeover. The
more the complex system being implemented is, the more involved will be the system analysis and the
design effort required for its implementation.

6.2.1 EQUIPMENT ACQUISITION

Here, the necessary equipment is acquired to implement the system. Major steps involved
in the implementation are installation of software. In case of this system there is no special hardware
requirement for the working of the software. In addition to basic hardware requirements one thing that
is essential is the software requirements with an operating system that has server support. The proposed
system can run on any PC, which works on android and any versions of it. Our software is platform
dependent and will run only on the windows platform after installing the software, it is essential to ensure
that the software is working accordingly with the existing software.

6.2.2 TRAINING

For this system, it was explained to the users how to use the system, what details are to be
given while creating a new profile, how to use it so that we get the maximum output out of it. The
proposed system may be entirely new, replacing an existing one or it may be modifications to the existing
system. In either case, proper implementation is necessary to provide a reliable system to meet
organizational requirements.

6.2.3 EVALUATION

Evaluation of the system is performed to identify its strength and weaknesses.

[Link] OPERATIONAL EVALUATION

Assessment of the manner in which the system functions, including ease of use, response
time, overall reliability and level of utilization.

6.2.4 ORGANIZATIONAL IMPACT

Identification and measurement of benefits to the organization in such areas like financial
concerns, operational efficiency and competitive impact.

College of Applied Science, Mavelikara

 40
6.2.5 USER MANAGEMENT ASSESSMENT

Evaluation of attitude of senior and user managers within the organization, as well as end
users.

6.2.6 DEVELOPMENT PERFORMANCE

Evaluation of the development process based on overall development time and effort,
conformance to budgets and standards, and other project management criteria includes assessment of development
methods and tools.

6.2.7 DOCUMENTATION

After the testing and implementation was completed, the whole system was presented and
documented in a readable manner. This was done to ensure that any corrections, manipulations or
updating are performed in future, the users would face no problem in performing those changes.
Documentations include the source code, the tables that were used to construct the base for the system,
the framework which is bound to the programs etc.

College of Applied Science, Mavelikara

 41

CHAPTER 7
SOFTWARE MAINTENANCE
Software maintenance denoted any changes made to a software product after it has been
delivered to the customer. Maintenance is inevitable for almost any kind of product. Most products need
maintenance due to wear and tear by use. Although software does not wear out like a piece of hardware
it “ages” and eventually fails to perform. So maintenance becomes necessity. Types of software
maintenance:

7.1 CORRECTIVE MAINTENANCE

Corrective maintenance of a software product is necessary either to rectify the bugs

observed while the system is in use.

7.2 ADAPTIVE MAINTENANCE

A software product might need maintenance when the customers need the product to run
on new platforms, on new operating systems, or when they need the product to interface with new
hardware or software.

7.3 PERFECTIVE MAINTENANCE

A software product needs maintenance to support the new features that users want it to
support, to change different functionalities of the system according to customer demands, or to enhance
the performance of the system.

7.4 PREVENTIVE MAINTENANCE

Modification of a software product after delivery to detect and correct latent faults in the
software product before they become effective faults.

College of Applied Science, Mavelikara

 42

CONCLUSION

The CivicAI project aims to create a platform that connects citizens, government
departments, and administrative staff, fostering a seamless environment for civic complaint
submission, intelligent routing, resolution tracking, and public service communication. With a
comprehensive set of features such as complaint management, AI-powered categorization, department
assignment, citizen dashboards, complaint tracking, feedback collection, notifications, AI-assisted
priority prediction, and duplicate detection, the application ensures a smooth experience for both
citizens and government personnel.

By incorporating role-based management for citizens, staff, and admins, CivicAI provides a controlled
and transparent workflow for civic complaint management. Citizens can submit and track complaints,
staff can manage assigned grievances and update resolution progress, and administrators can monitor
users, oversee departments, review analytics, and manage platform activity. Features such as image
uploads, location tracking, AI recommendations, sentiment analysis, and automated notifications
improve transparency, efficiency, and accountability within the system.

The project can be further expanded to include advanced features such as map-based complaint
visualization, real-time geospatial analytics, automated SMS alerts, AI-powered chatbot assistants for
citizen support, document verification for complex complaints, and mobile application support. These
enhancements would make the platform more useful for real-world civic governance and improve
citizen convenience.

The CivicAI project is a step toward modernizing civic services by making complaint reporting,
resolution tracking, and public service communication more accessible, reliable, and efficient for
everyone.

College of Applied Science, Mavelikara

 43

FUTURE ENHANCEMENT
Future enhancements for the CivicAI project could focus on improving convenience and
efficiency for citizens, staff, and administrators. Map-based complaint visualization and real-time
grievance alerts would allow citizens to view complaints in their area, track resolution progress
geographically, and identify recurring civic issues more easily. AI-driven complaint trend analysis
could predict systemic problems, identify high-risk areas, and suggest proactive interventions based on
historical data, complaint patterns, and seasonal variations. Adding mobile notification systems, SMS
alerts, and automated status updates would also improve the complaint tracking process and keep
citizens informed throughout the resolution lifecycle.

Another key area for enhancement is expanding analytical, reporting, and integration features.
Advanced analytics dashboards with predictive maintenance forecasting, department performance
benchmarking, resolution time optimization, and resource allocation recommendations would make
the platform more useful for administrative decision-making. Integration with government databases,
GIS mapping systems, and third-party civic services would increase accuracy and reduce manual data
entry. A dedicated multi-department coordination module could also be introduced, allowing complex
complaints involving multiple departments to be tracked, managed, and resolved collaboratively from
one unified interface.

The platform could also benefit from community-focused features and accessibility
improvements. Public complaint transparency portals, neighborhood issue tracking, citizen
engagement forums, and community feedback mechanisms could help users participate more actively
in civic governance. Multilingual support would make the system more accessible to citizens from
different regions, while voice-assisted complaint submission could help users report issues hands-free.
By focusing on these enhancements, the CivicAI project can become a more user-centric, transparent,
intelligent, and practical civic governance solution.

College of Applied Science, Mavelikara

 44

APPENDIX

10.1 SCREENSHOTS

Fig: 10.1.1 Home Pages

Fig: 10.1.2 Registration Pages

College of Applied Science, Mavelikara

 45

Fig: 10.1.3 Login Pages

Fig: 10.1.3 Admin Pages

College of Applied Science, Mavelikara

 46

Fig: 10.1.4 Staff Pages

Fig: 10.1.5 Citizen Pages

College of Applied Science, Mavelikara
 47

10.2 SOURCE CODE

[Link]

{% extends 'base/[Link]' %}
{% load static %}
{% block title %}Home{% endblock %}

{% block body %}
<div class="public-shell">
<header class="public-nav">
<a class="public-brand" href="{% url 'home' %}">
<span class="public-brand-icon"><i class="fas fa-city"></i></span>
<span>
<strong>CivicAI</strong>
<small>Smart city management</small>
</span>
</a>
<nav class="public-links" aria-label="Primary navigation">
<a href="#about">About</a>
<a href="#features">Features</a>
<a href="#demo">Demo</a>
<a href="#goals">Goals</a>
<a href="{% url 'accounts:login' %}">Login</a>
<a class="public-nav-cta" href="{% url 'accounts:register' %}">
Register
</a>
</nav>
</header>

<main>
<section class="public-hero">
<img
class="public-hero-image"
src="[Link]
c41746248156?auto=format&fit=crop&w=1800&q=80"
alt="Bright modern city street with public infrastructure"
/>
<div class="public-hero-overlay"></div>
<div class="public-hero-content" data-reveal>
<p class="public-kicker">AI-powered civic operations</p>
<h1>CivicAI</h1>
<p class="public-hero-copy">
Report public infrastructure issues, route them to the right
department, and track resolution from one clean citizen portal.
</p>
<div class="public-actions">
<a class="public-btn primary" href="{% url 'accounts:register' %}">
<i class="fas fa-user-plus"></i>
College of Applied Science, Maavelikara
 48
Create citizen account
</a>
<a class="public-btn secondary" href="#demo">
<i class="fas fa-circle-play"></i>
Watch demo
</a>
</div>
<div class="public-hero-metrics" aria-label="CivicAI platform highlights">
<span><strong>24/7</strong> issue intake</span>
<span><strong>AI</strong> categorization</span>
<span><strong>Live</strong> status tracking</span>
</div>
</div>
<div class="public-hero-panel" data-reveal>
<div class="hero-card-header">
<span class="status-dot"></span>
Complaint intake live
</div>
<div class="hero-ticket">
<strong>Streetlight outage</strong>
<span>AI route: KSEB</span>
</div>
<div class="hero-progress">
<span class="done">Submitted</span>
<span class="active">Assigned</span>
<span>Resolved</span>
</div>
</div>
</section>

<section class="public-section public-about" id="about">

<div class="public-section-grid">
<div data-reveal>
<p class="public-kicker">About us</p>
<h2>Built for faster, clearer public service.</h2>
<p>
CivicAI connects citizens, staff, and administrators through
a focused complaint workflow. Citizens submit issues with
location and evidence, AI suggests department and priority,
and staff resolve work with visible status updates.
</p>
<div class="public-mini-stats">
<span><strong>GPS</strong> location support</span>
<span><strong>AI</strong> priority hints</span>
<span><strong>Full</strong> feedback loop</span>
</div>
</div>
<div class="public-image-panel" data-reveal>
<img
College of Applied Science, Maavelikara
 49
src="[Link]
eccb494ad742?auto=format&fit=crop&w=1200&q=80"
alt="City planning and infrastructure view"
/>
</div>
</div>
</section>

<section class="public-section public-features-section" id="features">

<div class="public-section-head" data-reveal>
<p class="public-kicker">Features</p>
<h2>Every role gets a practical workflow.</h2>
</div>
<div class="public-feature-grid">
<article class="public-feature-card" data-reveal>
<i class="fas fa-robot"></i>
<h3>AI Auto-Categorization</h3>
<p>Classifies road, electricity, water, sanitation, and waste issues.</p>
</article>
<article class="public-feature-card" data-reveal>
<i class="fas fa-bolt"></i>
<h3>Priority Detection</h3>
<p>Highlights urgent complaints so staff can focus on impact first.</p>
</article>
<article class="public-feature-card" data-reveal>
<i class="fas fa-map-location-dot"></i>
<h3>Status Tracking</h3>
<p>Shows citizens progress from submission to assignment and closure.</p>
</article>
<article class="public-feature-card" data-reveal>
<i class="fas fa-chart-line"></i>
<h3>Admin Analytics</h3>
<p>Turns complaint volume, department load, and sentiment into insights.</p>
</article>
<article class="public-feature-card" data-reveal>
<i class="fas fa-location-dot"></i>
<h3>Hotspot Detection</h3>
<p>Surfaces repeat problem areas for planning and preventive action.</p>
</article>
<article class="public-feature-card" data-reveal>
<i class="fas fa-comments"></i>
<h3>Feedback Loop</h3>
<p>Collects citizen ratings, comments, and evidence after resolution.</p>
</article>
</div>
</section>

<section class="public-section public-demo" id="demo">

<div class="public-demo-layout">
College of Applied Science, Maavelikara
 50
<div class="public-demo-copy" data-reveal>
<p class="public-kicker">Video walkthrough</p>
<h2>How citizens submit a complaint.</h2>
<p>
Watch the full flow: create an account, open the citizen
dashboard, submit issue details, let AI route the complaint,
and follow the status until feedback is complete. The updated
demo includes narration and captions for a clearer walkthrough.
</p>
<ol class="public-steps compact">
<li><span>1</span>Register or login as a citizen.</li>
<li><span>2</span>Describe the issue and add location details.</li>
<li><span>3</span>Submit, track status, and share feedback.</li>
</ol>
</div>
<div class="public-video-card" data-reveal>
<div class="public-video-top">
<span>
<i class="fas fa-circle-play"></i>
Complaint demo
</span>
<span>Narrated walkthrough</span>
</div>
<div class="public-video-shell">
<video
controls
playsinline
preload="metadata"
src="{% static 'videos/complaint-demo.mp4' %}"
aria-label="CivicAI complaint submission demo video">
Your browser does not support the video tag.
</video>
</div>
</div>
</div>
</section>

<section class="public-section public-flow" id="flow">

<div class="public-section-grid reverse">
<div class="public-image-panel" data-reveal>
<img
src="[Link]
b586d89ba3ee?auto=format&fit=crop&w=1200&q=80"
alt="Clean public street and civic space"
/>
</div>
<div data-reveal>
<p class="public-kicker">Complaint flow</p>
<h2>From citizen report to verified resolution.</h2>
College of Applied Science, Maavelikara
 51
<ol class="public-steps">
<li><span>1</span>Citizen submits issue details, location, and image evidence.</li>
<li><span>2</span>AI categorizes the issue and estimates priority.</li>
<li><span>3</span>Staff receive assigned work and update progress.</li>
<li><span>4</span>Citizens review the outcome and submit feedback.</li>
</ol>
</div>
</div>
</section>

<section class="public-section public-insights" id="insights">

<div class="public-section-grid">
<div data-reveal>
<p class="public-kicker">Operational intelligence</p>
<h2>Dashboards that turn complaints into decisions.</h2>
<p>
CivicAI gives administrators charts for category trends,
priority load, department performance, citizen sentiment,
and location hotspots while staff see focused task queues.
</p>
</div>
<div class="public-image-panel" data-reveal>
<img
src="[Link]
bebda4e38f71?auto=format&fit=crop&w=1200&q=80"
alt="Analytics dashboard with charts"
/>
</div>
</div>
</section>

<section class="public-section public-goals" id="goals">

<div class="public-section-head" data-reveal>
<p class="public-kicker">Our goals</p>
<h2>Make civic service faster, fairer, and measurable.</h2>
</div>
<div class="public-goal-grid">
<div class="public-goal" data-reveal>
<strong>Accountability</strong>
<span>Every issue has a status, department, and timeline.</span>
</div>
<div class="public-goal" data-reveal>
<strong>Transparency</strong>
<span>Citizens can see progress instead of guessing what happened.</span>
</div>
<div class="public-goal" data-reveal>
<strong>Operational clarity</strong>
<span>Admins can spot bottlenecks and rebalance city work.</span>
</div>
College of Applied Science, Maavelikara
 52
</div>
</section>

<section class="public-cta-band">
<div data-reveal>
<p class="public-kicker">Start today</p>
<h2>Report civic issues with confidence.</h2>
</div>
<div class="public-actions" data-reveal>
<a class="public-btn primary" href="{% url 'accounts:register' %}">
<i class="fas fa-user-plus"></i>
Register now
</a>
<a class="public-btn secondary dark" href="{% url 'accounts:login' %}">
<i class="fas fa-right-to-bracket"></i>
Login
</a>
</div>
</section>
</main>
</div>
{% endblock %}

College of Applied Science, Maavelikara

 53

10.2 GANTT CHART

The Gantt chart was developed by Henry Gantt. Those are used in software project
management and enhanced version of standard Gantt chart. These are mainly allocating resources to
activities. It is a special type of bar chart. Each bar represents an activity. Bars are drawn alone a
time line. Length of each bar is proportional to duration of time planned for corresponding activity.

feb 20 feb 26 mar 15 mar 20 apr 15 apr 20

College of Applied Science, Maavelikara

 54

REFERENCE

Text Books:

 Fundamentals of Software Engineering, Fifth Edition, Rajib Mall- PHI 2018

 Software Engineering: A Practitioner's Approach (IRWIN COMPUTER

SCIENCE) Hardcover – 16 March 2014

Websites:

 [Link]

 [Link]

 [Link]

 [Link]

 [Link]

College of Applied Science, Mavelikara