view release on metacpan or  search on metacpan

t/expected-sample-pbib.rtf  view on Meta::CPAN

{\*\bkmkstart _Hlt17184583}{\*\bkmkend _Hlt17184583}}{\field{\*\fldinst {\insrsid12989836  STYLEREF 1 \\s }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 4}}}{\insrsid12989836 \_}{\field{\*\fldinst {\insrsid12989836  SEQ Figure \\* ARABIC \...
}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 2}}}{\insrsid12989836 {\*\bkmkend fBasicModels}. Dependencies between data, application, user-interface, environment, and intera}{\insrsid12989836 c}{\insrsid12989836 tion model
{\*\bkmkend _Toc19764591}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 The }{\i\insrsid12989836 data model}{\insrsid12989836 
 specifies the kind of data the users can create and interact with. To work with data, a }{\i\insrsid12989836 application}{\insrsid12989836  provides the necessary
 functionality. These two models are independent of the currently used or supported hardware device. Instead, available devices and other relevant parts of the enviro}{\insrsid12989836 n}{\insrsid12989836 ment are described by the }{\i\insrsid1298983...
environment model}{\insrsid12989836 . The }{\i\insrsid12989836 user-interface model}{\insrsid12989836  defines the framewo
rk for how the applications can be presented to the user, taking into account the properties of the environment model. These models are not applicable for ubiquitous computing applications only. Yet, due to the heterogeneous environment in which they...
ate, they have a strong need for a clear structure that gives the flexibility to adapt different components independently for different situations.
\par In the following, these five models are presented in more detail, including their relationship to the pr}{\insrsid12989836 e}{\insrsid12989836 viously identified requirements. Concrete examples of how these models have been applied are given a}{...
\insrsid12989836 f}{\insrsid12989836 {\*\bkmkstart _Ref517456041}terwards.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc2659658}{\*\bkmkstart sDataMo...
}{\*\bkmkstart _Toc19764437}{\*\bkmkend _Ref517456041}Data Model{\*\bkmkend _Toc2659658}{\*\bkmkend sDataModelConcept}{\*\bkmkend _Toc19764437}: Information Objects
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
It is a very common approach in application modeling to separate the application model from the data or domain model ({\field{\*\fldinst { HYPERLINK \\l VisualWorksUsersGuide}}{\fldrslt {ParcPlace-Digitalk, Inc., 1995}}}; {\field{\*\fldinst { HYPERLI...
 identified by {\field{\*\fldinst { HYPERLINK \\l JacobsonOOSE}}{\fldrslt {Jacobson {\i et al.} (1992)}}}, while the application model repr}{\insrsid12989836 e}{\insrsid12989836 sents the }{\i\insrsid12989836 behavior dimension}{\insrsid12989836 . Th...
\insrsid12989836 e}{\insrsid12989836 used independently.
\par Different applications can be specified and implemented for one kind of data. This can save much time if the current application domain has complex data structures or algorithms. On the other hand, applic}{\insrsid12989836 a}{\insrsid12989836 
tion models can be reused for different kinds of data, if the interface between the application and the data has been defined very carefully at an appr}{\insrsid12989836 o}{\insrsid12989836 priate level of abstraction.
\par The data model defines the classes and functionality of all objects that can be part of a document. A}{\insrsid12989836 c}{\insrsid12989836 cor
ding to an object-oriented view, data objects combine document state with methods to change the state. In the context of cooperative work (req. }{\field{\*\fldinst {\insrsid12989836  REF qCollaboration \\h  \\* MERGEFORMAT }{\insrsid12989836 
{\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000f000000710043006f006c006c00610062006f0072006100740069006f006e000000}}}{\fldrslt {\insrsid12989836 C\_1}}}{\insrsid12989836 ), it makes sense to choose a fine-grained model to gain more ...
ibility in defining different aspects of collaboration, like the degree of coupling (req. }{\field{\*\fldinst {\insrsid12989836  REF qFlexibleCoupling \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b020000000800000012000000710046006c0065007800690062006c00650043006f00750070006c0069006e0067000000}}}{\fldrslt {\insrsid12989836 C\_2}}}{\insrsid12989836 
). In ({\field{\*\fldinst { HYPERLINK \\l DragonflyArchitecture}}{\fldrslt {Anderson {\i et al.}, 2000}}}) the model facet represents the data model.
\par Following an object-oriented approach, the data model will usually consist of a network of multiple connected objects. For hypertext-like documents, e.g., it is popular to define one main containment hiera}{\insrsid12989836 r}{\insrsid12989836 
chy with additional connections defined by hyperlinks.
\par Depending on the actual application, data objects are not restricted to represent what is classically seen as a \'93document\'94
. In ({\field{\*\fldinst { HYPERLINK \\l PlacelessDocGeneralitySpecificity}}{\fldrslt {Edwards and LaMarca, 1999}}}) a much broader view on documents is described. If, for instance, physical devices, people, or tasks are also treated as special kinds...
, a uniform interface can be used. The term \'93domain model\'94, which is sometimes also used for the concept of a data model ({\field{\*\fldinst { HYPERLINK \\l VisualWorksUsersGuide}}{\fldrslt {ParcPlace-Digitalk, Inc., 1995}}}; {\field{\*\fldinst...
 documents. Although this term can be used interchangeably with \'93data model\'94, this paper uses the latter term in order to provide a clearer contrast with the application model.
\par Looking at the example of the Passage system, the data model covers all objects that should be attached to and carried with a passenger object. The implementation described below (see section }{\field{\*\fldinst {\insrsid12989836  REF sPassageIm...
h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000007300500061007300730061006700650049006d0070006c000000}}}{\fldrslt {\insrsid12989836 6}}}{\insrsid12989836 
) supports the generic document elements provided by the BEACH framework, but also new document elements d}{\insrsid12989836 e}{\insrsid12989836 fined by other BEACH modules.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart sApplicationModelConcept}
{\*\bkmkstart _Hlt19161511}{\*\bkmkstart _Toc19764438}{\*\bkmkend _Hlt19161511}Application Model{\*\bkmkend sApplicationModelConcept}{\*\bkmkend _Toc19764438}: Application Behavior
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
Application models are used to describe all application aspects such as manipulation of data objects. As application models define the }{\i\insrsid12989836 behavior}{\insrsid12989836  of the application, they specify control objects 
as defined in ({\field{\*\fldinst { HYPERLINK \\l JacobsonOOSE}}{\fldrslt {Jacobson {\i et al.}, 1992}}}).
\par For a \'93text\'94 object, the data model includes the string describing the text and text attributes like font or size. The application model adds the editing state for text, for instance, cursor position or selection.
\par Further, it can specify the degree of coupling between different users, i.e. it controls which parts of the editing state are shared by which users, and where private values are allowed. The workspace applic}{\insrsid12989836 a}{\insrsid12989836...
tion model, e.g., allows specifying different rotations of the workspace for two users working at an interactive table (see req. }{\field{\*\fldinst {\insrsid12989836  REF qDifferentFormsOfInteraction \\h  \\* MERGEFORMAT }{\insrsid12989836 {\*\dataf...
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710044006900660066006500720065006e00740046006f0072006d0073004f00660049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 H\_1}}}{\insrsid12989836 
), while all other properties are tightly coupled.
\par To be able to use different application models for the same data model, the data model has to be u}{\insrsid12989836 n}{\insrsid12989836 aware of any application model and represent document state only.
\par It has proven helpful to choose a rather fine granularity for some application models. This way, low-level application models with a well-defined functionality (e.g
. to edit a simple text) can be aggregated to form more complex models at a higher level of abstraction (e.g. an editor that can manage complete workspaces). Usually, a whole hierarchy of application models composed of generic, reusable parts and cus...
arts constitute an application ({\field{\*\fldinst { HYPERLINK \\l COASTModel}}{\fldrslt {Schuckmann {\i et al.}, 1999}}}). This way, the application model often forms a hierarchy that is isomorphic to the containment hierarchy of its assoc}{\insrsid...
\par Using small application models turns out to foster a new conception of what is regarded as an applic}{\insrsid12989836 a}{\insrsid12989836 tion. The application model is seen as a description of }{\i\insrsid12989836 additional}{\insrsid12989836 ...
 semantics for a data model, instead of the conventional approach of seeing data as a \'93supplement\'94 to be edited by applications. It therefore leads to an }{\i\insrsid12989836 information-centric}{\insrsid12989836 
 perspective on application models ({\field{\*\fldinst { HYPERLINK \\l iRoomVisualInstruments}}{\fldrslt {Winograd and Guimbretière, 1999}}}).
\par The Passage system, e.g., defines no new application model. Instead, it reuses the application models that are available for the data objects being attached
 to passengers. In fact, it associates the application model with a passenger object (in contrast to creating an association between passenger and data o}{\insrsid12989836 b}{\insrsid12989836 ject) as shown in figure }{\field{\*\fldinst {\insrsid1298...
 REF fPassageClasses \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b0200000008000000100000006600500061007300730061006700650043006c00610073007300650073000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 6}{
\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 3}}}{\insrsid12989836  below. This way, the current editing state (e
.g. selections, cursor position etc.) can be transferred using Passage; this allows users to go to another roomware component and co}{\insrsid12989836 n}{\insrsid12989836 tinue working there at exactly the same state.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart sUIModelConcept}{\*\bkmkstart _To...
{\*\bkmkstart _Toc19764439}User-Interface Model{\*\bkmkend sUIModelConcept}{\*\bkmkend _Toc2659659}{\*\bkmkend _Toc19764439}: Interface Elements
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 As traditional operating and window
 management systems have been designed for use with a trad}{\insrsid12989836 i}{\insrsid12989836 
tional desktop PC, the interface they offer has drawbacks when used with devices not having a mouse and keyboard or having different forms and sizes. For instance, if a menu bar is always at the to
p of the screen, it might be hard to reach at a wall-size display ({\field{\*\fldinst { HYPERLINK \\l PierLocationIndepInterfaces}}{\fldrslt {Pier and Landay, 1992}}}). Toolbars can take up a lot of pr}{\insrsid12989836 e}{\insrsid12989836 cious scre...
\par Therefore, the user interface aspects have to be separated from information and behavior of applic}{\insrsid12989836 a}{\insrsid12989836 tions. This is related to the }{\i\insrsid12989836 interface dimension}{\insrsid12989836 
 identified by {\field{\*\fldinst { HYPERLINK \\l JacobsonOOSE}}{\fldrslt {Jacobson {\i et al.} (1992)}}}. However, the BEACH conceptual model further distinguishes the }{\i\insrsid12989836 user interface}{\insrsid12989836  from the }{\i\insrsid12989...
, to allow accessing a shared user interface wit
h different modalities and different devices. The user interface model defines the components that are available in the user interface, while the interaction model specifies how they are presented and modified.
\par In the case of the Passage system, the user interface is rather simple; it consists of the virtual part of the bridge. The }{\i\insrsid12989836 virtual}{\insrsid12989836 
 part of the bridge is displayed on a roomware component whenever a passenger is detected on the }{\i\insrsid12989836 physical}{\insrsid12989836  part of the bridge (see figure }{\field{\*\fldinst {\insrsid12989836  REF fPassagePicture \\h }{
\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b0200000008000000100000006600500061007300730061006700650050006900630074007500720065000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 3}{\insrsid12989836 \_}{
\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 ).
\par The user-interface model allows one to define alternative user-interface concepts suitable for different interaction devices (req. }{\field{\*\fldinst {\insrsid12989836  REF qDifferentFormsOfInteraction \\h  \\* MERGEFORMAT }{\insrsid12989836 
{\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710044006900660066006500720065006e00740046006f0072006d0073004f00660049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 H\_1}}}{\insrsid12989836 
). Multiple-computer devices (req. {\*\bkmkstart _Hlt517580772}}{\field{\*\fldinst {\insrsid12989836  REF qCompositeRoomwareComponents \\h  \\* MERGEFORMAT }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710043006f006d0070006f00730069007400650052006f006f006d00770061007200650043006f006d0070006f006e0065006e00740073000000}}}{\fldrslt {\insrsid12989836 U\_2}}}{\insrsid12989836 {\*\bkmkend _Hlt5175...
}) and multi-device interaction (req. }{\field{\*\fldinst {\insrsid12989836  REF qMultipleDeviceInteraction \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001b00000071004d0075006c007400690070006c00650044006500760069006300650049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 UH\_2}}}{\insrsid12989836 
) make it necessary to have user interface elements that can be distributed and shared among di}{\insrsid12989836 f}{\insrsid12989836 ferent devices (see below).
\par By explicitly modeling an appropriate user-interface, all issues related to the hardware and physical environment can be addressed at one point, allowing applications and documents to be d}{\insrsid12989836 e}{\insrsid12989836 vice-independent.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart sPhysicalModelConcept}
{\*\bkmkstart _Toc2659660}{\*\bkmkstart _Toc19764440}Environment Model{\*\bkmkend sPhysicalModelConcept}{\*\bkmkend _Toc2659660}{\*\bkmkend _Toc19764440}: Context Awareness
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 One major property of ubiquitous c
omputing environments is the heterogeneity of the available d}{\insrsid12989836 e}{\insrsid12989836 vices. In order to provide a coherent user experience ({\field{\*\fldinst { HYPERLINK \\l DisappearingUICoherenceScope}}{\fldrslt {Prante, 2001}}}), t...
system must have a deeper understanding of the physical space\'94 ({\field{\*\fldinst { HYPERLINK \\l EasyLivingTechnologies}}{\fldrslt {Brummit {\i et al.}, 2000}}}). This raises the need for an adequate model of the application\rquote s physical en...
\par Therefore, the environment model is the representation of }{\i\insrsid12989836 relevant}{\insrsid12989836  parts of the \'93real\'94 world. On one hand, this includes a description of which devices are used, how they are configured, and which ca...
\insrsid12989836 a}{\insrsid12989836 bilities they have. This is the direct }{\i\insrsid12989836 hardware environment}{\insrsid12989836 , which can be employed by the user-interface model to adapt to different devices (req. }{\field{\*\fldinst {
\insrsid12989836  REF qDifferentFormsOfInteraction \\h  \\* MERG}{\insrsid12989836 E}{\insrsid12989836 FORMAT }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710044006900660066006500720065006e00740046006f0072006d0073004f00660049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 H\_1}}}{\insrsid12989836 
). This part corresponds to the platform model defined by the Plasticity framework ({\field{\*\fldinst { HYPERLINK \\l PlasticityFrameworkAgenda}}{\fldrslt {Thevenin and Coutaz, 1999}}}), or Aura\rquote s notion of enviro}{\insrsid12989836 n}{\insrsi...
\par In addition, other aspects can be included if they can influence the behavior of the software. Necessa}{\insrsid12989836 r}{\insrsid12989836 ily, it has
 to be possible to measure their relevant properties with sensors. Depending on detected changes in the }{\i\insrsid12989836 physical environment}{\insrsid12989836 , further actions can be triggered to reflect the current situation (req. }
{\field{\*\fldinst {\insrsid12989836  REF qDynamicConfiguration \\h  \\* MERGEFORMAT }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b0200000008000000160000007100440079006e0061006d006900630043006f006e00660069006700750072006100740069006f006e000000}}}{\fldrslt {\insrsid12989836 U\_4}}}{\insrsid12989836 ).
\par The Passage system is an example of how to react upon changes in the physical environment. As me}{\insrsid12989836 n}{\insrsid12989836 
tioned, the virtual part of the bridge is shown as soon as a physical object is detected on the physical part of the bridge. Thus, Passage needs to keep a repres
entation of the detected physical objects and the location (esp. bridge) where they have been sensed (fig. }{\field{\*\fldinst {\insrsid12989836  REF fPassageClasses \\h }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b0200000008000000100000006600500061007300730061006700650043006c00610073007300650073000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 6}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 ...
\insrsid12989836 ). This is part of the environment model. Additio}{\insrsid12989836 n}{\insrsid12989836 ally, the sensors used for detecting physical objects belong to the environment model as well.
\par Besides the physical environment, other contextual information \endash  such as the current task, project, or presence of co-workers \endash  could influence the behavior of the software, so long as this information is available to the applica
tion. This part refers to the }{\i\insrsid12989836 logical context}{\insrsid12989836  of the application.
\par Software with functionality depending on physical objects and their properties, or other aspects of the user\rquote s environment (req. {\*\bkmkstart _Hlt536717755}}{\field{\*\fldinst {\insrsid12989836  REF qContextAwareness \\h  \\* MERGEFORMAT...
\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b020000000800000012000000710043006f006e007400650078007400410077006100720065006e006500730073000000}}}{\fldrslt {\insrsid12989836 U\_3}}}{\insrsid12989836 {\*\bkmkend _Hlt536717755}) is ca...
}{\i\insrsid12989836 context-aware }{\insrsid12989836 
({\field{\*\fldinst { HYPERLINK \\l ContextToolkitAppDevelopment}}{\fldrslt {Salber {\i et al.}, 1999}}}). There is a strong need for context-aware applications in ubiquitous computing environments, as the large number of available devices, services,...
\insrsid12989836 r}{\insrsid12989836 action becomes too high. An environment designed to support the users needs, needs to aim at }{\i\insrsid12989836 implicit}{\insrsid12989836 
 interaction ({\field{\*\fldinst { HYPERLINK \\l SchmidtImplicitHCI}}{\fldrslt {Schmidt, 2000}}}). This can be accomplished by using changes in the real world\rquote s state to trigger software functionality.}{\cs31\super\insrsid12989836 \chftn {\foo...
\s32\qj \fi-144\li144\ri0\sa80\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin144\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\cs31\super\insrsid12989836 \chftn }{\insrsid12989836  However
, using detected context to trigger functionality always has the danger of relying on misinte}{\insrsid12989836 r}{\insrsid12989836 preted information, which can be very annoying for users.}}}{\insrsid12989836  T
herefore, the environment model must be capable of expres}{\insrsid12989836 s}{\insrsid12989836 ing relevant information, such as spatial relationships between physical objects.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart sInteractionModelConcept}
{\*\bkmkstart _Toc2659661}{\*\bkmkstart _Toc19764441}Interaction Model{\*\bkmkend sInteractionModelConcept}{\*\bkmkend _Toc2659661}{\*\bkmkend _Toc19764441}: Presentation and Interaction
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 To be able to support different styles of interaction (req. }{\field{\*\fldinst...
\insrsid12989836  REF qDifferentFormsOfInteraction \\h  \\* MERGEFORMAT }{\insrsid12989836 {\*\datafield 
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710044006900660066006500720065006e00740046006f0072006d0073004f00660049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 H\_1}}}{\insrsid12989836 , }{\field{\*\fldins...
\insrsid12989836  REF qPhysInteraction \\h  \\* MERGEFORMAT }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b0200000008000000110000007100500068007900730049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 ...
}}}{\insrsid12989836 ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software a}{\insrsid12989836 r}{\insrsid12989836 chitecture, and should not be confused with the \'93
interaction model\'94 describing the \'93look and feel\'94 of a user interface at a conceptual level as defined by {\field{\*\fldinst { HYPERLINK \\l BeaudouinLafonPostWIMPModel}}{\fldrslt {Beaudouin-Lafon (2000)}}}. I}{\insrsid12989836 n}{\insrsid12...
interaction model\'94 described by {\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary (1995)}}}.
\par As shown in figure }{\field{\*\fldinst {\insrsid12989836  REF fBasicModels \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000006600420061007300690063004d006f00640065006c0073000000}}}{\fldrslt {
\lang1024\langfe1024\noproof\insrsid12989836 4}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 2}}}{\insrsid12989836 
, the interaction model defines a way to interact with all other basic models. This is necessary, as all models can define aspects and functions that can be represented for and a}{\insrsid12989836 c}{\insrsid12989836 
cessed by the user. For example, a data object like a \'93text\'94 object often has a directly attached view and controller, enabling direct interaction with the text; then, interaction and data model communicate d}{\insrsid12989836 i}{\insrsid129898...