VAILANKANNI PUBLIC SCHOOL

ROYAKOTTAI ROAD , KRISHNAGIRI

PROJECT
IN
COMPUTER SCIENCE (083)
Academic Year 2022-23

PY-LUDO
NAME : …………………………………….

CLASS : …………………………………… .

ROLL.NO : ……………………………………..

REG. NO : …………………………………….

Under the Guidance

Of

Mr.Vignesh Padmanaban M.Sc,B.Ed.,

Pgt.Computer Science
 VAILANKANNI PUBLIC SCHOOL
ROYAKOTTAI ROAD , KRISHNAGIRI

BONAFIDE CERTIFICATE

This is to certify that this project report entitled

…………………………………………………………………….is a bonafide

record of the project work done by ..................................................

of class..............Reg.No........................in the academic year

2022- 2023.The project has been submitted in partial fulfillment

of AISSCE for practical held at Vailankanni Public school on
..........................

Internal Examiner External Examiner

PRINCIPAL
 ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends largely on the
encouragement and guidelines of many others. I take this opportunity to express my gratitude
to the people who have been instrumental in the successful completion of this project.

I express deep sense of gratitude to almighty God for giving me strength for
the successful completion of the project.

I express my heartfelt gratitude to my parents for constant encouragement

while carrying out this project.

I gratefully acknowledge the contribution of the individuals who contributed in

bringing this project up to this level, who continues to look after me despite my flaws,

I express my deep sense of gratitude to the The Principal,Mr. P.N.Ashok,

Vailankanni public school who has been continuously motivating and extending their helping
hand to us.

I express my sincere thanks to the academician The Vice-Principal

Mr.Emmanuel MJ Selvam, Vailankanni public school, for constant encouragement and the
guidance provided during this project

I am overwhelmed to express my thanks to The Administrative Officer for

providing me an infrastructure and moral support while carrying out this project in the school.

My sincere thanks to Mr.Vignesh Padmanaban, Master In-charge, A guide,

Mentor, who critically reviewed my project and helped in solving each and every problem,
occurred during implementation of the project

The guidance and support received from all the members who contributed and who are
contributing to this project, was vital for the success of the project. I am grateful for their
constant support and help.

Sincerely,
 CONTENTS

 Introduction
 Hardware and Software Requirement
 System Development Life Cycle (SDLC)
 Source Code
 Software Testing
 Output
 Conclusion
 Bibliography
 INTRODUCTION

Ludo Game project is written in Python. The project file contains python scripts
(game.py, run.py, painter.py, recorder.py). This is a simple console based strategy
board game which is very easy to understand and use. Talking about the gameplay,
all the playing rules are the same just like we play in real time Ludo.Here at first,
the user has to select players ,either human or computer. After selecting human, the
player has to enter details such as name and select color(red, green, yellow and
blue). The player can also start the game within two players if he/she wants.

After starting the game, a console based ludo board appears, other rules are the
same. First, the computer or the player has to roll the dice. The main thing in this
console based game is that the player just has to press “Enter Key” to roll the dice.
At the top of the board, it displays a dice with the number. The system keeps on
rolling until there’s a possible pawn to move. All the game movements are
performed automatically. Whenever the player tries to end the game, there’s an
option available to save the unfinished game so that he/she can continue it later. A
simple console GUI is provided for the easy gameplay. The gameplay design is so
simple that user won’t find it difficult to use and understand.

In order to run the project, you must have installed Python, on your PC. This is a
simple console Based game written for the beginners.
HARDWARE AND SOFTWARE
REQUIREMENT:

RAM : 2GB(Minimum)

4GB(Recommended)

Operating system : 32bitx86

64bitx64(Recommended)

Hard disk : Minimum250MBfreememory

Processor : dual core 2.80GHZ or Greater

Screen Resolution : 1366x768(optimal)

Graphics card : Minimum 64 GB

Platform : Windows 7/8/10 with SPI

Python version : Python 3.0 or Greater

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, 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
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 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.
This document receives a rigorous review by Agency technical and functional
representatives to ensure that it satisfies the business requirements. Concurrent with the
development of the system design, the Agency Project Manager begins development of
the Implementation Plan, Operations and Maintenance Manual, and the Training Plan.
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. 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.
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 renter 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 :-
from collections import namedtuple, deque

import random

from .painter import PaintBoard

Pawn = namedtuple("Pawn", "index colour id")

class Player():

'''Knows (holds) his pawns,

also know his colour

and choose which pawn to move

if more than one are possible

'''

def __init__(self, colour, name=None, choose_pawn_delegate=None):

'''choose_pawn_delegate is callable.

if choose_pawn_delegate is not None it is called

with argument list of available pawns to move

and expect chosen index from this list

if it is None (means computer) random index is chosen

'''

