4/4. /122/ password-protected: username: 122; password: digits 4-5-6 of DuckID.
6/6. Three C++ files created for this project in /122/p2/
File-- isValidTri.cpp: 27/27
3/3. File identifier must be isValidTri.cpp
7/7. program generates the I/O specification shown on p. 98
3/3. program prints true/false, not 1/0 for boolean output
5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc.
If statments are formatted using either next-line or end-of-line style. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
3/3. No global variables-- all variables declared at the top of the body of main.
3/3. No local constants-- if constants are used, they are declared at the top of the source file, following the #include section.
3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
File-- five-six-props.cpp: 27/27
3/3. File identifier must be five-six-props.cpp
7/7. program generates the I/O specification shown on p. 98
3/3. program prints true/false, not 1/0 for boolean output
5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc.
If statments are formatted using either next-line or end-of-line style. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
3/3. No global variables-- all variables declared at the top of the body of main.
3/3. No local constants-- if constants are used, they are declared at the top of the source file, following the #include section.
3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
File-- dayCount.cpp: 27/27
3/3. File identifier must be dayCount.cpp
10/10. program generates the I/O specification shown on the project 2 page
5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc.
If statments are formatted using either next-line or end-of-line style. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
3/3. No global variables-- all variables declared at the top of the body of main.
3/3. No local constants-- if constants are used, they are declared at the top of the source file, following the #include section.
3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
3/3. Project URL (including HTACCESS username and password) entered in Comments section
6/6. Attach Local File.. option used to submit three C++ source files created for this project
On or before the due-date submit the project using the BB Assigment in Projects > Submit Project. If you do not use this BB assignment turn-in feature, you will not have a score entered for this project in the gradebook, so please do not forget to do this on or before the due-date.
Programming Teams
Working as part of a two-member team is an option; groups of three or more are not not an option. If you work as a team:
A. You must notify the grader of both programmer names in the Comments section when submitting the project in Blackboard
B. Each partner must maintain copies of all project files, etc., in his or her /122/ folder on shell.uroegon.edu