A cognitive grammar to translate the ux research into requrements
"User centered design assumes that a research phase with a representative sample of the final users should be the basis for the definition of the functional and soft requirements of a project. How can we translate the results of the ux research into actionable requirements?
If you go to a gas station, you would be surprised if the station attendant were proposing you to refuel your car with wine instead of gasoline. This is because you have a schema of how your car works, and in such a schema, gasoline can not be substituted with wine. Those cognitive schemata helps us interpreting our world, interacting with it and organizing our behavior. Natural languages adapted to both our environment and the mental mechanisms that allow us to build, update and use our schemata.
If you, as a software developer, use a strongly typed language, then you know that you can not use a String when an Integer is required, just like you can not use wine instead of gasoline. Natural languages are *schema typed*: ""refuel my car with some wine"" is wrong just like *java.lang.Math.abs(""wine"")* is.
In my talk, I wish to give you some suggestions on how to informally analyse the verbal results of the ux research to identify the schemata, the ontologies, the taxonomies and the functions of your application."