Math4Team/RIT/Projects/Muthris: Difference between revisions

(2 intermediate revisions by one other user not shown)

Line 1:

=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 ~~(once the repository is working...)~~.

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 ~~April 29th~~, 2009==

==Project Updates as of Sepetember 2nd, 2009==

* Updated Wiki page

* ~~Falling back to~~ a ~~local Git repository to prevent further delays~~

* Menu system is working, but a few parts are still stubbed out

* ~~Working on flow charts~~

* Have overall project documentation

* ~~Working on file formats~~

* Have more detailed documentation of certain areas

* Have a project skeleton coded

* Still having Git repository issues ''(might have just been fixed...)''

==Developers==

*[[User:Dpk3062|Douglas Krofcheck]]

===Active===

===Inactive===

* [[User:Dpk3062|Douglas Krofcheck]]

==Goals==

* To be fun to play

Line 15:

Line 20:

* To follow good software engineering practices during development

==Schedule and Tasks==

* ~~By May 1st, 2009~~

* There is no schedule at this time as all active developers have transitioned to inactive developers due to school related time constraints

** Have completed most important flow charts

** Developers completed the Python tutorials

* By May 8th, 2009

** Have completed architecture documentation

** Developers completed the PyGame tutorials

* By May 15th, 2009

** Determine test plans

** Review design documents

** Start coding of system skeleton

* By May 22nd, 2009

** Determine future development plans

==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

** 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

* Readme with running instructions ''(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===

* 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==

* Git ~~repository not currently working~~ for ~~any developers~~

* Git pushing issues

* Developers ~~do not know~~ Python or PyGame ~~well~~

* Limited time available for development

* Developmental time constraints

* Developers are inexperienced with Python and PyGame

* Short overall time frame

==Other Info==

===~~Potential~~ Contacts===

===Project Contacts===

*[[User:Dpk3062|Douglas Krofcheck]]

===Links and Resources===

*[http://git.sugarlabs.org/projects/muthris Project Repository] ~~- (committing not yet working)~~

*[http://git.sugarlabs.org/projects/muthris Project Repository]

*[http://www.openoffice.org/ OpenOffice.org] - to read documentation files (.odt)

*[http://live.gnome.org/Dia 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

@@ Line 1: / Line 1: @@
 {{TOCright}}
+{{:Math4Team/RIT/Projects/Muthris/status}}
 =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 (once the repository is working...).
+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 April 29th, 2009==
+==Project Updates as of Sepetember 2nd, 2009==
 * Updated Wiki page
-* Falling back to a local Git repository to prevent further delays
+* Menu system is working, but a few parts are still stubbed out
-* Working on flow charts
+* Have overall project documentation
-* Working on file formats
+* Have more detailed documentation of certain areas
+* Have a project skeleton coded
+* Still having Git repository issues ''(might have just been fixed...)''
 ==Developers==
-*[[User:Dpk3062|Douglas Krofcheck]]
+===Active===
+===Inactive===
+* [[User:Dpk3062|Douglas Krofcheck]]
 ==Goals==
 * To be fun to play
@@ Line 15: / Line 20: @@
 * To follow good software engineering practices during development
 ==Schedule and Tasks==
-* By May 1st, 2009
+* There is no schedule at this time as all active developers have transitioned to inactive developers due to school related time constraints
-** Have completed most important flow charts
-** Developers completed the Python tutorials
-* By May 8th, 2009
-** Have completed architecture documentation
-** Developers completed the PyGame tutorials
-* By May 15th, 2009
-** Determine test plans
-** Review design documents
-** Start coding of system skeleton
-* By May 22nd, 2009
-** Determine future development plans
 ==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
+** 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
+* Readme with running instructions ''(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===
-* 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==
-* Git repository not currently working for any developers
+* Git pushing issues
-* Developers do not know Python or PyGame well
+* Limited time available for development
-* Developmental time constraints
+* Developers are inexperienced with Python and PyGame
-* Short overall time frame
 ==Other Info==
-===Potential Contacts===
+===Project Contacts===
 *[[User:Dpk3062|Douglas Krofcheck]]
 ===Links and Resources===
-*[http://git.sugarlabs.org/projects/muthris Project Repository] - (committing not yet working)
+*[http://git.sugarlabs.org/projects/muthris Project Repository]
 *[http://www.openoffice.org/ OpenOffice.org] - to read documentation files (.odt)
 *[http://live.gnome.org/Dia 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