1. iCasino Requirements,Design and Planning DemoRequirementsDesign Planning

2. iCasino Requirements and Testing Demo

3. Requirements Document Organized by various options and menus within the application. Example: Registration 2.1New users will be able to create an account by providing the following information: username, password, first name, last name, valid and unique email address. 2.1.1The username user attempts to register must be unique. 2.1.1.2Queries will be run on the user table in the database to determine this. If username is not unique, user will be prompted to enter a newusername. 2.1.2The username must be at least 5(five) characters and no more than 10(ten) characters long. 2.1.2.1Each character must and may only be a letter of the alphabet or a digit 0-9.

4. Test Matrix Tests are listed in a matrix format and named with a letter A-Z. The requirments document references specific tests in this matrix by name. Each test may be referenced by more than one requirement. 2.4.1Each test will be performed by 5 (five) randomly chosen individuals. 2.4.1.1These individuals must not be involved in the development of this application.

5. Testing Examples Requirement: 2.2Returning users will be able to log in by entering a username and password (see Test B). Test: Test B : After successful completion of registration (Test A), tester will input registered username and password in log in screen. Test passes if tester is taken to the main menu.

6. Testing Examples Requirement: 2.6.3.1If the sequence of numbers generated is not a winning sequence then the user will be taken to a screen that tells the user that he or she has lost. The current bet will be deducted from the user's account (see Test J). Test: Test J : Tester will play slots and a losing sequence will be generated. If a winning sequence is generated, tester will repeat test (up to 100 times) until a losing sequence is generated. Test passes if a losing sequence is generated, a screen is displayed informing the tester that he or she has lost, and the amount remaining in the user's account is exactly the previous amount minus the current bet.

7. Wolf (Arthur J.) Schedule: DateHoursDescription 09/27/041Read over requirements document, highlighting questionable requirements and phrases 09/28/04.5Met with requirements editor to discuss findings Requirement : 2.3Once logged in successfully, menus will provide a way for the user to move back from each screen. The term “each screen” implies each screen within the entire application. It is not true that the user can always move back to each screen. For example, once they have lost a game, they may not move back and replay the same game.

8. Thief (Vipul P.) Schedule: DateHoursDescription 09/27/041Read over requirements document, highlighting questionable requirements and phrases 09/28/04.5Met with requirements editor to discuss findings Requirement : 2.11.2Total flow will display total number of credits accumulated for all the games.. This is supposed to be user-specific but is not specified. Developers can only keep track of one calculation, the total number of credits for all users and display this same value regardless of who is logged in.

9. Requirements Editor (Omnia I.) Requirement : 2.3Once logged in successfully, the main and game menus will allow users to navigate to other accessible menus in the application. Requirement : 2.11.2Total flow will display total number of credits accumulated for all the games by the currently logged in user. Schedule: DateHoursDescription 09/27/041Met with wolf and thief to discuss their findings. 09/28/04.5Made appropriate changes to document in areas pointed out by wolf and thief. Back to Menu