Amrita Public School

Session : 2024 -25

Informatics Practices
(065)

Project File On
COVID-19
ANALYSIS
SYSTEM
SUBMITTED TO :
Ms. Garima Singh SUBMITTED BY:
Rohit Kumar
Class 12th B (Commerce)

1 | Page
 Board Roll No.
Amrita Public School
Teacher Sign:
Date of Submission
16/01/2025

CERTIFICATE

This is to certify that Rohit, student of Class XII B (Commerce) Amrita

Public School, has completed the research Project on Covid 19 Analysis
System under the guidance of Ms. Garima Singh during the year 2024-
2025 in partial fulfilment of Informatics Practices Practical Examination
conducted by Central Board of Secondary Education, New Delhi- 80.

Internal Examiner External Examiner

Signature :- Signature:-

Date: - School Seal :-

Principal :-
Signature :-
2 | Page
 ACKNOWLEDGEMENT

I would like to extend my sincere thanks to [Link] Singh ,my Informatics

Practices teacher, for her invaluable guidance and support throughout the duration of
this project. Her insights and feedback have been immensely helpful and have greatly
contributed to the completion of this work.

I am also grateful to my groupmates, for their assistance and encouragement. Their

ideas and perspectives have added significant value to this project.

Special thanks go to my family, who have provided me with the necessary resources
and a conducive environment to work on this project. Their constant encouragement
and belief in my abilities have been a source of motivation.

Lastly, I thank all those who directly or indirectly contributed to the success of this
project. Your support has been invaluable.

Rohit kumar

Class – 12th [Commerce]

Amrita Pubic School

3 | Page
 INDEX

SL NO DESCRIPTION PAGE NO

1 INTRODUCTION “COVID-19 ANALYSIS SYSTEM” 05

2 OBJECTIVES, FEATURES,BENEFITS OF THE PROJECT 05

3 OBJECTIVES OF PROJECT FOR STUDENTS 06

4 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 06

5 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 07

6 FLOW CHART 13

7 SOURCE CODE 13

8 OUTPUT 16

9 TESTING 19

10 HARDWARE AND SOFTWARE REQUIREMENTS 21

11 BIBLIOGRAPHY 22

4 | Page
 INTRODUCTION: COVID-19 ANALYSIS SYSTEM

This analysis explores the recovery rates of COVID-19 across different Indian
states. By visualizing the Recovery,Death, Active status of people in various states, we
aim to gain insights into regional variations in disease management and treatment
outcomes. This information can be valuable for policymakers and healthcare
professionals in developing targeted interventions to improve recovery rates
nationwide.

OBJECTIVES:
⮚ Gain Insights: Analyze the regional distribution of cases to understand the
impact of COVID-19 across different parts of the country.

This information can be valuable for policymakers and healthcare professionals in

allocating resources and implementing targeted interventions.

⮚ By visualizing and analyzing the data, we can gain a better understanding of

the regional disparities in COVID-19 spread and inform strategies for effective
disease management and control.

FEATURES:
1. User-friendly Interface: The program offers a menu-driven interface that is easy
to navigate.
2. Data Security: The program utilizes a CSV (Comma Separated File) Format for
data storage, ensuring the security and integrity of information.
3. Error Handling: The program incorporates error handling mechanisms to prevent
invalid data entries and unexpected program crashes.

BENEFITS:

1. Improved Efficiency
2. Enhanced Reports

5 | Page
 3. Informed Decision Making: Reports and visualizations provide valuable insights
for making good and valid arrangements in healthcare

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.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when developing small to

medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as exemplified

in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct a research or applied Computer Science

project, requiring writing and presentation skills which exemplify scholarly style in

computer science.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

6 | Page
 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.

7 | Page
 ● 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.
8 | Page
 ● Evaluate costs and benefits of alternative approaches to satisfy the basic functional
requirements
● Assess project risks
● Identify and initiate risk mitigation actions, and Develop 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’s job 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

