method : parameter --> result (or exeption) invocation of services may be
interfacing : method call --> coded client coded object may be
behavior : state --> services
For interface design according (4) we may check, if the service specification underlying their invocation signifies its implementation as coded object such, that the intended items become public and visible, this is: signified, as far and only as far as the performing operation requires.
Looking for the sign components for a coded object by applying questions accordingly, we may obtain
|(5)||Apply the operation needed :|
|set up any of its properties -->|
|creation of the required object|
The creation of a required object should answer the question: what properties are to set up if an operation needed is applied? Any components may be checked: is their relation to other components realized clearly and distinctly when composing a triadic sign relation? Are their concepts recognized at all?
By applying the sign characterization to any of the determined components their realizability and recognizability are categorized. Sign characterization may be applied to all components including the aesthetic design of interface components. For further details of applying characteristics see ( Haller, 1999).
Bense, M. ( 1983). Das Universum der Zeichen. Baden-Baden: Agis-Verlag.
Walther, E. ( 1979). Allgemeine Zeichenlehre. Stuttgart: DVA.
Haller, R. ( 1999). Zeichen im Zusammenhang. Universität Stuttgart: Diss.