Specifies the functional requirements of a page type or feature
Requirements that each state a trigger, the behaviour and the observable result
Can AI do this?
Not tested yet
No AI benchmark covers this knobit yet. New results are announced in the Can AI Do the Job? newsletter.
What it looks like in practice
Expected result: Requirements that each state a trigger, the behaviour and the observable result
How it is assessed: Each requirement has one behaviour and an acceptance test, and none prescribes the implementation
Related knobits
Builds on
- K-152 Distinguishes a business requirement from a design solution
- E-951 Distinguishes functional from non-functional requirements
All 3 knobits of Define technical requirements.
Source: ESCO skill 'define technical requirements' (ESCO v1.2.1); DO process activities P2.1, P6.2; ISPMA Software Product Management Body of Knowledge; the assessment criterion is this register's own and is in no reference text