In your opinion, should the documents listing what further needs to be done on the application development separate from the developer documentation describing design decisions and algorithms? It would be great to also explain the reason for the opinion on why it's clearer to do or not do so. Thanks in advance for the comments.
Asked
Active
Viewed 114 times
1
-
This should probably be community wiki if you don't want it to be closed as subjective. – Amber Sep 06 '09 at 23:28
-
How would I put this in the community wiki? – stanigator Sep 06 '09 at 23:31
-
If you click the edit link for your question, there should be a checkbox for it. – Amber Sep 06 '09 at 23:39
1 Answers
2
Yes, documentation of the existing system and documentation of prospective future changes should be separate.
The most important documentation is what the current system is, and what it does. Prospective changes don't provide anything of value from a maintenance perspective - just clutter. Prospective changes may be determined to be of lesser importance depending on various factors (most likely being money to fund), and timelines are adjusted accordingly.
OMG Ponies
- 325,700
- 82
- 523
- 502