Transfer: https: //blog.csdn.net/neikutaixiao/article/details/40819445
Business Requirements Document
Business Requirement the Document
BRD and MRD, PRD is considered to be together from marketing to product specification documents need to be established.
Product life cycle is the earliest document, and then the idea is long overdue in the brain, and its covering market analysis, sales strategies, profit forecast, usually for presentations to discuss the decision-making level, tend to be more short refining, no product details. Product demand contents of the document (report) or value-based business objectives described, the core of the product before use is for R & D investment by business executives as an important basis for decision-making assessment.
Differences with the PRD BRD
BRD different from the common MRD and PRD, since it is the basis for decision-making to assess the implementation of previous products, it is bound document (report) the content and format requirements intuitive enough, refining, highlight key points. As the authors of the report, you have to get the top understand that your report will show what kind of business value, companies recognize how to convince you of this project with a strong argument for, and generous R & D resources and marketing expenses . If the PRD will directly determine the quality level of the project, BRD's role is to determine the commercial value of your project. BRD excellent documentation, allowing decision-makers to fully report are attracted to your point of view, perhaps because of the economic forecasting Treasurer low-input high-yield reports presented and just around the corner; perhaps because of extensive technical director of the project involve surface headache endless; perhaps the company's VP and his ilk consequent report and see the broad prospects for rapid development in the coming year performance ......
it plainly, BRD need product manager (product designers) treat PRD, as the full application of market research, user research, needs analysis and other design tools to adequately explained the contents of the report. Based on this situation, obviously not for everyone a complete BRD standard format specification, will be able to get everything! Ha, maybe some people will say this is a bit alarmist, but I have always been in favor of, in the face of all "products" should be designed to look at it with eyes.
First, you should put the decision-making level as the audience your product --BRD, everything from here ......
Market Requirements Document
Market Requirement Document
This document belongs to the "process" of documents from the product during the project.
1 document the role of
the document is a product from the project into the "ready" stage to the "implementation" phase of the first document, its role is "Product of the Year for a product in the market planning level description," The quality of this document a direct impact on the project to carry out product and directly affect the realization of the strategic intent of the company's products.
2 Documentation significance
of the document is the product of a project "nexus" role, "up" is the accumulation of an integrated market data and records, "down" direction is the follow-up work instructions and work instructions.
3 documentation writers
write MRD, roughly the following aspects (in chronological order) approach:
1, project background;
2, Glossary;
3, feasibility analysis (preliminary research information and data + project targets);
4, a comprehensive description ( functional Overview + on other products);
5, detailed function (functional requirements + function point);
6, other description of the problem.
4 core document
in the document, focusing on the product is on the market where the customer (client), purchaser (buyer), user (user) as well as market demand, define and visualize them through prototype form
5 misconceptions
1) fundamental no MRD ideas, many companies the product manager classified as technical end, therefore, in reality, many product manager of product documentation is only focused on the functional description, but on the basis of market lacks sufficient knowledge and records;
2) the MRD and confuse the PRD, MRD is the foundation of the PRD, PRD is embodied in the MRD on product features.
3) copying foreign MRD template, from where, do not know where the destination, do not know, no head no tail, was a separate document.
Product Requirements Document
Product Requirements Document (Product Requirement Document, PRD) abbreviation.
Is a business requirements document (BRD) and Market Requirements Document (MRD) is described with more professional language.
Documents significance
of the document is the product of a project "nexus" role, "up" is MRD contents of inheritance and development, "down" is the technical content of MRD put in, the function of the product to R & D and Performance.
Documents written
in this document, the point is still the content of MRD, just focus on the "demand" and the demand itself is reflected in the MRD, the difference is that, PRD should MRD in content "product demand," the independent be described in detail.
This part of the PRD is the most written content, that is, demand analysis in the traditional sense, we are here mainly refers to UC (use case) document. The main content, specifically using the function described (each embodiment is useful UC typically brief, actors, pre-conditions, post-conditions, the UI description, process / subprocess / branching processes such as several large pieces), the function of the Visio do point of the business process, interface description, demo and so on. Demo aspects, may use dreamweaver, ps even simple drawing board painting it, sometimes there are UI / UE support, a high-fidelity demo, developed in the future that can be directly used.
The core document:
this document, the focus is on product description product features and performance (or "demand") with respect to the same content in the MRD, to be more detailed and quantified.
In some foreign companies, it is to allow the MRD and PRD combined into one document, often called "Marketing & Product Requirements Document".
This document may generally include the following:
the vision of the product (vision)
target markets and customers (target market and customers) description
competitor analysis (competitive summary)
more detailed description of the product's main feature
priority of these feature
Tentatively implementation schedule.
Example use (use cases), which may be described generally coarser, not necessarily to UML Use Case FIG.
Hardware and software product demand
product performance requirements
idea on sales, demand (direct or channel? Direct how do? Channels how to do?)
Ideas on the way technical support, needs (what kind of technical services?)
Development tools recommended :
the Rational Rose ★★★★ - related business practices familiar with the project happen.
visio 2007 ★★★★ - the business, dismembered off from the product level, so that unraveling part of the overall unified
mind manager ★★★ - the entry of the project, principled, well specified directory structure.
Axure ★★★ - Reception structure and layout, reasonable standard system off dim Hua yarn.
Word ★★★★★ - wearing a knitted mesh, put together demand, organized into the final product requirements document.
Misconceptions
1) PRD no raw data (MRD to reflect carrier) support, just personal experience, leadership department requirements or written instructions.
2) In the PRD, only the emphasis on "product features" description, description of the product and the lack of other indicators items. In a complete PRD, a total need of 10 products demand indicators explained, are "functional requirements, development requirements, compatibility requirements, performance requirements, expansion requirements, product documentation requirements, appearance requirements, product launches requirements, product support and training requirements, products or other requirements. "
3) copying foreign PRD template, from where, do not know where the destination, do not know, no head no tail, was a separate document.
---------------------
Author: neikutaixiao
Source: CSDN
Original: https: //blog.csdn.net/neikutaixiao/article/details/40819445
Copyright: This article is a blogger original article, reproduced, please attach Bowen link!