The public research computing environment should be open and extensible: a "community infrastructure." In order to use and participate in this environment, community members (researchers, application developers, service providers, campus IT administrators) must be able to access details about the system’s design, implementation status, and the driving user needs.
Note: In these use cases, the terms “service” and “service provider” are used broadly. Any of the following would be examples of “services” if they are shared with researchers: a computer system, a website or web-based application, a computer system with a specific software application installed for use, a high-capacity data storage device, a long-term data archiving service, a virtual machine (IaaS) host, a software repository, or an identity provider.
|Use Case ID||Title||Use Case Description|
|CI-01||Access system information|
|CI-02||Manually publish system information|
|CI-03||Automate changes to system information|
|CI-04||Publish current and desired system capabilities, their availability, and their implementation status|
|CI-05||Discover current and desired system capabilities, their availability, and their implementation status|
|CI-06||Rate the priority or quality of a community need or contribution|
|CI-07||Discuss a community activity|
|CI-08||Conduct an engineering review of a community contribution|
|CI-09||Discover and inspect system capabilities currently under development|
|CI-10||Discover and review engineering documents for a specific capability or component|
|CI-11||Manage the source code, documentation, and installable packages for a capability|