Process | Goals | Procedures | Data Stream Project | |||
Data | Model | Tool | People | |||
Acquisition | 1. Acquire specific components, tools, etc. 2. Buy or develop components, tools, algorithms, etc. | See examples on Table 3 | The acquisition depends on the business model. It can occur for data, tools and people. | Models are specific to each project, especially business ones. Computational models can be reused. | Tools can be acquired/purchased for specific projects. | People are needed for the Project and must be hired to form the Project teams. |
Retention | 1. Configuration Management. 2. Store Procedure. | See examples on Table 3 | Data for stream projects cannot be retained, but some batches can be stored, depending on the business model. | Models can be retained for later reuse in similar projects. | Tools, acquired or developed for a specific project, may be retained. | People are necessarily retained, because with their acquired expertise, they should perform better in future projects. |
Review | 1. Review project work products, tools, algorithms, etc. 2. Reuse. | See examples on Table 3 | There is no review for data. | Models can be revised, when starting new projects, to favor their reuse. | Tools and components developed for a specific project can be placed under configuration management to be reviewed at the start of a new project for reuse. | People should be used for future projects, receive new training and be promoted. |