Lifecycle method in relation to the UIDM
Introduction to the UIDM
The Users and Innovation Development Model (UIDM) is derived from JISC project work in the Virtual Research Environment area. The model is an iterative method for requirements elicitation, system design, prototyping, trial and improvement for systems in the web 2.0 and 'perpetual' beta improvement cycle domains. Use of the model is mandatory for projects in the JISC's Users and Innovation Capital Programme.
The UIDM is most completely described in the JISC Emerge VLE (login required), or in JISC Circular 02/07 Appendix F.
The UIDM is composed of sometimes overlapping and repeated cycles.
- Understanding the users
- Transition and decision
- Technical development
- Enhancing User Acceptance and Support.
Generally the UIDM was represented as a figure 8 (click to enlarge):
In late 2007 an alternate and more conventional representation was produced:
While there is a wealth of useful material that is building up around the UIDM, particularly for the stage 1 activities, and while the model is being to be used, it suffers from some 'teething' problems:
- The method lacks an activity with the all-important co-design of scope, contents, functionality, and user interface.
- Possibly some more attention is needed for partitioning and ordering of activities in the UIDM's iterative cycles.
However, neither of these points detracts from the very positive step that the UIDM makes in introducing greater consideration of users into JISC development methods, and the collection of user-centric design techniques offered by the UIDM.
The relationship between the lifecycle design method and the UIDM
The UIDM addresses a slightly more dynamic and fluid design, prototyping and development regime than the lifecycle method, although the lifecycle method achieves similar dynamism if used with a scope, contents, functionality and user interface design phase with strong user involvement, including, likely involvement in design and involvement in testing paper prototypes in a formative evaluation style.
Regarding different parts of the method:
| UIDM | Lifecycle method |
Understanding the users (and domain) Strong overlap in design techniques between methods |
Understanding the users, domain and processes Strong overlap as in lh column |
|
Transition and decision Scoping, build or buy decisions |
Design Iterative design (scope, contents, functionality, and user interface) and Iterative refinement of (paper) prototypes via formative evaluation |
|
Technical development analysis and design (use cases, CRC cards leading to an analysis-level system class structure, detailed system design class structure, coding, testing, implementation, rollout |
Technical design Detailed system design including service design |
|
Enhancing User Acceptance and Support Change management, including communication, training, help, summative user acceptance testing |
Implementation, testing, rollout Evaluation of the rolled out system is not done here, instead the lifecycle method uses the the outer loop as needed |
