6. Language and Style
6. Language and Style
← Formatting | Index | Next →
6.1 RFC 2119 Keywords
Use RFC 2119 keywords for requirement specification:
| Keyword | Meaning |
|---|---|
| MUST | Absolute requirement |
| MUST NOT | Absolute prohibition |
| REQUIRED | Equivalent to MUST |
| SHALL | Equivalent to MUST |
| SHALL NOT | Equivalent to MUST NOT |
| SHOULD | Recommendation |
| SHOULD NOT | Not recommended |
| RECOMMENDED | Equivalent to SHOULD |
| MAY | Optional |
| OPTIONAL | Equivalent to MAY |
Keywords MUST appear in ALL CAPITALS when used normatively.
6.2 Voice and Tense
| Rule | Description |
|---|---|
| Tense | Use present tense for describing system behavior |
| Voice | Use active voice where possible |
| Perspective | Avoid first person ("I", "we") |
| Subject | Refer to the system or specific components |
Correct: "The orchestrator executes nodes in dependency order."
Incorrect: "We will execute nodes in dependency order."
6.3 Technical Precision
| Rule | Description |
|---|---|
| Define first | Define terms before using them |
| Consistency | Use consistent terminology throughout |
| No synonyms | Avoid synonyms for technical terms |
| Reference glossary | Reference the glossary for definitions |
6.4 Objectivity
| Rule | Description |
|---|---|
| Facts | Present facts without advocacy |
| Trade-offs | Document trade-offs neutrally |
| Limitations | Acknowledge limitations explicitly |
| Tone | Avoid defensive or promotional language |
End of Section 6 — RFC Authoring Standards