documentation - What are the best practices for technical reports -


How do you, as a programmer , think that technical software should be reported on any software , In a way that can adapt the work of other programmers, takes it and can begin to feel connected to the code as soon as possible.

I see the documentation on two levels: SourceCode documentation and design documentation

Java code or equivalent style, then source code documentation is very useful. You can generate reference documentation automatically and use some IDE information well. Apart from this, it is thought that why things are happening or limit the comments of the source code on very difficult algorithms.

Design documentation should include a bigger picture. How to fit all the pieces together, note how things flow through the system, give an example (use cases, etc.) how different classes and sub-systems determine the new methodology to plug in where Will be invaluable in doing.

Most importantly, though, it is to document the system as of today's time, not how it was a year ago, or how it should have been otherwise, the document worse than waste Will be I think it would be difficult for you to find that you do not have to worry about any other "best practices".


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -