Why not. I am working with several individuals on a project to capture the existing logical and physical architectures of a system, then map out a road ahead for the new architectural baseline. It totally believe in the Scott Hanselman philosophy that “Documents have no teeth”. Once a document has been written, virtual or physical dust starts collecting.
I believe this is due to several reasons:
- Requirements change rapidly
- They are stored everywhere
- They are hard to search for relevant information
- Developers dislike documentation
- Changes in personnel
These are just a few of the reasons.
As a matter of course, there is value in collaboration and a centralized location to store this information to make it easily searchable. I have been an advocate of using SharePoint for a long time. But like everything else, it takes discipline (See Article)to make the site productive. The use of SharePoint is a habit. It must be accepted and integrated as part of the culture to share information. IMHO, restriction on the use of network folder shares is a must for SharePoint to be effective. Enough of that soapbox.
SharePoint 2007 has come out with a couple of new web parts, one being a Wiki. How cool is that. Our development team has bought into the wiki concept for documentation. A key to this will be to try and manage at least a decent structure to some of the documentation.
For more on Documents having no teeth, see