A simple state is one which has no substructure. A state which has substates (nested states) is called a composite state. Substates may be nested to any level. A nested state machine may have at most one initial state and one final state. Substates are used to simplify complex flat state machines by showing that some states are only possible within a particular context (the enclosing state).
Continue readingCategory: Unified Modeling Language
State Transition Diagram: A Heater Example
A state-transition diagram presents a sequence of states that an object goes through during its lifecycle. It is used to describe the changes of states for an object or for a component.
Continue readingWhat is Behavioral Things in UML?
The behavioral things is the dynamic part of the UML model. These are the verbs of a model. Represents actions in time and space. In general, there are two main kinds of behavioral things. (1) Interactions (2) state machines. They are the basic behavioral things that you may include in a UML model, typically the state machine diagram. Semantically, these elements are usually connected to various structural elements, primarily classes, collaborations, and objects.
Continue readingState Machine Diagram, PDFs and Resources from the Web
State Machine Diagram Note from OMG State Machine Slides – Lecture Notes by B. Beckert What is State Machine Diagram?
Continue readingState Machine Diagram vs Activity Diagram
UML State machine diagram and activity diagram are both behavioral diagrams but have different emphases. Activity diagram is flow of functions without trigger (event) mechanism, state machine is consist of triggered states.
Continue readingWhat is Case Management Model and Notation (CMMN)
CMMN is a graphical notation used for capturing work methods that are based on the handling of cases requiring various activities that may be performed in an unpredictable order in response to evolving situations. Using an event-centered approach and the concept of a case file, CMMN expands the boundaries of what can be modeled with BPMN, including less structured work efforts and those driven by knowledge workers. Using a combination of BPMN and CMMN allows users to cover a much broader spectrum of work methods.
Continue readingUse Case Diagram vs Use Case Specification
A Use Case describes a task that is performed by an actor yielding a result of business value for a business. A use case may be visualized as a use case diagram or/and in structured textual specification format:
Continue readingActivity diagram — A Quick Overview
UML activity diagram is another common tool used by UML to model the dynamic behavior of the system. It describes the sequence of activities and shows the flow of control from one activity to another. UML activity diagram is essentially a flow chart.
Continue readingHow to Identify Use Cases in UML Modeling
A use case approach is a kind of technique for identifying the business goals of a system. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy.
Continue readingUse Case Analysis — A Case Study
A use case is a requirements capture and documentation technique that can be written in plain text to describe in a narrative manner the actions and interactions of participants using the system. Finally, the functionality of the system should satisfy the purpose for which stakeholders use the system.
Continue reading