Corning Community College
CSCS1320 C/C++ Programming
OBJECTIVE
As we start our journey into programming, despite not yet having learned much, let us see how our observational and pattern-matching and problem solving skills can still yield productive changes toward the solution of a task.
TASK
You are to modify provided code, once functionality and operations of it are understood, to produce, as image output, a scene containing the following characteristics:
confined within a square resolution of at least 1000×1000 pixels
contain at least:
1 filled rectangle, no shorter than 32 pixels on any side
1 unfilled rectangle, no shorter than 64 pixels on any side
1 circle, diameter no smaller than 128 pixels
1 ellipse
utilize at least 8 uniquely mixed colors
NOTE: background not a substitute for required filled rectangle above
annotate your image with your initials, ideally in some corner
EDIT
You will want to go here to edit and fill in the various sections of the document:
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.
All code must compile cleanly (no warnings or errors)
Executed programs must display in a manner similar to provided output
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
No global variables (without instructor approval), no goto statements, no explicit 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 (make submit on lab46 will do this) by the deadline.
Let's say you have completed work on the project, and are ready to
submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
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:
39:gtf0:final tally of results (39/39)
*:gtf0:modified code appropriately to accomplish task [13/13]
*:gtf0:image elements abide by project specifications [13/13]
*:gtf0:removed unused code [13/13]
Pertaining to the collaborative authoring of project documentation
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