This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
design:functional_requirement [2020.03.12 13:30] 127.0.0.1 external edit |
design:functional_requirement [2021.05.18 13:53] (current) Fil Salustri [Specifying Functional Requirements] |
||
---|---|---|---|
Line 3: | Line 3: | ||
A functional requirement (FR) specifies //how// product characteristics are manifested by a product; they describe what a product has //to do//. Verbs are commonly used to specify functional requirements.</ | A functional requirement (FR) specifies //how// product characteristics are manifested by a product; they describe what a product has //to do//. Verbs are commonly used to specify functional requirements.</ | ||
- | Function | + | Function |
===== What is a functional requirement? | ===== What is a functional requirement? | ||
Line 13: | Line 13: | ||
<WRAP tip> | <WRAP tip> | ||
// | // | ||
- | The behaviour of a spring is to deform elastically. | + | The behaviour of a spring is to deform elastically. |
- | The // | + | The // |
</ | </ | ||
Line 32: | Line 32: | ||
Notwithstanding the foregoing discussion, it is generally rather silly to specify FRs with no mention at all of the physical nature of the product. This is because we generally already have some idea of what the product will be and do. [[http:// | Notwithstanding the foregoing discussion, it is generally rather silly to specify FRs with no mention at all of the physical nature of the product. This is because we generally already have some idea of what the product will be and do. [[http:// | ||
- | Furthermore, | + | So we can describe a FR as a sentence that takes the following form: " |
< | < | ||
- | So we can describe a FR as a sentence that takes the following form: "The product //does something//," | ||
- | |||
All FRs must use **active verbs** - verbs that describe some kind of dynamic. In particular, the following verbs must **never** be used in FRs: //to have//, //to be//, and //to be able to//. | All FRs must use **active verbs** - verbs that describe some kind of dynamic. In particular, the following verbs must **never** be used in FRs: //to have//, //to be//, and //to be able to//. | ||
Line 47: | Line 45: | ||
* The product must display enlarged images. | * The product must display enlarged images. | ||
- | * The robot must orient parts on the ground at any angle. | + | * The robot must orient parts on the ground at any angle. |
* We can mention the " | * We can mention the " | ||
- | * Resist | + | * The product must resist |
- | * There are various equivalent English forms for expressing FRs; here, there is an implication that we are talking about "the product" | + | * There are various equivalent English forms for expressing FRs. One might ask: "To what degree should the product resist bending?" |
* Excess heat must be dissipated to the ambient air. | * Excess heat must be dissipated to the ambient air. | ||
* The container must hold hot liquids. | * The container must hold hot liquids. | ||
Line 63: | Line 61: | ||
* Minimize material costs. | * Minimize material costs. | ||
* Cost is not a product function. And it clearly is an instruction to the designers, not about the product. | * Cost is not a product function. And it clearly is an instruction to the designers, not about the product. | ||
+ | * Cost can be represented as a constraint. | ||
* It must be possible to pour hot liquids into the cup. | * It must be possible to pour hot liquids into the cup. | ||
* This is a passive statement, more descriptive of the cup's user (which is part of the environment) than of the cup itself. | * This is a passive statement, more descriptive of the cup's user (which is part of the environment) than of the cup itself. |