Product Requirements Documents (PRDs) are a common tool for getting product teams on the same page at the beginning of product development cycles. Typically written by marketing, PRDs seek to lay out what functions a product must have in order to be competitive at launch in 2-3 years. As with any future prediction, it involves many assumptions about technologies, markets, and use cases. [1]
[1] By Robin Harris on ZDNet