2.1 Review of UML Flashcards
What is OMT?
Object Management Technique
- class model diagram
- state chart diagram
- data flow diagram
put together three views of a system into a cohesive view
What is UML?
Unified Modeling Language
- Standardized by Object Management Group (OMG)
- Supported by CASE tools
- Conceived by Rumbaugh, Booch, and Jacobson
- Used for analysis or design. The main distinction is the analysis is concerned with the problem being solved, design is concerned with the solution.
What are the two main categories of diagrams?
Structural - concerned with the pieces of the system that are always there and the relationships among them
Behavioral - concerned with the executions of the system. a diagram may only convey one execution. may need multiple sequence diagrams to convey all the behaviors of the system.
Class Model Diagram
- structural diagram
- aka static models
- structural properties
- classes and relationships
Relationships
Object Diagram
- structural diagram
- concerned with instances rather than classes
- convey a specific use of a class
Composite Structure Diagram
- structural diagram
- conveys internal structure of a class
Component Diagram
- structural diagram
- static implementation view
- models code entities
- used to convey architecture
Deployment Diagram
“Configuration of run-time processing nodes and the component instances and objects that live on them.” - UML Reference Manual
- structural diagram
- node denotes a computational device
- arcs indicate communications
Package Diagram
- structural diagram
- general purpose organizing mechanisms
- provide namespace scoping
- system is the top-level package
- dependency arrows between packages indicate the existence of dependencies between constituents
Profile Diagram
- structural diagram
- higher level; properties of diagrams, not models
- profiles allow you to extend the basic UML notation
Use Case Diagram
- behavior diagram
- a use case is a sequence of user-visible actions along with system responses
- useful for eliciting requirements and organizing development activities
- depicts the relationships among system actors and use cases
- stick figures denote external actors
- ovals are use cases
- lines without annotations indicate participation
«extends» and «uses» stereotype support factoring - use cases may be conveyed with unstructured text or in a table
Context Diagram
- behavior diagram
- NOT part of UML but provide interesting capabilities
- dataflow diagrams provide a different view
- DFD depict processes, actors, and the dataflows among them
Sequence Diagram
- behavior diagram
- conveys a single use case
- columns correspond to individual participants (usually objects)
- time marches down
- horizontal lines between columns indicate the passing of a message from one object to another object
Communication Diagram
- behavior diagram
- object diagram annotated with ordered interactions instead of links
- semantically equivalent to Sequence Diagram
Activity Diagram
- behavior diagram
- designed to communicate synchronization
- variant of a state machine in which multiple states may be simultaneously active (have their own threads of control)
- transitions typically triggered by activity completion
- used to model workflows, process synchronization, concurrency
Interaction Overview Diagram
- behavioral diagram
UML Timing Diagram
- behavioral diagram
State Diagram
- behavioral diagram
- most powerful and complex
- aka state charts
- extended finite state machines
Class Model of UML Metamodel
