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?
Requirements on optimising code
Hey there,
You will need a single requirement stating that there is a specific requirement for the code optimisation on the specific piece of code. This requirement results in the specific piece of work on the project schedule.
At the end of the day you will need requirements that justify the cash that is going to be forked out for the exercise. If its a small piece of work you can probably skip this. If its a big chunk of work, you'll need requirements that outline the business benefit to the piece of work. At the end of the day it has to tie back to requirements such as reducing the processing time, thereby enabling clients to get the info sooner, resulting in competitive advantage of xx$ etc. etc. Really boils down to a mini business case outlined in busines objectives linked expressed as requirements. Thats if you want to go that far!
I reckon log a single requirement. Convince everyone verbally, if you are sure of the business value, and get cracking! :-)