Scribd
Upload
27 views2 pages

Name: Ismael Orozco Grader: Sarah Masters Assignment: Lab 1 Final Grade Code Requirements: Style: (5%)

This document provides a grading rubric for Ismael Orozco's Lab 1 assignment. It evaluates various aspects of the code such as style, comments, input/output, required functions, function prototyping, and a README file. It provides detailed criteria for each category and shows that Ismael received full marks, earning a total grade of 99.5 out of 100.

Uploaded by

Pablo Ramirez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
27 views2 pages

Name: Ismael Orozco Grader: Sarah Masters Assignment: Lab 1 Final Grade Code Requirements: Style: (5%)

This document provides a grading rubric for Ismael Orozco's Lab 1 assignment. It evaluates various aspects of the code such as style, comments, input/output, required functions, function prototyping, and a README file. It provides detailed criteria for each category and shows that Ismael received full marks, earning a total grade of 99.5 out of 100.

Uploaded by

Pablo Ramirez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Name: Ismael Orozco

Grader: Sarah Masters


Assignment: Lab 1
Grade Total
Final Grade 99.5 100

Code Requirements:

Style: (5%)
 Code is easy to read, proper spacing is used 2 2
 No global variables are used 3 3

Comments: (15%)
 Code uses meaningful doxygen style comments with proper doxygen 15 15
formatting! (see doxygen.c on Canvas if you have questions about this formatting – link
found under Lab1 pdf)
 These comments should include file headers, in-code comments, and function
definitions (preferably NOT above the prototypes and instead with the actual function)

Input/Output: (10%)
 Script file shows program is compiled and run with no errors (5 points) 5 5
 Script file has correct input (2 point) Did not input float values for height and 1.5 2
base of triangle.
 Script file has correct output (3 points) 3 3

Lab Requirements: (50%)


 Code includes the following functions which are implemented correctly
 Naming of functions should match exactly what is shown below.
Points shown beside function name are for correct naming.
(4 points total for each function)
◦ area_rectangle() (1 point) 4 4
▪ correctly calculates the area of a rectangle (1 point)
▪ height and width are type int (2 points)
◦ perimeter_rectangle() (1 point) 4 4
▪ correctly calculates the perimeter of a rectangle (3 points)
◦ diagonal_rectangle() (1 point) 4 4
▪ returns a double (3 points)
◦ area_circle() (1 point) 4 4
▪ use pow (3 points)
◦ circumference() (1 point) 4 4
▪ correctly calculates the circumference of a circle (3 points)
4 4
◦ area_triangle() (2 points)
▪ height and base are doubles (2 points)
◦ hypotenuse() (1 point) 4 4
▪ correctly calculates the hypotenuse (3 points)
◦ perimeter_triangle() (1 point) 4 4
▪ calls hypotenuse() (3 points)
◦ exterior_angle() (4 points) 4 4
◦ interior_angle() (4 points) 4 4
◦ area_regular_polygon() (1 point) 4 4
▪ use tan() (3 points)
 Student uses function prototyping 6 6

README: (10%)
 Has accurate purpose 4 4
 Has detailed conclusion with the following sections: 6 6
◦ What I learned (2 points)
◦ Issues and how I fixed them (bug report) (2 points)
▪ Students MUST have a bug report! Saying “no bugs” is not an option.
◦ Improvements that can be made (2 points)

Code Quality: (10%)


 Code is easy to read and understand (5 points) 5 5
 Code is of good quality with good variable names (5 points) 5 5

Comments:

You might also like