chpatton013 / clue Goto Github PK

@chpatton013 You and me are the best team

https://github.com/chpatton013/clue/wiki/User-Documentation

Create the design so that the deck has a pre-set deck and is not randomized. This will allow for systematic testing for card and game functionality.

Update project.
Update wiki with dates complete.

Code and Integrate the remaining ServerController. Code and integrate the Game logic. Fix Compilation errors.

Described the storyboard that was put together and labeled the actions on the created images.

Hours: 1.5

Algorithm pseudocode for all methods in the ClientController and ServerController classes.

Retro
Time Spent - 2hrs
5/6/2014 5:30 am - 7:30 am

To everyone - Review the SRS and if there is any test case that might be avaliable to the section that you created.

(These were randomly selected. If you are unhappy with your placement, let me know)
Functional Requirements
The Deal, The Play, and The Turn : Steven Chiu and James Bilous
Action Cards : Ryan Quinlan and Christopher Patton

Quality Attributes
Platform Constraints, Reliability, Modifiability - Ryan Quinlan and Thomas Sanford
Usability, Performance, Deployment, Security - Brian Schacherer, Daniel Mangin, and Bennett Scalich

We also need to test Networking, but for now - Daniel Mangin

Carried out system tests June 1st, 2014 2 hours 3:00 pm - 5:00 pm

https://docs.google.com/spreadsheet/ccc?key=0AqvAJvjPt7oxdEMtLWh1b0tzTXg5ZDhKeXpMLTZmeUE&usp=drive_web#gid=0

Need to get the algorithms sorted out in pseudo code based on tasks assigned in class

Complete SRS Section 2: Functional Requirements

Chris Patton - @chpatton013 
Daniel Mangin - @AzureEnigma 

SRS is on Google Docs.

Complete SRS 5.1 Data Model

explanation

Create the deck so that it has the choice of not randomizing and accepting a pre-set deck of cards so the game can be systematically be tested for game and card functionality

Start Time: April 23, 2014 10:30 AM

2 Hours: Helping work on rough draft
https://docs.google.com/document/d/1nsMOFuI_k3fzsdcLzZEHF-cfTl-2uRBRUayiGLa_5as/edit

1 Hour: AI skeleton/javadocs

Sample ticket

Using this issue to log defects found during testing. Will merge defects to another area if needed.

Finished. 2 hours

Chapter 5

Complete SRS Section 4.0.

Work on SRS Section 3: Quality Attributes

Work on SRS Section 1: Vision and Scope. SRS is on Google Docs.

We really should add to it.

Complete the External Interfaces portion of the SRS document

Time Taken:
James Bilous 4/10 45 min. *Retroactive

DISREGARD

Complete the Data Dictionary portion of the SRS document

Feasibility Prototype Requirements:

1. User should load client and see list of Servers
2. User clicks on a server and is put in a Room
3. Users click begin and and are taken to a game.
4. Each user is dealt and shown two action cards.
5. Each user picks an action card in turn
   5a. Each action card drawn is shown to each client

Time Taken:
James - 4/18 10am - 11am - 1h (Design meeting) *Retroactive
Chris - 4/18 10am - 11am - 1h (Design meeting) *Retroactive

James - 4/19 2h (Java Networking / Game Object Representation Research ) *Retroactive

4 hrs 10 mins hours 10:30 pm - 2:40 pm

To everyone - Review the SRS and if there is any test case that might be avaliable to the section that you created.

(These were randomly selected. If you are unhappy with your placement, let me know)
Functional Requirements
The Deal, The Play, and The Turn : Steven Chiu
Action Cards(All snoop, super sleuth and private tip) : Ryan Quinlan
Action Cards(snoop and suggestion): Christopher Patton

Quality Attributes
Platform Constraints, Reliability - Brian Schacherer
Modifiability, Security - James Bilous
Performance, Deployment- Bennett Scalich

UI Testing
Thomas Sanford
Mark Feldman
Daniel Mangin

Networking - Daniel Mangin

If you finish with your test cases early, please let me know, as I might need you to help with another one.

Add overview.html to master branch, add class skeletons, post tutorials on overview files and javadocs and netbeans.

2 hours 9:00 pm - 11:00 pm

May 21 - 2 hours
May 22 - 3 hours
May 24 - 1 hour
May 25 - 2 hours
May 26 - 5 hours

Hello all,

If you are available to help on the high level design, please take a look at the available design jobs:
https://docs.google.com/spreadsheets/d/1fwkQW5XRZv-ePKhau67xXVzL9kXiHYfKAKkkhOe1NwA/edit?usp=sharing

If you are interested in working on a module, enter your name in the owner column.

Mr. Dalbey's high level design requirements document:
https://docs.google.com/document/d/1wUv-pjAQIi7JlKK4QbaL_T8Loo9Z5DLN6fK8-yl9TtE/edit?usp=sharing

Review the data dictionary and data model in the SRS, one can derive most of the classes/objects and relationships from these two.

There may be some dependencies (ie. building a complete Feasibility Prototype and building a more advance UML) that may prohibit a module from being 100% complete.

By next Tuesday(4/22), please have a rough draft ready for your module and be ready to discuss any issues.

Thanks,

Brian Schacherer