Object Oriented Programming using C#
Case Study
Since DummyBoard will have a collection of messages loaded it also has a one-to-many relationship with Message.
Note the use of the concise “ball and socket” notation for the DisplayBoardControl interface.
While the classes above will form the heart of the system an additional class will be required to drive and manage the
system as a whole.
A class ‘ApplicationWindow’ will be created. This will be the GUI that will run the system and this will allow the user will
interact with the system adding clients, messages etc.
Other additional functionality, not specified by the shop owner, is implicitly required. At the end of the day the details
of the ClientBook and MessageSet will need to be saved to file. This data will need to be restored next time the system is
run as the shop owner will clearly not want to enter details of all the clients every time they run the program. This again
will be driven from the interface but the body of the code will be devolved to the relevant classes.
11.5 Prototyping the Interface
While methods for gathering user requirements is beyond the scope of this text – it is always a good idea to prototype
an interface and get feedback on this before proceeding with the development.