Table of Contents
The Cyberinfrastructure Product Description represents all the key system and user scenarios for the stakeholders. It describes these elements for each release:
The Product Description is used by internal team members as well. The architecture team uses it to communicate system concepts, the development team as a basis for development, and the engineering team uses them for requirements mapping and evaluation, and system validation.
The Product Description contains a set of scenarios, or use cases, that describe intended functionality of the CI in the scope of each Release.
The use cases are written in terms of externally visible behaviors, while including all the most significant functional details of the systemʼs capabilities. They are written broadly and for a technical cyberinformatics audience, to provide high level organization and content, rather than referencing specific users, user groups, activities, and sites.
A page linking and summarizing all the use cases may be found at Product Description Use Cases.
A table of use cases is presented for each of the releases shown below. The Use Cases for a release are refined throughout the Inception and Elaboration phases.
The acceptance scenarios present end-to-end, domain-centric descriptions of observatory operations. They are written broadly and for the OOI community, to provide a means to describe system operations to stakeholders in OOI.
A page linking and summarizing all the acceptance scenarios may be found at Release 2 Acceptance Scenarios.
A table of acceptance scenarios is presented for each of the releases shown below. The Acceptance Scenarios for a release are refined throughout the Inception and Elaboration phases.
Information describing how these documents have been built and maintained, and techniques for consolidating information from them, may be found at
Skip to end of metadata Go to start of metadata