Minesweeper Game- Milestone 1

This article provides the requirements, functional and non-functional requirements, constraints, project risk, prototype demo link, conceptual designs, UML classes, and use case for Minesweeper Game- Milestone 1. It includes information on the number of clicks and time passed, board sizes, bombs placement, refresh and restart options, and proper messages. It also covers the robustness, usability, data integrity, response time, and scalability of the software. The article also discusses the constraints and project risks associated with the development of the game. Additionally, it provides a prototype demo link and conceptual designs in the form of UML classes and use case diagram.

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

3
MINESWEEPER GAME- MILESTONE 1
should and must allow the intake of larger inputs as and when needed due to the
increase in required data or functionalities.
Constraints
1. The use of high quality images for the purpose of representing the button icons will
consume a lot of memory space and make the application bulky.
2. For smaller screen sizes the application window will have to shrink as well. This will
lead to the improper visualization of the game board with the buttons looking too
small and the whole layout may become clumsy.
3. Updates are harder to be chipped in. This requires a confirmation from Google Play
store and only then can it be rolled out to the community. This process may
sometimes get too lengthy. The frequent updates in applications to fix requested
errors generally take 7 days to reach to a minimum of only 10% of the users. The bugs
in the developed system hence persists.

4
MINESWEEPER GAME- MILESTONE 1
Project Risk
The project is to be broken down into two primary phases in terms of development. In
the first phase, a simpler prototype of the application is to be designed and developed that
will suffice only to some of the basic requirements of the game. Reviews and bug reports will
be collected from this phase and then the main project phase will be initiated where the entire
game is to be designed and developed keeping in mind the improvements needed.
Being a comparatively smaller project, the application can be developed using the
agile software development process. Here, the preliminary requirements are first collected,
the software designs are finalized and consulted with the client. Furthermore, on approval
from the client, the final phase is to be designed, developed, tested and deployed.

5
MINESWEEPER GAME- MILESTONE 1
Prototype Demo Link
Link: https://
Reflection
The prototype demo currently consists of many limitations when contrasted against
the entire project requirement plans. This version only consists of the game board for the
Easy game mode. I have only managed to implement the 6*6 board within the initial
prototype. It however performs the game functionalities as close as possible. Furthermore, the
prototype is yet to implement the timer, which is prescribed to be implemented in the final
project and is under process.

6
MINESWEEPER GAME- MILESTONE 1
Conceptual Designs
UML Classes
Fig 1: UML Class Diagram

7
MINESWEEPER GAME- MILESTONE 1
Use Case
Fig 2: Use Case diagram