0% found this document useful (0 votes)
14 views28 pages

Air Quality Index Data Analysis Project

Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views28 pages

Air Quality Index Data Analysis Project

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

SRI CHAITANYA School

Techno Curriculum
The right mentor for IIT (JEE), Medical, Olympiad & All other competitive exam
CBSE AFFILIATION NO : 1930805 SCHOOL CODE : 55710 SUB CODE : 083

Air Quality Index – Data Analysis

ROLL NO :
NAME :
CLASS : XII
SUBJECT : COMPUTER SCIENCE
SUB CODE : 083

PROJECT GUIDE:

PROJECT WORK DONE BY:


SRI CHAITANYA School
Techno Curriculum
The right mentor for IIT (JEE), Medical, Olympiad & All other competitive exam
CBSE AFFILIATION NO : 1930805 SCHOOL CODE : 55710 SUB CODE : 083

COMPUTER SCIENCE PROJECT FILE


It has been certified that of XII,
during the academic year 2022-2023 have completed a project
on and
have given a satisfactory account of this in their project report.

Reg No.

Place: Chennai

Date:

Subject Teacher Principal


Submitted for All India Senior Secondary Certificate
Practical Examination Held on
EXAMINERS

INTERNAL EXTERNAL
ACKNOWLEDGEMENT
We wish to express our deep gratitude and sincere thanks to the Principal
for his encouragement and for all the facilities that he provided for this
project work.
We sincerely appreciate the Vice Principal for his magnanimity and
taking us into his fold for which we shall remain indebted to.
We extend our hearty thanks to Computer Science faculty, who guided us
in the successful completion of this project. We take this opportunity to
express our deep sense of gratitude for her invaluable guidance, constant
encouragement, immense motivation, which has sustained our efforts at all the
stages of this Project work.
We can’t forget to offer our sincere thanks to our class in charge, parents
and to our classmates who helped us to carry out this project work
successfully and for their valuable advice and support, which we received
from them time to time.
[Link] DESCRIPTION
01 INTRODUCTION

02 OBJECTIVES OF THE PROJECT

03 PROPOSED SYSTEM

04 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

06 SOURCE CODE

07 OUTPUT
08 TESTING
09 INSTALLATION PROCEDURE
10 HARDWARE AND SOFTWARE REQUIREMENTS

11 BIBLIOGRAPHY
Air Quality
Index
Data
Analysis

ASD
INTRODUCTION

This project titled 'Air Quality Index Data Analysis' is developed to analyze
and visualize air quality data of different Indian cities using Python, Pandas,
Matplotlib. The data is imported from a CSV file instead of being hardcoded
in the program, ensuring dynamic data handling and real-world usability.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the


programming knowledge into a real-world situation/problem and exposed
the students how programming skills helps in developing a good software.

• To analyze city-wise air pollution levels using AQI data.

• To perform statistical operations using Pandas.

• To visualize AQI trends using Matplotlib charts.

• To store and retrieve data efficiently using MySQL.

• To build an understanding of data analytics using Python in real-world

contexts.
PROPOSED SYSTEM

The Air Quality Index Data Analysis project automates the process of
reading, analyzing, and visualizing air pollution data. It provides insights
into which cities have higher pollution levels and helps in understanding
environmental health trends.

The system reads data from a CSV file, stores it in a MySQL database,
and performs various analyses using Pandas. Matplotlib is used to create
charts for better visual understanding.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that


divides complex projects into smaller, more easily managed segments or phases.
Segmenting projects allows managers to verify the successful completion of
project phases before allocating resources to subsequent phases.
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance phases.
However, the phases may be divided differently depending on the organization
involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation, concept-development,
and planning phases. End users of the system under development should be
involved in reviewing the output of each phase to ensure the system is being built
to deliver the needed functionality.
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an


opportunity.
The purpose of the Initiation Phase is to:
• Identify and validate an opportunity to improve business accomplishments
of the organization or a deficiency related to a business need.
• Identify significant assumptions and constraints on solutions to that need.
• Recommend the exploration of alternative concepts and methods to satisfy
the need including questioning the need for technology, i.e., will a change
in the business process offer a solution?
• Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is documented
in a Concept Proposal. The Concept Proposal includes information about
the business process and the relationship to the Agency/Organization.
• Infrastructure and the Strategic Plan. A successful Concept Proposal results
in a Project Management Charter which outlines the authority of the project
manager to begin
the project.
Careful oversight is required to ensure projects support strategic business
objectives and resources are effectively implemented into an organization's
enterprise architecture. The initiation phase begins when an opportunity to add,
improve, or correct a system is identified and formally requested through the
presentation of a business case. The business case should, at a minimum, describe
a proposal’s purpose, identify expected benefits, and explain how the proposed
system supports one of the organization’s business strategies. The business case
should also identify alternative solutions and detail as many informational,
functional, and network requirements as possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or


