use case diagram drafts

User Requirements

This game was designed to provide an interactive interface for consumers to enjoy the product. Players will be able to navigate through the menu bar and begin to initiate gameplay with relative ease with a straightforward menu with new game, continue game, instructions, credits etc.

M Mandatory Requirement This feature must be built into the final Product
D Desirable Requirement This feature may be built into the final product unless hindered by cost, Time constraints or security risk
O Optional Requirement These features may be built into the final product
F Future addition Features that will be later added into the final game












2.1 Input requirements
Label Requirement Necessity

1 Interface should be able to accept user input in a timely manner M
2 Touch features should be coherently responsive F























2.2 Output requirements
Label Requirement Necessity

1 Users should be able to quickly navigate through the game menu in order to learn and play the game M
2 The game must respond to the users commands in a timely manner M
3. User must be able to understand what is taking place in the game, and enjoying it. D




























2.3 Non-functional requirements
Speed and time requirements

Label Requirement Necessity

1 The balls and paddle of the game must be responsive and able to meet particular frame speeds in order to stop balls from entering the goal.
Issues: Ball physics have been a significant issue, as we have had to learn 3-D mathematics to resolve collision and hit detection problems D




















Reliability requirements
Label Requirement Necessity

1 The application should be able to maintain a form of stability in order to not crash during gameplay or cause any unexpected glitches D
2 The  application should function fully on the PC platform effectively, regardless of constraints
Issues: Platform was originally intended for an android device. M