He knows what he wants, what the other stakeholders want and so he needs to document this. The next step for John is to capture the different requirements. What the application is supposed to do ? Capture the use cases Then the Opaque actions contains there bodies which are editable thanks to the direct edit). It is possible to define a body to an Opaque Action by selecting the optional layer Body from the diagram toolbar. actor, subject (component, artifact, datatype, interface, collaboration, class), use case labels.In the use case diagram, it is possible to edit the elements labels (see Diagram editor/Editor main graphical area/Direct edit). It is possible to reconnect the source and the target of any kind of edge in the activity diagram :
The user can also delete a flow (see Diagram editor/Editor tab-bar/Delete element/from model).Īnd finally, he can reconnect flows. The following edge creation tools exist in the palette : Element It is possible to create a flow by selecting the edge creation tool from the palette and then clicking on a source element and a target element. The user can also delete an activity element (see Diagram editor/Editor tab-bar/Delete element/from model). When the Call Operation action tool is selected, a selection wizard is opened to ask the user to select an existing operation in the UML model : Tooltip tools are also available to create any kind of elements :Ĭreation tools are available in the activity diagram for the following types : Elementīrings together a number of alternative flow paths If the user selects a container, the element will be created under the corresponding semantic element in the UML model. It is possible to create activity elements by selecting the creation tools from the palette and then clicking on the diagram or an element.Ī diagram is associated to a package and when the user click on the diagram background the element is created under the corresponding package in the UML model. The activity diagram is a synchronized diagram which means that any elements existing under an activity in the UML model will be visible automatically in the activity diagram. The activity diagram is part of the behavioral diagrams in UML Standard, it is used to represent workflows of stepwise activities. To do so UML propose a very useful diagram : the activity diagram. He wants to catch the business process and checks if there is a precedent for this application. The purpose is to get an overall understanding of the system. What the application is supposed to do? What the application is supposed to be ?įirst, John tries to get a feel for the bigger picture of its application. The first questions John has to answer are :
0 kommentar(er)
