clue's People
clue's Issues
Rough Draft UML Class Diagrams
DISREGARD
Section 5.1 Data Model
Complete SRS 5.1 Data Model
Test Case Distribution
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
Coordinate Class Skeletons
User Documentation
Migrate SRS to Wiki
Non-dependent Class testing
4 hrs 10 mins hours 10:30 pm - 2:40 pm
Class Skeletons and Javadocs
2 Hours: Helping work on rough draft
https://docs.google.com/document/d/1nsMOFuI_k3fzsdcLzZEHF-cfTl-2uRBRUayiGLa_5as/edit
1 Hour: AI skeleton/javadocs
UI Prototype
Design - Make a way for a deck to have a pre-set order
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
GUI Implementation and integration
ClientController and ServerController pseudocode.
Algorithm pseudocode for all methods in the ClientController and ServerController classes.
Our README is empty
We really should add to it.
Algorithms
Need to get the algorithms sorted out in pseudo code based on tasks assigned in class
Section 4.0 Behavioral Requirements
Complete SRS Section 4.0.
Migrate Project Plan to Wiki
Section 2: Functional Requirements
Complete SRS Section 2: Functional Requirements
Chris Patton - @chpatton013
Daniel Mangin - @AzureEnigma
SRS is on Google Docs.
ServerController and Game
Code and Integrate the remaining ServerController. Code and integrate the Game logic. Fix Compilation errors.
SRS Revision
Finished. 2 hours
Rough Draft UML Class Diagrams
QA Checklist
Defects
Using this issue to log defects found during testing. Will merge defects to another area if needed.
QA Checklist
Start Time: April 23, 2014 10:30 AM
Design overview document
Add overview.html to master branch, add class skeletons, post tutorials on overview files and javadocs and netbeans.
FProto - Read design chapter
Chapter 5
Common Class Skeleton
2 hours 9:00 pm - 11:00 pm
Class Diagrams
Section 6.2: Rationale
System Tests
Carried out system tests June 1st, 2014 2 hours 3:00 pm - 5:00 pm
Section 3.0 Quality Attributes (Nonfunctional Requirements)
Schedule and Dependency Graph
Feasibility Prototype
Feasibility Prototype Requirements:
- User should load client and see list of Servers
- User clicks on a server and is put in a Room
- Users click begin and and are taken to a game.
- Each user is dealt and shown two action cards.
- 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
Section 2.0 Functional Requirements
@chpatton013 You and me are the best team
AI Psuedocode
Section 1: Vision and Scope
Section 5.2: Data Dictionary
Complete the Data Dictionary portion of the SRS document
Sample
Sample ticket
Section 1: Vision and Scope
Test Case Distribution
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.
Create Change Control Process Document
Implementation of AI and Tests
May 21 - 2 hours
May 22 - 3 hours
May 24 - 1 hour
May 25 - 2 hours
May 26 - 5 hours
Section 1: Vision and Scope
Work on SRS Section 1: Vision and Scope. SRS is on Google Docs.
we need a game
explanation
Coordinate the development and the review of our High Level Design milestone.
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
Design - Make a way for a deck to have a pre-set order
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.
UI Prototype
Described the storyboard that was put together and labeled the actions on the created images.
Hours: 1.5
Create soft deadline calendar
Integrate Source Code for: Player, LobbyJoinResponse, HintCard, AccusationRequest, ActionRequest
Update project.
Update wiki with dates complete.
Section 6.1 External Interfaces
Complete the External Interfaces portion of the SRS document
Time Taken:
James Bilous 4/10 45 min. *Retroactive
Section 3: Quality Attributes
Work on SRS Section 3: Quality Attributes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.