Requirements Document Alphabet Soup
Материал из Management Framework
Requirements Document Alphabet Soup - Explained Статья рассматривается различные виды аналитических документов связанных с разработкой продукта - BRD, MRD, PRD, FSD, PSD, SRS, IRS.
Цитаты из данной статьи:
- BRD - Business Requirements Document - focuses on defining the business needs of a project. The BRD identifies one or more business problems faced by customers that can be solved by the company's product. It then proposes a solution - usually a new product or enhancement to an existing product to address these problems. It may also include a high-level business case -- such as revenue forecast, market & competitive analysis, and sales/marketing strategy.
- MRD - Market Requirements Document - focuses on defining the market requirements for a proposed new product or enhancement to an existing product. Whereas the BRD identifies business problems and solutions to those problems - the MRD delves deeper into the details of the proposed solution. It may include some or all of these details:
- PRD - Product Requirements Document - focuses on defining the product requirements for a proposed new product or enhancement to an existing product. Whereas the MRD focuses on requirements from the perspective of market needs, PRD focuses on requirements from the perspective of the product itself. It usually delves into more details on features and functional requirements, and may also include screen shots and user interface flows. In organizations where the MRD doesn't include detailed requirements and use cases, the PRD covers those details.
- FSD - Functional Specifications Document - defines the complete details of a product's functional requirements with a focus on implementation. FSD may define the product specifications screen by screen and feature by feature. This is a document that can be directly used by engineers to create the product. Whereas the MRD and PRD focus on requirements from the perspective of market needs and product, FSD focuses on defining the product details in a form that can be implemented by engineers. FSD may also include complete screen shots and UI design details.
- PSD - Product Specifications Document - is a less popular acronym, but in organizations that have such a document, it is by and large the same as the Functional Specifications Document (FSD) described above.
- SRS - Software Requirements Specification - is another less popular acronym. In organizations that create an SRS, it has contents and details somewhere close to what is described above for PRD or FSD.
Материалы взяты с Requirements Document Alphabet Soup - Explained .
Смотри также
