Requirements

[GitPS]

This will be a place to discuss requirements that we feel need to be included in the project. I'm thinking we can just throw out informal ideas here and then discuss them more at our Tuesday meeting.

[immo99]

Notes for Meeting 9/24/2013

Requirements: Server: -Network based - Hosted off Pi -Run on Raspbian -Support >=8 connections -Handles all game logic for any game supported - Will not handle graphics. -Database storage engine -Holds user information: username, password, chip count, points

-Automatic client updates - Updates mandatory -Notifies client of update when the program is executed. -No closes program, Yes updates program and restarts

-Client: -Creates folder in the directory that it was originally executed in. -Must be able to locate server automatically or manually by input. -Platform updated by server to play necessary games -Blackjack and Euchre -Environment can change depending on games 2 jar files - 1 launcher and the program

Launcher: -Check minimum system requirements -Queries server for current version number, if version is old, update the jar -runs client jar

If we have time: -Encrypt communication between client and server -AI

[GitPS]

I think, originally, it was discussed that these requirements would be added to the doc directory of the project. I agree with this, but I think we should wait and see how we are supposed to layout the requirements before we do this. That was my thought when I asked Mike if we should just put them here instead. Hopefully everyone agrees.

[ghost]

General Requirements

• Portability: Must run on any computer that can run Java 1.7 and can connect to the server's network
• Connection and Installation must be simple (expand)
• If a computer is on the same network as the server, the client should 'normally' find the server automatically
• Installation should not require any steps you wouldn't normally expect during an installation (expand)
• Executing the program should be as simple as double-clicking the icon (under normal circumstances)
• User interface is non-technical and logically follows gameplay.
• Supported games adhere to the rules accessible to the general public from a notable organization
• User information is saved after unexpected disconnects
• Must support up to 1000 user accounts per server (definite upper bound)

[ghost]

Should we provide "help"? for the client, server, or for each game?

we could provide a basic "help" index for the server/client and provide links to "game-by-game" help/rules. (assuming those links are reliable)

[immo99]

1) SQlite looks good. 2)I think we'll have a help, but it will only display rules. On Sep 25, 2013 12:26 AM, "ajjensen13" notifications@github.com wrote:

Should we proved "help"? for the client, server, or for each game?

we basic help index for the server/client and proved links to "game-by-game" help/rules.

— Reply to this email directly or view it on GitHubhttps://github.com/GitPS/PiCasino/issues/2#issuecomment-25062719 .

[GitPS]

Should we provide "help"? for the client, server, or for each game?

we could provide a basic "help" index for the server/client and provide links to "game-by-game" help/rules. (assuming those links are reliable)

I think having some form of a help feature is a goo idea. It would really only need to be basic. Each game could also be responsible for include it's own help information as well.