Version 3 (modified by jbourne, 16 years ago) |
---|
TracNav menu
-
RDS/WIP project
- RDS/WIP Introduction
-
RDS/WIP World View...
- RDS/WIP Sample Queries
- RDS/WIP Staging Diagrams
- RDS/WIP 1.0 Plan
- RDS/WIP 1.0 Testing
- RDS/WIP 1.0 Process
- RDS/WIP 1.0 Inventory
- RDS/WIP 2.0 Plan
- RDS/WIP ID Generator
- RDS/WIP Domain Proposal
- RDS/WIP Requirements Table
- RDS/WIP Use Case: Discrete Editing
- RDS/WIP Use Case: CSV Upload
- RDS/WIP 1.0 General Use Cases
- RDS/WIP 2.0 General Use Cases
- RDS/WIP ISO 15926 Template Definitions
- RDS/WIP OWL/RDF Definition
- RDS/WIP OWL/RDF Project Plan
- RDS/WIP Forums
-
External
- RDS/WIP Use Case: Bulk Upload
Requirements Table
A table listing some coarse-grained requirements of the RDS/WIP systems, both 1.0 and 2.0. Human procedures and the organization to support them are more important than the system itself, but only only requirements relating directly to the technical execution are shown here.
Key
Numbers are used for urgency and letters for importance. 1 is most urgent - its for requirements that need to be delivered as soon as possible. A is most important - its for requirements that meet external obligations.
The order in the table represents the likely sequence of implementation - because of dependencies (which aren't shown), the order may not match the urgency/importance.
Table
Urgency | Importance | Release | Requirement |
1 | B | 1.0 | Reasonable performance for SPARQL endpoints |
2 | A | 1.0 | Map rdlfacade.org domains to endpoints |
4 | B | 1.0 | Improve standard of OWL/RDF representation |
3 | C | 1.0 | Target browser-based viewing of content to non-modellers |
4 | B | 1.0 | Provide path for uploads from brutus |
5 | A | 2.0 | Bulk upload of external contributions |
5 | B | 2.0 | Administration tools for external contributions |
5 | A | 2.0 | Discrete Editing Support? |