Metadata modeling

This is basically an adjusted class diagram as described in Booch, Rumbaugh and Jacobson (1999).

First of all, a concept is a simple version of a Unified Modeling Language (UML) class.

The class definition[1] is adopted to define a concept, namely: a set of objects that share the same attributes, operations, relations, and semantics.

Part of the process-data diagram of the requirements workflow in the Unified Process is illustrated.

A USE CASE consists of a description, a flow of events, conditions, special requirements, etc.

Generalization is visualized by a solid arrow with an open arrowhead, pointing to the parent, as is illustrated in Figure 3.

In Figure 4 generalization is exemplified by showing the relationships between the different concepts described in the preceding paragraph.

In Figure 10 aggregation is exemplified by a fragment of the requirements capture workflow in UML-Based Web Engineering.

Properties are written in lower case, under the concept name, as is illustrated in Figure 11.

In Table 1 a list presented Each CONCEPT requires a proper definition which is preferably copied from a standard glossary.

Fig.1 STANDARD, OPEN and CLOSED CONCEPTS
Fig.2 Example of STANDARD, OPEN and CLOSED CONCEPTS
Fig.3 Generalization
Fig. Example generalization
Fig.5 Association
Fig.7 Multiplicity
Fig.8 Example multiplicity
Fig.9 Aggregation
Fig.10 Example aggregation
Fig.11 Aggregation
Fig.12 Example aggregation