UML
Get flash to fully experience Pearltrees
UML state machine
UML state machine , [ 1 ] also known as UML statechart , is a significantly enhanced realization of the mathematical concept of a finite automaton in computer science applications as expressed in the Unified Modeling Language (UML) notation. The concepts behind it are about organizing the way a device, computer program, or other (often technical) process works such that an entity or each of its sub-entities is always in exactly one of a number of possible states and where there are well-defined conditional transitions between these states. UML state machine is an object-based variant of Harel statechart , [ 2 ] adapted and extended by UML. The goal of UML state machines is to overcome the main limitations of traditional finite-state machines while retaining their main benefits. UML statecharts introduce the new concepts of hierarchically nested states and orthogonal regions , while extending the notion of actions .
Activity diagrams are graphical representations of workflows of stepwise activities and actions [ 1 ] with support for choice, iteration and concurrency. In the Unified Modeling Language , activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control.
Activity diagram
UML logo Unified Modeling Language ( UML ) is a standardized, general-purpose modeling language in the field of software engineering . The Unified Modeling Language includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems.
Unified Modeling Language
Sequence diagram
Sequence diagram of e-mail message sequence A sequence diagram is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart . A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario.
In the early 1990s, there were 3 competing methods proposed to support object-oriented development - these were based on work by Booch (Booch, 1994), Rumbaugh (Rumbaugh, 1991) and Jacobsen (Jacobsen,1993). These approaches had much in comment and they were unified in the 1990s to create the Unified Modeling Language (UML) and the associated unified design process (Rumbaugh, Blaha, Premerlani, Eddy and Lorensen, 1991)(Booch, Rumbaugh and Jacobson, 1999, Rumbaugh, Jacobson and Booch, 1999a, Rumbaugh, Jacobson and Booch, 1999b). Since then, the UML has emerged as the standard notation for object-oriented modelling and design.
