Product Requirement

Product requirements document From Wikipedia, the free encyclopedia A Product Requirements Document (PRD) is a document containing all the requirements to a certain product. It is written to allow people to understand what a product should do. A PRD should, however, generally avoid anticipating or defining how the product will do it in order to later allow engineers to use their expertise to provide the optimal solution to the requirements. PRDs are most frequently written for software products, but can be used for any type of product and also for services. Typically, a PRD is created from a user's point-of-view by a user/client or a company's marketing department (in the latter case it may also be called Marketing Requirements Document (MRD)). The requirements are then being analysed by a (potential) maker/supplier from a more technical point-of-view, broken down and detailed in a Functional Specification (sometimes also called Technical Requirements Document). Components Typical components of a product requirements document (PRD) are: Title & author information Purpose and scope, from both a technical and business perspective Stakeholder identification Market assessment and target demographics Product overview and use cases Requirements, including functional requirements (e.g. what a product should do) usability requirements technical requirements (e.g. security, network, platform, integration, client) environmental requirements support requirements interaction requirements (e.g. how the product should work with other systems) Assumptions Constraints High level workflow plans, timelines and milestones (more detail is defined through a project plan) Evaluation plan and performance metrics Not all PRDs have all of these components. In particular, PRDs for other types of products (manufactured goods, etc.) will eliminate the software-specific elements from the list above, and may add in additional elements that pertain to their domain, e.g. manufacturing requirements. See also Marketing requirements document Product planning Product architect Product management Requirements Product requirements document - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Product_requirements_document 1 of 2 5/31/2015 11:28 AM

Upload
navee-naveen
Category

Documents
view
229
download
0

Embed Size (px):

description

Project Use

Transcript of Product Requirement

Product requirements documentFrom Wikipedia, the free encyclopedia

A Product Requirements Document (PRD) is a document containing all the requirements to a certain product.It is written to allow people to understand what a product should do. A PRD should, however, generally avoidanticipating or defining how the product will do it in order to later allow engineers to use their expertise toprovide the optimal solution to the requirements.

PRDs are most frequently written for software products, but can be used for any type of product and also forservices. Typically, a PRD is created from a user's point-of-view by a user/client or a company's marketingdepartment (in the latter case it may also be called Marketing Requirements Document (MRD)). Therequirements are then being analysed by a (potential) maker/supplier from a more technical point-of-view,broken down and detailed in a Functional Specification (sometimes also called Technical RequirementsDocument).

Components

Typical components of a product requirements document (PRD) are:

Title & author informationPurpose and scope, from both a technical and business perspectiveStakeholder identificationMarket assessment and target demographicsProduct overview and use casesRequirements, including

functional requirements (e.g. what a product should do)usability requirementstechnical requirements (e.g. security, network, platform, integration, client)environmental requirementssupport requirementsinteraction requirements (e.g. how the product should work with other systems)

AssumptionsConstraintsHigh level workflow plans, timelines and milestones (more detail is defined through a project plan)Evaluation plan and performance metrics

Not all PRDs have all of these components. In particular, PRDs for other types of products (manufacturedgoods, etc.) will eliminate the software-specific elements from the list above, and may add in additionalelements that pertain to their domain, e.g. manufacturing requirements.

See also

Marketing requirements documentProduct planningProduct architectProduct managementRequirements

Product requirements document - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Product_requirements_document

1 of 2 5/31/2015 11:28 AM

Requirements managementUser requirements document

References

Retrieved from "http://en.wikipedia.org/w/index.php?title=Product_requirements_document&oldid=662576723"

Categories: Marketing Software requirements

This page was last modified on 16 May 2015, at 11:58.Text is available under the Creative Commons Attribution-ShareAlike License; additional terms mayapply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registeredtrademark of the Wikimedia Foundation, Inc., a non-profit organization.

Product requirements document - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Product_requirements_document

2 of 2 5/31/2015 11:28 AM