Decision record templet wey dey use Planguage

Check https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf

Wetin be Planguage?

Planguage na planning language wey dey use dis keywords:

• Tag: Unique, persistent identifier
• Gist: Short summary of di requirement or area wey e address
• Requirement: Di text wey dey detail di requirement itself
• Rationale: Di reasoning wey justify di requirement
• Priority: Statement of priority and claim on resources
• Stakeholders: Parties wey di requirement materially affect
• Status: Di status of di requirement (draft, reviewed, committed, etc.)
• Owner: Di person wey responsible to implement di requirement
• Author: Di person wey write di requirement
• Revision: Version number for di statement
• Date: Di date of di most recent revision
• Assumptions: Anything wey fit cause problems if e no true now or later
• Risks: Anything wey fit cause malfunction, delay, or other negative impacts
• Defined: Di definition of one term (e better to use glossary)