47. Class Diagrams Class diagrams represent the static structure of the classes in the software system, and illustrate attributes, operations, and relationships between the classes.
48. Class Diagrams – A class Person - name: String - age: int + toString: String Name Attributes Operations
73. Use Case Diagrams Use case diagrams show the interactions of users and external entities with the system being created. They are very good for depicting high level requirements of a system.
76. Use Case Diagrams Use cases can also extend and include other use cases
77. Activity Diagrams Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. - Wikipedia
79. State Machine Diagrams State machine diagrams are used to depict the state transitions of a single object in response to events. They are modeled in a similar way as activity diagrams.
84. Sequence Diagrams - Entities Actor – represents external entities in the system. They could be human or external systems. General lifeline, represents an individual entity Entity, represents beans, and other objects that hold data or information. Boundary element, represents elements at the boundary of a system, such as UI elements or backend logic which deals with external systems. Control element, manages the flow of control for a scenario.
88. Communication Diagrams Communication diagrams (aka collaboration diagram) are similar to sequence diagrams, but they do not have lifelines, and are more free form in nature. The focus is usually object relationships between boundary, control, and entity types.
90. Interaction Overview Diagrams Interaction overview diagram is a special type of activity diagram, where each node is a link to another type of interaction diagram.