self.colour = colour

self.choose_pawn_delegate = choose_pawn_delegate

self.name = name
 if self.name is None and self.choose_pawn_delegate is None:

self.name = "computer"

self.finished = False

# initialize four pawns with

# id (first leter from colour and index (from 1 to 4))

self.pawns = [Pawn(i, colour, colour[0].upper() + str(i))

for i in range(1, 5)]

def __str__(self):

return "{}({})".format(self.name, self.colour)

def choose_pawn(self, pawns):

'''Delegate choice to choose_pawn_delegate func attribute

if it is not None

'''

if len(pawns) == 1:

index = 0

elif len(pawns) > 1:

if self.choose_pawn_delegate is None:

index = random.randint(0, len(pawns) - 1)

else:

index = self.choose_pawn_delegate()
 return index

class Board():

'''

Knows where are pawns.

Pawns are assigned with position numbers.

Can move (change position number) pawn.

Knows other things like

what distance pawn must past to reach end.

It just board. It does not know rules of the game.

'''

# common (shared) squares for all pawns

BOARD_SIZE = 56

# save (private) positions (squares) for each colour

# This is squares just before pawn finished

BOARD_COLOUR_SIZE = 7

COLOUR_ORDER = ['yellow', 'blue', 'red', 'green']

# distance between two neighbour colours

# (The distance from start square of one colour

# to start square of next colour)

COLOUR_DISTANCE = 14
def __init__(self):

#fn1353c

# get dict of start position for every colour

Board.COLOUR_START = {

colour: 1 + index * Board.COLOUR_DISTANCE for

index, colour in enumerate(Board.COLOUR_ORDER)}

# get dict of end position for every colour

Board.COLOUR_END = {

colour: index * Board.COLOUR_DISTANCE

for index, colour in enumerate(Board.COLOUR_ORDER)}

Board.COLOUR_END['yellow'] = Board.BOARD_SIZE

# dict where key is pawn and

# value is two size tuple holds position

# Position is combination of

# common (share) square and coloured (private) square.

self.pawns_possiotion = {}

# painter is used to visually represent

# the board and position of the pawns

self.painter = PaintBoard()
 # pool means before start1353

self.board_pool_position = (0, 0)

def set_pawn(self, pawn, position):

'''save position'''

self.pawns_possiotion[pawn] = position

def put_pawn_on_board_pool(self, pawn):

self.set_pawn(pawn, self.board_pool_position)

def is_pawn_on_board_pool(self, pawn):

'''return True of False'''

return self.pawns_possiotion[pawn] == self.board_pool_position

def put_pawn_on_starting_square(self, pawn):

start = Board.COLOUR_START[pawn.colour.lower()]

position = (start, 0)

self.set_pawn(pawn, position)

def can_pawn_move(self, pawn, rolled_value):

'''check if pawn can outside board colour size'''

common_poss, private_poss = self.pawns_possiotion[pawn]

 if private_poss + rolled_value > self.BOARD_COLOUR_SIZE:

return False

return True

def move_pawn(self, pawn, rolled_value):

'''change pawn position, check

if pawn reach his color square

'''

common_poss, private_poss = self.pawns_possiotion[pawn]

end = self.COLOUR_END[pawn.colour.lower()]

if private_poss > 0:

# pawn is already reached own final squares

private_poss += rolled_value

elif common_poss <= end and common_poss + rolled_value > end:

# pawn is entering in own squares

private_poss += rolled_value - (end - common_poss)

common_poss = end

else:

# pawn will be still in common square

common_poss += rolled_value

if common_poss > self.BOARD_SIZE:

common_poss = common_poss - self.BOARD_SIZE

 position = common_poss, private_poss

self.set_pawn(pawn, position)

def does_pawn_reach_end(self, pawn):

'''if pawn must leave game'''

common_poss, private_poss = self.pawns_possiotion[pawn]

if private_poss == self.BOARD_COLOUR_SIZE:

return True

return False

def get_pawns_on_same_postion(self, pawn):

'''return list of pawns on same position'''

position = self.pawns_possiotion[pawn]

return [curr_pawn for curr_pawn, curr_postion in

self.pawns_possiotion.items()

if position == curr_postion]

def paint_board(self):

'''painter object expect dict of

key - occupied positions and

value - list of pawns on that position

'''
 positions = {}

for pawn, position in self.pawns_possiotion.items():

common, private = position

if not private == Board.BOARD_COLOUR_SIZE:

positions.setdefault(position, []).append(pawn)

return self.painter.paint(positions)

class Die():

MIN = 1

MAX = 6

@staticmethod

def throw():

return random.randint(Die.MIN, Die.MAX)

class Game():

