Académique Documents
Professionnel Documents
Culture Documents
Prepared by
Muhammad Hassan Tariq FA15-BCS-091
Hassan Ali FA15-BCS-192
Supervised by
Ma'am Hina Habib
Table of Contents
1
Table of Contents I
List of Figures II
1. Introduction .............................................................................................................................................. 3
1.1 Purpose ............................................................................................................................................... 4
1.2 Document Conventions ...................................................................................................................... 4
1.3 Intended Audience .............................................................................................................................. 4
1.4 Scope: .................................................................................................................................................. 4
1.5 Overview: ............................................................................................................................................ 4
1.6 Business Context: ................................................................................................................................ 4
2. General Description: ................................................................................................................................. 5
2.1 Product Function ................................................................................................................................. 5
2.2 Similar System Information................................................................................................................. 5
2.3 User Characteristics ............................................................................................................................ 5
2.4 User Problem Statement .................................................................................................................... 5
2.5 General Constraints ............................................................................................................................ 5
3. Functional Requirements: ......................................................................................................................... 5
3.1 Control Setup ...................................................................................................................................... 5
3.2 Player Customization. ......................................................................................................................... 6
3.3 Sound and Visual Settings ................................................................................................................... 6
3.4 Visual Info During play mode .............................................................................................................. 7
3.5 Save, Resume and Exit Options .......................................................................................................... 7
3.6 Map, Weapon & Enemy ...................................................................................................................... 7
3.7 Difficulty Levels ................................................................................................................................... 8
4. Interface Requirements ............................................................................................................................ 8
4.1 User interface...................................................................................................................................... 9
4.2 Hardware Interface ............................................................................................................................. 9
4.3 Communications Interfaces ................................................................................................................ 9
4.4 Software Interfaces ............................................................................................................................. 9
5. Performance Requirement ..................................................................................................................... 10
6. Design constraints ................................................................................................................................... 10
6.1 Standard compliance ........................................................................................................................ 10
2
6.2 Hardware Limitation ......................................................................................................................... 10
7. Non-Functional Requirements: ............................................................................................................... 10
7.1 Security ............................................................................................................................................. 10
7.2 Reliability........................................................................................................................................... 10
7.3 Maintainability .................................................................................................................................. 10
7.4 Portability .......................................................................................................................................... 10
7.5 Reusability ......................................................................................................................................... 11
8. UML Diagrams ......................................................................................................................................... 11
8.1 Use Case ............................................................................................................................................ 11
8.2 Sequence Diagram: ........................................................................................................................... 13
8.3 Class Diagram: ................................................................................................................................... 14
9. Preliminary Schedule .............................................................................................................................. 16
9.2 Unity 3D ............................................................................................................................................ 16
9.3 Preliminary Budget ........................................................................................................................... 16
10. Appendices ............................................................................................................................................ 16
10.1 Abbreviations and Acronyms .......................................................................................................... 16
10.2 Technologies to be used ................................................................................................................. 16
10.3 References ...................................................................................................................................... 16
List of Figures
• Use Case Diagram
• Sequence Diagram
• Class Diagram
1. Introduction
This document is a software requirement specification for our unity game project which we will
be developing as our final year project. To introduce you to the document, we will first give the
purpose and scope of this document, then follow with an overall description of the game. This
document will also refer to functionality, that is what the resulting game is supposed to do, as
well as showing its functionality in detail using UML diagrams. This document also specifies the
necessary software and hardware requirements necessary to run this project.
1.1 Purpose
This document is the SRS for our "LONE SURVIVOR" game. The document describes the
functions and performance requirements of the software. The purpose of this document is to
3
provide comprehensive requirements and goals for our game. This document helps the reader to
visualize the intent of the developers and how they expect the game to be.
1.4 Scope:
This software will be a game that will be used for entertainment purposes. The goal of this
document is to provide a description of product features and requirements. The specified
requirements in this document will be used for designing all features and components of game.
This document can be modify as needed when any change are required during creation of the
game.
1.5 Overview:
We are creating a 3d survival game with the theme “LONE SURVIVOR”. The platform we will
be using to develop this product or game will be “Unity 3D”. The cost of this product will be
mainly used on buying assets via Unity Store and other sources, which will be used in producing
better results for the game and a better experience for the player.
4
2. General Description:
2.1 Product Function
This game is a survival game where the players aim will be to survive using items and other
tactics .The player can use different weapons to kill the enemies and eat food to regain health etc.
3. Functional Requirements:
These are the main features of our system.
3.1.2Technical Issues
Since it will be played on different devices some controls might not be supported.
5
3.1.4 Dependency
There is no dependency with other requirements.
3.1.5 Criticality
Its not a critical requirement since the game can run on default controls and changing them or not
wont bring too much change to the game.
3.2.4 Dependency
This is dependent on the 3d model of your character as well as the scripts used in player
customization.
3.2.5 Criticality
This is a critical requirement since attacking and healing are fundamental parts of our game
3.3.5 Criticality
Sound and visual settings are a must for any game.
6
The game must show visual information for the players characteristics as well as the
environments in the form of a mini map.
3.4.2 Technical Issues
Some devices with smaller screens might not show the visual info properly.
3.4.4 Dependency
The dependency will be on the maps of the game.
3.4.5 Criticality
This is a critical requirement because it will tell the player where to go and what to do.
3.5.4 Dependency
There is no dependency for this.
3.5.5 Criticality
This is one of the most important requirement since without this the player cant progress in the
game.
7
3.6.4 Dependency
3D environment dependent on unity3D tool.
3.6.5 Criticality
This is the most critical requirement since this is the main objective of the game.
3.7.4 Dependency
There is no dependency.
3.7.5 Criticality
This isn’t a critical requirement and only enhances player experience.
4. Interface Requirements
This project does not interface with and other software product and only interfaces with the user
for input and output.
8
4.1.1 GUI
9
4.1.2 CLI
This project involves no CLI.
4.1.3 API
API will be used in this project to build android.
10
4.1.4 Diagnostic
Debugging will be done by console window in unity 3D tool. It will tell whether the function is
running or not, if user would find any problem in this game or any error. User would be able to
give feedback on the google app store through commenting or email us directly with any
complaints.
5. Performance Requirement
Following are the Minimum requirement for this Product/Game:
OS: Windows 7 or 10
Harddisk : 1gb
7. Non-Functional Requirements:
7.1 Security
In our game not much security is required at the moment as it is for entertainment but later on
when we add in game purchases we will need some.
7.2 Reliability
This Project or game should not hang, the game should run smooth and the game should load
within 10 seconds.
11
7.3 Maintainability
This Project is maintainable as unity3d has a window for debugging which is the console so it is
easily maintainable.
7.4 Portability
It will also support low end systems.
7.5 Reusability
As there is always room of improvement, the subjected project will be of great help to bring
further versions in the same environment.
8. UML Diagrams
Some UML diagrams are provided to show the functionality of our project in detail.
12
Figure1.1 : Use Case Diagram
13
Figure 2: Sequence Diagram
14
8.3 Class Diagram:
This block diagram shows the interaction and actions performed by the users as well as the
functionality of the application.
15
Figure 3:Class Diagram
9. Preliminary Schedule
Finished week
Milestone
Id Forecast
Description Plan Actual
Week +/-
M-01 Use case diagram December
10,2018
M-02 Class diagram December
12,2018
M-03 Prepare SRS December
15,2018
M-04 Implementation
M-05 Remaining coding May 1,2019
M-06 Deployment Mar 25,2019
9.2 Unity 3D
This tool of designing 3D objects is freely available for personal use on internet.
10. Appendices
10.1 Abbreviations and Acronyms
SRS Software Requirement Specification
UML Unified Modeling Language
3D 3 Dimensional
PC Personal Computer
RAM Random Access Memory
OS Operating System
CPU Central Processing Unit
GB Giga Byte
10.3 References
https://unity3d.com/learn
16