So...
I think I basically know how to write "requirements documents", "functional specifications", and "design specifications." (All covered in those ISO9000 training classes, you know.)
But I think I need some advice on how I should write a "Critique" of an existing design. Basically, somehow enumerating all the things that should have been caught during the reviews of the requirements, specs, and implementation, but ... that chance was years ago (if such reviews ever happened at all), and now I'm looking to lay the groundwork for a re-write...
Essentially "this existing code/structure sucks because xxx", but in a nice and professional way, so that the stakeholders might listen instead of just getting defensive.
I suppose that one strategy would be to write a "functional specification" for how you think it SHOULD work, and then highlighting the ways in which the current implementation fails to do those things?
Thoughts?