Content Management/Supplemental Specifications: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Functionality ==
== Functionality ==


* File Parser <font color="red">(7)</font> - Accept content and sort appropriately into database.
* File Parser <font color="red">(6)</font> - Accept content and sort appropriately into database.



http://wiki.laptop.org/index.php?title=Content_Management/Supplemental_Specifications&action=edit
Edit
== Reliability ==
== Reliability ==


Line 11: Line 12:
== Performance ==
== Performance ==


* Quick Load Times 3 Seconds on a Broadband connection (for text and small images) <font color="red">(6)</font>
* Quick Load Times 3 Seconds on a Broadband connection (for text and small images) <font color="red">(5)</font>
* Optimized for high demand <font color="red">(5)</font>





Revision as of 20:51, 12 October 2007

Functionality

  • File Parser (6) - Accept content and sort appropriately into database.

http://wiki.laptop.org/index.php?title=Content_Management/Supplemental_Specifications&action=edit Edit

Reliability

  • Accurate search results (4) - Brings up all results that contain search terms, ordered by relevance whenever possible.


Performance

  • Quick Load Times 3 Seconds on a Broadband connection (for text and small images) (5)


Supportability

  • Should be localizable (3) - Localized language templates can be submitted to support multiple languages.
  • Install by copying files and running a script (8)


Implementation Requirements

  • PostgreSQL Database (2) - Developed with version 8.2.5. Anything newer should be fine.
  • Up to date Python Interpreter (1) - Developed with version 2.5.1. Anything newer should be fine.

*Numbers in red represent priority


Rationale

Ranking of supplemental specifications was done with the user and development in mind. If the system is not developed the user has no product so the Implementation Requirements were given highest priority. The localization and performance aspects were given next highest priority since they are the interface between our product and the client. The parsing and installation script were given lowest priorities because they only make it easier on the backend.