Requirements prioritization and project scope - Revision history

Stevenlawrance: Moved the context diagram to the top

2007-05-11T06:02:46Z

Moved the context diagram to the top

@@ 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.
 ==Requirements==
@@ Line 24: / Line 31: @@
 #Parallel work on the modules, focusing on those that address the account type feature
 #First release

Stevenlawrance: /* Context Diagram */

2007-05-11T06:01:12Z

Context Diagram

← Older revision		Revision as of 06:01, 11 May 2007
Line 28:		Line 28:
	[[Image:Context Diagram.png]]		[[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 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.

Stevenlawrance: /* Context Diagram */

2007-05-11T05:56:37Z

Context Diagram

← Older revision		Revision as of 05:56, 11 May 2007
Line 26:		Line 26:

	==Context Diagram==		==Context Diagram==
	~~Coming soon.~~.		[[Image:Context Diagram.png]]

	*Mozilla Thunderbird		The context diagram above depicts the Thunderforce part of the system being built and the components that it interacts with.
	*Thunderforce
	*Salesforce.~~com~~
	*SQLite

Stevenlawrance at 13:54, 9 May 2007

2007-05-09T13:54:37Z

← Older revision		Revision as of 13:54, 9 May 2007
Line 2:		Line 2:

	==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 11:
	==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==

Stevenlawrance at 13:52, 9 May 2007

2007-05-09T13:52:49Z

← Older revision		Revision as of 13:52, 9 May 2007
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

Stevenlawrance at 13:34, 9 May 2007

2007-05-09T13:34:19Z

← Older revision		Revision as of 13:34, 9 May 2007
Line 3:		Line 3:
	==Feature Priorities==		==Feature 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]].
	#Address Book		*R2: Address Book
	#Message Filters		*R4: Message Filters
	#Account Type		*R1: Account Type
	#Message Composition		*R3: Message Composition
	#Offline Mode		*R5: Offline Mode

	==Task Priorities==		==Task Priorities==

Stevenlawrance at 19:32, 8 May 2007

2007-05-08T19:32:06Z

← Older revision		Revision as of 19:32, 8 May 2007
Line 16:		Line 16:
	#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

			==Context Diagram==
			Coming soon..

			*Mozilla Thunderbird
			*Thunderforce
			*Salesforce.com
			*SQLite

Stevenlawrance at 07:03, 3 May 2007

2007-05-03T07:03:57Z

← Older revision		Revision as of 07:03, 3 May 2007
Line 16:		Line 16:
	#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

	~~==Schedule==~~
	~~The first release of Thunderforce is planned to occur around mid-August of this year. The details of the plan will work backwards from that release date.~~

	The following table depicts the current schedule for Thunderforce. Note that week 18 is the week beginning on April 30, 2007. Items in the table cells indicate when those activities should be completed by, which can be by the end of the week indicated.

	~~{\| border="1"~~
	~~! Week 18~~
	~~! Week 19~~
	~~! Week 20~~
	~~! Week 21~~
	~~! Week 22~~
	~~! Week 23~~
	~~! Week 24~~
	~~! Week 25~~
	\|-
	~~\|width="12.5%" valign="top"\|~~
	*Project plan and scope
	*Notional architecture
	~~\|width="12.5%" valign="top"\|~~
	*Identification of architectural risks
	*Experiment planning
	~~\|width="12.5%" valign="top"\|~~
	*Initial XML user interface language (XUL) files created
	~~\|width="12.5%" valign="top"\|~~
	*XUL files tested with Usability Engineering (UE)
	~~\|width="12.5%" valign="top"\|~~
	*XUL files refined
	*Experiment execution
	~~\|width="12.5%" valign="top"\|~~
	*Architectural refinement
	*Module identification and assignment
	*System code skeleton created
	~~\|width="12.5%" valign="top"\|~~
	*Sprint 1 kick-off
	~~\|width="12.5%" valign="top"\|~~
	\|}
	~~<br>~~
	~~{\| border="1"~~
	~~! Week 26~~
	~~! Week 27~~
	~~! Week 28~~
	~~! Week 29~~
	~~! Week 30~~
	~~! Week 31~~
	~~! Week 32~~
	~~! Week 33~~
	\|-
	~~\|width="12.5%" valign="top"\|~~
	*Initial integration tests using skeleton
	*End of sprint 1
	~~\|width="12.5%" valign="top"\|~~
	*Demonstration of sprint 1 functionality
	*Sprint 2 kick-off
	~~\|width="12.5%" valign="top"\|~~
	~~\|width="12.5%" valign="top"\|~~
	~~\|width="12.5%" valign="top"\|~~
	~~\|width="12.5%" valign="top"\|~~
	*End of sprint 2
	*Demonstration of sprint 2 functionality
	*Sprint 3 kick-off
	~~\|width="12.5%" valign="top"\|~~
	*Integration tests needed for release pass
	~~\|width="12.5%" valign="top"\|~~
	*Packaging
	*First pre-alpha release
	*End of sprint 3
	*Demonstration of sprint 3 functionality
	\|}

	~~==Sprints==~~
	~~The following lists the focus of each sprint:~~
	~~#Initial integration test creation and development of base functionality~~
	~~#Feature development and integration test refinement~~
	~~#Release finalization and packaging~~

Stevenlawrance: /* Sprints */

2007-05-03T07:02:15Z

Sprints

← Older revision		Revision as of 07:02, 3 May 2007
Line 90:		Line 90:
	#Initial integration test creation and development of base functionality		#Initial integration test creation and development of base functionality
	#Feature development and integration test refinement		#Feature development and integration test refinement
	#~~Integration test validation~~ and ~~extension~~ packaging		#Release finalization and packaging

Stevenlawrance: /* Schedule */

2007-05-03T07:01:54Z

Schedule

← Older revision		Revision as of 07:01, 3 May 2007
Line 78:		Line 78:
	*Sprint 3 kick-off		*Sprint 3 kick-off
	\|width="12.5%" valign="top"\|		\|width="12.5%" valign="top"\|
	*Integration tests ~~refined~~		*Integration tests needed for release pass
	\|width="12.5%" valign="top"\|		\|width="12.5%" valign="top"\|
	*Packaging		*Packaging