Software Requirements

Specification
for

Wizards Chess
Version 1.0 approved

Prepared by Aaron Friesenhahn

Team LAZT

3/10/2015

CopyrightbyKarlE.Wiegers.Permissionisgrantedtouse,modify,anddistributethisdocument.

SoftwareRequirementsSpecificationfor<Project>

Pageii

Table of Contents
Table of Contents.............................................................................................................ii
Revision History...............................................................................................................ii
1. Introduction.................................................................................................................1
1.1
1.2
1.3
1.4
1.5

Purpose........................................................................................................................... 1
Document Conventions....................................................................................................1
Intended Audience and Reading Suggestions.................................................................1
Product Scope................................................................................................................. 1
References...................................................................................................................... 1

2. Overall Description....................................................................................................2
2.1
2.2
2.3
2.4
2.5
2.6
2.7

Product Perspective.........................................................................................................2
Product Functions............................................................................................................ 2
User Classes and Characteristics....................................................................................2
Operating Environment....................................................................................................2
Design and Implementation Constraints..........................................................................2
User Documentation........................................................................................................ 2
Assumptions and Dependencies.....................................................................................3

3. External Interface Requirements..............................................................................3

3.1
3.2
3.3
3.4

User Interfaces................................................................................................................. 3
Hardware Interfaces.........................................................................................................3
Software Interfaces.......................................................................................................... 3
Communications Interfaces.............................................................................................4

4. System Features.........................................................................................................4
4.1
4.2
4.3
4.4
4.5
4.6

Move Sets........................................................................................................................ 4
Talking.............................................................................................................................. 4
Piece Removal................................................................................................................. 4
Winning Color Change.....................................................................................................5
A.I..................................................................................................................................... 5
Game Modes................................................................................................................... 5

5. Other Nonfunctional Requirements.........................................................................5

5.1
5.2
5.3
5.4
5.5

Performance Requirements.............................................................................................5
Safety Requirements.......................................................................................................6
Security Requirements.....................................................................................................6
Software Quality Attributes...............................................................................................6
Business Rules................................................................................................................ 6

Revision History
Name

Date

Reason For Changes

Version

SoftwareRequirementsSpecificationfor<Project>

1.

Introduction

1.1

Purpose

Page1

Wizards Chess v1.0 is a player versus player chess game related to that you would
encounter in the magical world of Harry Potter. The game will appear as a standardized
game of chess that two players take part in but will notice the color of the board to be
different from a traditional game board. Not only will they notice a color change but will
see that the chess pieces will talk to the players dependent on various events or
encounters.

1.2

Document Conventions

Bolded out key points in this packet will highlight anything that will hold high value or
priority to keep note of as well as any bullets points that follow will break down our high
priority object to detail. Bullet points in general will break down objectives as needed to
highlight within said objectives of important details, this may not mean that the objective is
in high priority but only to detail the objective further to understand.

1.3

Intended Audience and Reading Suggestions

This document is intended for our professor, developers, testers and users. This packet
contains information on details of the Wizards Chess operations of the game such as how
to play the game, what to expect and what differs from Wizards Chess and a normal game
of chess.

1.4

Product Scope

The objective of Wizards Chess, like a standard game of chess, is to take your opponents
king piece. Meaning to have one of your pieces occupy the opponents king piece making
the king no longer available for play. To achieve this you must corner the opponents king
to not allow it for any more moves. If there is an available move the king can move to
avoid being taken it must make one of the available moves to ensure its safety. The player
must plan out how they want to arrange their pieces to achieve this.

1.5

References

Our team website is http://lazt.weebly.com/ where we have documented our team

members, their roles, a timeline of our project which describes the steps we will take to
complete the project and the dates we hope to accomplish this by.

SoftwareRequirementsSpecificationfor<Project>

2.

Overall Description

2.1

Product Perspective

Page2

This project is a class project but intended for others such as close friends and family to
be able to enjoy something that a small group of students were able to put together in a
semester's time and call it their own piece of work.

2.2

Product Functions

The users will be able to:

Play a turn by turn based game of chess
Observe how the players pieces are communicating with the player
keep track of what pieces have been taken by both players with a display alongside the board

2.3

User Classes and Characteristics

There are no restraints in this software as it is intended to be used by everyone on the

same level, no higher administrators being separated in access from a normal user
access.

2.4

Operating Environment

The product will be developed in a Windows 7 and Windows 8 operating environment. We

will be programming using netBeans in a .java platform.

2.5

Design and Implementation Constraints

The challenge we face is if we will be able to complete the project to its full potential within
the time requirements. The developers will be responsible for seeing the project to
completion within the given time as well as keeping up with any needed updates and bug
fixed.

2.6

User Documentation

Rules for chess

How to move game pieces

SoftwareRequirementsSpecificationfor<Project>

2.7

Page3

Assumptions and Dependencies

Time management will be a factor that we need to keep in mind as we have only a couple
months to complete the project and have quite a few things to implement such as the
rules that we need the game to follow and turn by turn base with only one move per each
player a turn. We must consider making a way for the player to finalize their turn letting the
player decide not to finalize the move from a wrongly moved piece.

