Overview
This guide is intended to document the process for generating requirements for the Common Metadata Repository (CMR).
This document is still in work.
CMR Requirements Hierarchy At Glance
Requirement Level | Example |
|---|---|
| Theme | Metrics |
Component | Search and Discovery |
Epic | Keyword Searching |
User Story | As an Operations Team Member, I want to be able to query dataset search parameters so that I can generate reports |
Tools in Use
The CMR will utilize Jama to record, review, and approve system requirements and JIRA to record and track system issues.
References
- This document references definitions and borrows heavily from Agile 101, available here: http://agile101.wordpress.com/2009/08/10/the-difference-between-agile-themes-epics-and-user-stories/
- Jama resides within the Earthdata ecosystem at the following URL: https://rms.earthdata.nasa.gov/
- JIRA also resides within Earthdata at https://bugs.earthdata.nasa.gov/
- To gain access to either the Jama or JIRA tool, please request CMR Jama Access via support@earthdata.nasa.gov
Assumptions
It is assumed that all requirements will be developed and maintained in the Jama tool. If requirements have previously been maintained in Word or Excel, these requirements shall be imported into Jama.
Vocabulary
Components
The CMR will consist of several sub-system components. Requirements in Jama will be developed for each of these sub-systems and will have a corresponding component within the tool. These components can be created as needed and have a set of Epics and a set of User Stories underneath a component for organizational purposes.
Overview
Content Tools