Common document types for Internet product design-BRD, MRD, PRD, FSD

BRD

Business Requirements document, commercial requirements documentation. This is the product declaration cycle in the earliest of the document, and should have been the idea of the brain, its content involves market analysis, sales strategy, profit forecasts, and so on, usually with the eldest brother Ppt, so it is relatively short refining, no product details.

The business requirements document focuses on defining the business needs of the project. BRD to be able to name one or more of the business problems customers encounter, and to solve these problems through the company's products. It then suggests a solution-usually a new product or an improvement in the existing product-to address these issues. BRD may also include a high-level business case, such as revenue forecasts, market competition analysis, and sales/marketing strategies. BRD is usually written by someone with a product manager, product Marketing Manager, or industry analyst title. In small companies, it may be written by senior executives or even founders. BRD is typically a continuous 1-3-page Word document, or a PowerPoint document that does not exceed 10 pages.

MRD

Market Requirements document, marketing requirements documentation. Get the boss's approval, the product into the implementation, need to first out of the MRD, specifically to have a more detailed analysis of the market and competitors, through what functions to achieve business purposes, functional/non-functional requirements of which several blocks, the priority of the function and so on. In practical work, the possible outputs of PD at this stage are Mind manager's thought diagram, Excel's Feature list, etc.

            a. features needed to solve business problems
             b. Market competition Analysis
             c. Functional and non-functional requirements
             d. Priority of features/requirements
            e. Use cases

The MRD is usually written by someone with a product manager, product Marketing Manager, or industry analyst title. The MRD is usually a contiguous 5-25-page Word document, or, as described later, in some organizations or even longer.

PRD

Product Requirements document, production requirements documentation. Progress is a refinement, this part is the most written content of PD, that is, the traditional sense of demand analysis, we here mainly refer to the UC (use case) document. The main content is the specific description of the use of the function (each UC generally has a use case summary, the actors, preconditions, post conditions, UI description, Process/Sub-process/branching process, and so on a few chunks), Visio does the function point business process, interface description, demo, etc. Demo, may use Dreamweaver, PS or even draw a simple drawing board, and sometimes there will be ui/ue support, out of the high-fidelity demo, development can be directly used in the future.

The Product requirements document (PRD) focuses on defining market requirements for improvements to a proposed new product or existing product. With the MRD focusing on the difference in demand from a market need perspective, PRD focuses on the need to look at the product from its perspective. Often more in-depth details on features and functional requirements, and may also include screen and user interface processes. In institutions where the MRD does not include specific needs and use cases, PRD contains these specific elements. PRD is usually written by someone who has a product manager, an industry analyst, or a product analyst title. PRD is usually a continuous 20-50-page Word document, or even longer for complex products.

Reminder: Some agencies combine the MRD and PRD described here into a single document, and say the final document is the MRD. In this case, the MRD includes the content described in this paragraph, as well as the previous paragraph describing PRD, and may exceed 50 pages.

FSD

Functional specifications Document, features detailed description. A bit like "Summary design", this step begins to converge on the development, the product UI, the details of the business logic are determined, the document is refined and kept up to date. Accordingly, there are a lot of content, such as table structure design, to be written by the project manager.

The feature specification document (FSD) focuses on implementation, defining all the details of the product's functional requirements. FSD may define product specifications through a single screenshot and functional points. This is a document that allows an engineer to create a product directly. With MRD and PRD focusing on market needs and product perspectives, FSD focuses on defining product details in tabular form, and then allowing engineers to implement these details. FSD may also include full screen and UI design details. FSD is usually written by a person with a product analyst, engineering lead, or project manager title – the author usually belongs to the engineering department. A word or similar document that is typically dozens of pages in a row.

Common document types for Internet product design-BRD, MRD, PRD, FSD