Bundle-PBib
view release on metacpan or search on metacpan
t/expected-sample-pbib.rtf view on Meta::CPAN
\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...
rectly, bypassing user interface and application models. Alternatively, a \'93visual interaction area\'94 being part of the user interface model, provides functionality that has an immediate visual representation re}{\insrsid12989836 n}{\insrsid12989...
dered by the interaction model. In other cases, the interaction model will not access the data model d}{\insrsid12989836 i}{\insrsid12989836
rectly. Instead, it is associated with an appropriate application model as a mediator to the data model. This way, the interaction style can be adapted depending on which application model is used to access a data model.
\par As an appropriate
interaction style depends on the available interaction devices and the associated user interface, a suitable interaction model can be chosen depending on the environment and user-interface model. For visual-based interaction, an adapted version of th...
el-view-controller concept ({\field{\*\fldinst { HYPERLINK \\l MVCCookbook}}{\fldrslt {Krasner and Pope, 1988}}}; {\field{\*\fldinst { HYPERLINK \\l COASTooSyncGroupware}}{\fldrslt {Schuckmann {\i et al.}, 1996}}}) has proven su}{\insrsid12989836 c}{...
of the model-view-controller concept is not further structured. It can refer to each of data, application, user interface, or environment model.
\par Passage defines an interactive visual representation (for the virtual part of the bridge) and physical a}{\insrsid12989836 c}{\insrsid12989836
tions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (see section }{\field{\*\fldinst {\insrsid12989836 REF sModelLayer \\r \\h }{\insrsid12989836 {\*\datafield...
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000c00000073004d006f00640065006c004c0061007900650072000000}}}{\fldrslt {\insrsid12989836 5.2}}}{\insrsid12989836 ) and a sensor model providing the basis for detec}{\insrsid12989836 t}{\insrsid12989836 ...
ing physical o}{\insrsid12989836 b}{\insrsid12989836 jects (see section }{\field{\*\fldinst {\insrsid12989836 REF sSensorModel \\r \\h }{\insrsid12989836 {\*\datafield
08d0c9ea79f9bace118c8200aa004ba90b02000000080000000d0000007300530065006e0073006f0072004d006f00640065006c000000}}}{\fldrslt {\insrsid12989836 6.1}}}{\insrsid12989836 ).
\par {\*\bkmkstart sConceptualSharing}{\*\bkmkstart _Toc19764442}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2.3\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar
\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Second Dimension: Coupling and Sharing{\*\bkmkend sConceptualSharing...
{\*\bkmkend _Toc19764442}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Whenever multiple devices are involved in a software system, th
e question arises, which parts of the system should be local to a device or shared between several. This has to be clarified for both the a}{\insrsid12989836 p}{\insrsid12989836 plication code and its state. While }{\i\insrsid12989836 distributing co...
\insrsid12989836 among devices is a technical question unique to every application, }{\i\insrsid12989836 sharing state}{\insrsid12989836 has conceptual implications, which this section addresses.
\par Today, many applications still run entirely local to a single computer, or access only data that is di}{\insrsid12989836 s}{\insrsid12989836 tributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW system...
\i\insrsid12989836 access to shared data}{\insrsid12989836 and }{\i\insrsid12989836 coupling the applications }{\insrsid12989836
of collaborating users ({\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary, 1995}}}). Therefore, coupling has to be applied to both the data and the application model ({\field{\*\fldinst { HYPERLINK \\l COASTModel}}{\...
\par In the context of ubiquitous computing environments, this view has to be extended. In addition to data and application, also information about the physical environment, e.g., the presence of nearby users or other avai}{\insrsid12989836 l}{
\insrsid12989836 able interaction devices, has to be exchanged by different devices and applications.
\par As discussed above, in a ubiquitous computing environment elements of the user interface can be di}{\insrsid12989836 s}{\insrsid12989836 tributed among several machines (req. }{\field{\*\fldinst {\insrsid12989836 REF qCompositeRoomwareComponent...
\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000001d000000710043006f006d0070006f00730069007400650052006f006f006d00770061007200650043006f006d0070006f006e0065006e00740073000000}}}{\fldrslt {\insrsid12989836 U\_2}}}{
\insrsid12989836 ) or among different devices (req. }{\field{\*\fldinst {\insrsid12989836 REF qMultipleDeviceInteraction \\h }{\insrsid12989836 {\*\datafield
08d0c9ea79f9bace118c8200aa004ba90b02000000080000001b00000071004d0075006c007400690070006c00650044006500760069006300650049006e0074006500720061006300740069006f006e000000}}}{\fldrslt {\insrsid12989836 UH\_2}}}{\insrsid12989836 ). Based on the sep}{
\insrsid12989836 a}{\insrsid12989836 ration of concerns that has been previously identified, Dewan\rquote s definition of coupling ({\field{\*\fldinst { HYPERLINK \\l DewanFlexibleUICoupling}}{\fldrslt {Dewan and Choudhard, 1991}}}) can be refined. C...
sharing the same interaction, user interface, or editing (application) state}{\insrsid12989836
among several users or devices. Coupling can thus simply be implemented as accessing the same user interface or application model. This is an important benefit of using shared user interface and application models.
\par Depending on how much state is shared, the }{\i\insrsid12989836 degree of coupling}{\insrsid12989836
can be controlled. If all involved user interface and editing state is shared, a tightly coupled collaboration mode is realized; if only the same data model is shared, users work loosely coupled (req. }{\field{\*\fldinst {\insrsid12989836 REF
qFlexibleCoupling \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b020000000800000012000000710046006c0065007800690062006c00650043006f00750070006c0069006e0067000000}}}{\fldrslt {\insrsid12989836 C\_2}}}{\insrsid12989836
). This is related to the coupling model d}{\insrsid12989836 e}{\insrsid12989836 scribed in ({\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary, 1995}}}).
\par Even, if some models are not coupled, one can profit from sharing environment, user interface, and application models. As the information encapsulated in the models is accessible to all clients, it is po}{\insrsid12989836 s}{\insrsid12989836
sible to provide }{\i\insrsid12989836 awareness information}{\insrsid12989836 in the user interface. Typical for CSCW applications is the pr}{\insrsid12989836 o}{\insrsid12989836
vision of workspace or activity awareness ({\field{\*\fldinst { HYPERLINK \\l GroupKitAwarenessWidgets}}{\fldrslt {Gutwin {\i et al.}, 1996}}}; {\field{\*\fldinst { HYPERLINK \\l InterlocusActivityAwareness}}{\fldrslt {Nomura {\i et al.}, 1998}}}). T...
mation provides a means of giving add}{\insrsid12989836 i}{\insrsid12989836 tional awareness hints to remote users.
\par Beyond the provision of awareness in CSCW systems, sharing the environment model allows a new kind of awareness for ubiquitous computing environments. The information embodied in the enviro}{\insrsid12989836 n}{\insrsid12989836
ment model can be used to give environmental awareness.
\par This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that \'93sharing\'94 can be implemented in many different ways. In the case of collaborating devices with quite varying pro...
\endash especially in terms of memory, performance, or network co}{\insrsid12989836 n}{\insrsid12989836 nection \endash a shared object does not necessarily have to have the same implementation for different pla}{\insrsid12989836 t}{\insrsid1298983...
forms (see e.g. Manifold ({\field{\*\fldinst { HYPERLINK \\l ManifoldArchitecture}}{\fldrslt {Marsic, 2001}}}) or Pocket Dream Team ({\field{\*\fldinst { HYPERLINK \\l QuickStepChallenges}}{\fldrslt {Roth, 2002}}})). For example, a shared \'93image\'...
top PC than on a PDA. At the conceptual level, however, both implementations refer to the same shared object.
\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 _Toc2659663}{\*\bkmkstart _Toc197...
Sharing the Data Model{\*\bkmkend _Toc2659663}{\*\bkmkend _Toc19764443}: Collaborative Data Access
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 In order to access and work collaboratively with shared data (req. }{\field{\*\...
\insrsid12989836 REF qCollaboration \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b02000000080000000f000000710043006f006c006c00610062006f0072006100740069006f006e000000}}}{\fldrslt {\insrsid12989836 C\_1}}}{\insrsid12989836
), it is widely agreed that a shared model for documents reduces the complexity in dealing w
ith distributed applications. While there are well-established models defining a shared data model providing read-only access only (e.g. the world-wide-web), it is much more complicated to allow simultaneous modific}{\insrsid12989836 a}{\insrsid12989...
tions at a fine granularity.
\par Most popular toolkits and frameworks for computer-supported cooperative work provide some mech}{\insrsid12989836 a}{\insrsid12989836
nism to manage a shared-object space. In toolkits with a centralized architecture ({\field{\*\fldinst { HYPERLINK \\l RendezvousDemands}}{\fldrslt {Patterson, 1991}}}), the document is necessarily shared. Replicated (or semi-replicated
({\field{\*\fldinst { HYPERLINK \\l GroupwareArchitectures}}{\fldrslt {Phillips, 1999}}})) systems create a shared-object space by synchronizing the replicated objects ({\field{\*\fldinst { HYPERLINK \\l ClockArchitecture}}{\fldrslt {Urnes and Graha...
ared \'93environments\'94 have been introduced as shared data structures that can trigger cal}{\insrsid12989836 l}{\insrsid12989836 backs upon changes.
\par Application designers thus have to decide to which degree or for which parts of their application shared access to data is desirable or necessary. For the Passage system, a shared data model enables a straigh}{\insrsid12989836 t}{\insrsid1298983...
forward access to data objects from different computers, which is necessary when a passenger is tran}{\insrsid12989836 s}{\insrsid12989836 ferred to another roomware component.
\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 _Toc2659664}
{\*\bkmkstart sApplicationModelSharing}{\*\bkmkstart _Toc19764444}Sharing the Application Model{\*\bkmkend _Toc2659664}{\*\bkmkend sApplicationModelSharing}{\*\bkmkend _Toc19764444}: Workspace Awareness & Degree of Coupling
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836
To have an easy way of getting information about the editing state of other users, it has been proposed not only to share the data model, but also to share the application model ({\field{\*\fldinst { HYPERLINK \\l COASTModel}}{\fldrslt {Schuckmann {\...
provide awareness about editing activities. Taking again the exa}{\insrsid12989836 m}{\insrsid12989836 ple of a text-edit application model, sharing it opens the opportunity to visualize, e.g., text cursors or sele}{\insrsid12989836 c}{\insrsid12989...
tions of remote users.
\par By changing the state of the application model, the degree of coupling or other possible work modes can be controlled (req. }{\field{\*\fldinst {\insrsid12989836 REF qFlexibleCoupling \\h }{\insrsid12989836 {\*\datafield
08d0c9ea79f9bace118c8200aa004ba90b020000000800000012000000710046006c0065007800690062006c00650043006f00750070006c0069006e0067000000}}}{\fldrslt {\insrsid12989836 C\_2}}}{\insrsid12989836
). Users working with the same application model can work tightly coupled with rich awareness information ({\field{\*\fldinst { HYPERLINK \\l COASTModel}}{\fldrslt {Schuckmann {\i et al.}, 1999}}}). Tightly coupled work could for
t/expected-sample-pbib.rtf view on Meta::CPAN
9494949494947b4b4b6c5d5d5d6c4b4b5d7b6c244b949494949494949400989b009494949494949494940094874b3b1b949494949494947b3b060206362a3b3b
3b2a2a2a1b246c6c3b7b9494949494949400a2a4009494949494949494940094946c4b067b9494947b2a0602060f2a3b5d7b7b6c5d6c879494946c5d873b8794
9494949494003436009494949494949494940094947b4b1b1b6c2a06060f1b3b3f677b949494949494949494949494874b5d5d94949494949400595b00949494
949494949494009494944b4b1b2a2a2c5d7b87879494949494949494949494949494949494948794949494949400808200949494949494949494009494945d3b
4b5d7b879494949494949494949494949494949494949494949494949494949494008a8c00949494949494949494009494948787879494949494949494949494
94949494949494949494949494949494949494949400b0b300000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000004244050000000701010000000800000026060f000600ffffffff0100040000002d010100040000002d0103001c000000fb0210000700
00000000bc02000000000102022253797374656d0077ed07664607008a0100000a000600000007008a0100000a00040000002d01050004000000f00104000f00000026060f001400544e505004000c000000000000000000000000000900000026060f000800ffffffff01000000030000000000}}{\insrsid1298983...
\par }\pard\plain \s23\qj \li278\ri374\sa200\widctlpar\aspalpha\aspnum\faauto\adjustright\rin374\lin278\itap0 \f4\fs18\lang1033\langfe1033\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc19764593}Figure {\*\bkmkstart fDesignDimensionsRWAp...
{\field{\*\fldinst {\insrsid12989836 STYLEREF 1 \\s }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 4}}}{\insrsid12989836 \_}{\field{\*\fldinst {\insrsid12989836 SEQ Figure \\* ARABIC \\s 1 }}{\fldrslt {
\lang1024\langfe1024\noproof\insrsid12989836 4}}}{\insrsid12989836 {\*\bkmkend fDesignDimensionsRWApp}.}{\lang1024\langfe1024\noproof\insrsid12989836 Notation for the three design dimensions }{\insrsid12989836 of the BEACH conceptual model
{\*\bkmkend _Toc19764593}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 The BEAC
H conceptual model can be used as the basis to structure architectures and applications for ubiquitous computing and roomware environments. Figure }{\field{\*\fldinst {\insrsid12989836 REF fDesignDimensionsRWApp \\h }{\insrsid12989836 {\*\datafield ...
08d0c9ea79f9bace118c8200aa004ba90b0200000008000000170000006600440065007300690067006e00440069006d0065006e00730069006f006e007300520057004100700070000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 4}{\insrsid12989836 \_}{
\lang1024\langfe1024\noproof\insrsid12989836 4}}}{\insrsid12989836 suggests a graphical notation that can be used in design diagrams to denote the position of classes within the design dimensions of the co}{\insrsid12989836 n}{\insrsid12989836
ceptual model. This aids developers in understanding the d}{\insrsid12989836 e}{\insrsid12989836 sign of a ubiquitous computing application.
\par In favor of being applicable to a wide range of applications and architectures, the
model specifies a coarse-grained structure at a high level of abstraction. Thereby, the conceptual model leaves much freedom for application developers and architects to choose approaches appropriate for the problem at hand. Foremost, the conceptual ...
does not impose a restricted set of }{\i\insrsid12989836 architectural styles}{\insrsid12989836 ({\field{\*\fldinst { HYPERLINK \\l JacobsonOOSE}}{\fldrslt {Jacobson {\i et al.}, 1992}}}; {\field{\*\fldinst { HYPERLINK \\l GroupwareArchitectures}}{...
ending on the constraints of the platform and requirements in terms of collaboration, an arbitrary distribution architecture can be selected.
\par To show how the BEACH conceptual model can be applied, the next sections presents the BEACH software framework and a sample application that was built using the framework.
\par }\pard \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0\pararsid9272531 {\insrsid9272531 {\b {\i <<again some stuff removed>>}}
\par {\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 3\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpar
\jclisttab\tx432\hyphpar0\aspalpha\aspnum\faauto\ls128\outlinelevel0\adjustright\rin0\lin432\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 References
\par }\pard\plain \s56\qj \fi-284\li284\ri0\widctlpar\tx284\aspalpha\aspnum\faauto\adjustright\rin0\lin284\itap0\pararsid9272531 \f236\fs18\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {{{\*\bkmkstart BuildAppFWsViewpoints}{Ale...
{\*\bkmkend BuildAppFWsViewpoints}}\par
{{\*\bkmkstart DragonflyArchitecture}{Anderson, G. E., Graham, T. N., and Wright, T. N., 2000. Dragonfly: Linking Conceptual and Implementation Architectures of Multiuser Interactive Systems. In: Proceedings of the 22st International Conference on So...
{\*\bkmkend DragonflyArchitecture}}\par
{{\*\bkmkstart BeaudouinLafonPostWIMPModel}{Beaudouin-Lafon, M., 2000. Instrumental Interaction: An Interaction Model for Designing Post-WIMP User Interfaces. In: Proceedings of the CHI 2000 conference on Human factors in computing systems (CHI'00), ...
{\*\bkmkend BeaudouinLafonPostWIMPModel}}\par
{{\*\bkmkstart EasyLivingTechnologies}{Brummit, B., Meyers, B., Krumm, J., Kern, A., and Shafer, S., 2000. Easyliving: Technologies for Intelligent Environments. In: Proceedings of the 2nd International Symposium on Handheld and Ubiquitous Computing ...
{\*\bkmkend EasyLivingTechnologies}}\par
{{\*\bkmkstart PACUIArchitecture}{Coutaz, J., 1997. PAC-ing the Architecture of Your User Interface. In: Proceedings of the 4th Eurographics Workshop on Design, Specication and Verication of Interactive Systems (DSV-IS'97), Springer, Heidelberg, New ...
{\*\bkmkend PACUIArchitecture}}\par
{{\*\bkmkstart ZypherTailorability}{Demeyer, S., 1996. Zypher\endash Tailorability as a Link from Object-Oriented Software Engineering to Open Hypermedia, Ph.D. thesis, Vrije Universiteit Brussel, Departement Informatica.}
{\*\bkmkend ZypherTailorability}}\par
{{\*\bkmkstart DewanFlexibleUICoupling}{Dewan, P. and Choudhard, R., 1991. Flexible user interface coupling in a collaborative system. In: Human factors in computing systems conference proceedings on Reaching through technology, ACM Press, pp.\~41\en...
{\*\bkmkend DewanFlexibleUICoupling}}\par
{{\*\bkmkstart SuiteCouplingUIs}{Dewan, P. and Choudhary, R., 1995. Coupling the User Interfaces of a Multiuser Program, ACM Transactions on Computer-Human Interaction 2\~(1), 1\endash 39.}
{\*\bkmkend SuiteCouplingUIs}}\par
{{\*\bkmkstart DijkstraTHEstructure}{Dijkstra, E. W., 1968. The structure of the "THE"-multiprogramming system, Communications of the ACM 11\~(5), 341\endash 346. {\field{\*\fldinst { HYPERLINK http://doi.acm.org/10.1145/363095.363143}}{\fldrslt {htt...
{\*\bkmkend DijkstraTHEstructure}}\par
{{\*\bkmkstart PlacelessDocGeneralitySpecificity}{Edwards, W. K. and LaMarca, A., 1999. Balancing Generality and Specificity in Document Management Systems. In: INTERACT '99, IOS Press, pp.\~187\endash 195.}
{\*\bkmkend PlacelessDocGeneralitySpecificity}}\par
{{\*\bkmkstart GoFDesignPatterns}{Gamma, E., Helm, R., Johnson, R., and Vlissides, J., 1995. Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley.}
{\*\bkmkend GoFDesignPatterns}}\par
{{\*\bkmkstart GroupKitAwarenessTradeoffs}{Gutwin, C. and Greenberg, S., 1998. Design for Individuals, Design for Groups: Tradeoffs between power and workspace awareness. In: Proceedings of the ACM 1998 conference on Computer supported cooperative wo...
{\*\bkmkend GroupKitAwarenessTradeoffs}}\par
{{\*\bkmkstart GroupKitAwarenessWidgets}{Gutwin, C., Roseman, M., and Greenberg, S., 1996. A Usability Study of Awareness Widgets in a Shared Workspace Groupware System. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Wor...
{\*\bkmkend GroupKitAwarenessWidgets}}\par
{{\*\bkmkstart HCIContextInfrastructure}{Hong, J. I. and Landay, J. A., 2001. An Infrastructure Approach to Context-Aware Computing, Human-Computer Interaction 16\~(2\endash 4), 287\endash 303.}
{\*\bkmkend HCIContextInfrastructure}}\par
{{\*\bkmkstart JacobsenSoftwareModelling}{Jacobsen, E. E., 2000. Concepts and Language Mechanisms in Software Modelling, Ph.D. thesis, Faculty of Science and Engineering, University of Southern Denmark. {\field{\*\fldinst { HYPERLINK http://www.mip.s...
{\*\bkmkend JacobsenSoftwareModelling}}\par
{{\*\bkmkstart JacobsonOOSE}{Jacobson, I., Christerson, M., Jonsson, P., and Övergaard, G., 1992. Object-Oriented Software Engineering, a Use Case Driven Approach, ACM Press, Addison Wesley.}
{\*\bkmkend JacobsonOOSE}}\par
{{\*\bkmkstart iRoomPointRight}{Johanson, B., Hutchins, G., Winograd, T., and Stone, M., 2002. PointRight: Experience with Flexible Input Redirection in Interactive Workspaces. In: Proceedings of the 15th annual ACM symposium on User interface softwa...
{\*\bkmkend iRoomPointRight}}\par
{{\*\bkmkstart MVCCookbook}{Krasner, G. E. and Pope, S. T., 1988. A Cookbook for Using the Model-View-Controller User Interface Paradigma in Smalltalk-80, Journal of Object Oriented Programming (JOOP) 1\~(3), 26\endash 49.}
{\*\bkmkend MVCCookbook}}\par
{{\*\bkmkstart ManifoldArchitecture}{Marsic, I., 2001. An Architecture for Heterogeneous Groupware Applications. In: Proceedings of the 23rd International Conference on Software Engineering, IEEE Computer Society Press, pp.\~475\endash 484. {\field{\...
{\*\bkmkend ManifoldArchitecture}}\par
{{\*\bkmkstart PACAMODEUS}{Nigay, L. and Coutaz, J., 1991. Building User Interfaces: Organizing Software Agents. In: Esprit'91 Conference Proceedings, ACM Press, New York, NY, pp.\~707\endash 719. {\field{\*\fldinst { HYPERLINK http://citeseer.nj.nec...
{\*\bkmkend PACAMODEUS}}\par
{{\*\bkmkstart InterlocusActivityAwareness}{Nomura, T., Hayashi, K., Hazama, T., and Gudmundson, S., 1998. Interlocus: Workspace Configuration Mechanisms for Activity Awareness. In: Proceedings of the ACM 1998 Conference on Computer Supported Coopera...
{\*\bkmkend InterlocusActivityAwareness}}\par
{{\*\bkmkstart NowackStructuresInteractions}{Nowack, P., 1999. Structures and Interactions\endash Characterizing Object-Oriented Software Architecture, Ph.D. thesis, Faculty of Software Engineering and Technology, University of Southern Denmark. {\fi...
{\*\bkmkend NowackStructuresInteractions}}\par
{{\*\bkmkstart XWebJoinCapture}{Olsen, Jr., D. R., Nielsen, S. T., and Parslow, D., 2001. Join and Capture: A Model for Nomadic Interaction. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software Technology (UIST'01), vol.\~3, no...
{\*\bkmkend XWebJoinCapture}}\par
{{\*\bkmkstart ParnasDecomposingSystems}{Parnas, D. L., 1972. On the criteria to be used in decomposing systems into modules, Communications of the ACM 15\~(12), 1053\endash 1058. {\field{\*\fldinst { HYPERLINK http://doi.acm.org/10.1145/361598.36162...
{\*\bkmkend ParnasDecomposingSystems}}\par
{{\*\bkmkstart RendezvousDemands}{Patterson, J. F., 1991. Comparing the Programming Demands of Single-User and Multi-User Applications. In: Proceedings of ACM SIGGRAPH Symposium on User Interface Software and Technology (UIST'91), ACM Press, New York...
{\*\bkmkend RendezvousDemands}}\par
{{\*\bkmkstart GroupwareArchitectures}{Phillips, W. G., 1999. Architectures for Synchronous Groupware, Tech. Rep., Queen's University, Kingston, Ontario K7L 3N6. {\field{\*\fldinst { HYPERLINK http://phillips.rmc.ca/greg/pub/}}{\fldrslt {http://phill...
{\*\bkmkend GroupwareArchitectures}}\par
{{\*\bkmkstart PierLocationIndepInterfaces}{Pier, K. and Landay, J. A., 1992. Issues for Location-independent Interfaces, Tech. Rep., Xerox PARC, Palo Alto, CA, USA. {\field{\*\fldinst { HYPERLINK http://www.cs.berkeley.edu/~landay/research/publicati...
{\*\bkmkend PierLocationIndepInterfaces}}\par
{{\*\bkmkstart DisappearingUICoherenceScope}{Prante, T., 2001. Designing for Usable Disappearance\endash Mediating Coherence, Scope, and Orientation. In: Workshop Proceedings "Distributed and Disappearing User Interfaces in Ubiquitous Computing", ACM...
{\*\bkmkend DisappearingUICoherenceScope}}\par
{{\*\bkmkstart BEACHCreativityTools}{Prante, T., Magerkurth, C., and Streitz, N. A., 2002. Developing CSCW Tools for Idea Finding\endash Empirical Results and Implications for Design. In: Proceedings of the 2002 ACM Conference on Computer Supported C...
{\*\bkmkend BEACHCreativityTools}}\par
{{\*\bkmkstart RefactorySmalltalk}{Roberts, D., Brant, J., and Johnson, R., 1997. A Refactoring Tool for Smalltalk. In: Pattern Languages of Program Design, vol.\~3 of {\i Software Patterns}, Addison Wesley, ch.\~25. {\field{\*\fldinst { HYPERLINK ht...
{\*\bkmkend RefactorySmalltalk}}\par
{{\*\bkmkstart GaiaGaiaOS}{Román, M., Hess, C. K., and et al., 2001. GaiaOS: An Infrastructurre for Active Spaces, Tech. Rep., Universiy of Illinois at Urbana-Champaign, Department of Computer Science, 1304 West Springfield Avenue, Urbana, IL, 61801-...
{\*\bkmkend GaiaGaiaOS}}\par
{{\*\bkmkstart GroupKitCSCW92}{Roseman, M. and Greenberg, S., 1992. GROUPKIT: a groupware toolkit for building real-time conferencing applications. In: Proceedings of the conference on Computer-supported cooperative work, ACM Press, pp.\~43\endash 50...
{\*\bkmkend GroupKitCSCW92}}\par
{{\*\bkmkstart GroupKitRealTime}{Roseman, M. and Greenberg, S., 1996. Building Real Time Groupware with GroupKit, A Groupware Toolkit, ACM Transactions on Computer-Human Interaction 3\~(1), 66\endash 106.}
{\*\bkmkend GroupKitRealTime}}\par
{{\*\bkmkstart QuickStepChallenges}{Roth, J., 2002. Seven Challenges for Developers of Mobile Groupware. In: Workshop "Mobile Ad Hoc Collaboration", CHI 2002, Minneapolis.}
{\*\bkmkend QuickStepChallenges}}\par
{{\*\bkmkstart ContextToolkitAppDevelopment}{Salber, D., Dey, A. K., and Abowd, G. D., 1999. The Context Toolkit: Aiding the Development of Context-Enabled Applications. In: Proceeding of the CHI 99 conference on Human factors in computing systems (C...
{\*\bkmkend ContextToolkitAppDevelopment}}\par
{{\*\bkmkstart SchmidtImplicitHCI}{Schmidt, A., 2000. Implicit Human Computer Interaction Through Context, Personal Technologies 4\~(2+3), 191\endash 199. {\field{\*\fldinst { HYPERLINK http://www.teco.edu/}}{\fldrslt {http://www.teco.edu/}}}.}
{\*\bkmkend SchmidtImplicitHCI}}\par
{{\*\bkmkstart COASTooSyncGroupware}{Schuckmann, C., Kirchner, L., Schümmer, J., and Haake, J. M., 1996. Designing Object-oriented Synchronous Groupware with COAST. In: Proceedings of the ACM 1996 Conference on Computer Supported Cooperative Work (CS...
{\*\bkmkend COASTooSyncGroupware}}\par
{{\*\bkmkstart COASTModel}{Schuckmann, C., Schümmer, J., and Seitz, P., 1999. Modeling Collaboration using Shared Objects. In: Proceedings of International ACM SIGGROUP Conference on Supporting Group Work (GROUP'99), ACM Press, New York, NY, pp.\~189...
{\*\bkmkend COASTModel}}\par
{{\*\bkmkstart EasyLivingUbiComp}{Shafer, S. A. N., 2001. Ubiquitous Computing and the EasyLiving Project. In: 40th Anniversary Symposium, Osaka Electro-Communications University. {\field{\*\fldinst { HYPERLINK http://www.research.microsoft.com/easyl...
{\*\bkmkend EasyLivingUbiComp}}\par
{{\*\bkmkstart AuraFramework}{Sousa, J. and Garlan, D., 2002. Aura: An Architectural Framework for User Mobility in Ubiquitous Computing Environments. In: Software Architecture: System Design, Development, and Maintenance (Proceedings of the 3rd Work...
{\*\bkmkend AuraFramework}}\par
{{\*\bkmkstart ColabWYSIWISRev}{Stefik, M., Bobrow, D. G., Foster, G., Lanning, S., and Tatar, D., 1987. WYSIWIS Revised: Early Experiences with Multi-User Interfaces, ACM Transactions on Information Systems 2\~(5), 147\endash 167.}
{\*\bkmkend ColabWYSIWISRev}}\par
{{\*\bkmkstart RoomwareiLAND}{Streitz, N. A., Geißler, J., Holmer, T., Konomi, S., Müller-Tomfelde, C., Reischl, W., Rexroth, P., Seitz, P., and Steinmetz, R., 1999. i-LAND: An interactive Landscape for Creativity and Innovation. In: Proceeding of th...
{\*\bkmkend RoomwareiLAND}}\par
{{\*\bkmkstart RoomwareSecondGeneration}{Streitz, N. A., Prante, T., Müller-Tomfelde, C., Tandler, P., and Magerkurth, C., 2002. Roomware: The Second Generation. In: Video Proceedings and Extended Abstracts of the ACM Conference on Human Factors in C...
{\*\bkmkend RoomwareSecondGeneration}}\par
{{\*\bkmkstart RoomwareMatters}{Streitz, N. A., Rexroth, P., and Holmer, T., 1997. Does 'roomware' matter? Investigating the role of personal and public information devices and their combination in meeting room collaboration. In: Proceedings of the E...
{\*\bkmkend RoomwareMatters}}\par
{{\*\bkmkstart RoomwareNextGeneration}{Streitz, N. A., Tandler, P., Müller-Tomfelde, C., and Konomi, S., 2001. Roomware: Towards the next generation of human-computer interaction based on an integrated design of real and virtual worlds. In: Carroll, ...
{\*\bkmkend RoomwareNextGeneration}}\par
{{\*\bkmkstart BuildAppFWsFWsDomainModels}{Succi, G., Predonzani, P., Valerio, A., and Vernazza, T., 1999. Frameworks and Domain Models: Two Sides of the Same Coin. In: Fayad, M. E., Schmidt, D. C., and Johnson, R. E. (eds.), Building Application Fra...
{\*\bkmkend BuildAppFWsFWsDomainModels}}\par
{{\*\bkmkstart HUMANOIDModel}{Szekely, P., Luo, P., and Neches, R., 1992. Facilitating the Exploration of Interface Design Alternatives: The HUMANOID Model of Interface Design. In: Proceedings of the ACM Conference on Human Factors in Computing Syste...
{\*\bkmkend HUMANOIDModel}}\par
{{\*\bkmkstart BEACHSyncCollaboration}{Tandler, P., 2001. Software Infrastructure for Ubiquitous Computing Environments: Supporting Synchronous Collaboration with Heterogeneous Devices. In: Abowd, G. D., Brummitt, B., and Shafer, S. (eds.), Proceedin...
{\*\bkmkend BEACHSyncCollaboration}}\par
( run in 0.672 second using v1.01-cache-2.11-cpan-39bf76dae61 )