Can I have some more refernce links please
Thanks
Main Topics
Browse All TopicsI am a software developer and I had created documentaion of the project which I ahd finished coding recently.
I need some seggestion and turtorial refrence that can help me understand which type of documentaion will be suitable for me.
The basic reason for this documentation is that if someone new work on this project after me then this document will help him.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Fantastic! A developer that wants to document their code for the next person.
Several different types of documentation types....Architecture, Technical, User are the most common.
Wikipedia gives a basic overview at http://en.wikipedia.org/wi
One good point is to document code. There are some utilities that, if you write your source code right, will generate the documentation for you. One noted example is JavaDoc. It looks for specific line formats and can build a web-based document for you.
Personally, if a small scale system, a good old Word document would suffice, once you define the contents.
If too vague, I can point elsewhere....
Bob
Depending on the size and scope of the project, you may want different types of documentation. For example, it goes without saying that you should document your code. Done properly, you can generate all sorts of things (such as dependency graphs) directly from your source code. This depends on your programming language. I rather enjoy doxygen for my C++ code, for example. The generated documentation can help a developer modify existing code.
Next, consider if you must have other types of documentation. Topics that I think might be covered include:
What is required to build the code. List all dependencies, compilers used, environment, included libraries (logging libraries are common, for example). Is the code in a repository? If not, you have likely failed! If so, good for you, now tell me EXACTLY how to get the code out.
Include specific step by step build instructions. Exactly what steps are used to build the code. I prefer code so specific that a non-computer type person can create a complete functional build and installation.
List testing procedures. How can I tell if things work correctly? Unit tests, system tests, etc.
Business Accounts
Answer for Membership
by: emoreauPosted on 2007-09-05 at 10:30:00ID: 19834145
see http://blogs.msdn.com/sand castle/