Changes between Version 6 and Version 7 of GLOBAL_SPEC_STRUCTURE_R0
- Timestamp:
- 09/11/08 14:46:36 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GLOBAL_SPEC_STRUCTURE_R0
v6 v7 1 Global Spec Structure must contain all available data about functional requirements. 1 == Analysis == 2 === Overview === 3 Global Spec Structure must be our "road map" for the Global Specification. It must contain requirements what artifacts will be kept, where we will store them, and how they must be structured. 2 4 5 === Task requirements === 3 6 * Define what artifacts will be kept 7 * Define which file formats for which artifacts well be used 4 8 * sophie2-gui-elements - google spreadsheet 5 9 * master_spec - odm 6 10 * DND Table - define what will be the columns of the table - what can be drag and where can be drop, where this document will be kept 7 * define what other documents we will need, what their structure will be, and where it will be kept 8 11 * define what other documents we will need, what their structure will be, and where they will be kept 9 12 * Define where the artifacts will be kept 10 13 * Google Docs … … 12 15 * Trac 13 16 14 * It is good to keep our artifacts in such ways that they are as easy as possible to manage 17 === Requirements to the task result === 18 The result of this task must be a wiki page. 19 20 === Implementation idea === 21 * It is good to keep our artifacts in such ways that they are as easy as possible to manage. 22 * We must avoid scattering artifacts and create such structure that doesn't contain any unnecessary documents, but cover all needed specifications. 23 24 === Examples === 25 Currently we store following artifacts: 26 * sophie2-gui-elements - google spreadsheet 27 * master_spec - odm 28 * DND Table - define what will be the columns of the table - what can be drag and where can be drop, where this document will be kept 29 30 === How to demo === 31 Show the structure of the available artifacts and explain in what formats and where they will be kept. Explain how they will be managed, and how will be added new ones. 32 33 == Design == 34 == Implementation == 35 == Testing ==