http://bicep.dei.uc.pt/index.php?feed=atom&target=Rafael&title=Special%3AContributions
BiCEP - User contributions [en]
2026-09-05T04:19:53Z
From BiCEP
MediaWiki 1.15.2
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-09T14:17:41Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || 1000 Streams, 1000 Events/sec, 1000 Queries || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || 1000 Streams, 1000 Events/sec, 1000 Queries || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:24:58Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:24:28Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="20%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:24:16Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"<br />
|-<br />
! Code !! width="60%" | Requirement !! width="20%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:24:03Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"=== Generic ===<br />
|-<br />
! Code !! width="60%" | Requirement !! width="20%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:23:52Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"=== Generic ===<br />
|-<br />
! Code !! width="60%" | Requirement !! width="30%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:23:00Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* '''Web Server'''<br />
* '''Web Service Provider''' &mdash; provides third-party applications with a way to access this system (as well our mobile device application)<br />
<br />
=== Business Tier ===<br />
<br />
* '''Scheduler''' &mdash; orchestrates all the business process<br />
* '''Query Engine''' &mdash; allows the user to perform queries and apply filters to historic information<br />
* '''CEP Engine''' &mdash; allows the user to define alert rules<br />
* '''Crawler''' &mdash; polls each source for update in a timely manner<br />
** '''Collector''' &mdash; concurrent/distributed polling mechanism<br />
** '''Adapter API''' &mdash; provides the interface shared by all source adapters<br />
<br />
=== Data Tier ===<br />
<br />
* '''Master / Scheduler''' &mdash; schedules, replicates and routes requests through data nodes<br />
* '''Lock Service''' &mdash; low level locking mechanism<br />
* '''Data Nodes''' &mdash; represents each place were data is stored<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:20:32Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* '''Web Server'''<br />
* '''Web Service Provider''' &mdash; provides third-party applications with a way to access our system (as well our mobile device application)<br />
<br />
=== Business Tier ===<br />
<br />
* '''Scheduler''' &mdash; orchestrates all the system's components<br />
* '''Query Engine''' &mdash; allows the user for perform queries and apply filters to historic information<br />
* '''CEP Engine''' &mdash; allows the user to define alert rules<br />
* '''Crawler''' &mdash; polls each source for update in a timely manner<br />
** '''Collector''' &mdash; concurrent/distributed polling mechanism<br />
** '''Adapter API''' &mdash; provides the interface shared by all source adapters<br />
<br />
=== Data Tier ===<br />
<br />
* '''Master / Scheduler''' &mdash; schedules, replicates and routes requests through data nodes<br />
* '''Lock Service''' &mdash; low level locking mechanism<br />
* '''Data Nodes''' &mdash; represents each place were data is stored<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:18:24Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|right|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* '''Web Server'''<br />
* '''Web Service Provider''' &mdash; provides third-party applications with a way to access our system (as well our mobile device application)<br />
<br />
=== Business Tier ===<br />
<br />
* '''Scheduler''' &mdash; orchestrates all the system's components<br />
* '''Query Engine''' &mdash; allows the user for perform queries and apply filters to historic information<br />
* '''CEP Engine''' &mdash; allows the user to define alert rules<br />
* '''Crawler''' &mdash; polls each source for update in a timely manner<br />
** '''Collector''' &mdash; concurrent/distributed polling mechanism<br />
** '''Adapter API''' &mdash; provides the interface shared by all source adapters<br />
<br />
=== Data Tier ===<br />
<br />
* '''Master / Scheduler''' &mdash; schedules, replicates and routes requests through data nodes<br />
* '''Lock Service''' &mdash; low level locking mechanism<br />
* '''Data Nodes''' &mdash; represents each place were data is stored<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|right|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:17:40Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|frame|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* '''Web Server'''<br />
* '''Web Service Provider''' &mdash; provides third-party applications with a way to access our system (as well our mobile device application)<br />
<br />
=== Business Tier ===<br />
<br />
* '''Scheduler''' &mdash; orchestrates all the system's components<br />
* '''Query Engine''' &mdash; allows the user for perform queries and apply filters to historic information<br />
* '''CEP Engine''' &mdash; allows the user to define alert rules<br />
* '''Crawler''' &mdash; polls each source for update in a timely manner<br />
** '''Collector''' &mdash; concurrent/distributed polling mechanism<br />
** '''Adapter API''' &mdash; provides the interface shared by all source adapters<br />
<br />
=== Data Tier ===<br />
<br />
* '''Master / Scheduler''' &mdash; schedules, replicates and routes requests through data nodes<br />
* '''Lock Service''' &mdash; low level locking mechanism<br />
* '''Data Nodes''' &mdash; represents each place were data is stored<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|frame|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:07:11Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|frame|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* Web Server<br />
* Web Service Provider<br />
<br />
=== Business Tier ===<br />
<br />
* Scheduler<br />
* Query Engine<br />
* CEP Engine<br />
* Crawler<br />
** Collector<br />
** Adapter API<br />
<br />
=== Data Tier ===<br />
<br />
* Master / Scheduler<br />
* Lock Service<br />
* Data Nodes<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|frame|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:05:17Z
<p>Rafael: </p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|System Architecture]]<br />
<br />
=== Presentation Tier ===<br />
<br />
* Web Server<br />
* Web Service Provider<br />
<br />
=== Business Tier ===<br />
<br />
* Scheduler<br />
* Query Engine<br />
* CEP Engine<br />
* Crawler<br />
** Collector<br />
** Adapter API<br />
<br />
=== Data Tier ===<br />
<br />
* Master / Scheduler<br />
* Lock Service<br />
* Data Nodes<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Architecture
9ticks:Software Architecture
2008-10-08T23:02:36Z
<p>Rafael: /* Data Source */</p>
<hr />
<div>== System Architecture ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|System Architecture]]<br />
<br />
<br />
== Data Source ==<br />
<br />
[[Image:9ticks_DataSource_v01.png|Data Source]]<br />
<br />
<br />
This diagram represents the base structure of the 9ticks data organization. It is "relational database"-oriented and '''must not''' be seen as the final architecture. It will be surely needed a '''less normalized''' and '''distributed''' approach.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T23:01:40Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"=== Generic ===<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T23:00:38Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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<br />
|-<br />
| REQ_0702 || The system shall provide a web service for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0703 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0704 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T23:00:06Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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<br />
|-<br />
| REQ_0701 || The system shall provide a web service endpoint for third-party applications. || || 1 || Draft<br />
|-<br />
| REQ_0701 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0701 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:56:46Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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<br />
|-<br />
| REQ_0701 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0701 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:56:23Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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 || <br />
|-<br />
| REQ_0701 || The system shall be internationalized. || i18n || 5 || Draft<br />
|-<br />
| REQ_0701 || The system shall allow OpenID authentication. || || 5 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:56:01Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0102 || User shall apply queries or filters to data sources. The result shall be considered as another source, widely available. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|-<br />
| REQ_0607 || The solution shall provide low response times. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Assorted ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| 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 || <br />
|-<br />
| REQ_0701 || The system shall be internationalized. || i18n || 1 || Draft<br />
|-<br />
| REQ_0701 || The system shall allow OpenID authentication. || || 1 || Draft<br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:47:14Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0504 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0603 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0604 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0605 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0606 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:46:15Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be able to be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be able to be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be able to be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be able to be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be able to be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be able to be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be able to be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar/equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be able to be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be able to be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be able to be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be able to be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be able to be selected. || || 1 || Draft <br />
|-<br />
| REQ_0310 || Each custom source shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user's alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be alerted in a short time window. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0501 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and scalability. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and scalability. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:36:58Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0501 || An efficient scheduling policy shall be in place. || || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:33:33Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define when and how be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:30:42Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:30:11Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0011 || User shall perform all operations in real-time. || Minimum delays. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:27:49Z
<p>Rafael: /* Sources */</p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. Details are TBD. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:24:58Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall tag sources. || || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0008 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0009 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0010 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || There shall exist a data source API. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T22:14:54Z
<p>Rafael: </p>
<hr />
<div>{| class="TablePager sortable" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:14:29Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
* To see an '''unsorted list of requirement''' folow '''[[9ticks:Unsorted_List_of_Requirement|this]]''' link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Unsorted_List_of_Requirement
9ticks:Unsorted List of Requirement
2008-10-08T22:13:28Z
<p>Rafael: New page: {| class="TablePager" border="1" width="100%" |- ! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status |- | REQ_0001 || User shall access the system through a ...</p>
<hr />
<div>{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|-<br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:12:18Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
To see an unsorted list of requirement folow [[9ticks:Unsorted_List_of_Requirement|this]] link.<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:11:43Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
To see an unsorted list of requirement folow [[9ticks:Unsorted_List_of_Requirement|this]] link.<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:10:01Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0001 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0003 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0004 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0005 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0006 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0007 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0008 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0009 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|-<br />
| REQ_0102 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0102 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0201 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|-<br />
| REQ_0202 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0203 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0204 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0205 || A predefined Traffic source shall be subscribed. || Route must be provided. || 1 || Draft <br />
|- <br />
| REQ_0206 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 1 || Draft <br />
|- <br />
| REQ_0207 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 1 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0302 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0303 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0304 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0305 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0306 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0307 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0308 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0309 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0401 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0402 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0501 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0502 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0503 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0601 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0602 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0602 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T22:08:06Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0002 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0001 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0001 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0002 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|-<br />
| REQ_0002 || Queries, visualizations and filters shall be stored for future re-utilization by any user. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0001 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0002 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0002 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0105 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0107 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Each user alert rules shall be processed on-the-fly. || Use a CEP engine, Esper maybe. || 1 || Draft <br />
|-<br />
| REQ_0301 || User shall be notified of an alert as soon as possible. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many sources, many events and many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || An aggregation engine shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0301 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0301 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0301 || A locking service must be in place. || Low level concurrency prevention. || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T21:57:51Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0002 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0001 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0001 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0002 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0001 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0002 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0002 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0105 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0107 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Event Processing ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || asd || asd || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || An aggregation mechanism shall be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0301 || A fault tolerant mechanism must be in place. || Replicate data. || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T21:55:01Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0002 || User shall access the system through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall access the system through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0001 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0001 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0002 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0001 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0002 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0002 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0105 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0107 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Each source must be polled for updates every "refresh rate"-times. || Based on each source's refresh rate. || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft <br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || An aggregation mechanism must be in place. || Summarize older data. || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall have good performance and be scalable. || || 1 || Draft<br />
|-<br />
| REQ_0301 || The solution shall handle stress peaks. || Many Sources, Many Events and Many users | || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T21:42:44Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Generic ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0002 || The system shall be accessed through a web browser. || || 1 || Draft <br />
|-<br />
| REQ_0002 || The system shall be accessed through a mobile device. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall subscribe sources. || || 1 || Draft<br />
|-<br />
| REQ_0001 || User shall visualize each source from several perspectives. || e.g.: textual, bar chart, pie chart, ... || 1 || Draft <br />
|-<br />
| REQ_0001 || User shall visualize sources in comparison mode. || e.g.: overlap two stock quotes || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall define how to be alerted of events. || || 1 || Draft <br />
|-<br />
| REQ_0002 || User shall visualize the history of any source. || || 1 || Draft<br />
|-<br />
| REQ_0002 || User shall perform queries over the gathered data. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0001 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0002 || Data source API specifications TBD || || 1 || Draft <br />
|- <br />
| REQ_0002 || Each source shall have associated tags. || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0105 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0107 || A predefined eBay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
<br />
<br />
<br />
<br />
=== Crawler ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Req || Desc || 1 || Draft <br />
|}<br />
<br />
<br />
=== Data Store ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Req || Desc || 1 || Draft <br />
|}<br />
<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed, yet.</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T21:23:49Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Data Source API ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0001 || A data source API should be built. || Every source, predefined or custom, must use this API. || 1 || Draft <br />
|- <br />
| REQ_0002 || Data source API specifications TBD || || 1 || Draft <br />
|}<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0101 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0105 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0107 || A predefined Ebay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
=== Something ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Req || Desc || 1 || Draft <br />
|}<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed.</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Architecture
Talk:9ticks:Software Architecture
2008-10-08T21:14:36Z
<p>Rafael: New page: Please place the comment followed by 4 tildes. For instance: Discussion open! <nowiki>~~~~</nowiki> will produce: Discussion open! Rafael Marmelo 21:10, 8 October 2008...</p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks
Talk:9ticks
2008-10-08T21:14:27Z
<p>Rafael: New page: Please place the comment followed by 4 tildes. For instance: Discussion open! <nowiki>~~~~</nowiki> will produce: Discussion open! Rafael Marmelo 21:10, 8 October 2008...</p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:14:08Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:13:58Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance,<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:13:27Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:13:17Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!<br />
<br />
Yeah!\\[[User:Rafael|Rafael Marmelo]] 21:13, 8 October 2008 (GMT)</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:11:24Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)<br />
<br />
== Discussion ==<br />
<br />
Your comments here!</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:10:48Z
<p>Rafael: </p>
<hr />
<div>Your comment here!<br />
<br />
----<br />
<br />
Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open! [[User:Rafael|Rafael Marmelo]] 21:10, 8 October 2008 (GMT)</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:10:16Z
<p>Rafael: </p>
<hr />
<div>Please place the comment followed by 4 tildes. For instance:<br />
<br />
Discussion open! <nowiki>~~~~</nowiki><br />
<br />
will produce:<br />
<br />
Discussion open!<br />
[[User:Rafael|Rafael Marmelo]] 21:05, 8 October 2008 (GMT)</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:06:31Z
<p>Rafael: asd</p>
<hr />
<div>Discussion open!<br />
[[User:Rafael|Rafael Marmelo]] 21:05, 8 October 2008 (GMT)<br />
<br />
== asd ==<br />
<br />
asdsd</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:05:39Z
<p>Rafael: </p>
<hr />
<div>Discussion open!<br />
[[User:Rafael|Rafael Marmelo]] 21:05, 8 October 2008 (GMT)</div>
Rafael
http://bicep.dei.uc.pt/index.php/Talk:9ticks:Software_Requirements
Talk:9ticks:Software Requirements
2008-10-08T21:05:12Z
<p>Rafael: New page: Discussion open! ~~~~</p>
<hr />
<div>Discussion open! [[User:Rafael|Rafael Marmelo]] 21:05, 8 October 2008 (GMT)</div>
Rafael
http://bicep.dei.uc.pt/index.php/9ticks:Software_Requirements
9ticks:Software Requirements
2008-10-08T21:01:07Z
<p>Rafael: </p>
<hr />
<div>== Requirements Overview ==<br />
<br />
* Retrieve, interpret and store data source events<br />
* Web and mobile-based frontends<br />
* Predefined and custom data sources<br />
* Visualizations<br />
* Queries<br />
* Alerts<br />
* History<br />
* Tags<br />
<br />
<br />
== List of Requirements ==<br />
<br />
[[Image:9ticks_SystemArchitecture_v01.png|thumb|System Architecture]]<br />
<br />
* The distinction between user, functional and non-functional requirements is ignored<br />
* The requirements are sorted by logical groups<br />
* Each requirement has been assigned with the following properties:<br />
** '''Code''' &mdash; REQ_[0-9]{4}<br />
** '''Requirement'''<br />
** '''Comment'''<br />
** '''Priority''' &mdash; from 1 to 5 (1 as highest)<br />
** '''Status''' &mdash; Draft, Approved, In Progress, Testing, Finished<br />
<br />
<br />
=== Predefined Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! align="center" | Status<br />
|- <br />
| REQ_0100 || A predefined Stock source shall be subscribed. || Market and quote must be provided. || 1 || Draft <br />
|- <br />
| REQ_0101 || A predefined Weather source shall be subscribed. || Location must be provided (defaulting to the IP physical location). || 1 || Draft <br />
|- <br />
| REQ_0102 || A predefined Sports source shall be subscribed. || A specific match (source is only that match) or generic team (all team matches) must be provided. || 1 || Draft <br />
|- <br />
| REQ_0103 || A predefined Flight source shall be subscribed. || Flight number and flight date must be provided. || 1 || Draft <br />
|- <br />
| REQ_0104 || A predefined Traffic source shall be subscribed. || Route must be provided. || 2 || Draft <br />
|- <br />
| REQ_0105 || A predefined RSS Feed source shall be subscribed. || RSS URL must be provided. || 2 || Draft <br />
|- <br />
| REQ_0106 || A predefined Ebay item source shall be subscribed. || Item ID must be provided. || 2 || Draft<br />
|}<br />
<br />
<br />
=== Custom Sources ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0201 || User shall use a browser extension to select some peaces of information he wants to monitor. || || 1 || Draft <br />
|- <br />
| REQ_0202 || The information selected with the browser extension shall be automatically typed. || May be overridden by the user. || 1 || Draft <br />
|- <br />
| REQ_0203 || System shall recognize basic data types. || e.g.: integer, decimal, percentage, time, date, string, ... || 1 || Draft <br />
|- <br />
| REQ_0204 || System shall connect similar / equivalent data types. || e.g.: Celsius, Fahrenheit, Kelvin, ... ; Meter, Mile, Yard, Foot, ... ; Euro, U.S. Dollar, Pound, Swiss franc, ... || 1 || Draft <br />
|- <br />
| REQ_0205 || Any single HTML item shall be selected. || e.g.: a table cell or an anchor. || 1 || Draft <br />
|- <br />
| REQ_0206 || Every repetitive HTML item shall be selected. || e.g.: all main titles || 1 || Draft <br />
|- <br />
| REQ_0207 || An HTML table shall be selected. || || 1 || Draft <br />
|- <br />
| REQ_0208 || Parts of an HTML table shall be selected. || e.g.: a row whose cell at nth column has the value X || 1 || Draft <br />
|- <br />
| REQ_0209 || All items inside a bounded polygon shall be selected. || || 1 || Draft <br />
|}<br />
<br />
=== Something ===<br />
<br />
{| class="TablePager" border="1" width="100%"<br />
|-<br />
! Code !! width="50%" | Requirement !! width="40%" | Comment !! Priority !! Status<br />
|-<br />
| REQ_0301 || Req || Desc || 1 || Draft <br />
|}<br />
<br />
== Requirement Traceability Matrix ==<br />
<br />
Not needed.</div>
Rafael