Requirement
The goal of this project is to implement a card game and make sure that the game follows the specific rules. Of course, we also aim at providing the user a good playing experience and clearly guide on how to play it. This section of the document contains the description of the requirements, the constraints and the quality standards that it must meet.
In this section, we are going the give a detailed specification of all the features that should be implemented in the project through user cases. A total of 10 use cases have been outlined for this project. Each of them is assigned an identifier, an importance and a difficulty out of 5. An importance of 5 suggests that the use case is crucial for the proper function of the game whereas an importance of 1 suggests that the use case is optional to the main function. Since the resource limited, some use cases may be eventually scoped down.
The game's name PokemonGoBack will be referred as PGB in the following section.
- Documentation. PGB's components, functions, algorithms and design will be fully documented;
- Ease of Play. PGB will be user-friendly. By developing clear views and comprehensive user interface, PGB will be a system that feels familiar and intuitive to use.;
- Responsive. PGB will perform at a satisfactory speed, which will directly contribute to its practicality and real-world usability;
- Extensive error-handling. Through rigorous testing and exception handling, DSG will handle errors invisible to the user, and always fulfill the minimum guarantee of each system requirement;
- Modularity. By making each feature as a separate module, PGB will be an extensible system to which adding new features is easy;
- Open Source. PGB will be an open source project, which means all of its code will be available to the public through an open Git repository. Through public contributions, PGB will be an application that will be constantly be improved hopefully.