Draw a diagram to express your ideas, structures, processes, and workflow. Choose the correct diagram for the desired purpose. Diagrams can perfectly illustrate your texts and documents. Learn how to draw various diagrams using the following tutorials.
UML diagrams are divided into two main groups - structure diagrams and behavior diagrams. Behavior diagrams include a subgroup of interaction diagrams. There are 14 types of UML diagram types in total. Each type of UML diagram focuses on a specific aspect of the UML model. Sometimes, creating a UML diagram may be not easy task, but Software Ideas Modeler will help you to manage it. The tutorials in this section shows you how to make various UML diagrams.
Complex and high hazard systems should be properly analyzed to prevent or reduce possible risks. There are tools as FTA, ETA, and FMEA you can use for analytical purposes.
A BPMN diagram offers a graphical representation for process modeling and describing. The processes are presented as flows of tasks, events, and process branches (realized by gateways), organized in swimlanes.
An event tree analysis is a powerful analytical tool that allows you to analyze an event within a system with its possible consequences and probabilities of various outcomes.
FTA (Fault Tree Analysis) diagram is used to analyze and understand possible risks, especially in high-hazard industries. It is a top-down diagram that organized the events and lower-level events using Boolean logic operators.
Use the roadmap tool to create a good-looking roadmap that depicts a plan of a project, the planned stages for new features and modules. Roadmaps are used to present what a team or a company wants to release or develop in the upcoming period or later in the future.
The Layer diagram is a type of a block diagram. It can be used to depict a higher architecture or a concept of a solution.
A user stories diagram is the easiest way how to capture and define user requirements. The user stories may be organized within hierarchies and periods (called sprints). The epics represent the top level of the user story hierarchy. The requirements are organized in the form of statements - As ... I can ... so that ...
A decision matrix (or decision table) is the right choice, if you want to resolve possible outcomes of many combinations of conditions. It allows you to define conditions and possible actions. Then you define the rules which show what conditions lead to what actions.
Screen Flow Diagram allows you to connect your wireframes into a flow with branches according to the user's interactions.
An entity-relationship diagram (E-R diagram or ERD) describes types of a data domain and how they are interconnected. It has an irreplaceable position in data modeling. It is used to design data models, especially for database systems.
Data Flow Diagram (DFD) shows a flow of data in a process or a system. It also depicts inputs and outputs.
A flowchart is a diagram that depicts a workflow, process, or algorithm. It may be used to show a succession of steps on how to solve a task. This article lists all supported flowchart symbols.
User Interface Diagram describes the appearance of application screens and forms in form of wireframes. The amount of details is up to the designer's decision. The diagram may represent only the basic layout, highlight some parts of layout or it may provide a detailed view on the designed user interface and its various aspects.
Draw various shapes in your diagrams. Software Ideas Modeler offers dozens of basic shapes that can be used on any diagram. You may find the shape tools in the Drawing group in the toolbox.
UML Profile Diagram describes and defines extensions to UML language. The extension mechanism allows you to adjust the language to a specific domain or platform. The extensions are defined via stereotypes.
UML timing diagram is focused mainly on time, it shows the changes of classifiers in time depicted on a timeline. The timelines are stacked vertically, the time increases from left to right.
UML Interaction Overview Diagram provides a high-level view on interactions in a system or a subsystem. It depicts the flow in similar way as an activity diagram, but instead of action nodes it uses other interaction diagrams and interaction references.
A composite structure diagram shows the internal structure of a classifier, its parts and ports via which it communicates with the environment. It models collaborations where each element has its defined role.
UML Deployment Diagram depicts deployment of artifacts on nodes. It is used for showing the placements of artifacts (software, system, module, etc.) on physical nodes (hardware, server, database, etc.) and the relationships between particular parts of the solution.
A component diagram offers a view on a complex system. It depicts the interfaces provided and/or required by the parts of the system and the relationships between the parts. The parts are represented by components and other artifacts.
A UML package diagram shows dependencies between the packages in the model. It depicts the structure and organization of project in the large scale.
An object diagram is a structural UML diagram. It describes a system or its part at a specific time. It models instances, their values and relationships. It may be used to show examples of data structures.
A state machine diagram describes states of en entity (device, process, program, software, module, etc.) and transitions between the states. Conditions specifies when a transition from a state to another state may be used.
A UML communication diagram shows interactions in the form of messages between objects and parts, which are represented by lifelines. Communication Diagram is a modified form of UML Sequence Diagram, but unlike it, its elements do not have to be ordered horizontally and may have any position in the diagram.
An activity diagram is a behavior diagram that shows a scenario using a flow of actions. It models a sequence of actions, decisions based on conditions, concurrent branches and various cycles.
A sequence diagram models communication among objects in sequential order. It shows objects, classes, and actors involved in the scenario and exact order of messages. It consists of vertical lines which belong to lifelines and horizontal lines of messages.
A use case diagram consists of use cases, actors and relationships among them. It presents a user interaction with the system, and defines the specifications of use cases.
A class diagram is a static diagram that describes the structure of a system by showing its classes with their attributes and operations and the relationships among objects. This tutorial explains how you can draw UML class diagrams and what usage they have.