Feedback Model
FIGURE 15: UML ACTIVITY DIAGRAM FOR FEEDBACK MODEL
Description of scenario
This model is a special case of the outsourcing model, in which a third party data collecting organisation agrees to supply XCRI data back to the provider. This model is particularly useful if the provider is setting up new systems and does not yet have high quality data capture processes.
The provider inputs the data into the data collector’s system, usually by keying it. This process permits the data collector to impose data structures, data entry standards and vocabularies (for example by using drop-down lists or prescribed classification systems). The data collector can then carry out validation, checking and further classification of the data prior to returning it in XCRI format to the provider.
The provider is then able to use the XCRI data to populate its own course advertising systems, gaining value through the use of information with standardised vocabularies.
Typified by
Characteristic |
Description |
| Number of courses | Any |
| Complexity of provision | Any |
| Number of sources | Typically a new source or data store coming on stream |
| Quality of authoring | Data will be keyed into a 3rd party system |
| Data structures | Well defined data structures in the 3rd party system |
| Update frequency | Typically this is a ‘one-off’ activity, so maintenance of the data is not required. |
| Audit trail | |
| Centralisation | Data is centralised both in the 3rd party system and new HEI system. |
| Process capability | As this is a ‘one-off’ activity, it can be treated as an ad hoc process. |
| Technical capability | Technical capability for the new internal system and for XCRI import is required at the HEI. |
| Organisational context | Any |
| Resources | Resources for import into the new system is needed. |
TABLE 7: CHARACTERISTICS OF THE FEEDBACK MODEL
Example
Not given; this model has not yet been encountered in a live situation, though it has been proposed.
