Homework 4 Details for MPCS 5141

Each homework assignment will consist of a small problem in some OO code, which is somehow problematic, given your developing understanding of good OO best practices and patterns, you will improve, thus eliminating any negative issues in the code you are given. Each homework assignment is intended to give every student hands-on experience with the core concepts covered during the course.  You may code your solution to the problem in any legitimate OO language of your choice.  You need to submit labs to the TAs for grading--see submission instructions below.  Generally, unless otherwise specified, you will have one week to complete each assigned homework problem.

See the syllabus for information on grading.  Turning in lab assignments on time is required, without exception, and all late deliveries will be penalized, regardless of cause.  Submit your assignments to the subversion repository according to the directions on the syllabus page.

You may write these solutions in any programming language of your choice.  Our suggestion is now is not the time to learn a new programming language along with the concepts themselves.  So our suggestion is to use whatever programming language you  know best.

Homework 4   Due: 5:00 pm, Monday, March 2, 2020

Coding Problem: 

BACKGROUND:

Like all programming-related problems, learning a new programming language or style is not an exercise in reading but rather an exercise in thinking and typing.  This homework is designed to give you  hands-on experience in some fundamental skills involved in object-oriented design and coding.  You will generally find the References section below helpful in addition to the required and recommended reading. 

WHAT YOU NEED TO DO:

 See the code here.  You are to read and understand the code, what it is intending to accomplish, and what the responsibilities are of the class or classes.  Nonetheless, there are one or more problems in the code which require your insight in their amelioration.  Your mission, should you choose to accept it, is to "fix" the problem(s) in the code, without introducing any new problems, by coding a replacement set of code in any legitimate object-oriented programming of your choice.  Be sure to include a README with instructions on how to compile (if necessary) and run your coded solution.

Very important:  Inside comments at the top of your coded solution, you are to fully describe the problem(s) in the original code as you have determined it, and describe why your solution eliminates the original problem(s).

References:

You may find the following references helpful:

https://web.archive.org/web/20100927032339/http://objectmentor.com/resources/articles/isp.pdf

https://en.wikipedia.org/wiki/Interface_segregation_principle

https://en.wikipedia.org/wiki/Aspect-oriented_programming

https://martinfowler.com/bliki/RoleInterface.html

https://www.linuxjournal.com/article/4540

http://erwyn.bloggingabout.net/2005/10/20/mixins-generics-and-extension-methods-in-c/

https://en.wikipedia.org/wiki/AspectJ

Submitting:

Use the folder named "hw4" in your Subversion repository. See the syllabus for more info about submission using Subversion. Upload your HW4 solution file(s) and any supporting materials to the repo.