For example, introduce stereotypes for each important requirement type with tags consisting requirement specific information and define types of links for tracing requirements, such as derive, satisfy, support. Another aspect on which system analyst’s work in some projects is definition of data structure. It can be done using conventional requirement modelling diagrams. If necessary, object diagrams can also be used for defining samples for explanation or testing of data structure defined in class diagrams. Since the focus here is on data structure, class operations compartments can be hidden in the diagram (Figure 6).
Comparing to conceptual analysis, more elements are used here, such as attributes and association end specifications, enumerations, and generalization. Although such model is considered to be part of design, in practice quite often it is created and maintained by system analysts. For data-centric applications, it is very important to do data-flow diagrams showing information flows between different classifiers, e.g. system-context diagram indicates information flows from system to outside world entities, i.e. actors or external systems that need to be integrated.