MagicDraw 18.5 Documentation

Skip to end of metadata
Go to start of metadata

In software development, the diagram is the equivalent of a blueprint. To meet the various needs of many parties, we often need several different "blueprints" of the same system. Furthermore, every system is described by many different aspects. For example:

  • Functional (static structure and dynamic interactions)
  • Nonfunctional (timing requirements, reliability, and deployment)
  • Organizational (work organization and mapping to code modules)

MagicDraw supports the following diagrams that are defined in UML 2:

  • No labels