Requirements prioritization and project scope: Difference between revisions
Jump to navigation
Jump to search
(New page: The requirements fed into the feature list, and the prioritization of those features will appear on this page. <pre>Coming soon!</pre>) |
No edit summary |
||
| Line 1: | Line 1: | ||
The [[Requirements elicitation|requirements]] fed into the [[Features|feature list]], and the prioritization of those features will appear on this page. | The [[Requirements elicitation|requirements]] fed into the [[Features|feature list]], and the prioritization of those features will appear on this page. | ||
==Feature Priorities== | |||
#Account Type | |||
#Address Book | |||
#Message Composition | |||
#Message Filters | |||
#Offline Mode | |||
==Task Priorities== | |||
#Notional architecture of the entire extension | |||
#Identification of architectural risks | |||
#Design and execution of experiments to reduce architectural risks | |||
#Architectural refinement and modularization of the extension | |||
#Parallel work on the modules, focusing on those that address the account type feature | |||
#First release | |||
Revision as of 14:08, 2 May 2007
The requirements fed into the feature list, and the prioritization of those features will appear on this page.
Feature Priorities
- Account Type
- Address Book
- Message Composition
- Message Filters
- Offline Mode
Task Priorities
- Notional architecture of the entire extension
- Identification of architectural risks
- Design and execution of experiments to reduce architectural risks
- Architectural refinement and modularization of the extension
- Parallel work on the modules, focusing on those that address the account type feature
- First release