How do I document code change requirements?
We have some code changes that need to be made because they were poorly written. basically, a developer looked at some old code and has found some areas of opportunity. They are going to modify the code to make it perform better. They created a project initiation document that says they are going to rewrite the code and now they want a requirements document. To me the only requirement is to streamline the code for better performance.
It seems a little over kill to try to put a requirements specification document together for this project (which has already been completed).
What do you tihnk? Any suggestions on how I should go about documenting this kind of project?
Corrective Action on account of Code Review
If the functionality of the system is not being changed, then what you have described is a case of action taken on account of a review process. Instead of creating requirements document, I think you should just document the suggested improvements for code optimization and upon approval by the concerned personnel, perform those. You can also probably make this a Process improvement action item for future projects. Just my 2 cents.