Write some Software

The objective of this task is to become familiar with the development of object-oriented approaches, particularly concentrating on the selection of suitable classes and the appropriate use of encapsulation and polymorphism. The structured programme written for task 1 is to be converted to an object-oriented programme and some extensions added. The following features should be added to the task 1 code. • Add menu items that allow the user to request that the current state of the program be saved and previously saved state be loaded. • Add one or more member functions to allow all relevant data and other information to be saved to a file (you may choose a fixed file name). • Add one or more member functions to allow all relevant data and other information to be loaded from a file (using the same fixed file name as that used for saving). The following also forms part of the specification. • The program must use an object-oriented approach; it must contain only member functions (other than main() which should do no more than create the first object). • All members must be private. • Document properly the code you add. Don’t document every line of code - just the major blocks of code (see the marking scheme). • The structure of your code should be neat and easy to follow. • provide the following files: (a) a copy of the source code as a text file with name [login to view URL]; (b) a copy of the source code as a PDF; (c) a copy of the executable. A sample of the feedback sheet you will receive after the task has been marked is also attached. The marking scheme is also shown on the feedback sheet. Before writing your code you will need to think carefully about the following (HINT: these are hints!). • Decide on the classes you need. You should also be careful to include a set of classes that implement the functionality of the code in such a way that they could be used by other developers. • To establish suitable member functions, take into account the responsibilities of each class; for example, which class should perform the filtering operation? • Encapsulation dictates that, as far as possible, an object should be responsible for its own data. • Use polymorphism only as appropriate. The general rule is that if an inbuilt operator matches the purpose of a member function then it should be overloaded. • Use inheritance only where necessary. Only if you can reasonably say that object A is a type of object B should A inherit from B.