2. Description of the methodology

The methodology that we shall use is outlined below. We must note here that there are many methodologies in the bibliography, as the Rational Unified Process (RUP) [Kruchten, 2000], or the ICONIX method [Rosenberg, 1999], to name a few.

Our methodology consists of the following general steps:

2.1.   Short description of the system taking into account the system requirements.

2.2.   Use case analysis: Identification of use cases and use case diagrams development.

2.3.   Package analysis: Identification of packages and development of a package diagram of use cases.

2.4.   Domain analysis: An initial class diagram (or set of class diagrams), which consists of domain classes from the use case diagrams documentation that correspond to the real world.

2.5.   Robustness analysis to define objects and their attributes from the use case diagrams

2.6.   Interaction analysis: Creation of interaction models (sequence and collaboration) from robustness analysis.

2.7.   Creation of class diagrams (static model).

2.8.   Creation of state and activity diagrams for the most important classes of the system.

2.9.   Implementation analysis (creation of component and deployment diagrams).