Planguage: Requirements Analysis

Background

Tom Gilb developed Planguage, a language driven by keywords that enables the writing of quantifiable, testable quality criteria. Planguage is intended to quantify qualitative claims in plans, specifications, and designs. Planguage offers numerous advantages, including being simple to learn, adaptable, small, and extensible, and preventing omissions by giving a uniform set of specifications for quality needs.

The inability to clearly define what is genuinely desired is one of the most frequent causes of project failure. This often begins at the requirements phase, where what is required should be apparent, but this is rarely the case. Weak requirements result in specifications, plans, and construction that fall short of the needs of the original client.

Creeping requirements are a second issue that stems from the first. It is considerably more straightforward for customers to change their opinions and expectations when those criteria are unclear. It is simpler to regulate if you clearly understand what is required.

Structure

PLAN [01-Oct 2023]: Full product release GIST: Develop ABC product ready for product release STAKEHOLDER [planning, final signoff]: Product Quality Manager AUTHORITY [final signoff]: Marketing Manager METER [Product]: Signed off acceptance by <those with final signoff> MUST [01-Sep 2012]: Partial product release WISH [01-Aug 2012]: Full product release Format (Keywords and Syntax) One element per line Keyword �tag� in capitals Tag qualifiers in [square brackets] Further description after colon : <angle brackets enclose fuzzy items that may need improving> Template GIST A short description to help understanding PLAN The level at which success can be claimed SCALE The scale of measurement used to quantify the statement METER The process or device used to measure using the SCALE MUST The minimum level required to avoid failure  STRETCH The best if everything goes perfectly WISH A desirable level of achievement RECORD The best-known achievement  PAST Previous results that may be used for comparison  TREND A set of historical data or extrapolation of this STAKEHOLDER  A person or organisation materially affected AUTHORITY The person, group or level of authorization allocated DEFINED The official definition of a term Summary Although this method is excellent for precise descriptions in the portions that need close attention (which is often more than is realised), a requirements document will often need more narrative than is offered by a Planguage style. Additionally, it is beneficial in legal agreements like contracts and proposals where parties may be held accountable for certain things. Precision is a key concept in Planguage. It makes you deliberate and define everything. It is also a useful facilitation tool that allows you to sit down with others and discuss their needs and thoughts. Most importantly, it provides you with a clear document that will result in a product of greater quality and sooner. Further Reading Gilb, Tom, A Handbook for Systems & Software Engineering Management using Planguage, Addison Wesley 2001 Gilb97a Gilb, Tom, Requirements-Driven Management: A Planning Language, Crosstalk, June 1997