1. ROSE's role (1) Project start phase Generates a case box diagram of the Case Model (2) Refining Phase Developer, a cooperation map, first to develop objects, and its interaction between each other. Class block diagram display the inter-object interval. (3) Constructing the initial phase generation component block diagram, display the correlation between system components, and generates the frame code of the system. (4) The new development code is transferred to the model by reverse engineering to the model, thereby reflecting the changes in the development phase to the model. (5) At this stage, ROSE is mainly used to update the model when the software product is completed. 2. How to select a default programming language such as selecting a VC language is, Tools-> Options-> notation-> default-> VC . 3. Use of Use Case View The USE CASE view includes all roles in the system, using cases and USE case block diagrams, may also include some Sequence and Collaboration block diagrams. At the beginning of the project, the main user of the USE CASE view is customer, analyst and project administrator. These people use the case, the USE case block diagram, and the use of documents to determine the high-level view of the system. Using cases only focus on the role of the system, not to pay attention to its implementation details. 4. The Logic view uses two-step Logic view with two-step method, first labeled the analysis class and then markes the design class. The so-called analysis is not related to the language. For example, there is a Boundary class, a Control class, an Entity class, etc. Design classes have specific language characteristics, such as Java classes, or C classes. There is no correspondence between the analysis class and the design class. 5. Logic view There is a role logic view Follow the system's logical structure. In this view, you want to mark the system components, check the information and functionality of the system, check the relationship between the formation. Reuse here is a major purpose. Determining the repetition class and packages by carefully assigning the information and behavior of the class, the combination class, and the relationship between the classes and bags. Once you have completed multiple projects, you can add new categories and packages to your reputation library. Future projects can assemble existing classes and packages without having to start from scratch. 6. Using the control unit supports multi-user parallel development ROSE supports multi-user parallel development through the control unit. The control unit in ROSE enables any packages in the USE CAS view, Logical view, or Compinent view. In addition, the Deployment view and the Model Properties unit can also control. When a unit is controlled, it is stored in a file independent of the model other departments. In this way, stand-alone files can be used to control the SCC's version control, such as the basic tools of Rational ClearCase, Microsoft SourceSafe, and Rose. The control unit can be loaded or unloaded from the browsing model. You can also check the import and exit (Checked IN and OUT) using the control tool. 7. The main benefit of the input and output model is a majority of object mechanisms is reused. Repeated use is not only available for code, but also for models. It is necessary to make full use of repeated use. Rose supports output and input models and model elements. The model or partial model can be output. Enter another model. Note: When you want to output a package or class, you must select the things in the logical view; to output the model, it is something other than this. 8. Use case and role use cases and roles to describe the range of the system, using cases include everything in the system, and the roles include everything outside the system. No program details are considered. Using a case is the advanced function block provided by the system, the role is an object interacting with the system.
9. ISE CASE View How to Arrange MAIN view in Use Case View primarily to display the case package. As for the use case in the package, you can place it in an additional view, this view is named by the name of the package, which can be separated from the main view to make the entire USE CASE view clearer. 10. Regarding the predetermined rules of USE Case View (1). Do not moderate communication between roles, because the role is outside the system; (2). Box diagram Displays the usage case but regardless of their execution order, So don't draw arrows between using the case, unless expressed the use of relationships and extensions; (3). Every case must be started by the role, that is to say there is an arrow, except for the use of relationships and extensions; (4). You can regard the database as the layer below the entire USE CASE box. You can use a case to enter information in the database, and then access the information in the database in another case, do not draw arrows between using the case Show information flow (with 2: Do not draw arrows between using cases unless expressed the use of relationships and extensions). 11. Differential use cases using cases and traditional methods are a case-oriented process rather than achieving a process, therefore different from traditional functional decomposition. Functional Decomposition Pay attention to how to break down into a system-processed small block, and use case first pay attention to the user's needs. 12. How to find a case checking the documentation provided by the case, while inquiring what the end customer needs: (1) What is this system to do? (2) Do users want to maintain any information (generated, read, update, delete)? (3) Do users tell the system to the system? (4) Do you want some changes and events to tell users? 13. Some suggestions on the use of cases (1) Use the case independent of programming details, it is concerned that the system's function is not how to implement this function. (2) Use the case is a high-grade view, not too much, the number of usage cases of general users is 20 to 50. It can be used to use the relationship and extended relationship to use the case to make the necessary decomposition, or the case combination is used as groups to facilitate organization. (3) Use the case to follow the user using the system. Each case should represent a complete transaction between users and systems to provide users with a certain value. Use the case should be named after the business is named instead of the computer technology term, it should make the customer at a glance. Using cases usually use verbs or verb phrases to describe the final result of the customer, the customer does not care about what to do with these needs. 14. How to check if the case is complete (1) whether each function requires at least in one case? If required not in use, it will not be implemented. (2) Do you consider how each user uses the system? (3) What information is provided to the system each user? (4) What information has each user receive from the system? (5) Do you consider the maintenance problem? Someone will start and turn off the system.
(6) Does all external systems that the system want to interact? (7) What information is received from the system from the system, what information is sent to the system? 15. Refining the case of the case - Reproduction Event Stream (1) Brief Description: Describe the role of the case; (2) Prerequisites: Conditions must be met when starting using cases; (3) Main event streams and other event streams: The specific details of the case are described in the main event stream and other event streams. The event stream is to pay attention to the system, not how to do A. How to use the case; b. Use various paths of the case; C. Use the normal (main) process of the case; D. Deformation of the main event stream using the case (other event stream); E. Error event stream; f. How to use the case end. (4) Post-event conditions: It must be true after the case is completed. 16. Each case in the name of the case should have a unique name. Using a case should be named from a customer perspective to help determine the project range. The case name is used should also be independent of the implementation method. To avoid phrases that use cases to contact specific implementations, such as Internet. Use cases to name the verbs and phrases. 17. There are three categories: system users, other systems that interact with the system, time. Time is used as a role that a certain event is triggered. For example, the ATM machine may run some coordinated processing every night. Since the event is not within our control, it is a role. 18. Role version Although there are multiple options, only one actor can be selected. 19. The role base is made to make a certain role requires how many instances. 20. Use cases and roles to support four relationship communication relationships, use relationships, extended relationships (Extends Relationship, Actor Generalization). Communication: Role and Use Cases; Use: Make a case where you can use another use case feature, usually used to construct some two or more case-commonly used accessible functions. As shown in the figure below, the authentication process can be shared. Extension: Make a case to expand another function of using a case. It is similar to the use of relationships, all of which is separated from the common function to another in the case, but the direction of the arrow in the legend is just the opposite. The role is generalized: indicating that several characters have some commonality. For example, company customers and individual customers are customers, their relationships are shown in the following figure, and this relationship is not always necessary. In general, only when the system is considered to be characterized by another role. If the company's customers launched some personal customers who don't start, it is best to perform roles. If the two customers use the same case, there is no need to perform roles. If the two customers use the same case case, it is only a slightly different, and there is still no need to perform roles. The fine difference can be represented in the event stream document of the case. twenty one. About the use of cases, the nodes of the role This chapter ends how to use cases, roles, and USE case block diagrams. The requirements of the system are set up in all cases and roles. First, be a master USE case block diagram, the overall view of the system is displayed. Other block diagrams can then be generated. Demonstrate use cases and roles interaction. Use the case to use and expand other cases. Also directly communicate with the cases.
One case always needs another case when using the case's function. One case option is available to extend the use of the case when using the case. If a case is used or expanded another case, the user is a phenomenon using a case. The case where the use of the role involved is specific to the specific use case. Roles can be communicated with cases to demonstrate which role is involved in which case. The roles can also be inherited with each other. For example, students may be roles in the system, and we must further divide students into full-time and half-day students. At this time, full-time and half-day students inherit the student role. twenty two. Object of persistence (1) Continuous Persistent: Save to database or other continuous memory, such as hard drives, discs, or floppy disks. (2) Static STATIC: Static object is saved in memory until the program terminates, and does not save in the external continuous memory, the global objects in C . (3) Temporary Transient: Temporary object is only saved in memory in a short time. Note: If the sustainability of the object's class is set to Persistent, the persistence of the object can be set to Persistent, Static or Transient. If the continuousness of the object's class is set to Transient, the persistence of the object can only be set to static or transient. twenty three. Different points (1) of the sequence diagram and collaboration maps Only the sequence diagram has a control focus FOCUS OF Control (2) Only the collaboration map has a data stream: the data stream is a value returned after the object is sent to another object. (3) Collaboration diagram shows information flow, but does not display time. Collaborative diagrams show messages between the relationships between the objects and between objects. From the designer, which object can be seen is a bottleneck, or find those objects need to communicate directly. twenty four. Synchronization of messages (1) Simple Simple: Messages run in a single control thread. (2) Synchronous SYNCHRONOUS: After the customer issues a message, wait for the supplier to respond to this message. (3) Block BALKING: The customer issues a message to the supplier, if the supplier cannot receive a message immediately, the customer gives up this message. (4) Timeout Timeout: The customer issues a message to the supplier, if the supplier cannot receive a message at the specified time. (5) Asynchronous asynchronous: Whether the message is received or not, there is no other thing regardless of the message. 25. The frequency of the frequency message of the message can be sent by the message according to the specified time interval, for example, once every 30 seconds. (1) Periodic: Regular message; (2) NUMPORTEC: Uncertain messages, only once, or send it in irregular time. 26. Two steps of legal transactions mutual map: Focus on the advanced information of customers concerned. At this time, the object has not mapped the class, and the message has not been mapped. These pictures are just let analysts, customers, and other people interested in business processes to understand the logical flow of the system. Step 2: After the client is unified, the team adds more details. The block diagram is more useful to developers, testers, and other members of the project, and the role of customers is not big. First, add the object. It may be added to the control object, the database connection object, the security handler object, the error handling object, and the like. Usually each interaction map has a control object, responsible for the program in the scenario.
All interactions of a case may share a control object, so a control object can handle all program information of the case. Note that the control object does not perform any business processing, just send messages to other objects. Control objects are responsible for coordinating the effects of other objects and entrustment responsibilities. Therefore, the control object is sometimes referred to as a manager object. The benefits of using control objects are capable of separating business logic and program logic. Next, map each object to a class. You can map to the ready-made class or the newly generated class. Next, each message mapping in the block diagram will be operated. Second, the details of the design objects and messages, the continuity of the object, the message synchronization, and the message frequency, and the like. Finally, a model quality report is generated, showing unmapped objects and messages. 27. How to find classes (1) You can start from the event stream of the case to see the nouns in the event stream. (2) Check the object in the interaction, and find classes through the commonality of the object. Search for class to consider three different layers: Entity, Boundary, Control. 28. Types of categories, parametric, instantiated classes, class utilities, parameterized utilities, instantiated class utilities, and categories. (1) Parameterization class ParameterizedClass: Used to generate a series of other classes, usually parameterized is a container, also known as template. Set the value of the parameter in Detail-> Formal Arguments. (2) Instantiated class instantiatedclass: Parameterized by actual variable value. (3) Class utility CLASSUTILITY: is a set of operations, such as mathematical functions. Class utility often uses the functions provided by the extended programming language or placing a group of generally available function blocks to use many systems. (4) Parameterized Utility ParameterizedClassutility: Yes Generate Class Utility Template. (5) Instantiated class utility instantiatedclassutility: is the parameterized utility of the parameter. (6) Metai Metaclass: An example of a molic class is a class rather than an object. Parameterized and parameterized utilities is a category. 29. Three types of types: physical classes Entity, Border Boundary, Control class control. (1) Boundary Boundary Classes: At the junction of the system and the outside, all forms, reports, interfaces such as hardware such as printers and scanners. Looking for a boundary class to find cases, there is at least one border class between each "Role-Use Case", which may be shared with other "roles - use cases". (2) Entity Entity Classes: Save information to be placed in continuous storage. Substations are typically in an event stream and interactive diagram, which is the most meaningful class of the user, usually named by business domain. Typically, a table can be generated for each entity class in the database. (3) Control class Contro classes: Coordinates other classes of work. Each case usually has a control class that controls the order in which the time in the case is used. Note: The Control class does not complete any feature, and other classes do not send a lot of information to the control class, but there are a lot of information that makes a lot of information, and the case is just entrustment to other classes. To this end, the control class is also known as the management class. There may be many control classes to be shared between many cases. These control classes can analyze the functions used by the system.
30. Settings the visibility of the settings Visibility option to determine if you can access this class outside, there are three options: (1) Public: All other classes in the system can access this class. (2) Protected, private: This class can be accessed in nested classes, friendships, or all kinds in all kinds. (3) Package or Implementation: This class can only be accessed by other classes in the same package. 31. The class base can set the number of instances of the class. There is also a "role" of the base. 32. The storage requirements of the class indicate the relative or absolute memory requirements of each class. Class utility, parameterized utility, instantiated class utility cannot use this field 33. The continuous Persistent: information in the class object is stored in the database or other permanent storage. Class utilities, parameterized utility, instantiated class utility cannot use this field. 34. Setting the class concurrency concurrency Description Class in the presence of multiple control threads. Sequential: There is only one control thread, and the class is working properly, and it cannot be guaranteed when there are multiple control threads. Guarded: When there are multiple control threads, the class is working normally, but the classes in different threads should cooperate with each other to ensure that they do not interfere with each other. Active: Class has its own control threads Synchronous: When there are multiple control threads, the normal work does not need to cooperate with other classes because other classes itself can process mutually exclusive situations. 34. Use packets (1) in a class block diagram (1), subcontract, such as physical classes, Entity, Border Class Boundary, Control Class Package Control. (2) Press Function Bracket such as secure package security, error handling package Error Handling ... 35. How to Find Properties (1) Review usage case. Look for nouns in the event stream. (2) Demand document. Demand may introduce the system requirements which information is collected, which is the properties of the class. (3) Check the database structure. If the database structure has been defined, the fields in the table are attributes. Note that the database table and the entity class are not always one or one. The properties of the class should not be too much, and if too much can be broken down into smaller classes. The number of attributes of the class is preferably controlled below 10 to 15. The same attribute is not too small, too little can be merged. 36. How to distinguish between attributes and classes (1) Consider whether this information is active, if there is a category processing; (2) According to the specific needs. 36. Setting the attribute tolerance description attributes how to store attributes in the class. Press value by value: Property is placed in the class. For example, if the attribute is defined as a string, the string is placed in the definition of the class to reference by reference: attribute is placed outside the class, and the class points to this property. Unspecified: No to specify the inclusion type. Default setting. 37. Setting the properties of the class to be static such that all this class object is shared. 38. Specifying a derivative attribute is the property generated by other properties. 39. Type of operation (1) Implementation Implementor Operations: Implement some business functions. The implementation operator can be found from the interactive block diagram. Each implementation should be able to retrore the requirements: requirements -> Use the case-> Event stream -> message -> operation. (2) Manager Operations Manager Operations: Managing objects and constructs.
