cis339 no handshakes needed

Your demonstrations of how to create both method contract and the method specification for the GetCourseByCourseID() method of the CourseList class were very well received by your team members. They then asked you for one final demonstration of how to implement the method specification using an object-oriented (OO) programming language and see the method actually execute.

You realize that it is easy to implement the method specification in an OO programming language, but it is hard to test it because the rest of the application is not developed yet. You decided, therefore, to write two pieces of code.

1. Code that implements the GetCourseByCourseID() method
2. Code that implements a unit test for that method alone (outside of any other application code)

This way you can demonstrate the method implementation and also verify its correct behavior.

You are under a deadline constraint for this deliverable, so you asked some of your peer architects for help. They each are well versed in different OO languages like VB.NET, C#, and Java and they all have done unit testing before so they are familiar of how to construct one.

Your peer architects provided you with partially-completed shells for your demonstration. Each shell contains:

1. complete code for the Course class;
2. partially completed code for CourseList class; and
3. complete code for the CourseListTest class that unit tests the CourseList.GetCourseByCourseID() method.

Your task is now easy. Just select one of these shells and complete the code for the partially completed CourseList by coding it GetCourseByCourseID() method. When you compile and run the shell, it will automatically test your GetCourseByCourseID() code to ensure its correct behavior.

 

• A copy of the code you wrote for the GetCourseByCourseID method() of the CourseList class in your favorite OO programming language
• A screen shot of the output of running the provided unit test in the shell (the CourseListTest class) showing that your code works as expected. Note that these unit tests only print out messages of testing problems. If your code is correct, the unit tests will succeed silently without any success messages.
• a zip file of the completed shell after you added your code so that the shell could be executed on a different machine.
• Verification and validation of your work
• Explanation of your work