Cis 170 Ilab 2 of 7 Essay examples

971 Words Sep 17th, 2014 4 Pages
HELPIDO.COM

------------------------------------------------
Follow this link to get the tutorial

http://helpido.com/cis170ilab-2-of-7/
------------------------------------------------

CIS/170 - iLab 2 of 7
________________________________________

Scenario/Summary
You will code, build, execute, debug, and test two programs using decision structures. The first program will calculate the shipping charge based on a given purchase amount. The second program translates a given TV channel to its call sign.
Deliverables
Submit the following to this week’s Dropbox:
1. A zipped Visual Studio project folder for each programming exercise. Refer to the Deliverables section of the Week 1 iLab page for detailed instructions on
…show more content…
To be able to debug a program of syntax and logic errors
7. To be able to make decisions
Your lab grade will be based upon:
1. the formatting of your source code;
2. the use of meaningful identifiers;
3. the extent of internal documentation; and
4. the degree to which an exercise’s specifications are met.
Preparation:
If you are using the Citrix remote lab, follow the login instructions located in the iLab tab in Course Home. iLab 2 Part A: Calculate Shipping Charge
Requirements

Your mission: Write a program that gets the amount of a purchase from the user and then calculates the shipping charge, based on the following table:
$0.00 – $250.00: $5.00
$250.01 – $500.00: $8.00
$500.01 – $1,000.00: $10.00
$1,000.01 – $5,000.00: $15.00 over $5,000.00: $20.00
Sample output from program:
Enter a purchase amount to find out your shipping charges.
Please enter the amount of your purchase: 234.65
The shipping charge on a purchase of $234.65 is $5.00.
Press any key to continue . . .
Tips

Best practice: Put yourself in the place of the program. What questions would you ask a customer in order to get the best input? How would you determine the correct shipping charges if you had to make the decisions yourself?
Write out the questions you would ask yourself on paper as pseudocode and/or in Visual Studio as C# comments, and then implement them one by one, testing as you go. Remember to not

Related Documents