Changes between Version 10 and Version 11 of PLATFORM_STANDARDS_DESIGN
- Timestamp:
- 09/25/08 14:20:25 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PLATFORM_STANDARDS_DESIGN
v10 v11 1 1 Design should be started after the Analysis for this revision has passed review (>=3 points). A task with non-reviewed analysis and design gets review at implementation. In that case the mark is for design and analysis, too. Design section for each task should cover implementation method for this task revision (what has to be done exists in Analysis section) - how it should be implemented. For each task in Design section, please include: 2 2 Depending on task type design section should contain 3 * Coding tasks - Design of these tasks should describe technology that will be used for reaching task's requirement. 3 * Coding tasks - Design of these tasks should describe technology that will be used for reaching task's requirement. These tasks should be designed by a developer. 4 4 * Required libraries 5 5 * Implementation methods, suggested algorithms, etc. 6 6 * UML diagrams (class diagrams) where needed 7 7 * Initial tests 8 * Bug Fix - Design of bug fixes is similar to Coding tasks' design, but should also answer the questions why does this bug appear, which part of the code is guilty for the wrong functionality (what was wrong with the code, why it was not suitable). Design also contains auto-tests that prove bug wouldn't be presented after implementation. 8 * Bug Fix - Design of bug fixes is similar to Coding tasks' design, but should also answer the questions why does this bug appear, which part of the code is guilty for the wrong functionality (what was wrong with the code, why it was not suitable). Design also contains auto-tests that prove bug wouldn't be presented after implementation. These tasks should be designed by a developer. 9 9 * In which module did the bug appear 10 10 * In which part of the code did the bug appear … … 13 13 * UML diagrams (class diagrams) where needed 14 14 * Initial tests 15 * Document - Design should point which tools will be used, how the document will be created. 15 * Document - Design should point which tools will be used, how the document will be created. Depending on specific task, these tasks may be designed by developer or qa. 16 16 * Required auxiliary tools 17 17 * Basic content of the document, a sentence for every fundamental thing. These will be expanded in Implementation section. 18 18 * Useful external links 19 19 * Image/Diagram requirements - content, file types, file sizes, position, etc. 20 * Setup - Design section should be decided which computer appliance will satisfy the requirements, how it will be set up, what technologies will be used. Give links to websites of software solutions that should be used. 21 * Hardware requirements - point specific hardware requirements, limitations if any 20 * Setup - Design section should be decided which computer appliance will satisfy the requirements, how it will be set up, what technologies will be used. Give links to websites of software solutions that should be used. These tasks should be designed by a developer. 21 * Hardware requirements - point specific hardware requirements, limitations if any. 22 22 * Software requirements - point which of the suitable tools will be installed and configured. 23 * Maintenance - Design explains what should be done for meeting the requirements, links to tools that will be used, algorithms, diagrams and whatever is needed for an easy implementation. 23 * Maintenance - Design explains what should be done for meeting the requirements, links to tools that will be used, algorithms, diagrams and whatever is needed for an easy implementation. Depending on specific task, these tasks may be designed by developer or qa. 24 24 * If script are needed, design and link them 25 25 * Link any used tools for maintaining appliances/files.
