Three: Use case
Basic concept and related introduction of use case
Main methods: exchange with customers, a collection of use cases is the need for the entire system
How to distinguish user objectives and system interactions
Acquisition of an example model:
The use case model is the basic tool for acquiring requirements, planning, and control project iterative processes. It is one of the first steps to be done in the initial stage and is one of the main tasks of the refinement phase.
a, get the executor
Getting the use case first to find out the user of the system.
(1) Who uses the main function of the system (main user)?
(2) Who needs to support their daily work?
(3) Who will maintain, manage the system to work properly (auxiliary users)?
(4) What hardware needs to control?
(5) What system needs to interact with other systems? This is the system contains other computer systems and other applications.
(6) What is interested in the results of the system?
b, get the use case
Some issues have been made for each executive, then get the use case from the actor's answer to these issues.
(1) What functions required by the executor ask the system (what do people need to do)?
(2) What types of information in the executor needs to read, generate, delete, modify, or storage systems?
(3) What are the system incidents that must be reminded? or
(4) What are the executives must remind system events? How do these events represent the function of the use case?
Problem for the system
(1) What input output does the system need? Where is the input? Where is the output?
(2) What is the main problem with the current operating system (perhaps some manual operation rather than computer systems)?
