IT computers - class diagram

A few notes on the class diagram:

• I have taken the 'standard configuration' for a particular model to mean the set of default options. If the customer wishes to change an option, the changeOption() method is used.

• Server, Desktop and Portable are inherited subclasses of Computer.

• In the Order class, status can take the values “customer accepted”. “received”, “cancelled”, “processing”, “completed” and “awaiting dispatch”

• the Address class exists separately rather that being incorporated into the Customer class. This is for future flexibility – we may require additional addresses in future e.g. DeliveryAddress2

• the abstract PaymentMethod class exists because we may want to add other payment methods e.g. DebitCard