Minesweeper Game- Milestone 1

Running head: MINESWEEPER GAME- MILESTONE 1
Minesweeper Game- Milestone 1
Name of the student:
Name of the University:
Author note:

1
MINESWEEPER GAME- MILESTONE 1
Table of Contents
Requirement Analysis................................................................................................................2
Functional Requirements.......................................................................................................2
Non-functional Requirements................................................................................................2
Constraints..............................................................................................................................3
Project Risk................................................................................................................................4
Prototype Demo Link.................................................................................................................5
Conceptual Designs....................................................................................................................6
UML Classes..........................................................................................................................6
Use Case.................................................................................................................................7

2
MINESWEEPER GAME- MILESTONE 1
Requirement Analysis
Functional Requirements
1. The number of clicks and time passed in seconds for a particular game session, is to
be displayed at the top.
2. There must be two board sizes, 6*6 as easy mode and 12*12 as the difficult mode.
The gamer must be presented with the option to choose their mode of difficulty and
start the game.
3. There must be 10 bombs placed randomly on the board for the easy mode and 20 for
the difficult.
4. User must be allowed to refresh and restart the game whenever necessary.
5. A proper Congrats or failure message must be shown with the Click and Time played
information when a bomb is hit or a victory is achieved.
Non-functional Requirements
1. Robust: The software or application needs to be robust. It must be able to handle
tactfully all the wrong decisions taken by the user and never lead to a program crash.
2. Usability: Being an android application software, the application must be able to run
on all the newer android devices and the interface device must be flexible enough to
fit into any screen resolution.
3. Data integrity: Necessary and permitted data within the application needs to be
thoroughly available within the respective nodes of the application.
4. Response Time: The application should be able to respond as quickly as possible to
every user interactions.
5. Scalability: The program should be so moulded that it is kept open to any changes,
additions and modifications for newer requirements in the near future. The program