8.2.                    Description of the methodology

To summarize:

• For each use case create a robustness diagram which depicts the basic and the alternative flows of action
• Identify the types of objects (i.e. boundary, control or entity objects)
• Create the links between them (basic and alternative flows of action) according to the description of the use case
• This is a good start to initiate the class diagram of the system and identify most of the attributes of the classes.

Robustness diagrams are not to be delivered in the final documentation of the system. They are simple assist diagrams that will help us to identify the objects of the system, which will help us to produce the sequence diagrams of the following step. They are created in order to be thrown away once they accomplish their job.