...
In this model a user represents someone who (1) will be affected in some way by the SKOPE system, and (2) we choose to take into account when designing, implementing, or deploying the system.
Researcher | Scholar in the social and natural sciences who wants browser-based access to the best-available reconstructions of key environmental variables for a given location and temporal interval. |
Tinkerer | Researcher with a more focused interest in a specific reconstruction model, and who wishes to adjust parameters and rerun the models. |
Modeler | Researcher who seeks to build and offer broad access to new or modified models and/or retrodicted environmental data through SKOPE. |
Data provider | Representative of an organization that has granted to SKOPE users access to data via the SKOPE system. |
Devop | Person responsible for developing, testing, deploying, configuring, administering or troubleshooting the SKOPE system. |
...
System Functions
These are the essential capabilities of the system including things that the system does and that users do with the system.
...
Sometimes referred to as non-functional requirements, system attributes are those desirable, positive characteristics of the system that distinguish it from alternative approaches to performing the same functions. These attributes are the qualities that make it beneficial to perform the system functions via the SKOPE system rather over using ad hoc scripts, running individual programs directly, or managing data manually,
Transparent | |
Responsive | |
Secure | |
Modular | |
Testable |