Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  List of Project Documents
Previous Previous
 
Next Next
New Post 4/29/2010 11:17 PM
User is offline ram
1 posts
No Ranking


List of Project Documents 

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

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  List of Project Documents

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC