There will be six programming assignments and six written assignments in this course.
If you find yourself in an emergency situation and can not deliver a homework on time,
immediately inform the instructor, and be prepared to document your emergency in writing, in strict
adherence to UTA policy. Also,
while working with other persons on non-graded example problems from
the textbook is a good way to help you develop your understanding and
insight into the techniques of problem solving, homework solutions
must be your work only. Violations of this will not be tolerated and
result in severe penalties for all parties involved, in strict compliance to official UTA policy.
Programming assignments have to run on the ACS machine omega.
All homework submissions (written and programming) must be submitted via Blackboard. Interim reports for programming assignments should be submitted via e-mail to the instructor and the TA.
Late submission policy:
All assignments are graded out of 100 points. Assignments submitted late will be penalized, at a rate of 2 penalty points per hour. The submission time will be the time shown on Blackboard. Any assignment submitted more than 50 hours late will receive no credit. Exceptions will only be made for documented emergencies, in strict adherence to UTA policy. Computer/network crashes are NOT an acceptable excuse for late submissions (if worried, submit early, you can always revise your submission till the deadline).
Assignments:
- Assignment 0. Do ASAP. You do not have to submit anything, and you will get no credit for it. However, if you do not complete this you may have problems submitting the next assignments on time.
-
Task 1: make sure that you can log in to omega.uta.edu, and that you can compile a "hello world" program in your favorite language among C, C++, Java, and Python. If you have trouble logging in, contact helpdesk@uta.edu.
-
Task 2: make sure that you can log in to Blackboard and that you understand how to submit an assignment. You can even submit something temporary for Assignment 1, you can always update your submission before the deadline.
- Programming Assignment 1. Interim report due Wednesday 08/31/2011, 11:55pm. Assignment due Sunday 09/04/2011, 11:55pm.
- Written Assignment 1. Due Monday 09/05/2011, 11:55pm.
Solution.
- Programming Assignment 2. Interim report due Monday 09/12/2011, 11:55pm. Assignment due Sunday 09/18/2011, 11:55pm.
- Written Assignment 2. Due Monday 09/19/2011, 11:55pm.
Solution.
- Programming Assignment 3. Interim report due Monday 10/03/2011, 11:55pm. Assignment due Sunday 10/09/2011, 11:55pm.
- Written Assignment 3. Due Monday 10/10/2011, 11:55pm.
Solution.
- Programming Assignment 4. Interim report due Monday 10/17/2011, 11:55pm. Assignment due Sunday 10/23/2011, 11:55pm.
- Written Assignment 4. Due Monday 10/24/2011, 11:55pm.
Solution.
- Programming Assignment 5. Interim report due Monday 11/07/2011, 11:55pm. Assignment due Sunday 11/13/2011, 11:55pm.
- Written Assignment 5. Due Monday 11/14/2011, 11:55pm.
Solution.
- (Optional) Programming Assignment 6. Interim report due Monday 12/05/2011, 11:55pm.
Assignment due Thursday 12/08/2011, 11:55pm.
Note: This assignment is optional, but NOT extra credit. For students who do not submit this assignment, their programming assignment average will be computed based on the previous five programming assignments. For students who submit this assignment, if their score in this assignment improves their programming assignment average, then (and only then) it will be taken into account.
- Written Assignment 6. Due Monday 11/28/2011, 11:55pm.
Solution.
- CSE 4308 assessment:
-
The CSE 4308 assessment (making up 6.7% of the grade for CSE 4308 students) will consist of written assignment 3 and programming assignment 3. The grading rubric for the assessment is described here.