Write a valid use case _ read Note 04

The 11th chapter, as the last chapter in the first part of this book, provides several alternative use case formats. The first is a full formal use case format, first a single column of text, followed by no conditional statement, and finally the number sequence for the extended part is a combination of numbers and letters. I personally after reading this book, I prefer this format, the reason is that I have seen after the habit of seeing, another reason is that the extension of the number of part of the rules more acceptable to me.

After looking at several formats, can not help but curious, how there will be so many templates to reference, so not rigorous indeed unlike our engineering documents such as the requirements, look back only to know, the original impact of the use case writing format of many factors, From the social culture to the level of understanding to the relevant requirements of the project personnel to experience to coverage to the complexity of the impact. In addition, in different requirements analysis phases, the requirements for use cases are not the same, from the need to understand use case templates, to business process modeling use cases to determine system requirements use case size to short-term efficient project use cases, which vary depending on the time period.

The use case of the format of the final choice, you can use such a sentence instead of "timely, see a person likes."

From chapter 12th into the new section, the book begins to discuss some of the topics that are often discussed. The second part of the content is simple, not so systematic, but for a small problem began to tell, so, next, I will step on the watermelon skin!

Look at the teacher Wang told a semester of software requirements analysis, but also feel that the teacher has not started me, see the 12th chapter of the topic is like a bosom friend Ah! Really ah, "when to calculate the completion", exactly what should be done in the prophase of demand analysis, when can solve, just calculate the completion of work? This book gives us a definite definition: 1) Has named all the actors associated with the system and user Goal 2) captures all the trigger conditions of the system 3) write all user target use cases and necessary summary use case and sub-function use case 4) Each use case description is clear enough 5) the investor confirms that the use case set covers all their needs. In fact, after reading these five requirements, I always feel that these requirements exist and do not exist, there is no quantitative to give the requirements, too much concept, but no origin significance.

Before writing a use case for a project given by a teacher, it was felt that some use cases were written in one which felt that the use case was too plump, and was singled out for writing, and too barren, and here is an effective method: "Simply explain each use case, or divide the use case into multiple clusters." To tell the truth, the content of this article does not give an example, concrete implementation is not as simple as theory.

In the process of learning the soft work, crud is often said to be a word, that is, the deletion and modification, of course, the small use case of database-based operations is called crud use cases. The details here are mainly reflected in the optional data stream divided into four or five parts corresponding to the CRUD-related operations.

Write a valid use case _ read Note 04