Infographic element Progress Bar shows a visual representation of progress. This tutorial shows you how to harness all its capabilities.
If you want to create a new diagram from a part of an existing diagram, you may copy the desired elements, add a new diagram and paste the elements into it. Or you may do it in just a click. This tutorial shows you how.
The models and diagrams are organized in projects. A project contains all elements, relationships, documentation, diagrams, other specific parts, and their associated data, fields and styling settings.
Drag and drop is a very useful and intuitive technique. Software Ideas Modeler supports drag&drop actions wherever it is possible.
The ERD tool provides many useful features to help you work with diagrams. One of them is the highlighting of the context parts in the diagram.
The Mediator is a behavioral design pattern. It describes interactions between objects. The use of a mediator solves the problem of the complexity of communication. The objects communicate through the mediator object instead of each other.
The Iteration design pattern describes how to iterate a collection so that the iteration algorithm is decoupled from the collection class.
Setting Manager provides access to settings - it allows the user to read and write settings of various types. It organizes the setting in hierarchical groups.
The executed commands may be stored in a stack to provide undo and redo functionality. These diagrams show the structure and behavior of a command stack.
You can turn the steps of an algorithm to a flow of nodes in a flowchart.
Help for Software Ideas Modeler
Software Ideas Modeler needs for its run installed .NET Framework 4.5.2.
Software Ideas Modeler offers various editions that include different subsets of all features. During the evaluation period, you may try any of the offered editions and find the one which suits your needs best.
The following steps show you how to apply your license you get to e-mail after your purchase.
You have installed Software Ideas Modeler and you want to start to work with it. This article guides you through the first steps after running the application.
Server provides support for user cooperation, global repository and tasks.
Removing Software Ideas Modeler from your computer is very easy.
Class Diagram is a static structure diagram which describes the structure of a system by showing its classes with their attributes and operations, and the relationships among objects.
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.
Sequence diagram models communication among objects in sequential order. It shows object, 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.
Activity diagram is a behavior diagram, which shows a scenario using a flow of actions. It models a sequence of actions, decisions based on conditions, concurrent branches and various cycles.
UML Communication Diagram shows interactions in 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.
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.
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 use to show examples of data structures.
UML Package Diagram shows dependencies between the packages in the model. It depicts the structure and organization of project in the large scale.
Component diagram offers a view on a complex system. It depicts the interfaces provided and/or required by the parts of system and the relationships between the parts. The parts are represented by components and other artifacts.
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.
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 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.
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 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.
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.
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.
Flowchart is a diagram which depicts a workflow, process or algorithm. It may be used to show a succession of steps how to solve a task.
Data Flow Diagram (DFD) shows a flow of data in a process or a system. It also depicts inputs and outputs.
Entity Relationship Diagram (E-R diagram or ERD) describes types of a data domain and how they are interconnected. It is used to design data models, especially for database systems.
Screen Flow Diagram allows you to connect your wireframes into a flow with branches according to the user's interactions.