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?
Question
Brandon, just so I understand ..has the code re-engineering already been completed ? Or is it that the project was completed and upon completion it was discovered that the code could be improved ?
If it's the latter does your company have a change management process in place ? If so why wouldn't it be a change request ? The request should outline the scope , reason for the change, cost etc... If the change is of sufficent size ( dependant on the scope) then you might want to treat it as a seperate project..if that's the case then a I would do a new requirement spec...on a side note if they have created a PID then it does suggest that the change to the application could be substantial.