58
edits
Changes
Jump to navigation
Jump to search
Line 33:
Line 33: − + − + − + − Want + − + − + − + − + − Want + − + − - Get GUI design and layout out to community and get feed back right away on it(soon to be done)+ − + + − + − + − Want + − + − + + − + − + + + + + − + − Want + − + − + + − + − Want + − +
changed milestones to reflect recent group additions and a new time table
==Milestones==
==Milestones==
1) Design Doc(done)
1) Learn Python/Get GroupMembers
Need
Need
- Design GUI interface and layout
- Know python and have dev environment set up
- Finalize remaining milestones
- Get group members
Date
- Learn Python(not done at all)
- To be done by end of RIT's winter break (1/4/2010)
2) GUI Layout(done)
2) Create Teacher Interface
Need
Need
- Finalize GUI design and layout
- Able to accept input from user
- Get screen shots of GUI design and layout onto the wiki(linking directly to the flash)
- Transitions from screen to screen smoothly
- Stores all the information in a format easily sent over networks
- Learn more Python(not done at all)
- Able to display all of the class information regardless of number of students (up to 15)
Date
3) Create GUI
- To be done within 2 weeks of being back from break (1/18/2010)
3) Create Student Interface
Need
Need
- Actually make GUI in python
- Able to accept input from user
- Finalize ideas about the rest of prototype (how much I can do with remaining time)
- Transition from screen to screen smoothly
- Gathers all of the desired information easily
- I/O with user (just input text and using it)
Date
4) Create the rest of the prototype
- To be done withing a week of teacher's interface (1/25/2010)
4) Get Networking working
Need
Need
- Complete prototype
- Teacher is able to create and share activity
5) Distribute
- Students are able to join activity
- Information is able to be passed from student XO to teacher XO
Date
- To be as done as possible by end of class (Week of 2/22/2010)
5) Test
Need
Need
- Get it out to the community and get feedback
- Multiple tests in many different situations
- Feedback from community on usefulness and what else is desired
- Find a developer or two interested in coding actual functionality
Date
6) Finalize Design Doc
- As long as there is support for the project
6) Add features
Need
Need
- Using information/feedback from community, create a final design document and get it out to the community
- Features to be added will determine needs
Date
- Find a developer or two interested in coding actual functionality
- Needs will determine dates
==Recent Updates==
==Recent Updates==