\section{Introduction}

Engineering education and process improvement actions always stress the
importance of ''SMART''ness of requirements.
Table~\ref{tab:FFTSsmartList} shows the meaning of SMART.
The original use of this acronym was by George T. Doran, in an article about
management goals and objectives~\cite{article:WritingSmartManagementGoals}.
Today the acronym is mostly used to stress the {\bf specificity} and {\bf measurability},
the ''ART'' part is used in many variations as shown in this list.

\myTable{FFTSsmartList}{The meaning of SMART}

It is a sound advice to write product specifications with the SMART acronym in mind,
every violation is a potential problem. However it is also important to try to capture
and communicate the understanding on which these smartened specifications are based.
This understanding often deals with much more fuzzy issues.

By following one example it is shown which fuzzy inputs are provided in the beginning,
what the different stakeholder needs are and how these inputs can be transformed into
more SMART specifications.
