ORCID user stories and use cases
Download as PPTX, PDF2 likes597 views
This document discusses generating user stories and use cases for ORCID integration. It provides examples of a user story and use case template. The schedule involves brainstorming user stories in groups, filtering and combining them, then voting on the most important ones to develop into use cases. The use cases will then be taken to a hack day event.
ORCID user stories and use cases
- 2. User story As a ………. I want ………. So that ……….
- 3. User story As a Research administrator I want To have an institutional ORCID dashboard So that I can see how many researchers in my institution have registered for an ORCID
- 4. Use Case • Gives information about how a feature or function would actually work including • Why the use case is important • Who is involved • Which systems or applications are involved • What steps the user goes through to use the function
- 5. Today we are going to… • Generate lots of user stories for ORCID integration/use - good, bad, indifferent • Filter and deduplicate the user stories • Vote to find the most important user stories • Write use cases based on the most important user stories • Take those use cases to the hack day on 18th October
- 6. Schedule • Brainstorm - individually write down as many user stories as you can think of (10 minutes) • Grouping exercise - in small groups pool your user stories, deduplicate and re-write as a single list (20 minutes) • …Repeat (20 minutes) • Finalise user stories all together (30 minutes) • Vote on the stories (15 minutes) • Use case development in groups (1 hour +)
- 7. User story As a Research administrator I want To have an institutional ORCID dashboard So that I can see how many researchers in my institution have registered for an ORCID
- 8. Use Case • User Story starting point • Summary description • Rationale: why is this important • Users/actors: list of people involved in use case • Systems/applications: list of systems or applications involved in the use case
- 9. • Pre-conditions: what things must have already happened for the use case to start • Standard flow: what happens in what order - what does the user do, what happens as a result • Variations to standard flow: any variations to the standard flow that could occur • Post-conditions: what the system will have done by the end of the steps described in the standard flow Use Case
- 10. http://bit.ly/2dzTVdB Use case example and template is available at: