I. Basic Type Business Use Case Box: Displays interactions between business use cases and business roles, indicating the functionality of the entire organization, is drawn from the perspective of the mechanism. The business use case is used to display the business execution process. The business role represents anyone who interacts with the company outside the company, not the role or personnel in the company, such as customers and manufacturers. The role or personnel in the company are expressed as business workers. Use case block diagram: Display the interaction of the case and the role. Use a case representation from the user's aspect to the system, that is, the system function is represented. The role is the main body of the system, indicating a person or system using system information. The Business Use Case block diagram is independent of the automation process, and the USE case block diagram is for the automation process. There is no one in the business use case and the case of use. Activity block diagram: Demonstrate the function stream in the system, define where workflow begins, where is the end, which activities have occurred in the workflow, what happens in any order. Sequence block diagram: Display the functional flow in the case. This block diagram is useful to the project. Collaboration block diagram: The display information is the same as the sequence block diagram. The Sequence block diagram illustrates the interaction of the object and the role over time; while the Collaboration block diagram displays the interaction of the object and the role. Class block diagram: Display the interaction between the system and classes in the system. Provides a static graphic of the interrelationship of a class machine. STATECHART block diagram: provides a way to model the model object. You can model the dynamic function of the system. Not each class creates a StateChart block diagram, only for complex classes. If the class object has a variety of states, the performance in each state is not large, and you need to be created. The STATECHART block diagram can be generated directly through the ROSE plugin. Component block diagram: Show the physical view of the model, also display software components in the system and its interrelationships. Deployment block diagram: Displays the physical layout of the network and the location of various components. Second, the purpose ● The entire project group uses the business use case block diagram to understand the system for the system ● Customer and project administrators obtain the system's advanced view with the USE case block diagram, determine the scope of the project ● Project administrators use the USE case box diagram and document river project decomposition Being manageable Small Modules ● Analysts and Customer Use Case Document Understand the functionality of the system ● Technician use case documentation Start writing User Manual and Training Program ● Analybled staff and developers use sequence and collabration block diagrams to understand the system logic, system Messages between objects and objects ● Quality personnel use case documentation and sequence, Collabration block diagram to get the information required for test scripts ● Developers use class box diagrams and StateChart block diagrams to obtain details of each part of the system and their interrelationships ● Deployment People use the Component and Deployment block diagrams to display the executables, DLL files, and other components to be created, and the deployment position on these component networks ● The entire group model is used to ensure that the code follows the requirements, and the code can return to demand. Third, the activity block diagram ● Swimwide Show who is responsible for the task in the block diagram ● Activity is the step in the workflow ● The business object is the action in the workflow image entity Activity includes: ● ON Entry is used to enter the activity. ● ON EXIT is operated when exiting the activity ● Do FOR is operated in an active operation ● ON Event is used in a specific event. The user case block diagram 1. Role includes a system user, another system, time of interaction. It is usually naming as a role in action 2. The case is the function block provided by the system, that is, how people use the system. Use a case is the respective implementation of business use. Usually a requirementable tracking process is: Service Example - System Sample - Event Stream - "Sequnce / Collaboration Block Diagram -" Class Block Diagram - "Component Block Diagram -" Code 3. The event stream builds the logic flow of the case. The purpose is to describe what the system is dry, not how to do it. Event streams often include: ● Brief description of the role of the case, and the final result to be reached.
● Prerequisites ● Main event streams include how to start, various paths, error flows, how to end ● Other event streams ● Afterwards, INTERACTION block diagrams include sequence block diagrams and collaborative block diagrams. Sequence is sorted by time, can display control focus; collaboration can display data streams. 1. Establish the step: (by analyzing the event) ● Look for object ● Looking for role ● Adjusting the message to block Figure 2. Function By block diagram, you can determine whether you need to develop a class, the class is related to each class, or each class responsibility. 3. Example sequence block diagram: 4. Interchange sequence block diagram to the Collaboration block diagram is easy to interplace. Browse- "CREATE COLLABORATION. . . . 6. Class block diagram 1. Some parameters explain: Export Control: Sets the candidate, determine whether the class outside the package can access the class. MultiPlic: Sets the class base. Represents the number of instances. Space: Set the storage requirements of the class, that is, the required relative or absolute memory. Utilities and parameterized categories cannot use the Space field. Persistent: Sets the sustainability of the class. The Persistent class indicates that there is also existence other than the application execution, that is, the information in the class object is stored in a database or permanent storage. The information in the TRANSIENT object is not in the permanent storage. Concurrency: Sets the concurrency of the class, describing the performance when there is a plurality of control threads. SEQUENTIAL, only one control thread, can not guarantee whether the class can work properly when there are multiple threads. Guarded: There are multiple control threads, work normally, but the classes in different threads will cooperate with each other and cannot interfere with each other. . Active: The class has its own control thread. Synchronous: There are multiple threads, work normally, do not need to collaborate with other classes, itself can be mutually exclusive. NESTED: Use nested classes, one class can nested another class. STEREOTYPE: Plate type, equivalent to template. 2. Property format: Name: data type = initial value In Tool- "option Select the Notation tab, select or cancel the Visibility AS ICONS check box, you can also select the default language in Default. 3. Operation format: Name (argument1: argu1 type, argument2: argu2 type): Return TypeProtocol: Specifies the operation protocol, describing the customer's operation on the object, and the order of operation execution. Such as: Hire () Must Be Run Prior To Executing Promote (). The information entered here does not affect the generation of the operation code. Qualification: Specifies the language specific qualification of the operation. Exceptions: Lists an exception that can be thrown. Will affect the generation of operation code. 4.Containment relational paint method, for example, move the mouse to the class icon, then move the mouse slightly until the class icon is not selected, double-click, right-click the one end of the arrow, choose Containment of-> by value . 7. The StateChart block diagram shows an object from the created lifecycle created to the delete, you can create a dynamic behavior of the class. This is a block diagram of a class, right-click the desired class in the browser, select New- "StartChart Diagram. 8. Deployment view deployment view Consider the physical deployment of the application, including the processor, device, process, and processor and device connections.
