General discussion

Locked

Documenting a undocumented system

By lunateth ·
I have taken on a project that has for the most part been built, but it is buggy and has no requirements, scope, or technical specification docs. In your experience, what is the best way to go about building a specification from an existing system,all while sorting out bugs?

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

From my experience

by jeubeda In reply to Documenting a undocumente ...

1. The big picture. Elaborate a document describing what the system do in short. It will help you to decompose it in more manageables modules, and to concentrate on the relevants parts.
2. If you have a tool to do it, document the physical objets (data relations), and function calls (funtional relations), in order to get a first net of relations.
3. Select what will be relevant for you, giving a priority order to drill down the system.

Hope this helps

Back to IT Employment Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums