This paper describes the working methods of application and product manager of the Product Requirements Document (PRD).
First, the concept
PRD more attention to the needs of the product itself, details of the various features and functions will be described in detail, PRD also often include a user interface and user processes.
If you do not include a variety of features and details of the characteristics of a company in the MRD, the content will be described by the PRD.
Second, the contents
1, functions, product name
2, Version History
3, Function
(1) list of features and priority (MindManager or list)
(2) Objective Function
(3) Detailed description
- block, prototype drawing, description field, the requirements (rules)
- Example: field, type, required, validation, error
(4) page structure of FIG.
- Page => subpages => Modules => element module => constraints
4. Business Process
(1) business process diagram (similar to FIG lane, the process described can be added)
(2) example user cases
- in accordance with the user's dimensions, which can do things, permission
- figure, table, or
5, business rules
6, interface prototypes (breadth, priority)
(1) Page flowchart
(2) a prototype FIG page
- user scenarios, functional description, priority, input / preconditions described demand, output / postconditions supplement
7, data requirements (depth, can gradually iteration)
(1) Input Output
(2) limits
(3) Data Format
8, the market operators demand
(1) functional requirements
(2) Compatibility
(3) Performance
(4) release
(5) Support and Training
(6) sales ideas, needs
9, other needs
(1) interact recommendations
(2) performance requirements
(3) environmental requirements
(4) Option
10, assessment feedback
(1) opinions and suggestions
(2) Duration hours
(3) demand and workload assessment review score
(4) Summary of previous communication advice