Features
Features:

Product Tour >

Edraw AI >

Paid Plans:

Individuals >

Business >

Eduaction >
Resources
Blog

History

How-tos & Tips

Discovery

Biography

Business Analysis

Examples

AI concept Map

Free AI Mind Map Generator

Onenote Mind Map

Bcg Matrix Examples

Nike Marketing Strategy

Unilever SWOT Analysis

Make Mind Maps in Google Docs

Guide

FAQs

What's New

Resource Center
Templates
All Templates

Brain Storming Templates

Strategy and Planning Templates

Project Management Templates

Product Management Templates

Human Resources Templates

Agile Workflow Templates

Marketing Templates

Education Templates

Fun and Games Templates

User Gallery
Download
Pricing
Enterprise

MindMap Gallery A must-have product requirements document for product managers

A must-have product requirements document for product managers

It mainly introduces the main composition and writing method of product requirements document, and uses the RP format to illustrate. Hope this helps!

Edited at 2023-11-24 15:26:59

PlotWizard

Recent works View more works>>

A must-have product requirements document for product managers

PlotWizard

Recent works View more works>>

Recommended to you
Outline

Product Requirements Document-PRD

common forms

RP format

When drawing a prototype, directly write a description corresponding to the page content.

Document format

Organize the prototype into a Word document and write a specific requirements description in the document

main content

RP format

Product introduction

Release Notes

Interactive self-check sheet

Product overview

Feature list

Project schedule

product architecture

Structure diagram

flow chart

Product prototype

global description

Role/Function Permissions

Loading method

Global elastic layer

Common fields

network anomaly

global interaction

concrete prototype

Function Description

non-functional requirements

Buried demand

Performance requirements, etc.

Document format

Product introduction

Purpose

scope

terminology

User role description

role description

product description

Target

Overall process

Function overview

Functional requirements description

Functional structure

Function Description

Other product requirements

Performance requirements

Monitoring needs

Compatibility requirements

Risk Analysis

Risk prevention measures

Risk response measures

Related documents

appendix

Such as demo

Functional requirements description

PRD core content

Mainly used to describe the functional requirements of the product

Let other people clarify the functional aspects beyond the prototype

Mainly write functional descriptions (process descriptions, requirements descriptions)

Describe the business process and functional process of the product in the document in the form of a flow chart

Description of Requirement

The most common content is the interactive description of the writing page

interaction

definition

Do something and get feedback

Common interaction types

visual interaction

sound interaction

tactile interaction

Basic forms of interaction

Swipe right to return to the previous page

Next page move right overlay

Bottom call operation

List switching mode

Element control interaction

button

press

Not clickable

hint

toast prompt

Pop-up prompt

Word

Interactive instructions

The core “product” output by interaction designers and product managers

The “users” we target are downstream colleagues—UI designers, development engineers, and test engineers.

how to write

Page flow (between pages)

It can express the overall process of the product and help colleagues understand the relationship between business, functions and pages. It is generally reflected through the prototype structure.

Content layout (within the page)

What is the structure of the page, what modules are there, and the basic layout

What kind of data (text, pictures, video, audio) is displayed, and what is the display style or format? Where does the data come from?

Explain the display rules in different states (login, loading, role, network, presence or absence of content, etc.)

Interaction and feedback (control logic)

Interactive logic, what effect does the control operation on the page have, and where will it jump to? Also pay attention to interactive data logic (restrictions) and abnormal feedback (operation errors), etc.

step

Page description

Divide the overall page structure and, if necessary, describe the relevant paths clearly

label naming

Label and name the prototype according to the divided structure

Writing instructions

Area page description

Regional function description

nitty gritty

unit format

Two digit date and month

information desensitization

colon between time minutes

Space in the middle when displayed on mobile phone

Amount separated by commas every three digits

Phone shows short and medium lines in the middle

character limit

in characters

One Chinese character counts as two characters

in words

Example

Nick name

telephone number

Verification code

comments

Article title

Article abbreviated content (exceeding content is displayed as...)

dynamic rules

operate

Pull down to refresh

Loading (end of list/reaching the bottom)

profile picture

Link to profile page

General rules

20 items in the initial list, 20 items loaded each time

network anomaly

Prompt "Please check the network"

Input box

There is prompt content

"***" prompt after entering the content

How to write interactive instructions

Under what circumstances or which interfaces can you enter the login interface?

Which interface will you enter after logging in successfully?

Where to go after canceling login

Interface transition method, such as entering the interface from bottom to top and leaving the interface from top to bottom.

Account input box

Field format requirements, field length, category (Chinese characters, letters, numbers, mobile phone number)

Is there a default prompt copy? For example, if you logged in last time, will your last account be displayed?

Whether the cursor is placed in this input box, whether the keyboard is displayed, and which view the keyboard uses

When to detect whether the user fills in correctly, prompts for correct filling, incorrect prompts, and feedback prompts when they are displayed and when they disappear

Whether the content of the input box supports one-click clearing

Password input box

Field format requirements

When to check whether the format matches

Which view of the keyboard is displayed after the cursor is placed

Whether the content of the input box supports one-click clearing

Whether password visibility is supported and how to switch the visible state

Is it available or not? When is it available or not?

After clicking, it will prompt that you are logging in.

How to prompt for successful login and which interface to jump to?

There are several login failure scenarios (account not registered, network abnormality, etc.). How and when to prompt in different failure scenarios?

Whether the prompt method for multiple failed logins has been changed?

Which interface to click to enter

What is the interface jump method?

close button

Which interface to click to enter

What is the transition method of the interface?

Precautions

The prototype should draw the default state first, and then draw the effect after interaction (static rules first, then dynamic rules; normal first, then abnormal)

In order to prevent users from falling into deeper layers, a single process is generally required to jump up to three times (except for special circumstances), and common temporary views do not count.

When designing mandatory execution pages (such as mandatory registration), other jump exits are generally not provided to allow users to stay highly focused, form a logical closed loop, and reduce the occurrence of errors, but use with caution.

Weak execution processes (such as browsing, viewing details) can provide jump exits (such as sharing) to increase traffic

In the completion stage, you can generally set up a quick return to allow users to return from deeper levels faster.

Prototype Interaction Description

Practical examples

Personal center