The first thing I read is to write a valid use case book, the introduction of what is the first to explain what is a use case, my understanding of the use case is a different user and system to interact with a typical scenario of the description, the basic pattern of these use cases are the first few definitions such as the main performer, scope, level project related personnel and interests, Pre-conditions and so on, to describe the user's main scene, and my own perception is that the use cases must be represented by use case diagrams, but the language text is very clear, whether it is the business people or hardware and software developers or designers can use cases to describe the requirements, About the use case black box is not too concerned about the specific details, said the different methods applicable to different environments, the size of the software to use the formal level of the requirements are also different, the formal use of a case pattern to add a scene, definition, rather than the whole is only to describe the scene, From the use cases can be seen in part or the main requirements, the purpose of the use case is aimed at users, let users know in advance what the new system is.
Writing effective use cases-Book 1
