This page (revision-11) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 2 KB jmyers to previous
10 26-Nov-2021 10:22 3 KB jmyers to previous | to last
9 26-Nov-2021 10:22 3 KB jmyers to previous | to last
8 26-Nov-2021 10:22 4 KB jmyers to previous | to last
7 26-Nov-2021 10:22 4 KB jmyers to previous | to last
6 26-Nov-2021 10:22 4 KB jmyers to previous | to last
5 26-Nov-2021 10:22 4 KB jmyers to previous | to last
4 26-Nov-2021 10:22 6 KB jmyers to previous | to last
3 26-Nov-2021 10:22 6 KB jmyers to previous | to last
2 26-Nov-2021 10:22 7 KB jmyers to previous | to last
1 26-Nov-2021 10:22 1 KB jmyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 71 removed 36 lines
Example
Development Approach
This is an optional section to describe the steps the developer would go through in fulfilling the project goals.
1.
Questions / Additional Notes
This section should contain questions that have been or need to be asked/answered so that the project can be completed.
1.
Development Problems / Issues
Provide an outline of all problems, issues or challenges encountered while doing the development work (or anticipated up front).
Implementation
This section MUST be filled out by the developer. It should provide an outline of any business or technical setup required, a list of all processing considerations, and a list of all functions involved in the setup and usage of the feature.
Resources Released
This does not need to include java classes but should include icons, style changes and documents.
Quality Assurance
Note the QA person, date, feature QA’d and any comments or set up notes along with the severity or urgency of the issue. Please do not repeat the whole Requirements / Features section here. Include where you were working, the test case and all steps required to reproduce the issue [if needed].
Document Revision History
Identifies each document version and who made the change and when.
Version Author/Date Description
1.00 EC20110628 Initial Version