Chapter 3
The written use case is extremely personal, everyone has his own style, and each organization has a way to do things according to their own culture and business, so there is no universal process of creating the use case.
3.1 BreadthbeforeDepth
the reason:
• Demand collection is a discovery process, and the use case is written is an iterative process;
? People have already begun to write the details of the use case;
People waste energy or fall into too many details, usually lose their focus and unable to describe all possible extension conditions;
• Overview from the early days is beneficial;
The more details of the initial prepared, the more changes must be made after the system;
and so:
The energy is preserved by first developing an exception, and then gradually increases detail, and a set of related examples is developed in parallel. After completing the outline use case, with the increase in the system, it is constantly increasing the accuracy of the use case, avoiding all the use cases of all use cases or only one use case.
3.2 Spiraldevelopment (Spiral Development)
the reason:
Understanding the behavior of the system can take a lot of time and require progressive analysis;
Delay is expensive. To complete the writing of the use case as soon as possible;
Demand is likely to change after analysis;
The cost of demand costs is expensive;
and so:
Developed with an iterative, width priority, each iteration will increase the accuracy and accuracy of the use case.
Basic process:
Starting from simple things, such as a participant / use case list;
Briefly describe the main scene of the main scene, that is, high-rise cases, to include the main range of the use case;
The subset of the extension summary and fill the details;
Comment and adjust;
3.3 MultipleForms
Different projects require different degrees of formation, and each person has different preferences for templates, requiring everyone to use the same use case template to play only.
the reason:
Each person's personality, experience, and experienced exercise, each development organization has its own unique personnel, history and culture;
Different projects have different needs;
Different writing teams require different degrees of specifications and strictness;
Use public writing forms in organizations to help exchange;
It is not a good idea to use different templates on the same project;
therefore:
According to the project-related risk, project characteristics, and write formats in the person involved, the organization is used inside the organization in the development of the project.
3.4 TowtireReView (review)
Many people may need to review the use case, which is an expensive time.
the reason:
The review is necessary for verification and confirmation writing and content;
It has a vested interest in the use case;
Each person involved is very expensive, trouble and slow;
If you review only by a small writing group, you will not consider the interests of all people;
The review may be expensive, bored, time consuming.
and so
Two types of review: The first is a review by a smaller internal team, which may be repeated many times; the second is a review by the entire team, it may only be done once.
3.5 quittingtime
Developing an exemplary model that exceeds involving people and developers not only waste resources, but also delay project progress.
the reason:
The huge fear of ignoring important needs has led the construction personnel and the crowd to extend the demand collection activities;
Most people can work with a reasonable fuzzy work, that is, they are self-cleaning;
Detailed explanation of lies does not make them more accurate;
and so:
Stop development cases after the need for use case is complete and in line with the participants;
Test: Complete, readable, logically correct, sufficiently detailed developers.
Do you identify all participants and goals and compile them into documents?
• Customer and its representatives are recognized by the case, and each usage is readable and correct?
Can designers implement these use cases?
3.6 Writerlicense
Small format differences are not important, and after all system issues, there are some format issues in time, or they can stop writing;
