DesignWIKI

Fil Salustri's Design Site

Site Tools


design:functional_requirement

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
design:functional_requirement [2021.05.18 13:53]
Fil Salustri
design:functional_requirement [2021.05.18 13:53] (current)
Fil Salustri [Specifying Functional Requirements]
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://www.boeing.com/|Boeing]] doesn't design cars, and [[http://www.ford.ca|Ford]] doesn't design airplanes. It is obvious that at a certain level, we will have some idea about the physical nature of the product. Planes don't look like cars; probably, they never will((Well, maybe not //never//.... {{youtube>EHXnLCIgNug}})). There are of course exceptions: consider the two telephones shown to the right.  Nonetheless, no FR should explicitly refer to a design intervention's physical characteristics. 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://www.boeing.com/|Boeing]] doesn't design cars, and [[http://www.ford.ca|Ford]] doesn't design airplanes. It is obvious that at a certain level, we will have some idea about the physical nature of the product. Planes don't look like cars; probably, they never will((Well, maybe not //never//.... {{youtube>EHXnLCIgNug}})). There are of course exceptions: consider the two telephones shown to the right.  Nonetheless, no FR should explicitly refer to a design intervention's physical characteristics.
  
-<imgcaption f2 right|Is this still a telephone?>{{ iphone4.jpg?300}}</imgcaption> 
-  
 So we can describe a FR as a sentence that takes the following form: "The product //does something//," where the //does something// part is a verb or verb clause describing an action or reaction of the product within its operating environment. So we can describe a FR as a sentence that takes the following form: "The product //does something//," where the //does something// part is a verb or verb clause describing an action or reaction of the product within its operating environment.
  
 +<imgcaption f2 right|Is this still a telephone?>{{ iphone4.jpg?300}}</imgcaption>
 + 
 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//.
  
design/functional_requirement.1621360396.txt.gz · Last modified: 2021.05.18 13:53 by Fil Salustri