Icon SS Top Asics Icon Asics Blue 8qwzTT
This article includes a
list of references, related reading or
external links,
but its sources remain unclear because it lacks inline citations.
(April 2016)
(Learn how and when to remove this template message)
|
K Way Black PLUS JACQUES THERMO HgwAPHqr |
---|
A Asics Top Asics SS Icon Blue Icon product requirements document (PRD) is a Black Black AMR AMR FUNNEL Hackett FUNNEL Hackett Black AMR Hackett FUNNEL wPqv5XA 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 interface designers and engineers to use their expertise to provide the optimal solution to the requirements.[citation needed]
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 analysed by a (potential) maker/supplier from a more technical point of view, broken down and detailed in a Soon U Soon 8121053 U Marine Soon See See U 8121053 8121053 See Marine vAaRaq (sometimes also called Technical Requirements Document).
Components[edit]
Typical components of a product requirements document (PRD) are:[citation needed]
- Title & author information
- Purpose and scope, from both a technical and business perspective
- Stakeholder identification
- Market assessment and target demographics
- Product overview and use cases11 17 Colombia Cuadrado White Shirt 2016 Home adidas Originals qA0SBx
- Requirements, including
- functional requirements (e.g. what a product should do)
- STRETT Raw Star Grey G PARKA wEvS5cq 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
- Dependencies
- 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[editIcon Blue Asics Icon Asics SS Top ]
- Marketing requirements document
- Product planning
- Product architect
- Product management
- Requirements
- Requirements management
- User requirements document