• Andy Turner's NCeSS e-Infrastructure MoSeS Use Case Web Page

  • [An image of Andy Turner]

  • Introduction

    • This is for developing an NCeSS e-Infrastructure Project Use Case for MoSeS.
    • Contents:
      • Use Case
      • References
      • Validation and Metadata

  • Use Case

    • Scenarios
      • Scenario 1
      • Scenario 2
      • Scenario 3
    • Scenario 1
      • Description
        • A planner wants to examine the potential consequences of a hospital closure on the city and generate a report which links to full details of the work and summarises the findings. Some of the important issues are changes in emergency service cover, general changes in traffic patterns, changes in the accessibility to health services based on the reallocation of services to other hospitals, clinics and surgeries.
      • Actions
        • Login to the MoSeS portal.
        • Start a new project.
        • Identify relevant data.
        • Identify relevant models.
        • Develop an outline of work.
        • Choose appropriate report template.
          • If appropriate report template does not exist, use default which may be customised to provide a new template.
        • Run some models.
        • Examine results.
        • Generate report.
    • Scenario 2
      • Description
        • A Health and Social Care Planner wants to assess/examine the spatial variation in current and future demand for health and social care services in their area and compare this with current and planned provision.
    • Scenario 3
      • Description
        • A Housing Corporation Planner wants to assess/examine the spatial variation in current and future demand for affordable housing in their area and compare this with current and planned provision.
    • Scenario 4
      • Description
        • A Local Education Authority Planner wants to assess/examine the spatial variation in current and future demand for primary and secondary school places in their area and compare this with current and planned provision.

  • References

    • What is a USE CASE?
      • Taken from: UML for Use Cases Workshop 2006-01-05 to 2006-01-06 : Richard Hopkins: A Review of Scenarios and Use Cases
        • A collection of Scenarios, expressing all possible behaviours as actor tries to achieve goal
        • Covers all success and failure variants
        • May combine similar Scenarios into one Use Case
        • Can have complex, nested, structure
        • Formal structure
          • Constitutes a contract for behaviour
          • But may start as an incomplete, single-scenario, use case
        • Scenarios
          • less formal structure
          • Easier to gather from non-technical groups
          • Useful for discussion, but incomplete – not a contract
      • Taken from: JISC Information Environment Portal Activity: supporting the Needs of e-Research. - Scenarios, Use Cases and Reference Models - Rob Allan, Rob Crouchley, Caroline Ingram. 2006-11-21
        • In software engineering, a use case is a technique for capturing the potential requirements of a new system or software change. Each use case provides one or more scenarios that convey how the system should interact with the end user or another system to achieve a specific business goal. Use cases typically avoid technical jargon, preferring instead the language of the end user or domain (subject) expert.
        • Use cases which have informed the development of the Information Environment are documented [20]. They include the basic cases for: enter; survey and discover; detail; use record; request, authorise, access; use resource.
        • [20] A. Powell and L. Lyon JISC Information Environment Architecture http://www.ukoln.ac.uk/distributed-systems/jisc-ie/arch/functional-model/

  • Validation and Metadata

    • [Validate XHTML 1.0] [Validate CSS]
    • Version 0.1.0 of this file last modified 2007-05-04.
    • Page hosted on the School of Geography webserver at the University of Leeds.
    • Copyright: Andy Turner, University of Leeds