Difference between revisions of "Math4Team/RIT/Projects/Muthris"
Jump to navigation
Jump to search
(May 15 update) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{TOCright}} | {{TOCright}} | ||
| + | {{:Math4Team/RIT/Projects/Muthris/status}} | ||
=Muthris= | =Muthris= | ||
| − | Muthris is a math themed, Tetris-based game inspired by Cuyo. Players control falling blocks which must be grouped in certain ways in-order to clear that grouping from the board. For more details, see the project's Vision and Scope document contained in its Sugar Labs' Gitorious repository. | + | Muthris is a math themed, Tetris-based game inspired by Cuyo and is not yet ready for public release. Players control falling blocks which must be grouped in certain ways in-order to clear that grouping from the board. The main game engine is abstracted away from the levels for the easy creation and addition of new levels. For more details, see the project's Vision and Scope document contained in its Sugar Labs' Gitorious repository. |
| − | ==Updates as of | + | ==Project Updates as of Sepetember 2nd, 2009== |
* Updated Wiki page | * Updated Wiki page | ||
| − | * | + | * Menu system is working, but a few parts are still stubbed out |
| − | * | + | * Have overall project documentation |
| − | * | + | * Have more detailed documentation of certain areas |
| − | * | + | * Have a project skeleton coded |
| + | * Still having Git repository issues ''(might have just been fixed...)'' | ||
==Developers== | ==Developers== | ||
| − | *[[User:Dpk3062|Douglas Krofcheck]] | + | ===Active=== |
| + | ===Inactive=== | ||
| + | * [[User:Dpk3062|Douglas Krofcheck]] | ||
==Goals== | ==Goals== | ||
* To be fun to play | * To be fun to play | ||
| Line 16: | Line 20: | ||
* To follow good software engineering practices during development | * To follow good software engineering practices during development | ||
==Schedule and Tasks== | ==Schedule and Tasks== | ||
| − | * | + | * There is no schedule at this time as all active developers have transitioned to inactive developers due to school related time constraints |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Overall Plan== | ==Overall Plan== | ||
| − | The overall plan is basically the project requirements grouped by importance. | + | The overall plan is basically the project requirements grouped by importance. See the ''Vision and Scope'' document and the ''Haves and Have Nots'' section of this page for further details. |
| + | ==Haves and Have Nots== | ||
===Must Have=== | ===Must Have=== | ||
* Project Documentation | * Project Documentation | ||
| − | ** Vision and Scope ( | + | ** Vision and Scope ''(have)'' |
| − | ** Architecture docs ( | + | ** Architecture docs ''(have some)'' |
| − | ** Flow Charts ( | + | ** Flow Charts ''(have)'' |
| − | * Working code repository ( | + | * Working code repository ''(have some of the time...)'' |
| − | * Project schedule ( | + | * Project schedule ''(missing)'' |
| − | * At least one developer ( | + | * At least one active developer ''(missing)'' |
| − | * Text-based version of the game ( | + | * Text-based version of the game ''(being developed)'' |
| − | * | + | * Readme with running instructions ''(have)'' |
| − | |||
===Should Have=== | ===Should Have=== | ||
| − | * Skeleton - working, stubbed framework before general coding | + | * Skeleton - a working, stubbed framework before general coding ''(have)'' |
| − | * Installation tutorial | + | * Installation tutorial ''(partly)'' |
| − | * Program walk-through | + | * Program walk-through ''(missing)'' |
| − | * GUI version of the game | + | * GUI version of the game ''(missing)'' |
| − | * Build tutorial | + | * Build tutorial ''(missing)'' |
| − | * Project backup | + | * Project backup ''(have)'' |
| + | * Example lession plan ''(have)'' | ||
===Nice to Have=== | ===Nice to Have=== | ||
| − | * Unit tests | + | * Unit tests ''(missing)'' |
| − | * SRS Document | + | * SRS Document ''(missing)'' |
| − | * Release 1 | + | * Release 1 ''(missing)'' |
| − | * No major project risks | + | * No major project risks ''(missing)'' |
==Major Project Risks== | ==Major Project Risks== | ||
| + | * Git pushing issues | ||
* Limited time available for development | * Limited time available for development | ||
* Developers are inexperienced with Python and PyGame | * Developers are inexperienced with Python and PyGame | ||
==Other Info== | ==Other Info== | ||
| − | === | + | ===Project Contacts=== |
*[[User:Dpk3062|Douglas Krofcheck]] | *[[User:Dpk3062|Douglas Krofcheck]] | ||
===Links and Resources=== | ===Links and Resources=== | ||
Latest revision as of 21:19, 5 September 2010
| Status: | Unknown unknown |
Group Members: | Douglas Krofcheck |
| Muthris is a math themed, Tetris-based game inspired by Cuyo. Players control falling blocks which must be grouped in certain math related ways in-order to clear that grouping from the board. The level is lost when the board fills up with blocks. Players learn math skills by fun repetition of simple mathematical problems and the grouping of sets of numbers. Levels are abstracted away from the core game. This allows one to simple drop in new levels and learn different mathematical concepts. | |||
Muthris
Muthris is a math themed, Tetris-based game inspired by Cuyo and is not yet ready for public release. Players control falling blocks which must be grouped in certain ways in-order to clear that grouping from the board. The main game engine is abstracted away from the levels for the easy creation and addition of new levels. For more details, see the project's Vision and Scope document contained in its Sugar Labs' Gitorious repository.
Project Updates as of Sepetember 2nd, 2009
- Updated Wiki page
- Menu system is working, but a few parts are still stubbed out
- Have overall project documentation
- Have more detailed documentation of certain areas
- Have a project skeleton coded
- Still having Git repository issues (might have just been fixed...)
Developers
Active
Inactive
Goals
- To be fun to play
- To teach mathematical concepts
- To be discrete in its teachings
- To follow good software engineering practices during development
Schedule and Tasks
- There is no schedule at this time as all active developers have transitioned to inactive developers due to school related time constraints
Overall Plan
The overall plan is basically the project requirements grouped by importance. See the Vision and Scope document and the Haves and Have Nots section of this page for further details.
Haves and Have Nots
Must Have
- Project Documentation
- Vision and Scope (have)
- Architecture docs (have some)
- Flow Charts (have)
- Working code repository (have some of the time...)
- Project schedule (missing)
- At least one active developer (missing)
- Text-based version of the game (being developed)
- Readme with running instructions (have)
Should Have
- Skeleton - a working, stubbed framework before general coding (have)
- Installation tutorial (partly)
- Program walk-through (missing)
- GUI version of the game (missing)
- Build tutorial (missing)
- Project backup (have)
- Example lession plan (have)
Nice to Have
- Unit tests (missing)
- SRS Document (missing)
- Release 1 (missing)
- No major project risks (missing)
Major Project Risks
- Git pushing issues
- Limited time available for development
- Developers are inexperienced with Python and PyGame
Other Info
Project Contacts
Links and Resources
- Project Repository
- OpenOffice.org - to read documentation files (.odt)
- Dia - To view flow charts (.dia)
Initial Math4OLPC Educational Target
- 4.N.7 - Recognize classes (in particular, odds, evens; factors or multiples of a given number; and squares) to which a number may belong, and identify the numbers in those classes. Use these in the solution of problems