Use the specialized class icons to accurately represent the type of class and use the specialized relation symbols to accurately reflect the relationships of the entities. Note that while the abstract specification and the interface design are usually developed separately in an iterative approach, they are combined for documentation. The lower level types will be building blocks of the paradigm to be used for implementation such as a form or a code module in a Visual language. If not already covered above, design in detail and specify the data structures to be used in the implementation. If these include databases, define the table structure of all databases including full field descriptions and all relations.
Graphical languages are appropriate.
Note that a database is an object and may have been fully described in the previous section. If the material is covered under Architectural Design, this section is omitted. For each use case in the Requirements Specification there must be a use case realization here. It is possible that there will be several use case realizations here to show all the alternative and exception paths required. Use case realizations can be expressed by collaboration diagrams or by sequence diagrams with supporting text as needed.