Content tagged with: sequence diagram
This Unified Modeling Language (UML) tutorial shows how to start with a use case and how to elaborate it into activity, class, sequence, and communication diagrams. This tutorial is a must for beginners who want to understand the relationships between different UML diagrams! It introduces the life cycle and evolution of a granular business case.
In this blog post, Jürgen Wüst discusses the size and complexity of UML sequence diagrams. He describe and define a basic set of simple size and complexity measures for UML 2.x sequence diagrams.
This series walks you through Unified Modeling Language (UML) design and notation for Java-based application development. This article introduces one of the building blocks of the Unified Modeling Language: sequence diagramming. In the UML, sequence diagrams are used throughout the design process to demonstrate the internal interactions between actors and objects as a system executes over time. Sequence diagrams are used to model the use case scenarios, protocols in a framework, subsystems, classes and method logic.
This article explores how you can specify graph transformation-based rules for a classical problem of transforming from UML sequence diagrams to state machines. The specification of the transformation rules is based on the concrete syntax of sequence diagrams and state machines. It introduces tailored transformation support for sequence diagrams and a novel graphical operator to match and transform combined fragments.
The sequence and communications UML diagrams are presented in this short tutorial. A sequence diagram in a Unified Modeling Language (UML) that shows object interactions arranged in time sequence. A Communication diagram models the interactions between objects or parts in terms of sequenced messages. Communication diagrams represent a combination of information taken from Class, Sequence and Use Case diagrams describing both the static structure and dynamic behavior of a system.
This tutorial provides a quick introduction to the Unified Modeling Language. The purpose of this course is to present important highlights of the UML. The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential details of the underlying problem from its usually complicated real world. Several modeling tools are wrapped under the heading of the UML™, which stands for Unified Modeling Language™.
In this blog post, Geert Bellekens proposes the best practice of creating a specific sequence diagram for each operation of a class.
This multi-part blog post discusses how to use UML diagrams to test a set of functional requirements:
* Part I introduces use cases diagrams and explain how they can be used for testing
* Part II shows how to create test cases from activity and sequence diagrams
* Part III discusses when the use of UML diagrams for software testing is not appropriate and present the conclusions.
This video shows the relationships between the use cases and the sequence diagrams in the Unified Modeling Language.