Study record of product requirement document (iv)

The first three articles we have gradually combed the information structure of the product, the frame structure, the interface structure (prototype), this step we will begin to formally write the product requirement document (PRD document) according to the work done previously.

Through previous preparations, we were more aware of the requirements of the product and carefully considered the feasibility of the scheme, thus reducing the black hole that was easily overlooked when writing the document.

PRD documents do not have standard specifications, there is no unified template, each company is different, and everyone is different, this depends on personal habits and team requirements. Although the PRD documentation does not have a standard specification, there are two items that are essential: file identification and modification records. Document in the process of writing, we can constantly modify the perfect, but if the official release or to other members of the team, once the changes, in order to synchronize the document, we need to mark the changes in the document, notes to modify the record. With regard to document identification and modification of records, everyone has a similar format (e.g.).

PRD documents are commonly found in the following three ways: Word, picture, interactive prototype

First, Word

This is the traditional PRD document, there are four parts (specifically depending on your product requirements to be divided), are: Structure diagram, global description, channel function,. (In the first article I have said that the PRD document reader is more inclined to the technical staff, so the PRD document purpose is very clear, is to describe the functional requirements of the product, all PRD documents are no description of the market, and I also recommend that you try to reduce unnecessary text, In situations where readers can understand and understand the intent of the product, the fewer words the better. This is mainly because most people are not patient enough to read the PRD document carefully, so we should try to reduce the content of the document. ）

1. Structure diagram:
1.1, information structure diagram: mainly auxiliary service-side technician to create or adjust the data structure of the reference file
1.2, the product structure chart: mainly is the auxiliary design and the technical development personnel to understand the product the global structure, he and the user flowchart is different, the product structure chart only lists the product the channel and the page.

2, the overall description: The main explanation of the global function of the product, such as the website product page encoding, user role, mobile product caching mechanism, download mechanism, this kind of global function description. Here I give an example of the "State maintenance and recovery" of a mobile product, as shown below.

Maintenance and recovery of state
When the user exits the product (misoperation, home key, lock screen, auto power off), the product needs to maintain the state before the user operation, when the user returns to the product can still return to the previous state, and continue to use.
Maintenance status includes process operations, information browsing, text input, and file downloads.
Lock screen Status, if the user has a download task in the product, it remains downloaded.

3, Channel function: In the channel Unit, the page is the child, respectively describes the product channel, the page and the page module element function demand (format below).

Sample format
1. Channel Name: Channel Introduction and requirement description
2, Page 1: page description and Requirements
2.1, Page Module 1: module function Requirements Description
2.1.1, page Module 1-element 1: Function description
2.1.2, page Module 1-Element 2: Function description
2.2, Page Module 2: module function requirements Description

In writing the functional requirements, we need to consider the user's process, such as a "complete" button, we need to describe his completion, the system should not give feedback (feedback tips is what form feedback, content display What, there is no content need to tune the database), or to jump page (to which page, This page is the other channel page, or the function of the sub-page, if the sub-page will need to describe the sub-page module and element content.

4,: is the product drawings completed by the designer, and the actual development of the product to achieve the same fidelity.

Second, the picture

The image form of the PRD document is based on the description file, the traditional word form of the functional requirements of the description, which is often used in the field of mobile Internet, is actually a graphic form of interactive requirements files, but on the basis of more in-depth description of functional requirements.

For PRD documents in the form of images, we only need to describe the global description, and the requirements of other channel pages are displayed directly in pictures, which is more vivid and intuitive than the plain text of Word documents, so some product managers like to replace PRD documents in Word form in this way.

Third, the interactive prototype

The interactive prototype referred to here is the prototype design of the previous article, the product prototypes produced using interactive prototyping software such as Axure PR are very real and intuitive, and the prototype software supports element labeling and export of Word documents, so many product managers like to use Axure PR to complete the PRD document instead of Word.

When we made a prototype of the product through Axure PR, in fact he is already a perfect product demo, so we just need to add elements of the label, in the callout to explain the functional requirements, so that the exported HTML file more intuitive than Word documents, is a very efficient way to explain the product requirements.

———

No matter which method you use to produce a requirement document, the ultimate goal is to make it easier for team members to understand the intent of the product, so this is the most effective way to avoid the details of the black hole and efficiently complete the design and development of the product.

Study record of product requirement document (iv)