CS 3240 Winter 2005, Homework 2 </head> <body> <h4>Homework for Unsorted List, array implementation <br>due: Jan 14, 2005, 1:20pm via Blackboard (click on Course Materials, then the Homework 2 assignment, then View/Complete Assignment where you can start and complete the submission) </h4> <hr> Using the UnsortedType and ItemType classes from the text, you will write two versions of a function to indicate if the list is already sorted, in strictly descending order. (5, 3, -4) is in strictly descending order, but (5, 3, 3, 1) is not. (5) and the empty list are also in strictly descending order. One version is a <b>const</b> method in the UnsortedType class called <i>IsDescending</i> that does not take any parameters. The other is a function called <i>Decreasing</i> in a separate file "AuxUnsorted.cpp" that takes an UnsortedType as a parameter. Both functions return a <b>bool</b>. You will need "AuxUnsorted.h" to define the prototype for this function. <p> You will need to use the ComparedTo() method of the ItemType class. You may not modify ItemType, and you may not modify UnsortedType beyond adding <i>IsDescending</i>. </p> <p>Students using Java should do the same problem, but using the UnsortedStringList class as used in the first lab, and with String's instead of int's. Remember to use the compareTo() method of the String class.</p> <h5>Written portion</h5> <p>In the comments for each function, indicate what is the big-O complexity of the function and briefly explain why. <h5>Handing in the assignment and Grading</h5> <p> Zip together the source files (.h and .cpp) you used and turn in the zip file (Blackboard Task submissions unfortunately get renamed). <p> 70% of the credit is whether the code correctly determines if the list is sorted in descending order or not. If your code does not compile, your assignment will not receive any correctness points. 10% is for the big-O complexity explanation. The remaining 20% is based on programming style. Include your name in a comment on each file that you create or modify, indicate what you did in that file and the date you made the modification. Comment each function, use meaningful variable names (i as an index variable is ok, but otherwise, single letter variable names are a bad habit), use consistent indentation and provide proper spacing to make the code more readable. Never, ever, create your code in Word or another word processor. <p><b>WARNING:</b> This is an individual assignment. Do it on your own. If you can't, ask me for help. </body> </html>