An event in the Unified Modeling Language (UML) is a notable occurrence at a particular point in time.
Events can, but do not necessarily, cause state transitions from one state to another in state machines represented by state machine diagrams.
A transition between states occurs only when any guard condition for that transition are satisfied.
|
Unified Modeling Language
|
|
| Actors |
- Organizations
- Object Management Group
- UML Partners
- Persons
- Grady Booch
- Ivar Jacobson
- James Rumbaugh
|
|
|
| Concepts |
| Object oriented |
- Object-oriented programming
- Object-oriented analysis and design
- Object-oriented modeling
|
|
| Structure |
- Actor
- Attribute
- Artifact
- Class
- Component
- Interface
- Object
- Package
- Profile diagram
|
|
| Behavior |
- Activity
- Event
- Message
- Method
- State
- Use case
|
|
| Relationships |
- Aggregation
- Association
- Composition
- Dependency
- Generalization (or Inheritance)
|
|
| Extensibility |
|
|
| Other |
|
|
|
| Diagrams |
| Structure |
- Class
- Component
- Composite structure
- Deployment
- Object
- Package
|
|
| Behaviour |
- Activity
- State Machine
- Use case
|
|
| Interaction |
- Communications
- Sequence
- Interaction overview
- Timing
|
|
|
| Derived languages |
- Systems Modeling Language (SysML)
- UML eXchange Format (UXF)
- XML Metadata Interchange (XMI)
- Executable UML (xUML)
|
|
| Other topics |
- Glossary of UML terms
- Rational Unified Process
- Comparison of UML tools
- UML colors
|
|
| This Unified Modeling Language article is a stub. You can help Wikipedia by expanding it.
|