You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2022. It is now read-only.
There are a range of best practices for writing a good requirement. One version is:
After one year of level-2 usage, the battery-life, MUST, last 10 hours, when running level-3 applications.
{Condition} the {subject} {compliance} {verb} {object} {qualification}
Tasks
@camerons has developed a requirement-writing guide within Google, and has obtained legal approval to release this material to The Good Docs Project. @camerons to copy the material into github.
Possibly add a simple template file, to complement the guide.
Review the material and possibly refine to align with style practices within The Good Docs Project.
Create requirement-writing guide
Template description
There are a range of best practices for writing a good requirement. One version is:
Tasks
Helpful resources
The text was updated successfully, but these errors were encountered: