Requirements prioritization and project scope: Difference between revisions

From Thunderforce
Jump to navigation Jump to search
No edit summary
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==
==Requirements==
The detailed requirements are listed on another page. The high-level requirements are listed below:
*[[Features#R1: Account Type|R1: Account Type]]
*[[Features#R2: Address Book|R2: Address Book]]
*[[Features#R3: Message Composition|R3: Message Composition]]
*[[Features#R4: Message Filters|R4: Message Filters]]
*[[Features#R5: Offline Mode|R5: Offline Mode]]
 
==Priorities==
Note that some features have dependencies upon each other. This is a general list, and the actual module priorities will likely include functionality from all modules as the top priorities. The initial focus will be on associating both incoming and outgoing email messages with Salesforce.com records, but the architecture will factor in the [[Features|present long-range set of features]].
Note that some features have dependencies upon each other. This is a general list, and the actual module priorities will likely include functionality from all modules as the top priorities. The initial focus will be on associating both incoming and outgoing email messages with Salesforce.com records, but the architecture will factor in the [[Features|present long-range set of features]].
*R2: Address Book
*R2: Address Book

Revision as of 13:52, 9 May 2007

The requirements fed into the feature list, and the prioritization of those features will appear on this page.

Requirements

The detailed requirements are listed on another page. The high-level requirements are listed below:

Priorities

Note that some features have dependencies upon each other. This is a general list, and the actual module priorities will likely include functionality from all modules as the top priorities. The initial focus will be on associating both incoming and outgoing email messages with Salesforce.com records, but the architecture will factor in the present long-range set of features.

  • R2: Address Book
  • R4: Message Filters
  • R1: Account Type
  • R3: Message Composition
  • R5: Offline Mode

Task Priorities

  1. Notional architecture of the entire extension
  2. Identification of architectural risks
  3. Design and execution of experiments to reduce architectural risks
  4. Architectural refinement and modularization of the extension
  5. Parallel work on the modules, focusing on those that address the account type feature
  6. First release

Context Diagram

Coming soon..

  • Mozilla Thunderbird
  • Thunderforce
  • Salesforce.com
  • SQLite