General Instructions
1. No collaboration is permitted during this test. You may not consult with the tutors on this test. The only person you may interact with on this test is me. I will answer questions related to the interpretation of the instructions only.
2. No imports may be added to the source file. All 5 problems are solvable with plain vanilla python.
3. In the problems below, assume that I will test with additional data that is not shown. This additional data will comply with any assumptions given in the problem description but could vary in length and magnitude compared to the provided examples.
4. The doctest results for all tests passing will have this summary:
29 tests in csc401_midterm_test.txt
29 tests in 1 items.
29 passed and 0 failed. Test passed.
5. As usual, your deliverables are:
a. your updated .py source file
b. any additional data files you created for testing
6. When you are done:
a. upload your individual files to D2L, into the midterm submission folder. No zip/rar, etc. files will be accepted
b. double check that you have uploaded all the right files
Tips
1. Add a description for each function in the location indicated in the doc string. This is part of your grade.
2. Enter your code AFTER the doc string, replacing the word “pass”.
3. Pay close attention to whether the function is supposed to print, return or something else.
4. To get full credit for a problem, your solution must pass the provided tests.
5. Passing the tests does not guarantee full credit. If your solution arrives at the correct result but contains irrelevant code, or contains hard coded values that the function should have calculated, points will be deducted.
6. Develop your solutions incrementally. I recommend you add error handling last, since you will pass most tests without error handling. You will not get full credit without the error handling but it is better to get something working than to have a function that does have error handling but doesn’t actually work in any test cases.
7. If you print or add other statements for testing purposes, be sure to remove them before delivering your code to d2l.
8. Make sure the last thing you do before upload to D2L, is test. Too many students have lost points because they made 1 more “insignificant” change before upload, that actually caused their code to fail.
CS 340 Milestone One Guidelines and Rubric Overview: For this assignment, you will implement the fundamental operations of create, read, update,
Retail Transaction Programming Project Project Requirements: Develop a program to emulate a purchase transaction at a retail store. This
7COM1028 Secure Systems Programming Referral Coursework: Secure
Create a GUI program that:Accepts the following from a user:Item NameItem QuantityItem PriceAllows the user to create a file to store the sales receip
CS 340 Final Project Guidelines and Rubric Overview The final project will encompass developing a web service using a software stack and impleme