9 | Page
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 a
level 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 Master Plan.
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

10 | Page
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.
● Everything requiring user input or approval is documented and reviewed by the user.
Once these documents have been approved by the Agency CIO and Business
Sponsor, the final System Design Document is created to serve as the Critical/Detailed
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
11 | Page
 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. OIT Security staff assess
the system security and issue a security certification and accreditation prior to
installation/implementation.

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.
12 | Page
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 re enter
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.

FLOW CHART

PYTHON CSV CONNECTING

ASKS USER TO ENTER HIS CHOICE

YOUR NEED WILL BE FULFILLED THROUGH PYTHON BY

INTERACTING WITH CSV

ie. stored in CSV Data File

Getting information from CSV file

13 | Page
 SOURCE CODE

import pandas as pd
from tabulate import tabulate #This Library Helps to format data as table
import [Link] as plt
df1 = pd.read_csv("C:\\Users\\Maanu\\Documents\\COVID19 PANDEMIC DATA
[Link]",names=['States', 'Confirmed_Cases', 'Recovered_Cases', 'Death_Cases', 'Active_Cases'])

def show_dataframe():
print("Dataframe Containing Whole Covid-19 Data")
print(tabulate(df1))

def sumtotalcase():
print("Sum Total of Each Type Cases")
print("\t Confirmed Recovered Death Active Cases")
print(tabulate([Link][27:28,:]))

# 1. Bar Graph: Total of Each Case

def eachtype_bargraph():
total_cases = [Link][-1][['Confirmed_Cases', 'Recovered_Cases', 'Death_Cases', 'Active_Cases']]

[Link](figsize=(10, 5))
[Link](total_cases.index, total_cases.values, color=['blue', 'green', 'red', 'orange'])
[Link]('Case Type')
[Link]('Total Cases')
[Link]('Total Cases in India')
[Link]()

# 2. Line Graph: Total of Each Case

def eachtype_linegraph():
total_cases = [Link][-1][['Confirmed_Cases', 'Recovered_Cases', 'Death_Cases', 'Active_Cases']]

[Link](figsize=(10, 5))
[Link](total_cases.index, total_cases.values, marker='+', linestyle='-', color='r')
[Link]('Case Type')
[Link]('Total Cases')
[Link]('Total Cases in India')
[Link](total_cases.index)
[Link]()

# 3. Bar Graph: Highest vs. Lowest Death Rate

def bargraph_deathrate():
df1['Confirmed_Cases'] = pd.to_numeric(df1['Confirmed_Cases'], errors='coerce')
df1['Death_Cases'] = pd.to_numeric(df1['Death_Cases'], errors='coerce')
df1['Death_Rate_per_50'] = (df1['Death_Cases'] / df1['Confirmed_Cases']) * 50
14 | Page
 df1['Death_Rate_per_50'] = df1['Death_Rate_per_50'].fillna(0) # Replace NaN values with 0
df1_sorted = df1.sort_values('Death_Rate_per_50', ascending=False)
highest_state = df1_sorted.iloc[0]['States']
lowest_state = df1_sorted.iloc[-1]['States']
[Link](figsize=(10, 5))
[Link](['Highest (' + highest_state + ')', 'Lowest (' + lowest_state + ')'],
[df1_sorted.iloc[0]['Death_Rate_per_50'], df1_sorted.iloc[-1]['Death_Rate_per_50']])
[Link]('State')
[Link]('Death Rate per 50 Cases')
[Link]('Comparison of Highest and Lowest Death Rates')
[Link]()

#rk try: and except: functions have been used for error handling
while (True):
print("_"*80)
print("<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<'COVID-19 Analysis
System'>>>>>>>>>>>>>>>>>>>>\n")
print("<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<•CONFIRMED /RECOVERED /DEATHS /ACTIVE
CASES•>>>>>>>>>>>>>>>>>>>")
print("_"*80)
choice=int(input("\t\t\t\tEnter 1 To See Analysis\n\t\t\t\tEnter 2 For Data Visualization Through
Chart\n\t\t\t\tEnter 3. Exit\n\n"))
if choice ==1:
while (True):
try:
print("\t\t\t\tEnter Your Choice\n\t\t\t\[Link] Show Whole Covid Data\n\t\t\t\[Link] See Sum
Total of Each Cases\n\t\t\t\[Link] To Main Menu\n\n")
ch =int(input())
if ch==1:
show_dataframe()
elif ch==2:
sumtotalcase()
elif ch==3:
break
except:
print("Error ! Wrong Entry")
elif choice ==2:
while (True):

try:
print("\t\t\t\tEnter Your Choice\n\t\t\t\[Link] Graph Analysis Of Each Cases Type\n\t\t\t\
[Link] Graph Analysis of each Type of Cases\n\t\t\t\[Link] of Highest and Lowest Death Rate
State\n\t\t\t\[Link] To Main Menu\n\n")
ch =int(input())
if ch==1:
eachtype_bargraph()
elif ch==2:

15 | Page
 eachtype_linegraph()
elif ch==3:
bargraph_deathrate()
elif ch==4:
break
except:
print("Error ! Wrong Entry")
#Softwares are the means to help solving Problems
elif choice ==3:
break

OUTPUT

16 | Page
17 | Page
18 | Page
 TESTING

Software Testing is an empirical investigation conducted to provide stakeholders with

information about the quality of the product or service under test[1] , with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks
at implementation of the software. Test techniques include, but are not limited to, the process
of executing a program or application with the intent of finding software bugs.

TESTING METHODS
Software testing methods are traditionally divided into black box testing and white box testing.
These two approaches are used to describe the point of view that a test engineer takes when
designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory
testing and specification-based testing.
19 | Page
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to the

applicable requirements.[16] Thus, the tester inputs data into, and only sees the output from,
the test object. This level of testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output value (or behaviour), either
"is" or "is not" the same as the expected value specified in the test case. Specification-based
testing is necessary, but it is insufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception is very simple: a
code must have bugs. Using the principle, "Ask and you shall receive," black box testers find
bugs where programmers don't. But, on the other hand, black box testing has been said to be
"like a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the
software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases to check
something that can be tested by only one test case, and/or (2) some parts of the back end are
not tested at all. Therefore, black box testing has the advantage of "an unaffiliated opinion,"
on the one hand, and the disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has access to the
internal data structures and algorithms (and the code that implement these)

Types of white box testing:-

The following types of white box testing exist:
● api testing - Testing of the application using Public and Private APIs.
● Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in the program
to be executed at least once.
● fault injection methods.
● mutation testing methods.

20 | Page
 ● static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness of a test
suite that was created with black box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important function
points have been tested.
Two common forms of code coverage are:
● Function Coverage: Which reports on functions executed and
● Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage

HARDWARE AND SOFTWARE REQUIREMENTS

[Link] SYSTEM : WINDOWS 10 (64-bit) OR MAC OS HIGH SIERRA (10.13)

OR LINUX (UBUNTU 18.04 OR HIGHER

II. PROCESSOR : Intel Core i5, i7 (9th Or 10th Gen) 2.5GHz

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIA K8M800+8237R PLUS
CHIPSET FOR AMD ATHALON

IV. RAM : 4 GB or more

V. HARD DISK : 250 GB OR ABOVE

VI. CD/DVD (r/w multi drive combo): (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR : 21-inch

21 | Page
IX. KEY BOARD AND MOUSE

X. PRINTER

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

BIBLIOGRAPHY

⮚ INFORMATICS PRACTICES - Class XI By: Sumita Arora

⮚ INFORMATICS PRACTICES – Class XII By: Preeti Arora
⮚ WIKIPEDIA.
⮚ [Link].
⮚ QUARA

22 | Page
23 | Page