Use case models are now a mature technique in system analysis and design within the ICT industry. Within the analysis stage, use cases are intended for specifying functional requirements and for gaining consensus about these requirements to drive the subsequent design effort. They serve as a relatively simple means for an eclectic audience to sanity check proposed development or deployment of systems for a particular use. Consequently, ‘use case’ methods are apparently common place in healthcare applications.
Although many refer to use-case driven methodologies or strategies in the healthcare domain it is not clear whether or not the same thing is being used or being practiced consistently. A cursory glance at new proposals often hides the fact that what is meant by ‘use case and/or use case driven’ initiative varies from case to case both in terms of expression and volume of content. The context provided and the varied use of information models is also found to be problematic. Consequently to derive a repository of use cases for subsequent prioritising, comparison, testing and for future re-use becomes impossible.
Mandate 403, when implemented - and assuming it follows the recommendations- will place a heavy emphasis on the value of use cases both as a means of gaining consensus and in prioritising the work of the agencies involved. To achieve the desired objectives, it is essential that a clear and consistent use of this technique is deployed. The first CWA workshop indicates that the agreement on what a use-case is and how it should be used for the specified purposes is key to the whole initiative. It assumes that consensus already exists. If that is the case, then that event dictates the timing of this report’s completion.
[...]
ABANDON
cen:proj:35364
30.98
Project deleted
Jul 6, 2011