opportunity is validated by the Agency/Organization Program Leadership and the
Agency/Organization CIO.
The purpose of the System Concept Development Phase is to:
• Determine the feasibility and appropriateness of the alternatives.
• Identify system interfaces.
• Identify basic functional and data requirements to satisfy the business need.
• Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
• Evaluate costs and benefits of alternative approaches to satisfy the basic
functional requirements
• Assess project risks
• Identify and initiate risk mitigation actions, andDevelop high-level
technical architecture, process models, data models, and a concept of
operations. This phase explores potential technical solutions within the
context of the business need.
• It may include several trade-off decisions such as the decision to use
COTS software products as opposed to developing custom software or
reusing software components, or the decision to use an incremental
delivery versus a complete, onetime deployment.
• Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support the
Information Technology Project Request (ITPR) process.
• The ITPR must be approved by the State CIO before the project can move
forward.

PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development,


acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, is necessary to coordinate activities and manage project risks
effectively. The depth and formality of project plans should be commensurate
with the characteristics and risks of a given project. Project plans refine the
information gathered during the initiation phase by further identifying the specific
activities and resources required to complete a project.
A critical part of a project manager’ sjob is to coordinate discussions
between user, audit, security, design, development, and network personnel to
identify and document as many functional, security, and network requirements as
possible. During this phase, a plan is developed that documents the approach to
be used and includes a discussion of methods, tools, tasks, resources, project
schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality assurance
planning, concept of operations, system security, verification and validation, and
systems engineering management planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements using
high-level requirements identified in the Initiation, System Concept, and Planning
phases. It also delineates the requirements in terms of data, system performance,
security, and maintainability requirements for the system. The requirements are
defined in this phase to alevel of detail sufficient for systems design to proceed.
They need to be measurable, testable, and relate to the business need or
opportunity identified in the Initiation Phase. The requirements that will be used
to determine acceptance of the system are captured in the Test and Evaluation
Masterplan.
The purposes of this phase are to:
• Further define and refine the functional and data requirements and
document them in the Requirements Document,
• Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what
information is generated, who generates it, where does the information
go, and who processes it),
• Develop detailed data and process models (system inputs, outputs, and
the process.
• Develop the test and evaluation requirements that will be used to
determine acceptable system performance.
DESIGN PHASE
The design phase involves converting the informational, functional, and
network requirements identified during the initiation and planning phases into
unified design specifications that developers use to script programs during the
development phase. Program designs are constructed in various ways. Using a
top-down approach, designers first identify and link major program components
and interfaces, then expand design layouts as they identify and link smaller
subsystems and connections. Using a bottom-up approach, designers first identify
and link minor program components and interfaces, then expand design layouts
as they identify and link larger systems and connections. Contemporary design
techniques often use prototyping tools that build mock-up designs of items such
as application screens, database layouts, and system architectures. End users,
designers, developers, database managers, and network administrators should
review and refine the prototyped designs in an iterative process until they agree
on an acceptable design. Audit, security, and quality assurance personnel should
be involved in the review and approval process. During this phase, the system is
designed to satisfy the functional requirements identified in the previous phase.
Since problems in the design phase could be very expensive to solve in the later
stage of the software development, a variety of elements are considered in the
design to mitigate risk. These include:
• Identifying potential risks and defining mitigating design features.
• Performing a security risk assessment.
• Developing a conversion plan to migrate current data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and outputs.
• Allocating processes to resources.
• Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the preliminary
design for the system.
DEVELOPMENT PHASE
The development phase involves converting design specifications into
executable programs. Effective development standards include requirements
that programmers and other project participants discuss design specifications
before programming begins. The procedures help ensure programmers clearly
understand program designs and functional requirements. Programmers use
various techniques to develop computer programs. The large transaction
oriented programs associated with financial institutions have traditionally
been developed using procedural programming techniques. Procedural
programming involves the line-by-line scripting of logical instructions that are
combined to form a program. Effective completion of the previous stages is a
key factor in the success of the Development phase. The Development phase
consists of:

• Translating the detailed requirements and design into system components.


• Testing individual elements (units) for usability.
• Preparing for integration and testing of the IT system.
INTEGRATION AND TEST PHASE

• Subsystem integration, system, security, and user acceptance testing is


conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system.

Multiple levels of testing are performed, including:


• Testing at the development facility by the contractor and possibly
supported by end users
• Testing as a deployed system with end users working together with
contract personnel
• Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing, a final Independent
Verification & Validation evaluation is performed and all documentation
is reviewed and accepted prior to acceptance of the system.

IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the
user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives
established during the planning phase. Implementation includes user notification,
user training, installation of hardware, installation of software onto production
computers, and integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance with the
defined user requirements.
OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued


performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can be
effectively adapted to respond to the organization’s needs. When modifications
or changes are identified, the system may reenter the planning phase.

The purpose of this phase is to:

• Operate, maintain, and enhance the system.


• Certify that the system can process sensitive information.
• Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
• Determine when the system needs to be modernized, replaced, or retired.
SOURCE CODE

import pandas as pd

import [Link] as plt

#creating a database

df=pd.read_csv('C:\\Users\\admin\\Desktop\\IP project\\[Link]',index_col='City')

print(df)

#creating a bargraph for variation of aqi across the years

[Link](kind='bar', figsize=(10,6))

[Link]("AQI Levels of Indian Cities (2020–2025)")

[Link]("Cities")

[Link]("Air Quality Index")

[Link](title="years")

[Link](True)

[Link]()

# Calculate average AQI for each city

x = [Link](axis=1)

print([Link](x))

# Function to categorize AQI

def category(aqi_value):

if aqi_value <= 50:

return 'Good'

elif aqi_value <= 100:

return 'Moderate'
else:

return 'Unhealthy'

# Apply category function

categories = [Link](category)

# Color mapping for each category

color_map = {'Good': '#8FE388', 'Moderate': '#F9E79F', 'Unhealthy': '#F1948A'}

colors = [Link](color_map)

# Create bar graph for average AQI per city

[Link](figsize=(10,6))

[Link]([Link], x, color=colors)

[Link]("Average AQI of Cities (2020–2025)")

[Link]("Cities")

[Link]("Average AQI")

[Link](True, linestyle='--', alpha=0.5)

[Link]()

# --- Ranking part ---

# Calculate mean AQI per year

x_yearwise = [Link](axis=0).rename('Average AQI')

# Create a DataFrame to hold results

results_df = [Link](x_yearwise)

# Calculate rank (Rank 1 = lowest/best AQI)


results_df['Rank'] = results_df['Average AQI'].rank(method='min', ascending=True).astype(int)

# Sort by Rank

df_sorted = results_df.sort_values('Rank')

# Display results

print(df_sorted[['Average AQI', 'Rank']])

# Calculate average AQI per city

df['Average_AQI'] = [Link](axis=1)

# Function to categorize air quality

def category(aqi_value):

if aqi_value <= 50:

return 'Good'

elif aqi_value <= 100:

return 'Moderate'

else:

return 'Unhealthy'

# Apply function

df['Category'] = df['Average_AQI'].apply(category)

# Rank cities by AQI (highest = worst)

df['Rank'] = df['Average_AQI'].rank(ascending=False, method='dense').astype(int)

print("\nCity Health Report:")


print(df[['Average_AQI', 'Category', 'Rank']])

df['Category'] = df['Average_AQI'].apply(category)

# Count how many cities fall in each category

category_count = df['Category'].value_counts()

print("Number of cities in each category:")

print(category_count)

# Colors for each category

colors = {'Good': '#8FE388', 'Moderate': '#F9E79F', 'Unhealthy': '#F1948A'}

# Create the pie chart

[Link](figsize=(7,7))

[Link](category_count,

labels=category_count.index,

autopct='%1.1f%%',

startangle=90,

colors=[colors[label] for label in category_count.index],

textprops={'fontsize': 12},

wedgeprops={'edgecolor':'white', 'linewidth': 2})

[Link]('City Air Quality Category Distribution (2020–2025)', fontsize=14)

[Link]()

#variation of aqi over the years for Chennai


years=(2020,2021,2022,2023,2024,2025)

chennai=(86,81,85,90,81,85)

[Link](years,chennai,marker='o', color='violet', linewidth=2)

[Link]('AQI of Chennai')

[Link]()
CSV FILE ([Link])

OUTPUT SCREEN
INSTALLATION PROCEDURE

Pre-Requisites:

1. You have to have the following soft wares for the successful running of this
software; which are

I) Python (Only for the First time), it is downloadable from


'[Link]'.

II) MySQL (Only for the First time), it is downloadable from


'[Link]'.

Installation:

1. There will be two folders namely 'Python Files' and 'EXE files' in the folder
'Source Code'.

2. The folder 'Python Files' will contain the source code of the software in
python language.

3. Pre install the following modules

[Link] or pymysql

4. Open the files in any python editors and run it to start and work on the
software.

5. Then run the file '[Link]' to start and work on the software.

.
HARDWARE AND SOFTWARE REQUIREMENTS

I. OPERATING SYSTEM : WINDOWS 10 AND ABOVE

II. PROCESSOR : INSPIRON OR PENTIUM(ANY) OR AMD

III. RAM : 4 GB+

[Link] disk : SATA 40 GB OR ABOVE

SOFTWARE REQUIREMENTS:

I. Python

BIBLIOGRAPHY

• Informatics Practices - Class XI & XII By : Sumita Arora


• A Project Report ATM Project
• Website: [Link]
• [Link]

You might also like