IBM Rational Rose Reading Notes (1)

Chapter 1 Introduction to UML Development view supported by rose and its functions:1. The business use case diagram shows the functions provided by the entire organization. It is used to set system scenarios and form the basis for creating use cases. It shows the interaction between business use cases and business roles. The business use case indicates the execution process of the company, and the business role indicates the objects that the business needs to interact. 2. the use case diagram shows the interaction between the use case and the role. Use Cases indicate the requirements of the system from the user's perspective, so they indicate system functions. A role is a system entity, indicating the person or system that provides and receives system information. Which role is the use case and shows when the role receives information from the use case. Business Use cases do not correspond to use cases one by one. 3. The activity diagram describes the workflow. 4. The sequence diagram shows the functional process of the use case. The top part of the block diagram shows the involved roles and objects. Each arrow indicates the messages that are transmitted between the role and the object or between the object and the object to complete the required functions. Only show objects but not classes. 5. The content of collaboration is the same as that of sequence, but its format is not in chronological order, but tiled by objects. 6. The class block diagram shows the class content and relationships. 7. statechart Block Diagram for complex objects, may contain multiple States. This block diagram is used to describe the switching relationship between multiple States. 8. The component diagram describes the physical view of the model and shows the software components and their relationships in the system. A. H file is a group, A. cpp file is a group, and A. EXE is also a component. Describe the dependencies between them through the block diagram. Generally, an executable file and its dependent source file correspond to a component diagram. 9. Deployment diagram describes the physical layout of the network and the location of each component. Four Stages of the Rational Unified Process and the block diagram used1. Start collecting information and performing conceptual verification. Use the business use case diagram and use case diagram. 2. Refine the use cases and make structural decisions. Analysis, Design, coding, and testing. Use the use case diagram, activity diagram, sequence diagram, collaboration diagram, statechart diagram, and component diagram. 3. Construct the encoding. Block Diagram generated between use, through positive and reverse engineering. Use the deployment diagram. 4. Hand over to the user for the final preparation and deployment phase. Update the component and deployment blocks. Chapter 2 rose gameThis chapter describes how to use the rose interface. Role of the Model1. the group uses the business use case diagram to understand the business target of the system. 2. the customer and System Administrator use the use case diagram to obtain the advanced view of the system and determine the project scope. 3. the Project Administrator uses the use case diagram and documentation to break down the project. 4. analysts and customers use the use case document to learn about the functions provided by the system 5. technical authors use the use case document to compile user manuals and training programs. 6. Analysts and developers use sequence and collaboration diagrams to understand the logical process of the system and the messages between objects in the system. 7. Testers use the use case document, sequence, collaboration diagram to write test scripts 8. developers use the class diagram and statechart diagram to obtain the details and relationships of each part of the system. 9. the deployment personnel uses the component and deployment diagrams to display the executable files, DLL files, and other components created by Yao, as well as the deployment location of these components on the network. 10. the entire group uses the model to ensure that the Code complies with the requirements, and the code maliciously traces back to the requirements. 11. Use forward and reverse processes to ensure synchronization of models and codes. Four Views of the Rose Model 1. Use Case View:It contains all roles, use cases, and use case diagrams in the system, and may also contain sequence and collaboration diagrams. The Use Case view is an implementation-independent view in the system. It cares about the advanced shape of system functions, rather than the specific implementation method of the system. With the use case view, testers can write test scripts, and Technical authors can write user documents. Analysts and customers can confirm all their requirements, developers can see which advanced components and system logic the system creates.

 

2. logical view:Focus on how the system implements the functions proposed in the use case. It focuses on the logical structure of the system. It identifies system components, checks system information and functions, and checks the relationship between components. It is generally used by developers and architects. The interaction diagram can appear in the use case view or in the logical view. The heavy interaction diagram of the former shows the high-level structure, independent of implementation. For example, there can be an analysis class, which is a language-independent class. The interaction block diagram of the latter is implemented based on specific languages, and the classes are design classes. The analysis class can correspond to multiple design classes.

 

3. Component View:The main user is the person responsible for controlling the code and compiling and deploying the application. He describes the physical structure of the Code, components, and executable file organization.

 

4. Deployment View:The actual deployment of the system may be different from the logical structure of the system. Chapter 3 business modelThis chapter describes the business itself, the entities that interact with the business, and the real workflows in the business environment before designing the system. Business Model ConceptBusiness Model Research Institutions. In the process of establishing a business model, check the structure of the organization, the roles of the company, and the relationship between them. It also introduces structured workflows, major processes in the company, how these processes work, how they work, and whether there are bottlenecks. Business models focus on the following two aspects: first, the boundaries of an organization and who it wants to communicate? Second, the workflow in the organization and how to optimize the workflow in the organization? A business model includes the following concepts: 1. A business role is everything that interacts with the system. Each role is related to the activities of the company. 2. Business workers are roles in the Organization. A role is not a position. A person can assume multiple roles, but can only be in one position. 3. Business Use Cases business use cases are a set of related workflows in the Organization and are useful to business roles. Business Use Cases tell people what organizations do, and what they do will be conducive to the work of business and participants. All business use cases in the organization provide a complete description of the business objectives. Business Use Cases can be created in two ways: Text script and activity diagram (as described below ). 4. the business use case diagram shows the business cases, business roles, and interactions between business workers. It provides a complete model of the company's work, internal roles, and external roles; specify the scope of the Organization to view the content and boundaries of the Organization. 5. The activity diagram (activity diagram) shows the workflow of the use case in a legend. 1) solid points indicate the start state. 2) the angle rectangle is called activity. An activity is a step in a workflow and a task to be completed by a business worker. The activity contains multiple operations: a) Actions that occur when you enter the activity, marked with entryb) actions that occur when the activity leaves the activity, marked with Doc) actions that occur when you leave the activity, marked with exitd) the operation of a specific event is marked with the event and event name. 3) There are multiple swimming Paths Based on Business Roles and business workers. 4) The activity contains multiple operations. Column in the activity (rectangle. 5) The diamond represents the branch. 6) the horizontal line is called synchronization. 7) a rectangle represents an object. These objects are affected by the workflow and change the status during workflow execution. 6. Objects used during business operations of business entities or objects generated during business processes. 7. An organization unit is a collection of business workers, business entities, and other business model units. It is a mechanism for organizing business models. Procedure for establishing a business model1. identify a business role 2. mark the business worker 3. identify Business Use Case 4. show interaction (interaction between the first three), use the business use case diagram 5. document details, including the use of activity diagrams to describe business cases, and use business case reports to describe other information about the use cases. Tips for using rose to create a business model1. Use tools> Options> toolbar to add the tool to the left of the block diagram. 2. To add an item, you only need to drag the icon in the toolbar into the block diagram. 3. Delete is only deleted in the block diagram, and is still saved in the browsing area. CTRL + D is required to delete the page thoroughly. 4. The sub-branches in the browsing area do not indicate the inclusion relationship. If the other item is related to this item, it is listed in the branches of this item. 5. you can add and manage items in the query menu. you can view the properties of items in the report menu. the associations in the browsing area describes all the relationships. The branches of the relationship are related items of the relationship. 8. Organization Unit is a constructor of packet. It seems that there is nothing special except icons. 9. For detailed reference books, as long as you understand the concepts and functions, you can easily use rose for operations.