Skilirium

Distinguishes functional from non-functional requirements

E-951 · Knowledge knobit · Activity: Define technical requirements · Competence: Product management · Also needed in UX design, Delivery coordination

A functional requirement states what the system does for a trigger; a non-functional one states how well (performance, accessibility, freshness, security) and needs a threshold to be testable.

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: A functional requirement states what the system does for a trigger; a non-functional one states how well (performance, accessibility, freshness, security) and needs a threshold to be testable.

How it is assessed: Answers a written question on the functional and non-functional requirement correctly

Related knobits

Needed for

All 3 knobits of Define technical requirements.

Source: knowledge the ESCO skill 'define technical requirements' applies in DO process activities P2.1, P6.2; ISPMA Software Product Management Body of Knowledge; not checked against a reference text