<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>CSCS2320 Data Structures</fs></WRAP>
</WRAP>

======PROJECT: Debug And Polish (DAP0)======

=====OBJECTIVE=====
We've been on a steady stream of progress, breaking lots of new ground. More than a few deadlines have been encountered along the way, and perhaps not everything desired was able to get completed. Part of mastery is a constant revisiting and enhancing of what came before.

This project presents such an opportunity: focusing on our recent breakout implementation, here you will have the opportunity to stop and polish some aspects of breakout that may not have been as you would have preferred, or provide you with added time to implement some functionality you scrapped due to lack of time.

=====TASK=====
Take your ttb1-level breakout and enhance it with further functionality, features, and polish. Clean up first revision clunky code segments, further modularize, implement more efficient approaches to current implementation processes. Essentially, make the game presentation-ready, as if we were to put these on display for others to play.

Identity changes you have made in some comment block (perhaps at the top of your code where main() resides), indicating what improvements or enhancements or polish you have implemented.

=====EDIT=====
You will want to go [[/notes/discrete/fall2023/projects/dap0|here]] to edit and fill in the various sections of the document:

  * [[/notes/discrete/fall2023/projects/dap0|https://lab46.g7n.org/notes/discrete/fall2023/projects/dap0]]

{{page>notes:discrete:fall2023:projects:dap0&nouser&nodate&nomdate&editbtn}}

=====SUBMISSION=====
To be successful in this project, the following criteria (or their equivalent) must be met:

  * Project must be submit on time, by the deadline.
    * Late submissions will lose 33%  credit per day, with the submission window closing on the 3rd day following the deadline.
  * Executed programs must display in a manner similar to provided output
    * output  formatted,  where applicable,  must match  that of  project requirements
  * Processing must be correct based on input given and output requested
  * Output, if applicable, must be correct based on values input
  * Code must be nicely and consistently indented
  * Code must be consistently written, to strive for readability from having a consistent style throughout
  * Code must be commented
    * Any "to be implemented" comments **MUST** be removed
      * these   "to  be  implemented"   comments,  if  still  present  at evaluation time, will result in points being deducted.
      * Sufficient  comments  explaining  the point  of  provided   logic **MUST** be present
  * No global variables (without instructor approval), no goto statements, no calling of main()!
  * Track/version the source code in your lab46 semester repository
  * Submit  a copy of  your source code to  me using the  **submit** tool by the deadline.

====Submit Tool Usage====
Let's  say you  have completed  work  on the  project, and  are ready  to
submit, you  would do the following:

<cli>
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
</cli>

You should get some sort of confirmation indicating successful submission
if all went according to plan. If  not, check for typos and or locational
mismatches.

=====RUBRIC=====
I'll be evaluating the project based on the following criteria:

<code>
39:dap0:final tally of results (39/39)
*:dap0:enhanced or polished breakout game submitted [26/26]
*:dap0:statement in code comments indicate changes made [7/7]
*:dap0:all game and build related files submitted [6/6]
</code>

For those doing **discrete/dap0**, and wondering if the multibase function can be the entirety (or in fact considered as any) of your enhancement or polish here: no.

===Pertaining to the collaborative authoring of project documentation===

  * each class member is to participate in the contribution of relevant information and formatting of the documentation
    * minimal member contributions consist of:
      * near the class average edits (a value of at least four productive edits)
      * near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
      * near the class content contribution average (a value of at least 1kiB)
      * no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
    * adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
    * content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
      * no contributions, co-efficient is 0.50
      * less than minimum contributions is 0.75
      * met minimum contribution threshold is 1.00

===Additionally===

  * Solutions not abiding  by spirit of project will be  subject to a 50% overall deduction
  * Solutions  not  utilizing descriptive  why and  how comments  will be subject to a 25% overall deduction
  * Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
  * Solutions not organized and easy to  read (assume a terminal at least 90 characters wide, 40 characters tall)  are subject to a 25% overall deduction