9ticks:Software Requirements
From BiCEP
| Line 61: | Line 61: | ||
|- | |- | ||
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft | | REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft | ||
| + | |- | ||
| + | | REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft | ||
|} | |} | ||
| Line 134: | Line 136: | ||
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft | | REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft | ||
|- | |- | ||
| - | | | + | | REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft |
|- | |- | ||
| - | | | + | | REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft |
|- | |- | ||
| - | | | + | | REQ_0504 || The solution shall handle stress peaks. || 1000 Streams, 1000 Events/sec, 1000 Queries || 1 || Draft |
|} | |} | ||
| Line 152: | Line 154: | ||
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft | | REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft | ||
|- | |- | ||
| - | | | + | | REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft |
| + | |- | ||
| + | | REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft | ||
| + | |- | ||
| + | | REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft | ||
| + | |- | ||
| + | | REQ_0606 || The solution shall handle stress peaks. || 1000 Streams, 1000 Events/sec, 1000 Queries || 1 || Draft | ||
| + | |- | ||
| + | | REQ_0607 || The solution shall provide low response times. || || 1 || Draft | ||
| + | |} | ||
| + | |||
| + | |||
| + | === Assorted === | ||
| + | |||
| + | {| class="TablePager" border="1" width="100%" | ||
| + | |- | ||
| + | ! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status | ||
| + | |- | ||
| + | | REQ_0701 || The communication between the user and the system must be optimize in order of each client type. || Push-based vs pull-based. || 1 || Draft | ||
|- | |- | ||
| - | | | + | | REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft |
|- | |- | ||
| - | | | + | | REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft |
|- | |- | ||
| - | | | + | | REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft |
|} | |} | ||
