Visual Studio 2010 Architecture Guidance – Why are we talking about two types of sequence diagrams?

I have been reviewing the architecture guidance over the past few days, whereby the are getting close to opening the gates and publishing the guidance. Keep an eye on our Rangers blog for news on the guidance. There are a few things that made me wonder (frown) and therefore I believe it warrants a short post.

The guidance talks about two types of sequence diagrams that are supported by Visual Studio 2010.

Two? What is the difference?

  • The  UML sequence diagram forms part of a UML model and is typically used for design up-front.
  • The .NET sequence diagram is generated from program code and is not part of a UML model. This diagram is useful when developing code and the need arises for a visual picture that depicts its structure and which can be used as a comparison with the originally intended design.

.NET Sequence Diagram Example >>>

Go here for more information on the sequence diagrams: Support for UML Diagrams.

Are there any other schizophrenic artefacts?

Yes, there are also two kinds of class diagrams, with a similar origin.

  • The UML class diagram is part of a UML model and is typically drawn manually to help describe logical aspects of the design. In future the Visual Studio Feature Pack will also allow you to generate the UML class diagram from code … but more on that at a later stage.
  • The .NET class diagram is generated from code. It can be added to a code project, but is not part of a UML model.

In the next post we will look at another concept that caught my eye … the 4+1 View.

Comments (0)

Skip to main content