Project 7 - Tic-Tac-Toe Game Project-1
Project 7 - Tic-Tac-Toe Game Project-1
Project 7 - Tic-Tac-Toe Game Project-1
PROJECT REPORT ON
ROLL NO :
NAME :
CLASS :
XI
1
PROJECT GUIDE :
PGT (CS)
2
3
CERTIFICATE
down in the regulations of CBSE for the purpose of Practical [ Examination in Class
( Navdeep Aggarwal )
PGT Comp Sci
Master IC
Examiner:
Date:
4
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 16
09 OUTPUT 19
10 TESTING 20
12 BIBLIOGRAPHY 24
5
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.
INTRODUCTION
and Os is a paper-and-pencil game for two players, X and O, who take turns marking
the spaces in a 3×3 grid. The player who succeeds in placing three of their marks in a
6
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
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants
to stand against today’s merciless competition where not to wise saying “to err is
human” no longer valid, it’s outdated to rationalize your mistake. So, to keep pace
with time, to bring about the best result without malfunctioning and greater efficiency
so to replace the unending heaps of flies with a much sophisticated hard disk of the
computer.
7
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially had to maintain a lot of ledgers and a lot of paper work
has to be done but now software product on this organization has made their work
faster and easier. Now only this software has to be loaded on the computer and work
can be done.
This prevents a lot of time and money. The work becomes fully automated and
any information regarding the organization can be obtained by clicking the button.
8
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.
INITIATION PHASE
9
The Initiation Phase begins when a business sponsor identifies a need or an
opportunity.
10
The purpose of the System Concept Development Phase is to:
11
PLANNING PHASE
12
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.
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
13
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:
DEVELOPMENT PHASE
14
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:
Testing as a deployed system with end users working together with contract
personnel
15
Requirements are traced throughout testing,a final Independent Verification &
Validation evaluation is performed and all documentation is reviewedand
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 userrequirements.
FLOW CHART
16
SOURCE CODE
square_values = ["1", "2", "3", "4", "5", "6", "7", "8", "9"] number_of_turns
= 0 no_wins = True
player_1 = input("Enter a name for player 1 and press enter, leave blank to
leave as Player 1: ") player_2 = input("Enter a name for player 2 and press
== ""):
pass
#assigns X or O to players if
player_1_pick = "X"
18
#makes a move def make_a_move(player,
player_pick):
print("""
| |
{} | {} | {}
_____|_____|_____
| |
{} | {} | {}
_____|_____|_____
| |
{} | {} | {}
| |
square_values[7], square_values[8]))
try:
int(choice) if (1 <=
19
else:
ValueError:
square_values[value3] == "X"):
= False if(player_1_pick ==
else:
= False if(player_1_pick ==
else: pass
status_main if
20
(no_wins == True):
number_of_turns = number_of_turns + 1
make_a_move(player, pick) check_for_a_win(0,
1, 2) check_for_a_win(3, 4, 5) check_for_a_win(6,
7, 8) check_for_a_win(0, 3, 6) check_for_a_win(1,
4, 7) check_for_a_win(2, 5, 8) check_for_a_win(0,
4, 8) check_for_a_win(2, 4, 6) if (number_of_turns
status_main = False
square_values = ["1", "2", "3", "4", "5", "6", "7", "8", "9"] number_of_turns
= 0 no_wins = True
player_1 = input("Enter a name for player 1 and press enter, leave blank to
player_2 = input("Enter a name for player 2 and press enter, leave blank to
21
== "" or player_2 == ""): if (player_1
== ""):
(player_2 == ""):
pass
#assigns X or O to players if
player_1_pick = "X"
player_pick):
print("""
| |
{} | {} | {}
_____|_____|_____
| |
{} | {} | {}
_____|_____|_____
| |
{} | {} | {}
| |
22
""" .format(square_values[0], square_values[1], square_values[2],
square_values[7], square_values[8]))
try:
int(choice) if (1 <=
"O"): square_values.remove(choice)
= False else:
else:
ValueError:
value2, value3):
= False if(player_1_pick ==
23
"X"): print("Player 1 won!")
else:
= False if(player_1_pick ==
else:
pass
status_main if
check_for_a_win(0, 1,
2) check_for_a_win(3, 4, 5) check_for_a_win(6,
7, 8) check_for_a_win(0, 3, 6) check_for_a_win(1,
4, 7) check_for_a_win(2, 5, 8) check_for_a_win(0,
4, 8) check_for_a_win(2, 4, 6) if (number_of_turns
status_main = False
24
while (status_main == True):
func_1(player_1, player_1_pick)
25
TESTING
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.
SPECIFICATION-BASED TESTING
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, 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)
27
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.
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
BIBLIOGRAPHY
***
30