This hints at a possible bottleneck in the design. In the figure, one notices the fairly high amount of waiting requests at the PhoneNumberCheck action. In front of the actions, red bars show the amount of requests waiting for processing. Green coloring indicates that an action is currently active. The figure shows the status of a system after a certain running time.
Below, a snapshot of the running simulation is presented. The result of the transformation is a simulation using elements from the activity diagram library, configuring and connecting them according to the information obtained from the input activity diagram. For these elements, we have defined the simulation semantics and visual representations. We have created such a library containing elements known from activity diagrams. Instances of these library elements can interact through messages that are passed through ports and connectors. In AnyLogic, one can define libraries of elements that participate in simulations. The latter supports the understanding of problem sources, especially in early system design. AnyLogic is a simulation engine that can run simulations to analyze systems and provides visual representation of the running simulation. The output of the transformation is an AnyLogic simulation model.
It depicts the probability that a certain path is chosen by the decision.Īnnotated UML activity diagrams act as input to the transformation. It is set on control flows that originate in decision nodes. Not illustrated, but also utilized, is the Probability attribute. It is set for actions succeeding an initial node.
The Repetition attribute is utilized to set arrival rates. It is also indicated that the value is a mean ( mean) value, which is assumed ( asmd). It depicts the time required to perform the action. The Host Execution Demand is set for every action in the diagram. Two of the properties are set to meaningful values here: the Host Execution Demand and the Repetition. Performance attributes of the CreateOrder action The values set for the CreateOrder action are shown below. It defines a set of stereotype attributes that can be used to set concrete performance parameters. It is defined in the SPT profile and identifies one processing step that has performance properties. In the diagram, several elements are stereotyped with the PStep stereotype. The pizza ordering process as activity diagram In this use case, we use a simplified version of SPT that includes the parts of the specification required here.Īs an example, we consider a high level description of an online pizza ordering process illustrated below. Such information could be derived from knowledge and experience.Īnnotating performance information on UML models has been standardized in the SPT profile and its successor the MARTE profile. For instance, approximations of the time it would take to perform certain actions. However, in order to execute useful analysis, certain performance information has to be available. To lower costs and risks, it is desirable to run analysis on the modeled system before it is actually implemented. When designing software, system behavior can be modeled using UML by utilizing, for instance, activity diagrams. Such simulations can help to identify performance issues early in a software design process. This information is used to generate a simulation model that can be executed by the AnyLogic simulation tool from XJ Technologies. The actions and control flows in activity diagrams are annotated with performance information utilizing the UML profile for schedulability, performance, and timing (SPT). In this case study we present a transformation from annotated UML activity diagrams to AnyLogic simulation models. This use case presents a transformation from annotated UML2 activity diagrams to AnyLogic simulation models.
0 kommentar(er)
