Design object oriented software with Unified Modeling Language (UML).
Capture functional requirements with UML use case diagram. Each use case in a use case diagram represents a high level business goal that yields a measurable result of business values. (UML) Actors are connected with use cases to represent the roles that interact with the functions.
Model the structure of system by modeling its classes, their attributes and operations in a UML class diagram. UML class diagram is a blueprint of the classes (code level) required to build a software system. Programmers implement a software system with the help of both the class diagram and the class specification.
Visualize the interactions between users, systems and sub-systems over time through message passing between objects or roles. If class diagram represents the skeleton of classes by showing their attributes and methods, UML sequence diagram complete the classes by representing the programming logic to be filled in methods' body.
Collaboration between objects in runtime can be modeled in the UML tool, with a UML communication diagram. In a communication diagram, objects, called lifelines, are connected to represent the need of communication during the execution of an interaction. Messages can be added on top of the connectors to list the calls made from and to those lifelines.
Use UML activity diagram, the flowchart-based diagram to model the flow of control. Partition actions according to the type of participant involved.
State machine diagram is a critical design model for event-driven systems. Well-designed state machine shows accurately the essential states of objects as well as the triggers of state change, which facilitates the development of error-free state machine.
Model how a protocol works, with protocol state machine. Both behavioral and protocol state machines are supported in the UML tool.
Components diagrams are used to model the structure of systems by showing how little parts of the system gear up in forming a bigger part, or forming the entire software systems.
Models the physical deployment of software components with UML deployment diagram. In deployment diagram, hardware components (e.g. web server, mail server, application server) are presented as nodes, with the software components that run inside the hardware components presented as artifacts.
Arrange and organize model for large-scale project with package diagrams. Package diagram is also good in visualizing structure and dependency between sub-systems or modules.
View a snapshot of instances of classifiers in UML class diagrams. Similar to class diagrams, object diagrams show the static design of a system from a prototypical perspective.
Visualize the internal structure of a class or collaboration with UML composite structure diagram. Model a system from a micro point-of-view using UML composite structure diagram.
Timing diagrams model the behavior of objects throughout a given period of time. It is a commonly used UML tool for designing real-time and distributed systems.
Drag to move a time unit back and forth. Have a timing frame updated automatically according to your change.
View the sequence of interactions with UML interaction overview diagram. Interaction overview diagram helps represent complex scenario that involve multiple interactions presented as multiple UML sequence diagrams.
View the thumbnail of interaction diagrams or sequence diagrams. View and know the control flows of interactions.
Requirement is what your clients want and what your team have to fulfill. It is so important that needs to be managed carefully. The SysML requirement diagram provides a visual approach in representing and managing system requirements. In a requirement diagram, requirements are shown as blocks, with connectors in between, illustrating the derivation, dependency and grouping of requirements.
Define your own requirement types, with user-defined properties and appearance.
Produce a list of requirement to Excel for external manipulation. Import the file back for updating.
Visualize your system hierarchy. Define the system/component classifications in blocks to get a better picture of interconnections between these system components.
Take a closer look at your system design. Describe the internal structure of a system in terms of its parts, ports, and connectors.
Parametric Diagram is a restricted form of internal block diagram that shows only the use of constraint blocks along with the properties they constrain within a context. Parametric diagram is used to support engineering analysis, such as performance, reliability, and mass properties analysis.
Make internal links between different kinds of project artifacts. Those references work both in Visual Paradigm and in any document and Web contents generated from your design.
Maintain reference between software design and the business documents to help find out why a design decision was made.
Glance over a design. The tiny marker that appear in shapes' body indicates that the shapes have references added.
Insert model element references to rich text description. The referenced model elements will be linked and highlighted.