Content Management/Supplemental Specifications: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Functionality == |
== Functionality == |
||
* File Parser |
* File Parser - Accept content and sort appropriately into database. |
||
== Reliability == |
== Reliability == |
||
* Accurate search results |
* Accurate search results - Brings up all results that contain search terms, ordered by relevance whenever possible. |
||
== Performance == |
== Performance == |
||
* Quick Load Times 3 Seconds on a Broadband connection (for text and small images) |
* Quick Load Times - 3 Seconds on a Broadband connection (for text and small images) |
||
* Optimized for high demand <font color="red">(5)</font> |
|||
== Supportability == |
== Supportability == |
||
* Should be localizable - Localized language templates can be submitted to support multiple languages. |
|||
* Requires Localization <font color="red">(3)</font> |
|||
* Install by copying files and running a script |
* Install by copying files and running a script |
||
== Implementation Requirements == |
== Implementation Requirements == |
||
* PostgreSQL Database |
* PostgreSQL Database - Developed with version 8.2.5. Anything newer should be fine. |
||
* Up to date Python Interpreter |
* Up to date Python Interpreter - Developed with version 2.5.1. Anything newer should be fine. |
||
<nowiki>*</nowiki>Numbers in red represent priority |
|||
== Priority == |
|||
# Up to date Python Interpreter |
|||
# PostgreSQL Database |
|||
# Localization |
|||
# Accurate search results |
|||
# Quick Load Times |
|||
# File Parser |
|||
# Install by copying files and running a script |
|||
Number 1 and 2 are must-have functionalities. The rest will be implemented if there is enough time. |
|||
| Line 32: | Line 42: | ||
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. |
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. |
||
[[Category:Content Management]] |
|||
Latest revision as of 03:30, 16 March 2008
Functionality
- File Parser - Accept content and sort appropriately into database.
Reliability
- Accurate search results - 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)
Supportability
- Should be localizable - Localized language templates can be submitted to support multiple languages.
- Install by copying files and running a script
Implementation Requirements
- PostgreSQL Database - Developed with version 8.2.5. Anything newer should be fine.
- Up to date Python Interpreter - Developed with version 2.5.1. Anything newer should be fine.
Priority
- Up to date Python Interpreter
- PostgreSQL Database
- Localization
- Accurate search results
- Quick Load Times
- File Parser
- Install by copying files and running a script
Number 1 and 2 are must-have functionalities. The rest will be implemented if there is enough time.
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.