Corning Community College
OBJECTIVE
Take your explored component and prototype something you'd like to create with it. Start writing software to test various aspects of the desired end product.
Be sure to contribute useful background and operational information to this project documentation, to serve as a reference for others.
OVERVIEW
Your task is to:
apply your knowledge of the component to build something that uses it
write a program that demonstrates aspects of the desired functionality
there will be one more part to this project, so if you want to take a broader-term view:
Example:
fso0: figure out how to use an ultrasonic sensor
fso1: prototype a “useless” machine, using the ultrasonic sensor as a proximity sensor to determine if the user's hand is still near the switch (to avoid injury)
fso2: finished product of a “useless” machine
GRABIT
To assist with consistency across all implementations, data files for use with this project are available on lab46 via the grabit tool. Be sure to obtain it and ensure your implementation properly works with the provided data.
lab46:~/src/SEMESTER/DESIG$ grabit DESIG PROJECT
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 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$ make submit
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:
78:fso1:final tally of results (78/78)
*:fso1:used grabit to obtain project by the Sunday prior to duedate [13/13]
*:fso1:overview of project pursued to project page with description [13/13]
*:fso1:picture of project circuit to project page with description [13/13]
*:fso1:clean compile, no compiler messages [13/13]
*:fso1:program conforms to project specifications [13/13]
*:fso1:code tracked in lab46 semester repo [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