|
Project Web examples
Project Webs, PW, are today mostly used to handle common documents in projects.
We here list some experiences made
- Some systems provide 'push' facility when a new document or comment in a discussion is stored in the PW. If the user are not notified he/she has to search himself ('pull'). Some systems will make you aware as you log into the PW that you have unread documents (and which).
In some systems you can define roles that can be used to control view and access to documents to different persons (roles are specified by the one who stores the document on the PW).
- Some systems are very dependent on specific platforms to function (e.g. using special Microsoft Windows scripts and functionality). Platform dependency and special web browser dependency should be avoided.
- Very often it may be difficult to easily mirror the PW document containers
to your own computer. It is favourable to have your own copy when you are offline or when the project is finished and you need the documents for your own experience storage.
- It is important to early establish a structure and container naming/labels that will not change (but can be extended). The naming structure and labels should also be that clear so you
do not need to establish your paralell PW to be able to easily find documents.
|
BCSW, Frauenhofer, Germany
Byggeweb. Use in project 'IT på Byggepladsen' 2003-2004.
Byggeweb
Byggeweb
Rambøll internal project web. Used in Det Digitale Byggeri, 3D project.
COWI internal project web. Used in Det Digitale Byggeri, DACaPo project.
Google Docs, http://docs.google.com/
Confluence, http://www.atlassian.com/software/confluence/
|
|