'''Knows the rules of the game.

Knows for example what to do when

one pawn reach another

or pawn reach end or

player roll six and so on

'''

def __init__(self):

self.players = deque()

self.standing = []

self.board = Board()

# is game finished

self.finished = False

# last rolled value from die (dice)

self.rolled_value = None

# player who last rolled die

self.curr_player = None

# curr_player's possible pawn to move

self.allowed_pawns = []

# curr_player's chosen pawn to move

self.picked_pawn = None

# chosen index from allowed pawn

self.index = None

# jog pawn if any

self.jog_pawns = []
def add_palyer(self, player):

self.players.append(player)

for pawn in player.pawns:

self.board.put_pawn_on_board_pool(pawn)

def get_available_colours(self):

'''if has available colour on boards'''

used = [player.colour for player in self.players]

available = set(self.board.COLOUR_ORDER) - set(used)

return sorted(available)

def _get_next_turn(self):

'''Get next player's turn.

It is underscore because if called

outside the class will break order

'''

if not self.rolled_value == Die.MAX:

self.players.rotate(-1)

return self.players[0]

def get_pawn_from_board_pool(self, player):

 '''when pawn must start'''

for pawn in player.pawns:

if self.board.is_pawn_on_board_pool(pawn):

return pawn

def get_allowed_pawns_to_move(self, player, rolled_value):

''' return all pawns of a player which rolled value

from die allowed to move the pawn

'''

allowed_pawns = []

if rolled_value == Die.MAX:

pawn = self.get_pawn_from_board_pool(player)

if pawn:

allowed_pawns.append(pawn)

for pawn in player.pawns:

if not self.board.is_pawn_on_board_pool(pawn) and\

self.board.can_pawn_move(pawn, rolled_value):

allowed_pawns.append(pawn)

return sorted(allowed_pawns, key=lambda pawn: pawn.index)

def get_board_pic(self):

return self.board.paint_board()
def _jog_foreign_pawn(self, pawn):

pawns = self.board.get_pawns_on_same_postion(pawn)

for p in pawns:

if p.colour != pawn.colour:

self.board.put_pawn_on_board_pool(p)

self.jog_pawns.append(p)

def _make_move(self, player, pawn):

'''tell the board to move pawn.

After move ask board if pawn reach end or

jog others pawn. Check if pawn and player finished.

'''

if self.rolled_value == Die.MAX and\

self.board.is_pawn_on_board_pool(pawn):

self.board.put_pawn_on_starting_square(pawn)

self._jog_foreign_pawn(pawn)

return

self.board.move_pawn(pawn, self.rolled_value)

if self.board.does_pawn_reach_end(pawn):

player.pawns.remove(pawn)

if not player.pawns:
 self.standing.append(player)

self.players.remove(player)

if len(self.players) == 1:

self.standing.extend(self.players)

self.finished = True

else:

self._jog_foreign_pawn(pawn)

def play_turn(self, ind=None, rolled_val=None):

'''this is main method which must be used to play game.

Method ask for next player's turn, roll die, ask player

to choose pawn, move pawn.

ind and rolled_val are suitable to be used when

game must be replicated (recorded)

ind is chosen index from allowed pawns

'''

self.jog_pawns = []

self.curr_player = self._get_next_turn()

if rolled_val is None:

self.rolled_value = Die.throw()

else:

self.rolled_value = rolled_val
 self.allowed_pawns = self.get_allowed_pawns_to_move(

self.curr_player, self.rolled_value)

if self.allowed_pawns:

if ind is None:

self.index = self.curr_player.choose_pawn(

self.allowed_pawns)

else:

self.index = ind

self.picked_pawn = self.allowed_pawns[self.index]

self._make_move(self.curr_player, self.picked_pawn)

else:

self.index = -1

self.picked_pawn = None

#!/usr/bin/env python3

from ludo.cli import CLIGame

CLIGame().start()
 Software 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.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided its
design and development, so that it works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method employed, can be
implemented at any time in the development process, however the most test effort is employed
after the requirements have been defined and coding process has been completed.

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.

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.
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
OUTPUT :
 CONCLUSION

This project implements a LUDO game in 2D GUI format. This

application allows the user to play the game by simply opening the
python script and prompting the game to start. The game interface
is very simple and is easy to understand by the user. Since the
game is built in 2D the game performance is fast and efficient .
The game can also store user’s score information by setting up a
database connection from the python script. The individual’s
scores are displayed in a new window called highscore window
where the players can compare each other’s score.
 BIBLIOGRAPHY

Books - Computer Scienec with Python-PREETIARORA,

Computer Science with Python-SUMITAARORA
Youtube - https://youtu.be/JvfMTv1o5Zk
Website - http://ieeeproject.org

***