3.

External Interface Requirements

3.1

User Interfaces

The user interface for the Wizards Chess game would be fairly straightforward. The program
upon execution would ask the players to select a house from the novel series Harry Potter.
After each player selects the house the board will set up the chess pieces and the color of the
board itself would change with each turn to the active players house colors.
During the actual game the player would be able to select a chess piece and either drag and
drop or click the desired piece and again click the desired move-to location (drag and drop or
other move action will be determined at a later date).
The program would also offer options to replay the game, ask for a draw, surrender or give up,
depending on how the game is going.

3.2

Hardware Interfaces

The only hardware interface necessary would be to take in user mouse input and the
keyboard input so the users can enter their name. The system will need to be able to interpret
the user input of the mouse and determine where they clicked, what game piece is in that spot,
and where the following click would send the piece.

3.3

Software Interfaces

There will not be any need for interface between this program and other software. This game
program will be a stand-alone system.

SoftwareRequirementsSpecificationfor<Project>

3.4

Page4

Communications Interfaces

At first this game will not need any communication interfaces. It will be up to the user to go
online and manually check for a system update, download and install it. Possibly in the distant
future there may be an update that would allow the game to play multi-player online games,
but initially the game would not be an online system.

4.

System Features

4.1

Move Sets
4.1.1 Description and Priority
Giving each piece their own unique move sets and making sure that each
piece stays within them. This is High priority.
Benefit: 9
Risk: 7
4.1.2 Stimulus Response Sequences
When the player clicks on the piece and moves them.

4.2 Talking
4.2.1 Description and Priority
Making the pieces talk to each other or the player. This is Low priority.
Benefit: 5
Risk: 7
4.2.2 Stimulus Response Sequences
They could react to when a player tries to make an illegal move or when
they are selected.

4.3 Piece Removal

4.3.1 Description and Priority
Removing the pieces from the board either completely or putting them next
to the board. This is High priority.
Benefit: 7
Risk: 5
4.3.2 Stimulus Response Sequences
When a piece is knocked out by another one, the piece should be taken off
the board.

4.4 Winning Color Change

4.4.1 Description and Priority

SoftwareRequirementsSpecificationfor<Project>

Page5

Making the board change its colors to the current winning players. This is
Low priority.
Benefit: 5
Risk: 5
4.4.2 Stimulus Response Sequences
Whenever a player is winning, the board changes colors.

4.5 A.I.
4.5.1 Description and Priority
Enabling the player to be able to play against the computer. This is Low
priority.
Benefit: 7
Risk: 7
4.5.2 Stimulus Response Sequences
The player could have the choice between playing against another person or
being able to compete against the computer.

4.6 Game Modes

4.6.1 Description and Priority
Having different rules sets and pieces for certain game modes and changing
the difficulty of the computer. This is Low priority.
Benefit: 7
Risk: 7
4.6.2 Stimulus Response Sequences
The player could choose between different types of games to play and could
make the computer harder to beat.

5.

Other Nonfunctional Requirements

4.2

Performance Requirements

Performance requirements for the Wizards Chess project are:

1. Smooth animations for the pieces when clicking and dragging/clicking and placing
pieces to the available movement spots.
2. Fast loading time between turns and when, if time allows, it is the A.I.s turn,
allowing the game to go at a pace that will not damage the quality of the game.
3. The color of the board/background for the winning team to be smooth and not take
away from the performance of the game.
4. No lagging of the game as the error checks and checks of the king are being
calculated as well as each piece moves.
5. Turns work as they are designed; the turns do not stay on one person indefinitely
and switch between each play as they move one piece.
6. The game shall perform as well as any normal chess game would, with most or all
of the rules that would apply to chess.

SoftwareRequirementsSpecificationfor<Project>

Page6

7. To run smoothly on Windows 7 and other software we plan to run it on.

4.3

Safety Requirements

Take precautions to not cause irreparable damage to eyes or body. For example: do not
play this game for long amounts of time; exercise every now and then.

4.4

Security Requirements

The Wizards Chess may require a simple login and password so as to keep your account
when multiplayer online becomes available. We will take care of all problems that may
persist with Wizards Chess.

4.5

Software Quality Attributes

The Wizards Chess project is aimed to be very easy to use as you simply click and
drag/click and place the pieces and take turns as you play. As time goes on, we can begin
to add more eye-pleasing graphics to the pieces and background, and more versatile
moves for the pieces. It is very easy to maintain, reuse, and test as we test each piece
and give the option to reset the board when you win or at any time during the match. All
processes of the Wizards Chess project will be tested by us before we believe it is
available for release. Anything that may be wrong will be handled by us directly.

4.6

Business Rules

The business rules are as apply: we simply ask that you play and enjoy the game as we
have provided and kindly ask that, if you run into any problems, you contact us so that we
can fix it right away. We do not require any kind of information for you so that you can play
as we have kept it simple with the options to play against others.