Master the precise word combinations used when writing technical specifications and design documents in English. These collocations appear in RFCs, design docs, and requirements briefs.
0 / 5 completed
1 / 5
Before development starts, we need to ___ the requirements clearly in the technical spec.
We 'define requirements' in specification writing. 'Define' is the standard technical verb when formally establishing what something must do or be. 'Describe requirements' is also used but is less precise. 'Explain requirements' implies explaining to someone, not specifying them formally.
2 / 5
The spec must ___ all edge cases, including what happens when the API returns a null response.
We say a specification 'covers' edge cases, scenarios, or topics. 'Cover' means to include and deal with comprehensively. While 'address' works, 'cover edge cases' is the more natural collocation in documentation contexts.
3 / 5
We should ___ assumptions explicitly so that reviewers understand the scope of the design.
We 'state assumptions' in technical writing. 'State' is the formal verb for declaring something explicitly in a document. 'Express assumptions' is possible but more literary; 'say assumptions' is informal and not used in professional writing.
4 / 5
The engineering lead asked the team to ___ a draft spec by end of sprint so stakeholders could review it.
We 'write up a draft spec' — 'write up' means to put something into formal written form. All options are broadly possible, but 'write up' is the most natural collocation specifically for producing a document from notes or discussion. 'Produce a spec' is also professional.
5 / 5
During the review, the architect flagged that the spec failed to ___ the non-functional requirements adequately.
We 'capture requirements' in specification and product management English. 'Capture' means to accurately record something in a document. It is the dominant collocation: capture requirements, capture decisions, capture feedback. 'Record requirements' is also correct but less common in agile contexts.