CECS 100
LAB ASSIGNMENT 3
Assigned date: 9/18
Due date:   Wednesday 9/25
40 points

Objectives:

In this lab, you learn to create a Raptor flowchart.

After completing this lab, you will be able to:

Pre-Lab

Do the following activities before doing the lab assignment. 

Problem 1 [10 points]

A company ABC asked you to design a simple payroll program that calculates and employee's weekly gross pay, including any overtime wages. If employees work over 40 hours in a week, they will get 1.5 times of their regular hourly rate for all hours over 40. Your program asks the user to input hours worked for a week, regular hourly rate, and then display the weekly gross pay. Draw the Raptor flowchart to represent the logic of the problem. Name the Raptor flowchart file as lab3.rap.

Output sample

Enter weekly hours worked: 35
Enter hourly rate: 20
Weekly gross pay: $ 700

Output sample

Enter weekly hours worked: 50
Enter hourly rate: 30
Weekly gross pay: $1650

Grading

Name the Raptor flowchart file as lab31.rap. Do not change the file name to any other name. Submit the file to the Beachboard.

Problem 2 [10 points]

Do problem 6 Magic dates on page 152 in chapter 3. Input dd/mm/yyyy.

Problem 3 [10 points]

Convert the flowchart in the problem 1 into a Python program.

Problem 4 [10 points]

Convert the flowchart in the problem 2 into a Python program.

Grading

 

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.