SRS Hangman
SRS Hangman
SRS Hangman
SOFTWARE ENGINEERING
Hangman Game
Software Requirements Specification
Team:
Anne-Lise Griveau, 1262E
Maywadee Soytong, 1262E
Coordinator:
Dr. Ing. Goga Nicolae
Date created:
Monday, December 15, 2014
Delivery report
Delivery Report
(will be delivered along with the project)
Name
Group
_______________
______
____________________________ _________
____________________________
____________________________
_______________
______
____________________________ _________
____________________________
____________________________
_______________
______
____________________________ _________
____________________________
____________________________
Delivery date:
__________________________________
Signature
SRS
Table of Contents
POLITEHNICA UNIVERSITY OF BUCHAREST..........................................................1
SOFTWARE ENGINEERING..................................................................................1
DELIVERY REPORT............................................................................................2
TABLE OF CONTENTS.........................................................................................3
REQUIREMENTS ANALYSIS..................................................................................5
1. Introduction....................................................................................................................5
1.1. Purpose...................................................................................................................5
1.2. History.....................................................................................................................5
1.3. Scope......................................................................................................................5
1.4. Definitions, Acronyms and Abbreviations...............................................................5
1.5. References..............................................................................................................5
1.6. Structure..................................................................................................................5
2. General description.......................................................................................................6
2.1. Product Description.................................................................................................6
2.2. Product Functions...................................................................................................6
2.3. User description......................................................................................................6
2.4. Constraints..............................................................................................................6
2.5. Assumptions and Dependencies............................................................................6
3. System Requirements...................................................................................................7
3.1. External Interface Requirements............................................................................7
3.2. Functional Requirements........................................................................................7
3.3. Performance Requirements....................................................................................8
3.4. Design Constraints..................................................................................................8
3.5. Software System Attributes.....................................................................................8
3.6. Other System Requirements..................................................................................8
APPENDICES.....................................................................................................9
A1. Interview with the customer........................................................................................9
A2. System diagram..........................................................................................................9
A3. Use Cases Diagram....................................................................................................9
A4. Class Diagrams...........................................................................................................9
A5. Sequence Diagrams....................................................................................................9
A6. State Diagrams.........................................................................................................10
A7. Document Evolution..................................................................................................10
A8. Report regarding team meetings..............................................................................10
A9. Conclusions regarding the activity............................................................................10
SRS
Requirements Analysis
According to the IEEE STD-830-1993, IEEE Recommended Practice for Software Requirements
Specification.
1. Introduction
1.1. Purpose
The purpose of this document is to describe the software requirements for a Hangman game application.
1.2. History
This project doesnt represent a sequel of a functional project.
1.3. Scope
The hangman game is a game application whose purpose is to have the player guess a word by finding its
letters in a certain number of moves.
Its application field is games with a very slight educative note as this game can also help younger players to
better their spelling of common words.
1.5. References
[1] Dr.ir.N.Goga, Lecture Software Engineering, Polytechnic University of Bucharest, October 2014
[2] prof. Luca Dan Serbanati, Lecture Software Design Techniques, Polytechnic University of Bucharest,
October 2014
[3] Hangman (game), http://en.wikipedia.org/wiki/Hangman_(game), 26 October 2014, last visited 5
November 2014
1.6. Structure
The introduction of this document describes its purpose, scope and history of the project.
The General Descrition chapter describes the product resulting from the project and its usages.
The System Requirements chapter gives more details about the interface and functionalities of the final
products, as well as the different design constraints that should be respected.
The Appendices contain the UML diagrams that complement the system requirements chapter.
SRS
2. General description
2.1. Product Description
The product that will result from the project will be a game application of the hangman game. Its purpose will
be to entertain the player while improving his spelling ability.
Maintenance by adding new words to be guessed will be easy as the dictionary of words will be contained in
a simple file.
The interface should have few explicit buttons so as to be easily understood by the player.
This way the player will be able to start enjoying the game immediately without having to make efforts to
understand the way the game works.
2.4. Constraints
The application is a one player game.
We want the application to return the expected results in order not to spoil the fun of the player.
SRS
3. System Requirements
3.1. External Interface Requirements
User interface
The interface of the application is unique, it is the same for every user.
Hardware interfaces
The player interacts with the application using the classical input and output devices such as mouse,
keyboard, and computer screen.
Software (libraries or other parts/programs) interfaces
The application uses Java for the communication with the data files. In this way a high portability of
the sys application tem is assured, the only software interface needed being the one with JVM (Java
Virtual Machine) which can be easily installed on the common operating systems (Windows, Linux,
MacOS).
Application
2. Select a word and display underscores
3. Display the hints corresponding
Application
2. Display the character in place of
corresponding underscores (A)
3. Update the already proposed letters list
SRS
Main flow of events
Player
1. Input final character
Application
2. Display the completed word
SRS
Appendices
A1. Interview with the customer
A2. System diagram
A3. Use Cases Diagram
SRS
Propose character use case