"Writing effective use cases" reading Note II

Small force based on database operations is called a crud use case, each small use case expresses a separate requirement, and there are two different ways to handle this use case, either separating it or processing it with a single administrative entity use case. A generic search engine may be established when extracting system use cases or when there are many use cases that are roughly the same. Each target step of a use case is named like a child procedure call in a programming language, and the use case is used by someone other than the computer. Searching for anything will have the same steps, for the convenience of operation we can create a parameterized use case, which is an alias for each use case. The alias data values are then divided into three different levels of precision, simplifying the use case description to a certain extent.

When modeling business processes, it is necessary to document their systems through use cases prior to reorganization, to create external behavioral requirements that meet design requirements through use cases, and to document the new process of the letter using use cases after design. In the top-down analysis, it is necessary to understand the project stakeholders in the organizational behavior, the external main performers, the triggering events that the organization needs to respond to, the services provided by the Organization, and the successful results of the project stakeholders. The business design process can be described using black-box use cases, which will give full play to the technology, innovate resource groups and new processes. But as technology updates, white-box use cases are used, which does not involve technology, because the computer does the things that the person can accomplish.

In software requirements analysis, the use of regular tables will give a clear description of the function. A development group can use a use case to develop software design tasks to maintain the timeliness of use case mappings. The design task step does not correspond neatly with the use case unit, so a business object or behavior generated by a design task can be used in multiple use cases at the same time. In formulating a rough system function diagram, it is necessary to reach a consensus on the narrative mode adopted by the system, and then to reach a consensus on the application area, and focus on the system main performer and system target, and then write the system description and summarize. Then, to refine the function diagram, we first agree on the format, then write the use case and then review it. Use the application description as an exercise before the use case is written and summarize the use case as part of the project summary.

Use cases need to be modified when the use case lacks the functionality of the system or the role of the performer. Software development, the process of writing use cases need to have a lot of description, need to have strong expression ability, before it felt a real master-level character whether developers or engineers, will love sports, or music, obviously also have a strong literary literacy. It needs to be easy to read using examples when writing use cases. And when a person has a profound study of literature, sports or art, there will be great benefits in the work, can help people to open up ideas, horizontal vertical thinking of the two-way development is very important.

The use case is like an unfolding story, the top-level use case calls the outermost use case, and the outermost use case expands to the user target use case or sea level use case. The design scope is easy to cause confusion, people often have different views on the boundary of the system. It is important to understand that the scope of the business use case is that the business operation does not involve technical issues, and the design scope of the system use case is to design a computer system involving technical problems. You can use icons to differentiate between business use cases and system use cases or to place a picture of a system inside the system contained within the use case itself. People often make mistakes in development to reflect the most important issues, which are established in many areas. Each sentence of the use case describes a subsystem to be implemented, as well as the whole system from the outside of the system, and then describes the use case in a higher posture; the readability of the force must be stronger or it will lose its existence, and a use case may be used at different times to learn to migrate , the system is usually considered a black box, otherwise it will be difficult to read, you need to choose the correct path after the main success scene, learn to accept the change because the change is necessary in the whole process, the advantage refinement function and use case is very essential, need to grasp, and use collaboration diagram instead of text can improve readability. The use case hints are important, regardless of which stage it is necessary to consider completely.

Although the UML tool can be a lot of information that we get in the graph, the importance of the document is beyond doubt. A graph is a two-dimensional mnemonic basis that is intended for cognition. The inclusion relationship is a subroutine call from a programming language that requires various parameters to assist in the completion of the function. When there is a "user taking some action", consider using generalization, sometimes generalization contains only special actions. In this book there are a lot of details on things, in the ordinary small experiment, you will not notice, you must gradually standardize their work flow.

Writing an effective use case read the second of the notes