Java auction system

Using the model OOAD (Object Oriented Analysis & Design) for eAuction system, employ an OOP (Object Oriented Programming) process to develop a working prototype.

Every UML diagram in the model solution is important as each one models some aspect of the eAuction system.
However, the most important diagram is the Class diagram as it forms not only the starting point of your
prototype’s implementation but also models the majority of the eAuction system’s structure.

Ensure that your prototype is able to execute the tasks that are isolated in the Use Case diagram. The specific
steps involved in executing these tasks are described either in the requirements document or the model solution.
Where steps are poorly described you must use common sense / assumptions to implement those steps.

The eAuction system will require a menu system that should be implemented in the System class. You are not
required to store data (i.e. a Database or Comma Separated Value .csv file). You can as an alternative, hard code
test data for Users, Auctions etc.