Content Management/Supplemental Specifications: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
== Supportability == |
== Supportability == |
||
* Should be localizable <font color="red">(3)</font> |
* Should be localizable <font color="red">(3)</font> - Localized language templates can be submitted to support multiple languages. |
||
* Install by copying files and running a script <font color="red">(8)</font> |
* Install by copying files and running a script <font color="red">(8)</font> |
||
Revision as of 20:49, 12 October 2007
Functionality
- File Parser (7) - Accept content and sort appropriately into database.
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) (6)
- Optimized for high demand (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.