{scrollbar:icons=false}

Page info
title title

Introduction

An important part of the requirements gathering process is to engage end users and stakeholders.  In an infrastructure project of this nature, a good way to relay the types of functionality that will be supported is through user stories. This list is not meant to be exhaustive. These stories are representative of the types of functionality that will be directly supported by the infrastructure, as well as the types of tooling that will be enabled by the infrastructure.

Stories

Terminology

Priority

• Must: this story must absolutely be supported by the semantic infrastructure in order to meet the core needs of the community
• Should: this story should be supported by the semantic infrastructure because it represents important functionality without which many user needs will not be met
• Could: this story is not critical to the needs of the community but is "nice to have"

Status

• Draft: the story is still under development by the semantic infrastructure analysts
• Review: the story has completed the analysis process and is under a period of community review and comment
• Confirmed: the story has been reviewed and confirmed by the community

Requirements categories

Summary Level

• Cloud level --> Very high level, can involve multiple user goals - "Operate a Specimen Bank"
• Kite level --> High level, a business process that takes place over several hours, days or weeks involving many steps - "Handle a Specimen Order"

User Goals

• Sea Level --> something the actor is trying to get done - "one person, one sitting"

Subfunctions

• Underwater --> needed to accomplish user goals, typically can be used and reused - "Save as a File"
• Clam --> not usually expanded into a use case - "insert record into database"

{scrollbar:icons=false}