Chapter 3. Demand Capture N View Original
The first section of the previous page. Argouml guide Next
Chapter 3. Demand Capture
table of Contents
3.1. Introduction
3.2. Demand capture process
3.2.1. Process steps
3.3. Products for the demand capture process
3.3.1. Description documentation
3.3.2.
3.3.3. Use example
3.3.4. Requirements
3.4. Used in argouml
3.4.1. Participants
3.4.2. Use case
3.4.3. Contact
3.4.4.
3.4.5. Prototype
3.4.6. Documentation
3.4.7. System Boundary Box
3.5. Research on use case
3.5.1. Description documentation
3.5.2. Distinguished participants and use cases
3.5.3. Contact (unfinished)
3.5.4. Advanced chart features (unfinished)
3.5.5. Use example (unfinished)
3.5.6. Need to supplement the instructions (unfinished)
3.1. Introduction
Demand capture is a process of looking for the "customer" hope that the system should have.
The key to this step is that we are in the problem definition phase. At this stage we must describe all things from the "customer" perspective from the "customer".
The biggest error in the demand capture process is immediately considering various possible solutions. The solution design should wait until the analysis phase (see Chapter 4, analysis) is started. One of the steps in the analysis phase is to use the results in the demand phase and re-designed these results with possible solutions.
Remember that all of our use is an overcast handling process. [Translator Note: Evolution Model]
When we break the problem into a smaller part, we may also return to the demand capture process, and each small problem also requires their respective needs capture.
Since we try to define more and more requirements for the system, we also need to return to the requirements capture phase at each iteration.
Note The UML Standard Specification case diagram is the unique diagram used in the demand phase. The remaining illustration is used in "Process". The "process" in this chapter mainly refers to the "Rational Unified Process". [Translator Note: A set of standards developed by Randional, known as Rational Unified Process]
Previous 2.6. Case Study Returns this directory to return to the user manual directory Next page 3.2. Demand capture process
[Translator Note: This chapter corresponds to the "demand analysis" in domestic software engineering. In the translation process, the "demand capture" is used to use "demand analysis", and finally determine the former. Because "capture" is more reflected in the description of this process, it is not difficult to see that the author believes that the main purpose and work of this process is to faithfully reflect the needs of customers rather than why there is such a need or such demand. Role, so, use "capture" more accurate. ]
