NIH-NICHD-Ecosystem/UseCases

List of formalized interaction requirements for the NICHD ecosystem in standard Unified Modeling language informed by user-centered design best practices.

Library Main Navigation:     Ecosystem Use Case Library Home   |  User Stories   |   Use Cases   |   Efforts   |   Library Help

Use Cases

Each use case represents a specific interaction requirement from the User/Actor perspective, in standard Unified Modeling Language (UML)* language. Multiple use cases detailed in a use case diagram are used to define the scope of an Effort.

*External link, NIH is not responsible for content of external sites

For more information about our Library structure and documentation, visit the Library Help

Questions on library use cases? Contact ecosystem-help@ll.mit.edu

Use Case List

UC#	Use Case Name	Related Efforts	Related User Stories
UC1.1	Add Repository	E1: Data Repository Finder	(enabling functionality)
UC1.2	Publish Repository	E1: Data Repository Finder	(enabling functionality)
UC1.3	Edit Repository	E1: Data Repository Finder	S3: As NICHD staff, I want to be able to update a given field in the Data Repository Finder and track the date and reason for the change, so that I can go back later and review why that decisions was made
UC1.4	View Provenance	E1: Data Repository Finder	S3: As NICHD staff, I want to be able to update a given field in the Data Repository Finder and track the date and reason for the change, so that I can go back later and review why that decisions was made
UC1.5	Identify Repository	E1: Data Repository Finder	S30: As an NICHD researcher, I want to find the best data repositories for the sharing scientific data that I am generating in my project and understand the repository 's submission and sharing practices so I can complete my Data Management and Sharing Plan S31: As an NICHD program officer, I want to verify that researchers are using data repositories appropriate for the scientific data they plan to share and that their DMS Plan is consistent with the repository's expectations and requirements.