Use cases describe the work our EdUnify architectures should support or or enable. Use cases can be very general or specific, high-level descriptions or in-depth studies of processes. To be useful, use cases must be prepared by subject matter experts. These subject matter experts are often busy with other work besides the analysis and documentation of their work processes. For this reason, use case preparation is often best achieved with an iterative approach, starting with a high-level story or abstract and the building out a detailed story with in-depth analysis where necessary. In many cases, a high-level story is sufficient to support or validate a technical design. In other cases, more detail is required.
The group should consider a naming (categorization) and numbering convention for its use cases and these can be helpful in identifying use cases to be written, assigning them to analysts, and tracking them. This leads to other aspects of ontology. Specifically, the use cases should refer to a consistent set of actors and information systems. Because we are authoring and managing these in wiki format, we may wish to hyperlink to a consistent set of pages documenting and explaining these actors and applications.
The Task Force is preparing very specific, structured use cases that the EdUnify frameworks will support, and it will identify the specifications and technologies that it will develop or apply as informed by these use cases. The Task Force is preparing use cases in a common format to help identify the constituents served and processes addressed in each use case. There is a template which can be used to start each new use case.