Requirements document, which is actually quite complete

Hu Kunpeng

Requirements document, which is actually quite complete

2018.08.02 08:52:47

I remember that when LEARNING PRD document writing, I always hope to find a more comprehensive and detailed and easy to understand template. If you’ve ever had the same problem or haven’t yet come across a satisfactory answer, this may be a good reference.

(Before reading on, I want to ask: Why do I need to write a PRD document? Comments and discussions are welcome.

So, as usual, let’s flip the picture

Different companies, different teams or products have different requirements for PRD documents, and different PMS have different writing styles. This paper tries to be comprehensive and concise, and only gives a brief summary.

Let me write PRD like this. Ouch

Jane, it looks like this to me

In this paper, “Jian Shu” mobile terminal as an example, according to the above summary to write a simple PRD document framework, hoping to help fellow “Jian Shu” users better understand. (A PM rookie, Jane book new users, heavy document light analysis).

1. Version information

Brief the APP version information to indicate intent

2. Documentation

2.1 Document Overview

This document mainly describes the functional requirements of the APP and its design, aiming to clearly define the requirements details and logical flow of each module.

2.2 Document Reader

This document is mainly intended for the following readers: Developers, testers, product managers, market operation personnel, and management personnel of Jianshu APP project.

2.3 Technical Terms

Some technical terms can be explained here in advance (usually in table form) for later understanding, also see Appendix 8.4

Contents (omitted)

3. Product introduction

3.1 Product Positioning

Jianshu is committed to providing the best sharing experience, creating the best writing software for writers and the most elegant reading community for readers. “Communicate Stories, Communicate Ideas” is Jane’s slogan.

3.2 Product Features

Simple and elegant design, good communication atmosphere, rich article theme, Mardown rich text and other features

3.3 User Analysis

The main users are young people who like to share and communicate, love life and have literary atmosphere, and readers who like writing and want to deposit writing in the noisy network.

4. Product architecture

4.1 Product structure drawing

This article covers only the main modules and should be expanded to the smallest user visible unit.

Simple drawing of APP product structure

4.2 Information structure diagram

Information structure takes information as dimension, such as user information, user article information, user behavior information, etc., and product structure can be analyzed correspondingly, no longer stated.

4.3 Overall Flow Chart

The overall process illustrates the basic user behavior path of the product and facilitates product understanding.

Brief the overall flow chart of APP

5. Detailed function description

5.1 Function List

The function list provides an overview of function requirements and can be divided into module descriptions.

Sketch of APP function list

5.2 Prototype Interface

The description of requirements for each module function should include a detailed prototype interface diagram and flow chart as a simple diagram (reset password).

Schematic diagram of the prototype password reset APP

5.3 Use case flow

Simple book APP password reset flowchart

6. Non-functional requirements

6.1 Performance Requirements

1. Front-end content presentation should ensure smooth reading experience of users on WIFI and mobile networks;

2. The background information processing is stable and fast when thousands of users are online.

6.2 System Requirements

Compatible with All Versions of Android and IOS (including the latest version)

6.3 Operation Requirements

User/content management system development, user data analysis system development, etc

7. Project planning

Some projects or products do not include this section, but risk analysis and response strategies are usually explained.

8, the appendix

A large number of relevant reference documents can be appended to avoid excessive length of reading. This usually includes prototype /UI documentation, MRD/BRD documentation, technical documentation, and technical terminology.

As for the prototype of a simple product requirements document. Once again, this article is intended to provide a reference to the PPR document template. It is enough for you to remember the mind map at the beginning

Author: NetInSight

Link: https://www.jianshu.com/p/e89e97858be1

Source: Jane Book

Brief book copyright belongs to the author, any form of reprint please contact the author to obtain authorization and indicate the source.

Recommended readingMore highlights

• From 17.8.22 to 18.2.8 series on his writing every day A little bit of progress every day a little little little little little little little little little little little little little bit ~ ~ can only write a few words, from the start to imitate other people’s opinions, to now… That’s a handsome name
• Android – custom View postures for Android – View postures for Android passiontim
• One hundred dry goods shop | 22 actual combat dry goods, teach you ten steps to fix PRD document writing! (attached template) Welcome guests to another period of one Hundred dry goods shop ~ do you have such a time, in the product manager a little understanding of the stage, crazy anger fill online tutorials and dry goods? . User operation Notes
• Android NDK native method dynamic JNI reflection so file signature verification analysis before, about Android signature mechanism is a little… The wind clear vio
• Miscellaneous xing miscellaneous xing siesta only to wake up element qin, military blue blood is the original heart. Small bridge rustling day rain, and put a few feet of banana Yin. Flowers through the rain to send a small jasmine, wild cranes with the wind exhibition health ling. Fly into the jungle… Leaning on the sword in the clouds