User Tools

Site Tools


haas:spring2017:cprog:projects:cci0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:spring2017:cprog:projects:cci0 [2017/01/16 21:28] – [Syllabus] wedgehaas: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 Intro==== 
-Familiarize yourself with your Opus, and once there:+Familiarize yourself with your Journal, and once there:
   * customize it (title/subtitle)   * customize it (title/subtitle)
   * 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 Tuesday, the remainder of the intro Opus content will be due by this project's deadline.+**NOTE:** Week 1 journal entry will be due before Monday, the remainder of the intro Journal content will be due by this project's deadline.
  
 ====Mailing List==== ====Mailing List====
Line 55: Line 55:
  
 ====Personal/Per-User Lab46 Mercurial Repository==== ====Personal/Per-User Lab46 Mercurial Repository====
-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/common/repo|Lab46 mercurial repository]].
- +
-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/common/repo|Lab46 mercurial repository]].+
  
 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 to be eligible for full credit.
     * 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/version the source code in a repository   * Track/version the source code in a repository
-  * 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 your submitted source code is in a file called **hello.c*
 +  * 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/nickname 
 +    * 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 (assuming you have a program called hello.c):+Let's say you have completed work on the project, and are ready to submit, you would do the following:
  
 <cli> <cli>
-lab46:~/src/cprog/cci0$ submit cprog cci0 hello.c+lab46:~/src/cprog/cci0$ submit cprog cci0 hello.c info.text
 Submitting cprog project "cci0": Submitting cprog project "cci0":
     -> hello.c(OK)      -> hello.c(OK) 
 +    -> info.text(OK)
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
Line 137: Line 143:
 </cli> </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.
 +
 +I'll be evaluating the project based on the following criteria:
 +
 +<code>
 +39:cci0:final tally of results (39/39)
 +*:cci0:customized journal title [4/4]
 +*:cci0:customized journal intro [4/4]
 +*:cci0:subscribed to class mailing list [4/4]
 +*:cci0:joined class irc chat [1/1]
 +*:cci0:submitted info.text file [1/1]
 +*:cci0:provided requested information in info.text [4/4]
 +*:cci0:cloned lab46 mercurial repository into ~/src [1/1]
 +*:cci0:committed and pushed populated .hgignore file [3/3]
 +*:cci0:configured hgrc file [3/3]
 +*:cci0:submitted file called hello.c [1/1]
 +*:cci0:committed and pushed hello.c to repository [2/2]
 +*:cci0:adequate and consistent indentation in hello.c [1/1]
 +*:cci0:sufficient comments in hello.c [1/1]
 +*:cci0:executable runs without issue [3/3]
 +*:cci0:output conforms to project specifications [3/3]
 +*:cci0:adequate modifications in hello.c [1/1]
 +*:cci0:no compiler warnings for hello.c [1/1]
 +*:cci0:no compiler errors for hello.c [1/1]
 +</code>
haas/spring2017/cprog/projects/cci0.1484602080.txt.gz · Last modified: 2017/01/16 21:28 by wedge