This document provides descriptions of various types of documents used during different phases of a software development project. It outlines documents used before legal agreements are signed like RFIs, SOWs, and RFPs. During initial requirements gathering, BRDs are used. FRDs and FSDs are created during development. SRS documents have very detailed requirements. Post-development, RCAs, bug reports, and status reports are utilized for maintenance. Test cases and user manuals are also referenced.
This document provides descriptions of various types of documents used during different phases of a software development project. It outlines documents used before legal agreements are signed like RFIs, SOWs, and RFPs. During initial requirements gathering, BRDs are used. FRDs and FSDs are created during development. SRS documents have very detailed requirements. Post-development, RCAs, bug reports, and status reports are utilized for maintenance. Test cases and user manuals are also referenced.
This document provides descriptions of various types of documents used during different phases of a software development project. It outlines documents used before legal agreements are signed like RFIs, SOWs, and RFPs. During initial requirements gathering, BRDs are used. FRDs and FSDs are created during development. SRS documents have very detailed requirements. Post-development, RCAs, bug reports, and status reports are utilized for maintenance. Test cases and user manuals are also referenced.
Type of Document Phase For Whom Description Capacity
RFI Request for Information Before the Legal is Signed Client Client ask for the Product or service for their problem statement. 10 to 20 Pages Pre Requisitive SOW Scope of Work Before the Legal is Signed Client Boundaries that BA must adhere to in order to meet deadlines 5 to 10 Pages RFP Request for Purposal Before the Legal is Signed Client Customer requests quotes, costs, and features 10 to 20 Pages BRD Business requirement document Inital Phase Client High Level, Problem Statement, Solutioning, Features, What 40 to 50 pages FRD Functional Requirement Document Developement Phase Developer Atleast 100 pages Requirement phase Detailed version, Problem Statement, Feauture list, How to achive those featur list FSD Functional Specification Document Developement Phase Developer Atleast 100 pages SRS System or software requirement docu Developement Phase Developer Very Detailed, Problem Statement, Feauture list, How to achive those featur list Use atleast 500 pages RCA Root Cause Analysis Maintanence Phase Client/ Stakeholders Bug, When, Action to resolve that bug, future precoutions 2 to 5 pages Post Develpment Report Bugs Tracking Report Maintanence Phase Stakeholders Bug, When, Action to resolve that bug, future precoutions excel sheet Report Weekly Status Report Every Fortnight Stakeholders Update the Task and status of the projects. PPT QA User Cases Test Cases Develpment Phase Developers Created by the Testing team to test the functionality Depend on the document Maintanence Phase Manual User Manual After QA End Users Step By Step ways to user the Functionality Atleast 50 Pages