P.R.D. Samples
P.R.D. (Proposal, Requirements, Design) is a documentation process I learned while at Monolith. I like to think of it as a buy-in process.
The proposal is an overview of the feature being created and the rationale behind it. This allows others to comment on whether the system is needed, already exists, and/or requires global changes.
In the requirements document objectives for the new feature are described in detail. This document provides a focused and well-articulated framework that allows team members to provide feedback on changes and additions without encumbering the feature with unnecessary functions.
The design document brings the feature to the engineering level where implementation and it’s implications on areas such as memory, CPU, and serialization are discussed.
Together these documents provide a comprehensive description of the feature that allows team members to comment effectively before implementation.
Note: All samples were authored by me while working at Loose Cannon Studios and have been ok'ed for public view by Matt Scott, Loose Cannon Studios owner.