At the moment I am in my notice period at work.I have a working but quite poorly structured web-service running (that I wrote from scratch) that I do not have time to refactor.I need to document it (with UML or whatever works best) so that the person who inherits it doesn't curse my name every time they need to work on it.What are the best practical ways to achieve this? I have created a use-case diagram that I think will be helpful. Is there any way I can make understanding this mess as painless as possible for the next guy?
What is the best way to document a poorly written web service?
- Thread starter AlleyCat
- Start date