Requirements prioritization and project scope: Difference between revisions
No edit summary |
m (Moved the context diagram to the top) |
||
| (3 intermediate revisions by the same user not shown) | |||
| 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. | ||
==Context Diagram== | |||
[[Image:Context Diagram.png]] | |||
The context diagram above depicts the Thunderforce part of the system being built and the components that it interacts with. The user will interact with Mozilla Thunderbird, which will then invoke and receive instructions from Thunderforce. Thunderforce will use the SQLite database and Salesforce.com. | |||
The user, of course, can also use Salesforce.com directly. This diagram depicts the two user access points to Salesforce.com that are relevant to Thunderforce. Due to this existence of two access points, Thunderforce will need to be mindful of changes performed directly in Salesforce.com, and Thunderforce will need to ensure that changes performed in Mozilla Thunderbird are propagated to Salesforce.com as soon as permissible. | |||
==Requirements== | ==Requirements== | ||
The detailed requirements are listed on another page. The high-level requirements are listed below: | The [[Requirements|detailed requirements]] are listed on another page. The high-level requirements are listed below: | ||
*[[Features#R1: Account Type|R1: Account Type]] | *[[Features#R1: Account Type|R1: Account Type]] | ||
*[[Features#R2: Address Book|R2: Address Book]] | *[[Features#R2: Address Book|R2: Address Book]] | ||
| Line 11: | Line 18: | ||
==Priorities== | ==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 | *[[Features#R2: Address Book|R2: Address Book]] | ||
*R4: Message Filters | *[[Features#R4: Message Filters|R4: Message Filters]] | ||
*R1: Account Type | *[[Features#R1: Account Type|R1: Account Type]] | ||
*R3: Message Composition | *[[Features#R3: Message Composition|R3: Message Composition]] | ||
*R5: Offline Mode | *[[Features#R5: Offline Mode|R5: Offline Mode]] | ||
==Task Priorities== | ==Task Priorities== | ||
| Line 24: | Line 31: | ||
#Parallel work on the modules, focusing on those that address the account type feature | #Parallel work on the modules, focusing on those that address the account type feature | ||
#First release | #First release | ||
Latest revision as of 06:02, 11 May 2007
The requirements fed into the feature list, and the prioritization of those features will appear on this page.
Context Diagram
The context diagram above depicts the Thunderforce part of the system being built and the components that it interacts with. The user will interact with Mozilla Thunderbird, which will then invoke and receive instructions from Thunderforce. Thunderforce will use the SQLite database and Salesforce.com.
The user, of course, can also use Salesforce.com directly. This diagram depicts the two user access points to Salesforce.com that are relevant to Thunderforce. Due to this existence of two access points, Thunderforce will need to be mindful of changes performed directly in Salesforce.com, and Thunderforce will need to ensure that changes performed in Mozilla Thunderbird are propagated to Salesforce.com as soon as permissible.
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.
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