UML software engineering organization
Beautiful example: When is this UML activity diagram Scott W. Ambler
The UML activity diagram records logic, single-use cases, or logical flows for a single operation or method. In many ways, the active diagram is an object-oriented equivalent of the flowchart and data flow chart (DFD) in structured development. This reminder is adapted
Chapter 6 of The Object Primer 2nd Edition.
The activity diagram in Figure 1 describes how university new students will handle commercial logic.
The solid circle represents the starting point of the activity map, in fact, a placeholder, a solid circle with a border indicates the end point. Rounded rectangles represent the process or activity of the execution. In this figure, although you will notice the "Registration Workshop" Activity will call multiple times, these activities are quite closely mapped to the use case. The activity can be more detailed, especially in selecting the logic logic, not the senior business process. The rhombus represents the determination point, although the judgment point in this example has only two possible results; but even more possible results, it is equally easy. The arrow indicates the conversion between the activities, the flow order between various activities. The text on the arrow indicates that the conditions that continue to be met, always using the format "[Condition]". I guess that in the future version of UML, we will see the conditions recorded using the UML constraint representation (such as "{condition}"). The thick line indicates the beginning and end of the process that may be conducted in parallel; There are several ways to exit activities, as you can see "Fill in the Enrollment" activity. If you have fill in the form correctly, you can continue your college admission procedures. However, if the form is incorrect, you must get help (you may get help from the registrar) to fill in them correctly. Figure 1. The first enrolled UML activity map is very interesting because it saves the logic of several use cases identified in Figure 2. The usage model does not have a good order to express processing. For example, although the example shown in Figure 2 shows you clearly describes the type of functionality executed by the system, it does not express the order of these use cases that may occur. However, the activity map of Figure 1 has done this. In summary, the advantages and disadvantages of different models have different. Figure 2. Example of universities Reference information For more information on UML activities, see:
