English abbreviation for Product Requirements Document (PRD). It describes the business requirement document (BRD) and the market requirement document (MRD) in a more professional language. [Edit this paragraph] Document function This document is the most important document for the product project from the "conceptualization" stage to the "drawing" stage, and its function is "indexing and technicalizing the contents in MRD". The quality of this document directly affects whether the R&D department can clarify the function and performance of the product. [Edit this paragraph] Document Meaning This document plays a connecting role in the product project. "Up" is the inheritance and development of MRD content, while "Down" is to technicalize the content in MRD and explain the function and performance index of the product to R&D department. [Edit this paragraph] Document writing In this document, the basic point is still the content in MRD, but the focus is on "product requirements", and the product requirements themselves are actually reflected in MRD. The difference is that PRD should separate the content of "product requirements" in MRD and explain it in detail.

This part is the most written by PD, that is, demand analysis in the traditional sense. We mainly refer to UC (use case) documents here. The main contents include: the specific description of function usage (generally useful examples of each UC, actors, preconditions, postconditions, UI description, process/sub-process/branch process, etc. ), function point business process, interface description, demo, etc. produced by Visio. For Demo, it may be simply drawn with dreamweaver, ps or even sketchpad, and sometimes UI/UE will support the production of high-fidelity demo, and develop the kind that can be used directly in the future.

Document core:

This document focuses on the description of product functions and performance (namely "product requirements"), which is more detailed and quantitative than the same content in MRD.

In some foreign companies, MRD and PRD are allowed to be merged into one file, which is usually called "Marketing &；; Product requirements document. [Edit this paragraph] Misunderstanding 1)PRD is not supported by original data (MRD is the embodiment carrier), but written according to personal experience, departmental requirements or leadership instructions.

2) In PRD, only the description of "product function" is emphasized, but other indicators of the product are not explained. In a complete PRD, a * * * needs to explain 10 product requirements of the product, namely, "functional requirements, development requirements, compatibility requirements, performance requirements, expansion requirements, product documentation requirements, product appearance requirements, product release requirements, product support and training requirements, and other product requirements".

3) Copying foreign PRD templates, I don't know where it came from and where it will go, and I don't know, headless and tailless, a fragmented document. VISIO Overview Microsoft Office Visio 2007 is a new software produced by Microsoft Corporation, which can help IT and business professionals easily visualize, analyze and communicate complex information. It can convert complicated texts and tables that are difficult to understand into Visio charts at a glance. This software displays data by creating Visio charts related to data (instead of using static pictures). These charts are easy to refresh and can significantly improve work efficiency. Use various charts in Office Visio 2007 to understand, manipulate and * * enjoy information about organizational systems, resources and processes in an enterprise. Axureaxure Axure RP Overview can help website requirements designers to quickly and simply create annotated page diagrams, operation flow charts and interaction designs based on website architecture diagrams, and can automatically generate web pages and specification files for demonstration, providing demonstration and development.