Writing a good three concepts must master the use cases:
Range (scope): the real question is what is the system?
The main actors (primary actor): Who has the goal to be achieved?
Level (level): level target is high or low?
Definitions and embodiments associated with:
Performer (actor): the behavior of any person or thing has.
Stakeholders (stakeholder): there is a particular person or thing interested in the behavior of the system in question.
The main actors (primary actor): Start with the system in question is an interactive event, person or thing to achieve a goal.
Use cases (use case): the provisions of the contract in question system behavior.
Range (scope): Definition of the system is discussed.
Pre-conditions and guarantees (precondition and guarantee): Examples condition before and after the execution must be met with.
Main success scenario (main success scenario): everything goes situation.
Extension (extension): scene perform different situations arising in the process.
Extension number: different situation occurs in the main success scenario in which the step numbers (e.g., refer to step 4a and 4b are two different main success scenario case step 4).
Underlined with Example: When a reference to a further embodiment of a use case when, with the embodiment referenced underlined.
The actual project development process, people do not have time to go in most cases the use cases written in a formal, complete and beautiful, but only as far as possible to write "full." For more detailed description of the use case it is formal or informal; which parts and format is necessary.
Written in the style of embodiment, depending on the purpose of writing of different
In accordance with the requirements phase sub: ① demand in the discussion stage ----------- writing style "informal (casual)" The Future.
② requirements gathering stage of the Working Group -------- writing style "complete official."
Divided according to the purpose: ① black box use case: the system does not care about the internal details.
② white-box use cases: need to understand how the internal process operations.
It normally takes two use case template, an informal, a full formal.
Informal use case: a complete description of business processes related to the use cases.
Complete official use cases include: the main actors, in the context of the objectives, scope, level, project stakeholders and interests, pre-conditions, a minimum guarantee, to ensure success, trigger time, the main success scenario, expansion, changes in technology and data list priority, release, response time, frequency of use, the main executor of channels, secondary executor, executor of the secondary channels, in order to solve the problem.