Seilevel Partners LP
Writing Good Requirements
In this class, the focus is on how to write good requirements – the characteristics of good requirements and how to turn bad into good. It covers how to turn an implementation or operational statement into a requirement. It covers other data you need, such as rationale, in order to make understanding requirements easier over the project life cycle. It discusses types of requirements – functional, performance, reliability, etc. Theory is turned into practice using a set of exercises designed to give participants hands-on practice in identifying common errors in writing requirements. Students work as teams to determine problems with requirements - terminology, ambiguous terms, stating implementation and operations as opposed to requirements, and level distinctions. Examples of how to rewrite implementation and operational requirements as verifiable requirements are shown. Students are given a project scope and operational concepts and then perform a team exercise to define a set of requirements. Management of data relevant to requirements - rationale, traceability, allocation, and others are discussed.