Your cart is currently empty!
Unified Modeling Language (UML)
UML is a modeling language used to visualize, specify, construct, and document the structure and behavior of software systems.
UML uses:
- Shapes (фигуры)
- Lines (jooned)
- Icons (märgid)
- Labels / Text annotations (pealdised)
✅ Assignment: Create UML Diagrams
You are expected to create UML diagrams using the elements listed above. Depending on the type of system you’re modeling, you might choose one or more of the following common UML diagram types:
Examples of UML Diagram Types:
- Use Case Diagram – shows system functionality from a user’s perspective.
- Class Diagram – describes the structure of classes, attributes, and relationships.
- Sequence Diagram – models interactions between objects in time order.
- Activity Diagram – represents workflows or processes.
- State Diagram – shows state changes of a system or object.
- Component Diagram – visualizes components and their dependencies.
- Deployment Diagram – illustrates the physical deployment of software.
UML diagramming assignment
Types of UML Diagrams
1. Data Schema Diagram (Andmebaasi skeem)
Shows the structure of a database, including tables, their fields, and relationships between them. It helps visualize how data is organized, which aids in database design and management. This type of diagram also helps developers and database administrators maintain data integrity and understand entity relationships.
2. Use Case Diagram (Kasutuslooskeem)
Use case diagrams are used to define the main elements and processes of a system. The key elements are called actors, and the processes are use cases. The diagram shows which actors interact with each use case, helping to capture system functionality from the user’s perspective.
3. Class Diagram (Klassiskeem)
Used to detail use case diagrams and define the detailed design of the system. It groups actors into a set of related classes. Relationships (associations) between classes can be of type “is-a” or “has-a”. Each class provides functionality (called methods) and has a set of attributes that define it uniquely.
4. Object Diagram (Objektiskeem)
A specific type of class diagram that shows the state of objects at a particular moment during the system’s execution. It displays the instances of classes and their relationships at a certain point in time.
5. State Diagram (Olekuskeem)
Displays the various states that objects in a system go through during their lifecycle. Objects change their state in response to events in the system. The diagram shows the transitions from the initial state to the final state based on those events.
6. Activity Diagram (Tegevusskeem)
Describes the flow of actions or operations in a system. Similar to state diagrams, activity diagrams consist of actions, transitions, start and end states, and decision conditions.
7. Sequence Diagram (Jadaskeem)
Displays the interaction between objects in a time sequence. Its key feature is chronological order, showing the step-by-step exchange of messages between objects over time.
8. Collaboration Diagram (Koostööskeem)
Also called an Interaction diagram, it groups the interactions between different objects. Messages are numbered, showing the order in which interactions occur. It helps to identify all possible interactions between objects.
9. Component Diagram (Komponentskeem)
Illustrates the high-level components that make up a system and how they are interconnected. This helps to understand the structure and organization of the system’s parts.
10. Deployment Diagram (Juurutusdiagramm)
Shows the runtime elements of an application and how software components are deployed on hardware nodes (e.g., servers, devices).
11. Storyboard
Used in addition to a sitemap to help make design, technology, and budgeting decisions. A good storyboard gives all stakeholders a clear overview of the website being created. It doesn’t show every page but covers the key functional areas. It doesn’t include the visual design of the pages but outlines core elements on each page. It can be created by hand or with any graphic tool.