Developing Use Cases
An important aspect of the business plan is the assessment of the services to be provided by the DIH, as this will contribute to its viability (needs and contribution). A key part of this is to have a formalized process to capture industry requirements and to provide a statement of the services that may be provided by the DIH to address those requirements.
Use cases are a way to support this process, by providing a template to formalize industrial challenges and objectives, proposed services (including deliverables, timescales and cost), expected benefits and impact. In this way, use cases are a communication tool to: 1) facilitate the dialogue between the DIH and an organization during initial engagement, 2) support the definition of realistic and relevant projects and 3) negotiate scope, timescales and project price.
Use cases should be captured with significant input from the customer and should be developed on the basis of an understanding of the customer requirements and the value proposition offered by the DIH. As the use cases are seen as mechanisms to ensure concrete experience with the services of the DIH, the following elements are to be addressed:
- A description of the service that is to be provided by the DIH and its direct link to the business case of the customer.
- General description of the use case and/or description of your use case in a non-technical, user-focused way.
- Short description of the technical objectives for the use case.
- The expected benefits the customer hopes to gain from the service.
- A list the solutions and capabilities provided by the DIH.
- A more detailed description of the possible project scope and price.
For more information of the development of use cases and a template, click here.