fe7bcd161b10943decf7c7aa76ce50aca9fc2330
haas/fall2026/discrete/projects/magX.md
| ... | ... | @@ -0,0 +1,76 @@ |
| 1 | +# CSCS2330 Discrete Structures |
|
| 2 | + |
|
| 3 | +## PROJECT: MAKE A GAME (magX) |
|
| 4 | + |
|
| 5 | +## OBJECTIVE |
|
| 6 | + |
|
| 7 | +Learn and apply Discrete Structures, gain development experience, and collaborate with the class on the class project game effort. Practice good version control, and document your progress via good commit messages. Learn and utilize the lua programming language to give us a different angle on programming, gaining experience in a different, and higher-level language. |
|
| 8 | + |
|
| 9 | +Each week, actively participate and contribute in the development of the class project, via the repository. |
|
| 10 | + |
|
| 11 | +I am looking to see the following, for the purposes of this project’s evaluation: |
|
| 12 | + |
|
| 13 | + * exploring and implementing code in lua using `v32lua` |
|
| 14 | + * you are active. This will most likely manifest in a healthy number of meaningful commits to the project. |
|
| 15 | + * I would like to see at least 4 commits per week, ideally sprinkled throughout the week, that contain worthwhile changes. More is of course better. |
|
| 16 | + * you are implementing/using/involving Discrete Structures in your efforts. This will predominantly take the form of algorithms and optimizing, but you should be mindful of opportunities to explore: |
|
| 17 | + * bitwise logic |
|
| 18 | + * set theory |
|
| 19 | + * algorithmic runtime (big-O) |
|
| 20 | + * counting, incrementation, and its composites |
|
| 21 | + * optimization of code |
|
| 22 | + * modularization of code over time |
|
| 23 | + * being mindful of best/average/worst and edge cases |
|
| 24 | + * code contributions are indented, style consistent, and well commented |
|
| 25 | + * if a contribution breaks the build process, try to give some indication on what is wrong |
|
| 26 | + * along with any prescription for how you are working about resolving it |
|
| 27 | + * you document your progress via your commit messages |
|
| 28 | + |
|
| 29 | +Broader scale: |
|
| 30 | + |
|
| 31 | + * we are working towards a complete, finished game by the end of the semester |
|
| 32 | + * as appropriate, we’ll likely want to do some play testing, even by outsiders to give feedback on controls, etc. |
|
| 33 | + * another aim is to present this at the 2027 CCC Student Expo, so a poster will need to be created by the end of the semester |
|
| 34 | + * production of various teaser/promotional content along the way, that could be shared with the world (screenshots, screen captures, youtube videos, etc.) |
|
| 35 | + * the completed game + source + assets will be contributed to the Vircon32 Community Repo |
|
| 36 | + * so make sure any assets used, if we did not create them, have a permissive license |
|
| 37 | + |
|
| 38 | +## SUBMISSION |
|
| 39 | + |
|
| 40 | +Being repository-based, there's no specific submission steps aside from |
|
| 41 | +the making of regular, substantive, well-commented commits. I would like |
|
| 42 | +no fewer than FOUR (4) such commits each week. |
|
| 43 | + |
|
| 44 | +I'll be looking for the following: |
|
| 45 | + |
|
| 46 | +### RUBRIC |
|
| 47 | + |
|
| 48 | +I'll be evaluating the project based on the following criteria: |
|
| 49 | + |
|
| 50 | +``` |
|
| 51 | +SCORE:magX:final tally of results (SCORE/TOTAL) |
|
| 52 | +*:magX:made at least four meaningful commits [PTS/PTS] |
|
| 53 | +*:magX:implemented, used, or otherwise working with discrete structures [PTS/PTS] |
|
| 54 | +*:magX:documents efforts in descriptive commit messages to repository [PTS/PTS] |
|
| 55 | +*:magX:communicates, gives some updates via Discord project channel [PTS/PTS] |
|
| 56 | +*:magX:achieving progress towards end product and deployment [PTS/PTS] |
|
| 57 | +*:magX:codebase maintenance, code organization, optimization [PTS/PTS] |
|
| 58 | +*:magX:you have not been idle and missing in action [BALANCE/BALANCE] |
|
| 59 | +``` |
|
| 60 | + |
|
| 61 | +NOTE: BALANCE is the filler points to bring us up to the desired weekly total (which is a multiple of 26) |
|
| 62 | + |
|
| 63 | +The outline of semester progress: |
|
| 64 | + |
|
| 65 | +| week | project | points per item (PTS), balance | TOTAL | |
|
| 66 | +| ---- | ------- | ------------------------------ | ----- | |
|
| 67 | +| 3 | mag3 | 13,0 | 78 | |
|
| 68 | +| 4 | mag4 | 17,2 | 104 | |
|
| 69 | +| 5 | mag5 | 21,4 | 130 | |
|
| 70 | +| 6 | mag6 | 26,0 | 156 | |
|
| 71 | +| 7 | mag7 | 30,2 | 182 | |
|
| 72 | +| 8 | mag8 | 34,4 | 208 | |
|
| 73 | +| 9 | mag9 | 39,0 | 234 | |
|
| 74 | +| 10 | magA | 43,2 | 260 | |
|
| 75 | +| 11 | magB | 47,4 | 286 | |
|
| 76 | +| 12 | magC | 52,0 | 312 | |