...
Last Revised: March 2018
Status: Final Draft Approved by:
Overview
The Deposit Functional Requirements Group’s charge was to provide system functional requirements related to different methods of deposit/ingest into the repository, such as end-user deposit, staff deposit, mediated submission workflows, and batch ingest:
...
- Stakeholder representation and inputs – As documented in the approved charter, the group included members representing the interest of various operational units needing to provide requirements. The membership of this group was determined and approved by steering in consultation with library directors at the start of the Discovery Phase.
- Current state discussion and reviews – As an introductory measure, the group performed a review of current state ingest processes in order to provide background on active services and workflows across the institution. The process identified alignments and with the goal of bringing together disparate services. (Process Maps Review)
- LITS Business Analyst workshops – The group participated in two workshops facilitated by a LITS Business Analyst in order to begin requirements drafting. The initial workshop discussed a Business Canvas Model framing template in order to explicate activities and services in the current vs. future state. In a second workshop, the group reviewed guidelines for writing effective user stories, and began drafting stories.
- User Profiles – The group collaborated on user profiles to help frame the user stories and abstract the functional elements of the roles discussed in the current state review.
- Requirements drafting – The group went through a period of user story drafting, in coordination with their units.
- Analysis and alignment – The group went through several rounds of iterations as user stories were assessed and clarified and overlaps in requirements were identified. In some cases, similar stories were merged after consulting with team members, and in other cases closely related stories were left distinct if the user need was different. The revised stories were then mapped to the Deposit User Profiles, and team members did another collective review to indicate broader applicability of stories/features to their respective areas. (Inventory of Normalized User Stories)
...