Release Criteria Trial-2: Difference between revisions

Latest revision as of 15:54, 24 May 2007

Bug Criteria for release:

Performance and System Criteria for release:

Every activity must meet basic functionality with and without network connectivity
Every activity that has been part of a group activity can work properly without connectivity to collaborator(s)
Up to 5 XOs can collaborate on any one of the basic Activities
XOs can successfully activate with school server
XOs can backup user data to school server
B3s need to work in a mesh with B2s

Definitions

Blocking bug - User cannot execute basic feature function
High Priority bug - User can work around or execute the basic feature, but is not able to perform a secondary function
Normal Priority bug - Should fix in this release; not affecting a basic or secondary functionality
Low Priority bug - Nice to fix, but not required for this release

NOTE: Basic and Secondary functionality - Each activity has basic and secondary functionality defined in the Activities page

Revision as of 15:46, 24 May 2007 (view source) Kimquirk (talk \| contribs) No edit summary ← Older edit		Latest revision as of 15:54, 24 May 2007 (view source) Kimquirk (talk \| contribs) No edit summary
Line 25:		Line 25:


	* Basic functionality - Each activity has basic functionality defined in the [[Activities]] page		NOTE: Basic and Secondary functionality - Each activity has basic and secondary functionality defined in the [[Activities]] page
	* Secondary functionality - Activities must be able to use communications or collaboration capabilities. Must be able to open/edit/save across the mesh. This level of functionality would also include backup and restore of a file.