Examining the UML Models: Static Models

  • John Erik Hansen
  • Carsten Thomsen


In this chapter, we’ll introduce you to the UML diagrams known as structural diagrams, which describe the structure (static structure) of your solution. The following UML diagrams are structural diagrams:
  • Class diagram

  • Statechart diagram

  • Component diagram

  • Deployment diagram


Class Diagram Dependency Relationship Server Node Component Diagram Operation Category 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Static structure diagrams can be class diagrams or another diagram type covering the static structure (for example, an object diagram showing physical real-life objects).Google Scholar
  2. 2.
    This is true for all UML CASE tools and not just a disadvantage for VEA users.Google Scholar
  3. 3.
    In VEA, events are operations, because of UML 1.2 compliance. However, this isn’t the case in UML 1.4 and later.Google Scholar
  4. 4.
    Methods are functions by default in C#.Google Scholar
  5. 5.
    In C#, this is a method with the void keyword in the signature to indicate that it doesn’t return a value.Google Scholar
  6. 6.
    Well, your code wouldn’t work as intended if not, would it?Google Scholar
  7. 7.
    With garbage collection, the Finalize method isn’t really a destructor in the true sense, but we’ll stay with the OOP terminology.Google Scholar
  8. 9.
    NET assemblies can consist of one or more physical files, or even be in dynamic assemblies that are contained in memory. However, for the sake of this discussion, an assembly equals one physical file.Google Scholar
  9. 10.
    DLL hell“ refers to the annoying struggle of registering and unregistering the different versions of.dll files in the Registry, often resulting in a DLL version incompatible with the application being registered..NET solves this by making the assemblies (DLLs) self-describing through the use of a manifest, which means that registration is no longer necessary, and allows the use of side-by-side assemblies, or private assemblies.Google Scholar
  10. 11.
    VEA allows you to generate code without assigning your classes to components. You simply choose the physical file names when generating code.12. To some extent, this will prevent you from distributing your classes to different physical machines. This isn’t entirely true, however, because the same component can be running different machines at the same time.Google Scholar

Copyright information

© John Erik Hansen and Carsten Thomsen 2004

Authors and Affiliations

  • John Erik Hansen
  • Carsten Thomsen

There are no affiliations available

Personalised recommendations