CECS 100
LAB ASSIGNMENT 1
Assigned date: 9/4
Due date: 9/9
10 points

his assignment addresses the following lesson objective:

This lesson objective addresses the following course learning outcomes:

PreLab

Do the following activities before doing the lab assignment. 

Problem 1 - From chapter 1

  1. Do the multiple choice (25 questions) - use scantron E-882
  2. Do problems 3, 4 and 5 - use word document

Problem  2

Create a flowchart using Raptor and write a pseudocode to represent a logic of a program that inputs from the user the height and width of a wall, calculates and displays the amount of paint you need to cover the wall. It takes one gallon of paint for every 150 square feet of wall.

Sample output:

Enter the height (feet):  150
Enter the width (feet):   10
The amount of paint is 10 gallons.

Note: The bold letters mean the computer generates the output. The normal letters indicates the user enters the input from the keyboard.

Submission

  1. Demonstrate the lab assignment in the class before the class is ended.
  2. Upload the file lab1.rap to the BeachBoard.
  3. Write the pseudocode in the text entry box in Canvas.

 

Lab assignment Grading Rubric
Criteria Approx. % of Grade Excellent (100%) Adequate (80%)  Poor (60%) Not Met (0%)
Program Specification /Correctioness 50%(10 points) No errors, program always works correctly and meets the specification(s). Minor details of the program specification are violated, program functions incorrectly for some inputs. Significant details of the specification are violated, program often exhibits incorrect behavior. Program only functions correctly in very limited cases or not at all.
Readability 20% (4 points) No errors, code is clean, understandable, and well-organized. Minor issues with consistent indentation, use of whitespace, variable naming, or general organization. At least one major issue with indentation, whitespace, variable names, or organization. Major problems with at three or four of the readability subcategories.
Documentation 10% (2 points) No errors, code is well-commented. One or two places that could benefit from comments are missing them or the code is overly commented. File header missing, complicated lines or sections of code uncommented or lacking meaningful comments. No file header or comments present.
Code Efficiency 15% (3 points) No errors, code uses the best approach in every case. No errors, code uses the working approach in every case.  Code uses poorly-chosen approaches in at least one place. Many things in the code could have been accomplished in an easier, faster, or otherwise better fashion.
Assignment Specifications 5% (1 point) No errors N/A Minor details of the assignment specification are violated, such as files named incorrectly or extra instructions slightly misunderstood. Significant details of the specification are violated, such as extra instructions ignored or entirely misunderstood.