This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:spring2017:cprog:projects:cci0 [2017/01/16 21:28] – [Syllabus] wedge | haas:spring2017:cprog:projects:cci0 [2017/01/17 10:38] (current) – [Submission Criteria] wedge | ||
---|---|---|---|
Line 27: | Line 27: | ||
====Syllabus==== | ====Syllabus==== | ||
Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course. | Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course. | ||
- | ====Opus Intro==== | + | ====Journal |
- | Familiarize yourself with your Opus, and once there: | + | Familiarize yourself with your Journal, and once there: |
* customize it (title/ | * customize it (title/ | ||
* add an introduction | * add an introduction | ||
* create your first week content | * create your first week content | ||
- | **NOTE:** Week 1 opus entry will be due before | + | **NOTE:** Week 1 journal |
====Mailing List==== | ====Mailing List==== | ||
Line 55: | Line 55: | ||
====Personal/ | ====Personal/ | ||
- | Joe will likely have you use BitBucket for his side of the class; if you'd like to run with that, you may skip this step for this class. | ||
- | But note that you do have your own Lab46 mercurial repository, and you may make use of it for class-related purposes. | + | To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your [[/haas/spring2017/ |
- | + | ||
- | To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your [[/haas/fall2015/ | + | |
This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong. | This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong. | ||
- | Like the Opus, I will be looking for a minimal amount of repository-related activity PER WEEK (for example, I will be looking for AT LEAST 1 commit in relation to your program for week 1). | + | Like the Journal, I will be looking for a minimal amount of repository-related activity PER WEEK (for example, I will be looking for AT LEAST 1 commit in relation to your program for week 1). |
====Program to Implement==== | ====Program to Implement==== | ||
Line 108: | Line 105: | ||
To be successful in this project, the following criteria must be met: | To be successful in this project, the following criteria must be met: | ||
- | * Project must be submit on time, by the posted deadline. | + | * Project must be submit on time, by the posted deadline |
* Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline. | * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline. | ||
+ | * Early submissions can earn 1 bonus point per day in advance of the posted due date. | ||
* All code must compile cleanly (no warnings or errors) | * All code must compile cleanly (no warnings or errors) | ||
* all requested functions must be implemented in the related library or program | * all requested functions must be implemented in the related library or program | ||
Line 123: | Line 121: | ||
* Sufficient comments explaining the point of provided logic **MUST** be present | * Sufficient comments explaining the point of provided logic **MUST** be present | ||
* Track/ | * Track/ | ||
- | * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline. | + | * Submit a copy of your source code to me using the **submit** tool by the deadline. |
+ | | ||
+ | * Make sure it outputs exactly like the sample output above. | ||
+ | * Create and submit a text file called **info.text** that contains the following information: | ||
+ | * preferred name/ | ||
+ | * preferred e-mail address | ||
+ | * irc nick used in class chat (your username if unchanged) | ||
+ | * other information I should know | ||
====Submit Tool Usage==== | ====Submit Tool Usage==== | ||
- | Let's say you have completed work on the project, and are ready to submit, you would do the following | + | Let's say you have completed work on the project, and are ready to submit, you would do the following: |
<cli> | <cli> | ||
- | lab46: | + | lab46: |
Submitting cprog project " | Submitting cprog project " | ||
-> hello.c(OK) | -> hello.c(OK) | ||
+ | -> info.text(OK) | ||
SUCCESSFULLY SUBMITTED | SUCCESSFULLY SUBMITTED | ||
Line 137: | Line 143: | ||
</ | </ | ||
+ | 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. | ||
+ | |||
+ | I'll be evaluating the project based on the following criteria: | ||
+ | |||
+ | < | ||
+ | 39: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *: | ||
+ | *:cci0:no compiler warnings for hello.c [1/1] | ||
+ | *:cci0:no compiler errors for hello.c [1/1] | ||
+ | </ |