Professional Documents
Culture Documents
Final Documentation
Final Documentation
Normally games require little bit high space for playing games but this game is light that it
can be install in each and every handheld device with normal space. It does not require any
additional memory or space as it is small enough that any android phone be able to play this
game. Ludo is a board game it will be play by two to four players. At the beginning of the
game, each player's tokens are out of play and staged in one of the large corner areas of the
board in the player's color (called the player's yard). When able to, the players will enter their
tokens one per time on their respective starting squares, and proceed to race them clockwise
around the board along the game track (the path of squares not part of any player's home
column). When reaching the square below his home column, a player continues by racing
tokens up the column to the finishing square. The rolls of a cube die control the swiftness of
the tokens, and entry to the finishing square requires a precise roll from the player. The first
to bring all their tokens to the finish wins the game. The others often continue play to
determine second-, third-, and fourth-place finishers.
Table of Contents
CHAPTER 1: INTRODUCTION………………………………………….01
2.1.1 Introduction…...………..…………………………………………...07
2.3.3 Performance………………………………………………………..09
2.3.4 Scalability…………………………………………………..............09
2.3.5 Reliability…………………………………………………………..09
Introduction
1.1 Project Overview
Two, three, or four may play. At the beginning of the game, each player's
tokens are out of play and staged in one of the large corner areas of the board in the player's
color (called the player's yard). When able to, the players will enter their tokens one per time
on their respective starting squares, and proceed to race them clockwise around the board
along the game track (the path of squares not part of any player's home column). When
reaching the square below his home column, a player continues by racing tokens up the
column to the finishing square. The rolls of a cube die control the swiftness of the tokens, and
entry to the finishing square requires a precise roll from the player. The first to bring all their
tokens to the finish wins the game. The others often continue play to determine second-,
third-, and fourth-place finisher.
The scope of our application will be limited to the functional design of the original Ludo,
along with our own selection of additions and modifications to the same. It will support
saving and loading the states of games in progress, and also the ability to save or abandon a
game in progress.
• Start a game of Ludo select whether it should be a multiplayer or single player game
◦ depending on the rules do battle with another player, if they have pieces in the same spot of
the playing field. The battle consists of solving a mathematical problem. Whichever player
solves it fastest will be able to push the other player’s piece to another place on the playing
field.
• Load/save a game in progress: if a game is saved, make a copy of the current State of the
game. If a game is loaded, set its State to the target loaded State.
• Exit/forfeit a game in progress if there are no other human players in the game, quit the
application and lose all unsaved state. If there are other human players, the game will not
close for them.
• Start a game of Ludo select whether it should be a multiplayer or single player game
• select how many human players and computers to play against (4 in all),
Tools:
Technologies
Requirement Analysis
Software Requirement specification
Introduction
Ludo (from Latin ludo, "I play") is a simple board game, for two to four players, in which the
players race their four coins from start to finish according to dice rolls. Ludo is a board game
for two to four players, in which the players race their four tokens from start to finish
according to die rolls. Like other cross and circle games, Ludo is derived from the Indian
game Pachisi, but simpler. The game and its variants are popular in many countries and under
various names.
2.1 Purpose
The purpose of this application is to provide the indoor game service .The user can install
this amazing application on his/her smart phone and can get all feature of this application.
It contain two to four player .this game is played by adults and children’s as well. it is also
known as board game .The benefit of board game for kids? Some are obvious .kids enjoy
them and board games are opportunities for families to play together. In addition social
scientist has argued games teach lesson about getting along with others. Board game can
teach the important social skills.
Chapter 2
• Start a game of Ludo select whether it should be a multiplayer or single player game
• select how many human players and computers to play against (4 in all),
◦ depending on the rules do battle with another player, if they have pieces in the same spot of
the playing field. The battle consists of solving a mathematical problem. Whichever player
solves it fastest will be able to push the other player’s piece to another place on the playing
field.
If a game is saved, make a copy of the current State of the game. if a game is loaded, set its
State to the target loaded State.
• Exit/forfeit a game in progress if there are no other human players in the game, quit the
application and lose all unsaved state. If there are other human players, the game will not
close for them.
• Chat with other human players during a network game there will be a separate window
where players can exchange messages.
System communication
Internet connection
Chapter 2
Smart phone
Bluetooth
Design
Response time
There will not be a delay greater than 3 seconds between a user initiating an action,
and the system performing it.
Hardware Requirements
Software Requirement’s
i. Performance
Game running on mobile should have maximum throughput and maximum utilization.
ii. Scalability
As this game is for android mobiles so it is scalable with android OS platform.
iii. Reliability
As this game is for android mobiles so it is reliable with android OS platform.
According to our specifications, a successful implementation of Ludo will allow its user to do
all of the following:
• Start a game
• Roll a die
• Exit
• Show time
In summary, our overall criteria are to have a fully functioning Ludo game in terms of core
functionality, extended by our own features.
Actor: User
Pre-condition:
Use went to main Manu for choosing the game for start
Post condition:
Description
The user opens the main menu and chooses the number of player then click on the start
button the game will turn on.
Chapter 2
Actor: User
Pre-condition:
Post condition
Description
Actor User
Pre-condition
Post condition
Description
When user click on choose color the color will assign to the user.
Chapter 2
Pre-condition
Actor: Player
Post condition
Description
When the player click on the exit button after clicking the exit button the message is
displayed do you want to save the game click on yes or no then the game will be terminated.
Chapter 3
Software Design
3.1 Use Case Diagram
System
Start Game
Chose Color
User
Sound ON/OFF
Exit Game
Activity Diagram
Start game
start game
No
Yes
Activity Diagram
Choose Color
Select color
No
Yes
continue game
Activity Diagram
Sound ON/OFF
sound
mute/unmute No
Yes
Activity Diagram
Exit Game
Game
Exit No
Yes
User
User
Game Manue Choose color Play Game Win/Loss
2 : Chose color()
3 : Play game()
4 : Win or Loss()
User
Play game
Home Menu
Win/Loss
user 1
user 4
LAN
User 2 user 3
LUDO MODEL
+Board
+List_Player
View Player
+CanMovePice()
+LudoModel +EndGame() +Color
+Controler +MovePice() +SetPiceStatus()
+NextPlayerTurn() +SetPiceNumber()
+StartGame() +RollDie()
+EndGame() +GetPiceNumber()
+StartGame() +SetColor()
+InilizBoard()
+RollDie()
Board
+Squre<list> Die
Action
+Pices<list>
+DieValue
+Nthing
+SetColor()
+RollDie +RollDie()
+SetWon()
+MovePice
+GetColor()
+EndGame
+GetWon()
Piece Square
+Color +Piece
+GetWon
+AddPiece()
+SetColor() +RemovePece()
+SetWon() +SetColor()
+GetColor() +SetGoal()
+GetWon() +SetHouse()
Project Management
Milestones
4.1 Milestones
As we have been no mandatory deadlines for deliverable during the master thesis work. We
will present the work conducted at the end of each week to the supervisor. These may come
up with suggestions and directions to guide us in the further work.
Project Milestones
Project start
Project GUI
Project Defender
Documentation of 3rd chapter
50% development and documentation evaluation
Complete working web system
Integration of payment method
Complete documentation and testing
Deploy Solution
Project complete
Table 4.1 Project Milestones
Person Or
Resources Organization who Turnover Date
Received Resource
Describe or name the resources used
1.1.1.1.1 Project team
K H Sajjad Ahmad AAUR-UIIT
Muhammad Saad Zahoor AAUR-UIIT
Muhammad Hamza AAUR-UIIT
1.1.1.1.2 Facilities
Internet access
Reversed lab for project
Documentation of previous projects
in Library
1.1.1.1.3 Equipment
Intel(R)Core i3 KH Sajjad Ahmad
Intel(R)Core i5 Muhammad Saad
1.1.1.1.4 Software Tools
ADT
Android Studio
Microsoft office 2007
JDK
Resize
1.1.1.1.5 Other
Support of Supervisor Project Team
Support of Examiners Project Team
Table 4.2.3 Project Resources
Prioritize and describe the plans for responding to each risk identified and evaluated.