Foreword
In the product development process, "requirements document" and "needs analysis" and "requirements specifications" is the product development supporting documentation, is essential. Unfortunately, not only the layman can not distinguish silly, sometimes related practitioners and even deified product manager also could not tell. What causes the differences and doubts it? Three kinds of file name contains a demand, to what extent the definition needs to? Next, you need to uncover Past and Present misty veil.
I believe the need for clear documentation and requirements analysis and the difference between the role of the three reports and requirements specification, this problem can be solved.
Between the three types
Software Product Requirements Document
Software Product Requirements Document: Product Requirements Document (PRD) is a business requirements document (BRD) and Market Requirements Document (MRD) is described with more professional language, is a business unit of the proposed demand for professional language description file.
This document is a product from the project into the "conceptualization" stage to the "drawing" of the most important stage of a document. Of course, this definition is aimed at a completely new product. Broadly speaking, the description of the product demand, should include strategic and tactical products and strategic means: product positioning, target market, target audience, competitors and so on. Tactical refers to the product structure, the core business processes, described with specific functional description & like.
The main use of the object PRD are: development, testing, project managers, interaction designers, operators and other service personnel. According to PRD developers can learn the logic of the entire product; test cases can be built according to PRD; project managers can PRD split the work packages and assign developers; interaction designers can interactively design details by PRD. PRD is the most important document before the start of the project must be determined by the review.
demand analysis
Requirements Analysis: requirements analysis, also known as software requirements analysis, system analysis needs analysis or requirements engineering, is a developer of an intensive research and analysis, an accurate understanding of the specific requirements of the user and project features, performance, reliability, user non-expressed in the form of demand into a complete requirements definition, to determine what the system must do the process.
Needs analysis mainly for business and users, focusing on the business logic of the system to be solved to achieve the function described clearly broader. Usually the first demand analysis report, after the requirements specification.
Software requirements specification
Software requirements specification: SRS (Software Requirements Specification), the preparation of software requirements specification is to enable users and software developers both sides have a common understanding of the provisions of the original software, making it the basis for the entire development effort. Including hardware, functionality, performance, input and output, interface requirements, warning information, secret security, data and databases, documents and regulatory requirements, and so on.
Often oriented design requirements specification, developers, focusing on the restraint system, inputs, outputs and processes are clearly defined, more specifically, in more detail. However, due to technical thinking, develop popular on the market fast iterative, agile development and agile testing can not wait to write requirements specifications, get the prototype began development work, subsequent supplementary requirements specification only as the basis for product acceptance. (Technical thinking fast iterative, agile development and agile testing generally applicable to high technology is mature, and experienced R & D team, a solid basic skills, we can not stick to the form)
So the requirements document needs analysis and reporting as well as the link between the three requirements specifications and what kind of it? In fact, people are confused between the three is in the primary stage of development of software technology and software technology popularization stage, R & D units located at different periods in the principal contradiction caused.
Three links
The primary stage of development of software technology, most of the R & D units do not have the software research and development capabilities, how to do? Without the ability to develop a single, R & D department staffing incomplete, so he had to find a team with technical research and development capabilities are in the form of complete outsourcing of research and development. Party responsible for collating demand the responsibility of the business sector proposed the formation of business requirements document (BRD) and Market Requirements Document (MRD), B docking sorting out the Requirements Document (PRD), according to the analyst needs B "requirements document" finishing " needs analysis ", research and development manager, based on B" requirements document "and" needs analysis "sort out" requirements specifications. "
Software technology to be popular today, some of the R & D units have adequate financial and human resources for independent research and development. R & D units with independent research and development capabilities, the case of department staffing is complete, the business unit responsible for providing business requirements document (BRD) and Market Requirements Document (MRD) product manager in charge of sorting out the Requirements Document (PRD), the project manager responsible for the "demand analysis report ", R & D manager is responsible for providing" requirements specifications. "
R & D work, dealing with the needs of most of that person is the product manager, product classmates, you understand the differences and connections between all of these needs with the wording of the document it?
With the rise of the Internet economy, product manager became a hot term, and even deified, due to our lack of understanding of the product manager's job content and placed more expectations. In addition to product manager with professional skills, should also have the theoretical knowledge of the market, such as the theory of 4P, 4C theory, SMART principle, Boston Matrix, Ansoff matrix, SWOT analysis, product manager for the Internet of the future will not only need to develop products work the skills and techniques, but also realized the need to develop the ability of products, such as strategic planning, product definition, marketing programs and so on. Product manager is a person's overall quality has, instead of an all-powerful God, I believe there will be more books in the subsequent professional to help you analyze and interpret, let the dust settles.
Product managers face complex problems in practice, how to clarify the circumstances surrounding the find to break the law? By "King Kong" is to give you a Heart: Yunhe should live, Yunhe surrender their hearts. Should Wusuo Zhu, born of their heart.