Skip to main content
(in response to 3rd comment)
Source Link
NoChance
  • 12.5k
  • 1
  • 23
  • 39

Diagrams alone are not always helpful. For example, the use case diagram can't convey business rules in detail. The class diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

  • Use Case Diagram
  • Class Diagrams
  • Activity Diagram
  • Sequence Diagram

There are so many useful resources, but check these:

Edit-1 in response to Mark's comment.

While I don't use these resources day-to-day, they serve as quick reference for UML syntax. The above resources are chosen since they provide quick and somewhat comprehensive representation of UML diagrams. It shows common diagrams and helps the new UML user quickly see the difference between them. The first resource, the video, gives details about the Use Case and how it relates to other diagrams. The above resources are not expected to be enough for anyone who wants to learn UML or OOD, I realize that learning such topics was not intended in the original question.

Diagrams alone are not always helpful. For example, the use case diagram can't convey business rules in detail. The class diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

  • Use Case Diagram
  • Class Diagrams
  • Activity Diagram
  • Sequence Diagram

There are so many useful resources, but check these:

Diagrams alone are not always helpful. For example, the use case diagram can't convey business rules in detail. The class diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

  • Use Case Diagram
  • Class Diagrams
  • Activity Diagram
  • Sequence Diagram

There are so many useful resources, but check these:

Edit-1 in response to Mark's comment.

While I don't use these resources day-to-day, they serve as quick reference for UML syntax. The above resources are chosen since they provide quick and somewhat comprehensive representation of UML diagrams. It shows common diagrams and helps the new UML user quickly see the difference between them. The first resource, the video, gives details about the Use Case and how it relates to other diagrams. The above resources are not expected to be enough for anyone who wants to learn UML or OOD, I realize that learning such topics was not intended in the original question.

Formatting, citations
Source Link
user8
user8

Diagrams alone are not always helpful. For example, Use Casethe use case diagram can't convey business rules in detail. Class DiagramThe class diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

0-Use Case Diagram

1-Class Diagrams

2-Activity Diagram

3-Sequence Diagram

  • Use Case Diagram
  • Class Diagrams
  • Activity Diagram
  • Sequence Diagram

The following may be good for you (free tutorials) - In fact thereThere are so many useful resources..., but check these:

0-YouTube-Video-UML End-to-End - How to Diagram Your Software - Essential UML Tutorial

1-embarcadero

2-sparxsystems

3-OMG - Has several links that may help

Happy Modeling :)

Diagrams alone are not always helpful. For example, Use Case diagram can't convey business rules in detail. Class Diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

0-Use Case Diagram

1-Class Diagrams

2-Activity Diagram

3-Sequence Diagram

The following may be good for you (free tutorials) - In fact there are so many useful resources... but check these:

0-YouTube-Video-UML End-to-End - How to Diagram Your Software - Essential UML Tutorial

1-embarcadero

2-sparxsystems

3-OMG - Has several links that may help

Happy Modeling :)

Diagrams alone are not always helpful. For example, the use case diagram can't convey business rules in detail. The class diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

  • Use Case Diagram
  • Class Diagrams
  • Activity Diagram
  • Sequence Diagram

There are so many useful resources, but check these:

Source Link
NoChance
  • 12.5k
  • 1
  • 23
  • 39

Diagrams alone are not always helpful. For example, Use Case diagram can't convey business rules in detail. Class Diagram may be very useful since you may be able to generate class code and DLLs from it.

I find these diagrams the most useful:

0-Use Case Diagram

1-Class Diagrams

2-Activity Diagram

3-Sequence Diagram

The following may be good for you (free tutorials) - In fact there are so many useful resources... but check these:

0-YouTube-Video-UML End-to-End - How to Diagram Your Software - Essential UML Tutorial

1-embarcadero

2-sparxsystems

3-OMG - Has several links that may help

Happy Modeling :)