Use case that collects data from a source, performs basic checks and prepares the source for staging in. Typically used in business intelligence projects.
Characteristics
In the execution of a
Collect use case, a number of steps is performed:
- Check Source Presence. Only if a source file is delivered, processes need to be started.
- Archive Source. Better make sure you keep a kopy of what you received!
- Uncompress Source. In case of a zipped delivery, file need to be exgtracted and folowing processes must be done for all of these files.
- Check Source.The goal of this step is to do syntaxic checks on received data. *etc.
 Activity diagram for Collect use cases |
Variations
Different variations of this type of use case exist. These mainly depend on the type of source that is collected. This can be either:
- Push native. During the project also the source is being extracted from the source system.
- Push external. The source is being delivered (on a regular basis) by the source system. There is no need to implement any functionality to obtain the source.
- Pull.
- Direct. The new software reads into the source system, eiter in its database, or from (web) services the source system offers.
Estimation