UML Diagram is ideal for software developers and program managers who need to illustrate and interpret software application relationships, actions, and connections using the Unified Modeling Language (UML) notation. It works in the following fields:
Edraw is a new UML diagram and software diagram drawing tool for software engineers and designers. Edraw makes it easy to draw UML model diagram, COM and OLE, data flow model diagram, Jacobson Use Case, SSADM Diagram, Nassi-Shneiderman diagrams, Booch OOD diagrams, ROOM Diagram, Yourdon and Coad diagrams and Shlaer-Mellor OOA diagrams, program structure diagrams, enterprise application diagrams, UML use case diagrams, UML sequence diagrams, UML activity diagrams, UML collaborate diagrams, UML statechart diagrams, UML component diagrams, UML static structure diagrams, UML package diagrams and UML deployment diagrams.
The Edraw UML Model Diagram template provides full support for creating object-oriented models (model: An abstraction of a modeled system that specifies the modeled system from a certain viewpoint and at a certain level of abstraction.) of complex software systems.
UML Use Case Diagrams
In the early stages of a development project, use use case diagrams (use case: In a use case diagram, a representation of a set of events that occurs when an actor uses a system to complete a process. Normally, a use case is a relatively large process, not an individual step or transaction.) to describe real-world activities and motivations. You can refine the diagrams in later stages to reflect user interface and design details.
UML Static Structure Diagrams
Use static structure diagrams (static structure diagram: A diagram that shows the static structure of a model; that is, the elements that exist (such as classes and types, the internal structure of the elements, and their relationships to each other.) to create conceptual diagrams that represent concepts from the real world and the relationships between them, or class diagrams that decompose a software system into its parts.
UML Package Diagrams
Use package (package: A grouping of model elements represented in the UML by a symbol that resembles a manila file folder. Each element in a system can be owned by only one package, and one package can be nested in another.) diagrams to group related elements in a system. One package can contain subordinate packages, diagrams or single elements.
UML Activity Diagrams
Use an activity diagram (activity diagram: A special case of a statechart diagram in which all of the states are action states and the transitions are triggered by the completion of actions in the source state.) to describe the internal behavior of a method and represent a flow driven by internally generated actions.
UML Statechart Diagrams
Use a statechart (statechart diagram: A representation of a state machine, attached to a class or method, that describes the response of the class to outside stimuli.) diagram to show the sequence of states an object goes through during its life.
UML Sequence Diagrams
Use a sequence diagram to show the actors or objects participating in an interaction and the events they generate arranged in a time sequence.
Sequence diagram: An interaction diagram that shows the objects participating in a particular interaction and the messages they exchange arranged in a time sequence.
Actor: In a use-case diagram, a representation of a role played by an outside object. One physical object, therefore, may be represented by several actors. A communicates relationship indicates how an actor participates in a use case.
Object: Information created in another application and imported, embedded, or linked in a Visio drawing. The term object is used to refer to objects from other applications and OLE objects.
Event: An occurrence in Visio, such as a change to a shape formula or the deletion of a page.
UML Collaboration Diagram
Use a collaboration diagram (collaboration diagram: An interaction diagram that shows, for one system event described by one use case, how a group of objects collaborate with one another.) to show relationships among object roles such as the set of messages exchanged among the objects to achieve an operation or result.
UML Component Diagrams
Use a component diagram (component diagram: An implementation diagram that shows the structure of the code itself. From a component diagram, you can learn about compiler and run-time dependencies between software components, such as source code files or DLLs.) to partition a system into cohesive components and show the structure of the code itself.
UML Deployment Diagrams
Use a deployment diagram (deployment diagram: An implementation diagram that shows the structure of a run-time system. From it, you can learn about the physical relationships among software and hardware components and the distribution of components to processing nodes.) to show the structure of the run-time system and communicate how the hardware and software elements that make up an application will be configured and deployed.Tweet