List of Project douments

[work4muthu]

Hi,
I would like to know the order and/or list of project documents to be prepared for an IT Project. I'm planning to use UML for Modelling and design. I google'd on this for quite some time and came up with the below mentioned list.

Please let me know, if this is in correct order and contains all the proper document types for standard project. It might be a novice question for some, but please let me know your thoughts.

List Documents:

1. Vision and scope Document - Outlining the scope and boundary of the project. This is prepared by the Project BA.
2. Business Requirement Document - Detailing the System/functional and non-functional requirements from the stakeholders/users/management perspective. It will list the various functionalities available in the end system with phases of that availability. This will also contain the final business rules, user case description, use case diagrams, activity diagrams, wire-frames prepared and finalised during the requirement collection. This is prepared by the Project BA.
3. Software/System Requirement Document - Detailing the above finalised and approved BRD from the perspective of the developers and designs for the development of the systems. This document will contain the sequence diagram, class/component/package diagram, entity relationship diagram. This is prepared by the Project BA/TA.
4. Test Case Document - Prepare functional and non-function test cases based on the BRD and details those to the testing team. This is prepared by the Project BA/TA.
5. Deployment Document - Detailing the application connectivity and procedures of deployment for the deployment team. This document will contain the deployment diagram. This is prepared by the Project TA/BA.
6. End-user Guide - Details the how-to of the system and steps to access the various features in the system. This is prepared by the Project BA.
7. Support-Handover Document - Details the BAU team of technical/business perspective of the system and the business process that are automated in the system. This is prepared by the Project BA.

Thanks in advance,
Ram

 

[Bishfield]

Hi,

The basic outline of documents you have listed above seems to be about right and is in the correct order. The type and number of documents you use very much depends upon the nature and context of the project; the size of the project and number of stakeholders involved; and finally the Project Manager's approach and methodology being used. For example, if you are managing a very small project, I would suggest using very few documents and try combining information in to overarching documents (such as the Project Plan and business requirements spec). HOwever, if its a larger project, you may wish to break this information out in to several docs.

As a starting point, have a look at this website for guidelines:

http://www.project-documents.com

It outlines the key phases of a project, and which project documents you would expect to use at each stage of a project.

hope that helps

 

[stevepm]

The basic outline of documents you have listed above seems to be about right and is in the correct order. The type and number of documents you use very much depends upon the nature and context of the project; the size of the project and number of stakeholders involved; and finally the Project Manager's approach and methodology being used. For example, if you are managing a very small project, I would suggest using very few documents and try combining information in to overarching documents (such as the Project Plan and business requirements spec). HOwever, if its a larger project, you may wish to break this information out in to several docs."

well said

Regards,

Steve Mark

How I Pass the PMP Exam for the PMP Certifiaction

http://www.pmguide.net/Recommended/F1/PMPrepcast.php