You can generate UML diagrams to examine artifacts of C#
3.0 applications using UML notation in a single, tightly integrated
development environment.
About this task
With UML diagrams, you can examine an existing system to
identify the system's components and interrelationships and
to create representations of the system in another form. You can also
use UML diagrams to understand, analyze, and automatically abstract
the system's structural information from code to a new form at
a higher abstraction level. You can redesign the system for better
maintainability or to produce a copy of a system without access to
the design from which it was originally produced.
With IBM® Rational® Modeling Extension for Microsoft .NET,
you can visualize C# and CTS artifacts to:
- document application structure, using class diagrams.
- document as-implemented and what-if class interactions, using
sequence diagrams.
- perform architectural discovery and dependency analysis, using
browse diagrams.
- depict .NET types within diagrams in UML models as part of the
"mixed modeling" theory of operations.
Note: The
UML diagrams generated by C# visualization are read-only, and cannot
be used to modify the contents of a solution in Microsoft Visual Studio.
If you want to generate C# code from a UML model, you can create and
apply a transformation configuration.
A UML class diagram
depicts some or all of the components or elements in an application.
You can use class diagrams to examine and design the structures and
relationships C# and Common Type System (CTS) classes and data types.
You can create your own context to examine, understand, collaborate,
and design, using a subset of the classes in an application.
You
can use UML sequence diagrams to examine and design behaviors and
interactions of C# applications.
You can use
ephemeral, non-editable browse diagrams to create quick static views
and explore existing relationships in applications, and non-editable
topic diagrams to create dynamic views of applications
based on context and queries.