Index of /uml

[ICO]NameLast modifiedSizeDescription

 Parent Directory  -  
[DIR]bike_shop/2024-01-21 12:50 -  
[DIR]foxes_and_rabbits/2022-05-28 13:40 -  
[   ]bike_shop_v3.mdj2024-01-19 20:46 1.2M  — StarUML file
[   ]bike_shop_v6.mdj2024-01-21 11:50 780K  — StarUML file
[   ]fnr_uml_diagrams_v3.mdj2024-01-20 17:38 1.2M  — StarUML file
[   ]fnr_uml_diagrams_v6.mdj2024-01-21 12:34 443K  — StarUML file
[DIR]usecase/2024-01-20 20:52 -   1. UML Use Case Diagrams
[DIR]robustness/2024-01-20 20:54 -   2. UML Robustness Diagrams*
[DIR]activity/2024-01-20 20:55 -   3. UML Activity Diagrams
[DIR]class/2024-01-31 14:00 -   4. UML Class Diagrams
[DIR]object/2024-01-05 09:52 -   5. UML Object Diagrams
[DIR]package/2024-01-20 21:00 -   6. UML Package Diagrams
[DIR]sequence/2024-01-20 20:47 -   7. UML Sequence Diagrams
[DIR]communication/2024-01-20 20:43 -   8. UML Communication Diagrams (formerly collaboration diagrams)
[DIR]state/2024-01-21 12:32 -   9. UML State Diagrams
[DIR]component/2024-01-05 09:55 -   10. UML Component Diagrams
[DIR]deployment/2024-01-21 12:46 -   11. UML Deployment Diagrams

Organization and Classification of UML Diagrams

This site maintains folders for each type of UML diagram. The folders are organized (numbered) by the typical sequence in which they are created during the software engineering methodology. Hence they will start with the Use Case Diagram typically created in the Planning and Analysis phases — and end with the Deployment Diagram during the Implementation phase.

UML diagrams can also be organized by their type, specifically:

  • Structural Models
    • Class Diagram
    • Object Diagram
    • Package Diagram
    • Robustness Diagram*
  • Behavioral Models
    • Use Case Diagram
    • Interaction Diagrams
      • Sequence Diagram
      • Communication Diagram
    • Activity Diagram
    • State Diagram
  • Architectural Models
    • Component Diagram
    • Deployment Diagram

UML Documents by SDLC Phase

* Technically not a formal UML document. Robustness diagrams are considered a form of Class diagrams, but the original intent was these diagrams be closer to Interaction diagrams. I consider this informal UML document to be a hybrid between the Stuctural and the Behavioral.