synchro results from the CPAN

Bundle-PBib

\par }\pard\plain \s18\qj \li0\ri0\sb120\sa120\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Peter Tandler
\par }\pard\plain \s50\ql \li0\ri0\sa360\keep\keepn\nowidctlpar\hyphpar0\faauto\rin0\lin0\itap0 \f40\fs20\lang1024\langfe1024\cgrid\noproof\langnp1033\langfenp1033 {\insrsid12989836 FhG \endash  Fraunhofer Gesellschaft e.V.\line IPSI \endash 
 Integrated Publication and Information Systems Institute\line AMBIENTE \endash  Workspaces of }{\insrsid9272531 the Future}{\insrsid14965794 \line }{\field\fldedit{\*\fldinst {\insrsid14965794 HYPERLINK "http://ipsi.fraunhofer.de/ambiente/"}{
\insrsid12989836 {\*\datafield 
00d0c9ea79f9bace118c8200aa004ba90b0200000003000000e0c9ea79f9bace118c8200aa004ba90b4800000068007400740070003a002f002f0069007000730069002e0066007200610075006e0068006f006600650072002e00640065002f0061006d006200690065006e00740065002f000000}}}{\fldrslt {
\cs51\i\insrsid14965794 http://ipsi.fraunhofer.de/ambiente/}}}{\i\insrsid9272531  }{\i\insrsid12989836 
\par }\pard\plain \s34\ql \li0\ri0\sb240\sa240\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc265...
Abstract{\*\bkmkend _Toc2659586}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situatio
ns, it is desirable to take advantage of their properties for synchronous collaboration. Besides offering an adapted user interface, this requires that the software infrastructure is designed for }{\i\insrsid12989836 synchronous access}{\insrsid12989...
 to shared information objects using }{\i\insrsid12989836 heterogeneous devices}{\insrsid12989836  with }{\i\insrsid12989836 different interaction}{\insrsid12989836 
 characteristics. As this field is still emerging and no mature standards are at hand, it is necessary to provide guidance for UbiComp developers how to model their applic}{\insrsid12989836 a}{\insrsid12989836 tions to ensure both extensibility for f...
ture developments and reusability in new contexts.
\par In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software f
ramework that is the basis for the software infrastructure of }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  (the ubiquitous computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment at FhG-IPSI). The BEACH framework provides the functionality for synchronous cooperation and interaction with roomware components, i.e. room elements
 with integrated information technology. To show how the BEACH model and framework can be applied, the design of a sample application is explained. Also, the BEACH model is positioned against related work. In conclusion, we provide our experiences wi...
e current implementation.
\par }\pard\plain \s52\ql \fi-576\li576\ri0\sb120\sa60\keep\keepn\widctlpar\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\outlinelevel1\adjustright\rin0\lin576\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Keywo...
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836 , roo}{\insrsid12989836 m}{\insrsid12989836...
ware components
\par {\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1\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 Introduction
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Ubiquitous computing environments offer a wide rang
e of devices coming in many different sizes and shapes ({\field{\*\fldinst { HYPERLINK \\l UbiCompIssues}}{\fldrslt {Weiser, 1993}}}). Being often occupied by multiple users simultaneously, ubiquitous co}{\insrsid12989836 m}{\insrsid12989836 
puting environments must support synchronous work with information that is shared among all present devices. Due
 to the heterogeneous nature of ubiquitous computing devices, their software infrastructure must enable user interfaces taking advantage of their different properties. In addition, it must enable tight collaboration of users working with different d}...
\insrsid12989836 e}{\insrsid12989836 vices or sharing the same device.
\par Current operation systems provide no support for handling this heterogeneity. Synchronous collabor}{\insrsid12989836 a}{\insrsid12989836 
tion can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, 
but these systems have no support for heterogeneous devices. There are research prototypes aimed at managing devices with different interaction capabilities, but these projects mainly deal with interfaces for and discovery of simple services and lack...
ort for tight collabor}{\insrsid12989836 a}{\insrsid12989836 
tion. There is a need for a software infrastructure designed for handling heterogeneous environments, providing adequate interaction styles and user interface concepts, as well as offering capabilities for synchronous collaboration. A
s this kind of infrastructure is built on top of current operating systems, which handle the interaction with the specific hardware, it can be referred to as \'93meta-operating sy}{\insrsid12989836 s}{\insrsid12989836 tem\'94 ({\field{\*\fldinst { HY...
\par Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and I}{\insrsid12989836 n}{\insrsid12989836 formation Systems Institute in Darmstadt (Germany), in the context of the }{
\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  project on support for synchronous collaboration with roomware components ({\field{\*\fldinst { HYPERLINK \\l RoomwareMatters}}{\fldrslt {Streitz {\i et al.}, 1997}}}; {\fiel...
Roomware\'94 is a term we coined to refer to room elements with integrated information technology such as interactive tables, walls, or chairs.
\par The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called \'93BEACH\'94, the }{\ul\insrsid12989836 B}{\insrsid129898...
\insrsid12989836 sic }{\ul\insrsid12989836 E}{\insrsid12989836 nvironment for }{\ul\insrsid12989836 A}{\insrsid12989836 ctive }{\ul\insrsid12989836 C}{\insrsid12989836 ollaboration with }{\ul\insrsid12989836 H}{\insrsid12989836 
ypermedia. BEACH provides the software infrastru}{\insrsid12989836 c}{\insrsid12989836 ture for environments supporting 
synchronous collaboration with many different devices. It offers a user interface that also fits to the needs of devices that have no mouse or keyboard, and which require new forms of human-computer and team-computer interaction. To allow synchronous...
aboration BEACH builds on shared documents accessible via multiple interaction devices concu}{\insrsid12989836 r}{\insrsid12989836 rently.
\par During the development, BEACH was restructured and refactored ({\field{\*\fldinst { HYPERLINK \\l RefactorySmalltalk}}{\fldrslt {Roberts {\i et al.}, 1997}}}; {\field{\*\fldinst { HYPERLINK \\l JacobsenSoftwareModelling}}{\fldrslt {Jacobsen, 200...
 was needed to guide developers of ubiquitous computing applications. This led us to the work presented here. Parts of BEACH emerged into a software framework with an architecture that is structured according to the conceptual model for syn
chronous ubiquitous computing applications proposed in this paper. The model aims at offering both flexibility and extensibility for different devices that are part of ubiquitous computing environments.
\par {\*\bkmkstart sContributingAreas}{\*\bkmkstart _Toc19764383}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.1\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 Involved Research Areas{\*\bkmkend sContributingAreas}
{\*\bkmkend _Toc19764383}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Due to the nature of collabor
ative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. }{\field{\*\fldinst {\insrsid12989836 
 REF fContributingAreas \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b020000000800000013000000660043006f006e0074007200690062007500740069006e006700410072006500610073000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989...
}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 ):}{\cs31\super\insrsid12989836 \chftn {\footnote \pard\plain \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  Of course, this is a simplified view on the research areas, focussing on their contributions relevant within the context of this paper.}}}...
\insrsid12989836 
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f40\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Human-Computer Interaction (HCI) deals with user interfaces and interaction tec}{\insrsid12989836 h}{\insrsid12989...
niques.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous intera}{\insrsid12989836 c}{\insrsid12989836 tion with distributed computers.
\par {\pntext\pard\plain\s61 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s61\qj \fi-227\li227\ri0\sa120\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f40\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Software development techniques are needed to ensure extensibility and reusability.
\par }\pard\plain \s29\qc \li0\ri0\sb220\sa220\keepn\nowidctlpar\faauto\rin0\lin0\itap0 \f40\fs20\lang1031\langfe1033\cgrid\langnp1031\langfenp1033 {\insrsid12989836 {\pict{\*\picprop\shplid1025{\sp{\sn shapeType}{\sv 75}}{\sp{\sn fFlipH}{\sv 0}}
{\sp{\sn fFlipV}{\sv 0}}{\sp{\sn fLockAspectRatio}{\sv 1}}{\sp{\sn fillColor}{\sv 268435473}}{\sp{\sn fFilled}{\sv 0}}{\sp{\sn fLine}{\sv 0}}{\sp{\sn fLayoutInCell}{\sv 1}}}\picscalex34\picscaley34\piccropl0\piccropr0\piccropt0\piccropb0
\picw26264\pich13141\picwgoal14890\pichgoal7450\wmetafile8\bliptag-1236891099\blipupi-29{\*\blipuid b6468a25a3265f559acf25026407e277}
0100090000037b04000007002500000000001100000026060f001800ffffffff000010003effffffde01000082160000820d00000900000026060f000800ffff
ffff020000001700000026060f002300ffffffff04001b00544e5050140070f000300000000014000000440d07010000000000000a00000026060f000a00544e
505000000200f4030900000026060f000800ffffffff030000000f00000026060f001400544e505004000c00010000000100000000000000050000000b02de01
3eff050000000c02a40b44170500000004010d00000007000000fc020000eaeaea000000040000002d01000008000000fa020500010000000000000004000000
2d010100040000002d010000090000001d062100f000a00b4017e00140ff040000002d01000007000000fc020000ffffff000000040000002d01020004000000

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

\insrsid12989836 
\par }\pard\plain \s23\qj \li278\ri374\sa200\widctlpar\aspalpha\aspnum\faauto\adjustright\rin374\lin278\itap0 \f4\fs18\lang1033\langfe1033\langnp1033\langfenp1033 {\insrsid12989836 Figure {\*\bkmkstart fContributingAreas}}{\field{\*\fldinst {\insrsid...
 STYLEREF 1 \\s }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 \_}{\field{\*\fldinst {\insrsid12989836  SEQ Figure \\* ARABIC \\s 1 }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 
{\*\bkmkend fContributingAreas}.}{\lang1024\langfe1024\noproof\insrsid12989836  Conttibuting research areas for the design of collaborative ubiquitous computing applications.}{\insrsid12989836 
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
\par {\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.2\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 Outline of the Paper
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 In the following section, requirements for the software infrastructure of a ubi...
 computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following to illustrate the application of the BEACH model and framework. Based on the identified requi
rements, the proposed conceptual application model has been designed, which is presented next. The succeeding section presents the architecture of the BEACH software framework, which has been developed according to the structure suggested by the conc...
l model. The software design of the Passage system is explained as a sample application of the BEACH model and framework. To position the BEACH model against other approaches, the next section co}{\insrsid12989836 m}{\insrsid12989836 
pares the proposed model with related work. The paper closes with a discussion of the conceptual model and ideas for f}{\insrsid12989836 u}{\insrsid12989836 ture work.
\par }{\insrsid7697605 {\b {\i <<…. Bla bla bla … some stuff removed …>>}}
\par {\*\bkmkstart cConceptualModel}{\*\bkmkstart _Toc2659654}{\*\bkmkstart _Toc2659760}{\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpa...
\jclisttab\tx432\hyphpar0\aspalpha\aspnum\faauto\ls128\outlinelevel0\adjustright\rin0\lin432\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A Conceptual Model for Ubiquitous Computing Applications
{\*\bkmkend cConceptualModel}{\*\bkmkend _Toc2659654}{\*\bkmkend _Toc2659760}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A conceptual model defines the very high-level structure of an application ({\f...
 the definition by {\field{\*\fldinst { HYPERLINK \\l NowackStructuresInteractions}}{\fldrslt {Nowack (1999)}}} a \'93co}{\insrsid12989836 n}{\insrsid12989836 
ceptual model describes a conceptual understanding of something, and it is based on concept formation in terms of classification, generalization and aggregation. Hence, conceptual modeling implies abstra}{\insrsid12989836 c}{\insrsid12989836 tion\'94...

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

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

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

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

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

{{\*\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. vol.\~1, John Wiley & Sons, New York, NY, USA, pp.\~211\endash 214.}
{\*\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
{{\*\bkmkstart BEACHConnecTables}{Tandler, P., Prante, T., Müller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Sympos...
{\*\bkmkend BEACHConnecTables}}\par
{{\*\bkmkstart AMFFWPatternSyncGW}{Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp.\~225\endash 242. {\field{\*\fl...
{\*\bkmkend AMFFWPatternSyncGW}}\par
{{\*\bkmkstart Chiron2Architecture}{Taylor, R. N., Medvidovic, N., and et al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22\~(6), 390\endash 406.}
{\*\bkmkend Chiron2Architecture}}\par
{{\*\bkmkstart PlasticityFrameworkAgenda}{Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp.\~110\endash 117.}
{\*\bkmkend PlasticityFrameworkAgenda}}\par
{{\*\bkmkstart ClockArchitecture}{Urnes, T. and Graham, T. N., 1999. Flexibly Mapping Synchronous Groupware Architectures to Distributed Implementations. In: Proceedings of Design, Specification and Verification of Interactive Systems (DSV-IS'99), Sp...
{\*\bkmkend ClockArchitecture}}\par
{{\*\bkmkstart VisualWorksUsersGuide}{{\i VisualWorks User's Guide}. ParcPlace-Digitalk, Inc., 999 East Arques Avenue, Sunnyvale, CA, Revision 2.0 (Software Release 2.5), 1995.}
{\*\bkmkend VisualWorksUsersGuide}}\par
{{\*\bkmkstart UbiCompIssues}{Weiser, M., 1993. Some Computer Science Issues In Ubiquitous Computing, Communications of the ACM 36\~(7), 75\endash 84.}

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

e.V.<BR>IPSI &ndash; Integrated Publication and Information Systems
Institute<BR>AMBIENTE &ndash; Workspaces of the
Future<BR><FONT COLOR="#000000"><I><SPAN STYLE="text-decoration: none"><A CLASS="western" HREF="http://ipsi.fraunhofer.de/ambiente/">http://ipsi.fraunhofer.de/ambiente/</A></SPAN></I></FONT><I>
</I></FONT>
</P>
<H1 CLASS="heading-1*-western">Abstract</H1>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">The devices
available in ubiquitous computing environments offer new
possibilities for interaction. In the context of meetings and
teamwork situations, it is desirable to take advantage of their
properties for synchronous collaboration. Besides offering an adapted
user interface, this requires that the software infrastructure is
designed for <I>synchronous access</I> to shared information objects
using <I>heterogeneous devices</I> with <I>different interaction</I>
characteristics. As this field is still emerging and no mature
standards are at hand, it is necessary to provide guidance for
UbiComp developers how to model their applications to ensure both
extensibility for future developments and reusability in new
contexts.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">In this paper, a
conceptual model for synchronous applications in ubiquitous computing
environments is proposed. To test its applicability, it was used to
structure the architecture of the BEACH software framework that is
the basis for the software infrastructure of <SPAN LANG="">i-LAND</SPAN>
(the ubiquitous computing environment at FhG-IPSI). The BEACH
framework provides the functionality for synchronous cooperation and
interaction with roomware components, i.e. room elements with
integrated information technology. To show how the BEACH model and
framework can be applied, the design of a sample application is
explained. Also, the BEACH model is positioned against related work.
In conclusion, we provide our experiences with the current
implementation.</P>
<H2 CLASS="heading-2*-western">Keywords</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Synchronous
collaboration, heterogeneous devices, software architecture,
conceptual model, BEACH application model and framework, <SPAN LANG="">i-LAND</SPAN>,
roomware components</P>
<H1 CLASS="western">1Introduction</H1>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Ubiquitous computing
environments offer a wide range of devices coming in many different
sizes and shapes (Weiser, 1993). Being often occupied by multiple
users simultaneously, ubiquitous computing environments must support
synchronous work with information that is shared among all present
devices. Due to the heterogeneous nature of ubiquitous computing
devices, their software infrastructure must enable user interfaces
taking advantage of their different properties. In addition, it must
enable tight collaboration of users working with different devices or
sharing the same device.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Current operation
systems provide no support for handling this heterogeneity.
Synchronous collaboration can be handled by several
computer-supported cooperative work frameworks, groupware systems, or
middleware infrastructures, but these systems have no support for
heterogeneous devices. There are research prototypes aimed at
managing devices with different interaction capabilities, but these
projects mainly deal with interfaces for and discovery of simple
services and lack support for tight collaboration. There is a need
for a software infrastructure designed for handling heterogeneous
environments, providing adequate interaction styles and user
interface concepts, as well as offering capabilities for synchronous
collaboration. As this kind of infrastructure is built on top of
current operating systems, which handle the interaction with the
specific hardware, it can be referred to as &ldquo;meta-operating
system&rdquo; (Román et al., 2001).</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Over the last five
years, we have been working at IPSI, the Fraunhofer Integrated
Publication and Information Systems Institute in Darmstadt (Germany),
in the context of the <SPAN LANG="">i-LAND</SPAN> project on support
for synchronous collaboration with roomware components
[[Roomware-Matters], [Roomware-i-LAND], [Roomware-NextGeneration],
[Roomware-SecondGeneration]]. &ldquo;Roomware&rdquo; is a term we
coined to refer to room elements with integrated information
technology such as interactive tables, walls, or chairs.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">The work presented
here was originally triggered by the need to create a software
infrastructure for this roomware environment. This led to the
development of a software prototype called &ldquo;BEACH&rdquo;, the
<U>B</U>asic <U>E</U>nvironment for <U>A</U>ctive <U>C</U>ollaboration
with <U>H</U>ypermedia. BEACH provides the software infrastructure
for environments supporting synchronous collaboration with many
different devices. It offers a user interface that also fits to the
needs of devices that have no mouse or keyboard, and which require
new forms of human-computer and team-computer interaction. To allow
synchronous collaboration BEACH builds on shared documents accessible
via multiple interaction devices concurrently.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">During the
development, BEACH was restructured and refactored
(Roberts et al., 1997; Jacobsen, 2000) several times.
It became obvious that a <I>conceptual model</I> was needed to guide
developers of ubiquitous computing applications. This led us to the
work presented here. Parts of BEACH emerged into a software framework
with an architecture that is structured according to the conceptual
model for synchronous ubiquitous computing applications proposed in
this paper. The model aims at offering both flexibility and
extensibility for different devices that are part of ubiquitous
computing environments.</P>
<H2 CLASS="western"><A NAME="sContributingAreas"></A>1.1Involved
Research Areas</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Due to the nature of
collaborative ubiquitous computing environments, the results of
several related research areas have to be combined to gain an
integrated application model that covers all aspects of interaction
and collaboration (fig. 1-1.1):<SUP><A CLASS="sdfootnoteanc" NAME="sdfootnote1anc" HREF="#sdfootnote1sym"><SUP>1</SUP></A></SUP></P>
<UL>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Human-Computer
	Interaction (HCI) deals with user interfaces and interaction
	techniques.</FONT></P>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Ubiquitous
	computing (UbiComp) explores dynamic environments with heterogeneous
	devices.</FONT></P>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Computer-Supported
	Cooperative Work (CSCW) offers techniques to handle synchronous
	interaction with distributed computers.</FONT></P>
	<LI><P><FONT FACE="Times, serif">Software development techniques are
	needed to ensure extensibility and reusability.</FONT></P>
</UL>
<P LANG="de-DE" ALIGN=CENTER STYLE="margin-top: 0.39cm; margin-bottom: 0.39cm; widows: 0; orphans: 0; page-break-after: avoid">
<IMG SRC="sample_html_49014637.gif" NAME="Graphic1" ALIGN=BOTTOM WIDTH=342 HEIGHT=172 BORDER=0></P>
<P STYLE="margin-left: 0.49cm; margin-right: 0.66cm; margin-bottom: 0.35cm"><A NAME="fContributingAreas"></A>
<FONT FACE="Helvetica, sans-serif"><FONT SIZE=2 STYLE="font-size: 9pt">Figure
<SPAN LANG="">1</SPAN>&nbsp;1.1.<SPAN LANG=""> Conttibuting research
areas for the design of collaborative ubiquitous computing
applications.</SPAN></FONT></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">A successful model
for collaborative ubiquitous computing applications must combine the
results of all involved research areas.</P>
<H2 CLASS="western">1.2Outline of the Paper</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">In the following
section, requirements for the software infrastructure of a ubiquitous
computing environment to support synchronous collaboration are
discussed. A sample application, the Passage system, is introduced,
which is used in the following to illustrate the application of the
BEACH model and framework. Based on the identified requirements, the
proposed conceptual application model has been designed, which is
presented next. The succeeding section presents the architecture of
the BEACH software framework, which has been developed according to
the structure suggested by the conceptual model. The software design
of the Passage system is explained as a sample application of the
BEACH model and framework. To position the BEACH model against other
approaches, the next section compares the proposed model with related

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

Dimension: Coupling and Sharing</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Whenever multiple
devices are involved in a software system, the 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 application code and
its state. While <I>distributing code</I> among devices is a
technical question unique to every application, <I>sharing state</I>
has conceptual implications, which this section addresses.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Today, many
applications still run entirely local to a single computer, or access
only data that is distributed over a network. Aiming at synchronous
collaboration, crucial aspects of traditional CSCW systems are <I>access
to shared data</I> and <I>coupling the applications </I>of
collaborating users (Dewan and Choudhary, 1995). Therefore, coupling has to
be applied to both the data and the application model
(Schuckmann et al., 1999).</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">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 available
interaction devices, has to be exchanged by different devices and

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

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 modifications at a fine
granularity.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Most popular
toolkits and frameworks for computer-supported cooperative work
provide some mechanism to manage a shared-object space. In toolkits
with a centralized architecture (Patterson, 1991), the document
is necessarily shared. Replicated (or semi-replicated
(Phillips, 1999)) systems create a shared-object space by
synchronizing the replicated objects [[Clock-Architecture],
[Dragonfly-Architecture], [COAST-ooSyncGroupware]]. In later versions
of GroupKit (Roseman and Greenberg, 1992; Roseman and Greenberg, 1996) shared
&ldquo;environments&rdquo; have been introduced as shared data
structures that can trigger callbacks upon changes.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">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 straightforward
access to data objects from different computers, which is necessary
when a passenger is transferred to another roomware component.</P>

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

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 Working IEEE/IFIP Conference on So...
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-167.
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 the CHI 99 conference on Human f...
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 Computing Systems (CHI'02), ACM Press, New...
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 European Conference on Computer-S...
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, J. A. (ed.), Human-Computer Interaction...
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 Frameworks: Object-Oriented Foundations of Fra...
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 Systems (CHI'92), ACM Press, pp. 50...
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.), Proceedings of UbiComp'01: Ubiquitous Computing,...
Tandler, P., Prante, T., Müller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software...
Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp. 225-242. http://citeseer.nj.nec.com/439075.html.
Taylor, R. N., Medvidovic, N., and et al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22 (6), 390-406.
Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp. 110-117.
Urnes, T. and Graham, T. N., 1999. Flexibly Mapping Synchronous Groupware Architectures to Distributed Implementations. In: Proceedings of Design, Specification and Verification of Interactive Systems (DSV-IS'99), Springer, Heidelberg, New York, pp. ...
VisualWorks User's Guide. ParcPlace-Digitalk, Inc., 999 East Arques Avenue, Sunnyvale, CA, Revision 2.0 (Software Release 2.5), 1995.
Weiser, M., 1993. Some Computer Science Issues In Ubiquitous Computing, Communications of the ACM 36 (7), 75-84.
Winograd, T. and Guimbretière, F., 1999. Visual Instruments for an Interactive Mural. In: Proceeding of the CHI 99 conference on Human factors in computing systems (CHI'99) extended abstracts, ACM Press, New York, NY, pp. 234-235. http://graphics.sta...
<DIV ID="sdfootnote1">
	<P CLASS="sdfootnote-western"><A CLASS="sdfootnotesym" NAME="sdfootnote1sym" HREF="#sdfootnote1anc">1</A>
	Of course, this is a simplified view on the research areas,
	focussing on their contributions relevant within the context of this

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

\par }\pard\plain \s18\qj \li0\ri0\sb120\sa120\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Peter Tandler
\par }\pard\plain \s50\ql \li0\ri0\sa360\keep\keepn\nowidctlpar\hyphpar0\faauto\rin0\lin0\itap0 \f236\fs20\lang1024\langfe1024\cgrid\noproof\langnp1033\langfenp1033 {\insrsid12989836 FhG \endash  Fraunhofer Gesellschaft e.V.\line IPSI \endash 
 Integrated Publication and Information Systems Institute\line AMBIENTE \endash  Workspaces of }{\insrsid9272531 the Future}{\insrsid14965794 \line }{\field\fldedit{\*\fldinst {\insrsid14965794 HYPERLINK "http://ipsi.fraunhofer.de/ambiente/"}{
\insrsid12989836 {\*\datafield 
00d0c9ea79f9bace118c8200aa004ba90b0200000003000000e0c9ea79f9bace118c8200aa004ba90b4800000068007400740070003a002f002f0069007000730069002e0066007200610075006e0068006f006600650072002e00640065002f0061006d006200690065006e00740065002f000000}}}{\fldrslt {
\cs51\i\insrsid14965794 http://ipsi.fraunhofer.de/ambiente/}}}{\i\insrsid9272531  }{\i\insrsid12989836 
\par }\pard\plain \s34\ql \li0\ri0\sb240\sa240\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc265...
Abstract{\*\bkmkend _Toc2659586}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situatio
ns, it is desirable to take advantage of their properties for synchronous collaboration. Besides offering an adapted user interface, this requires that the software infrastructure is designed for }{\i\insrsid12989836 synchronous access}{\insrsid12989...
 to shared information objects using }{\i\insrsid12989836 heterogeneous devices}{\insrsid12989836  with }{\i\insrsid12989836 different interaction}{\insrsid12989836 
 characteristics. As this field is still emerging and no mature standards are at hand, it is necessary to provide guidance for UbiComp developers how to model their applic}{\insrsid12989836 a}{\insrsid12989836 tions to ensure both extensibility for f...
ture developments and reusability in new contexts.
\par In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software f
ramework that is the basis for the software infrastructure of }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  (the ubiquitous computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment at FhG-IPSI). The BEACH framework provides the functionality for synchronous cooperation and interaction with roomware components, i.e. room elements
 with integrated information technology. To show how the BEACH model and framework can be applied, the design of a sample application is explained. Also, the BEACH model is positioned against related work. In conclusion, we provide our experiences wi...
e current implementation.
\par }\pard\plain \s52\ql \fi-576\li576\ri0\sb120\sa60\keep\keepn\widctlpar\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\outlinelevel1\adjustright\rin0\lin576\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Keywo...
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836 , roo}{\insrsid12989836 m}{\insrsid12989836...
ware components
\par {\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1\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 Introduction
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Ubiquitous computing environments offer a wide rang
e of devices coming in many different sizes and shapes ({\field{\*\fldinst { HYPERLINK \\l UbiCompIssues}}{\fldrslt {Weiser, 1993}}}). Being often occupied by multiple users simultaneously, ubiquitous co}{\insrsid12989836 m}{\insrsid12989836 
puting environments must support synchronous work with information that is shared among all present devices. Due
 to the heterogeneous nature of ubiquitous computing devices, their software infrastructure must enable user interfaces taking advantage of their different properties. In addition, it must enable tight collaboration of users working with different d}...
\insrsid12989836 e}{\insrsid12989836 vices or sharing the same device.
\par Current operation systems provide no support for handling this heterogeneity. Synchronous collabor}{\insrsid12989836 a}{\insrsid12989836 
tion can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, 
but these systems have no support for heterogeneous devices. There are research prototypes aimed at managing devices with different interaction capabilities, but these projects mainly deal with interfaces for and discovery of simple services and lack...
ort for tight collabor}{\insrsid12989836 a}{\insrsid12989836 
tion. There is a need for a software infrastructure designed for handling heterogeneous environments, providing adequate interaction styles and user interface concepts, as well as offering capabilities for synchronous collaboration. A
s this kind of infrastructure is built on top of current operating systems, which handle the interaction with the specific hardware, it can be referred to as \'93meta-operating sy}{\insrsid12989836 s}{\insrsid12989836 tem\'94 ({\field{\*\fldinst { HY...
\par Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and I}{\insrsid12989836 n}{\insrsid12989836 formation Systems Institute in Darmstadt (Germany), in the context of the }{
\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  project on support for synchronous collaboration with roomware components ({\field{\*\fldinst { HYPERLINK \\l RoomwareMatters}}{\fldrslt {Streitz {\i et al.}, 1997}}}; {\fiel...
Roomware\'94 is a term we coined to refer to room elements with integrated information technology such as interactive tables, walls, or chairs.
\par The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called \'93BEACH\'94, the }{\ul\insrsid12989836 B}{\insrsid129898...
\insrsid12989836 sic }{\ul\insrsid12989836 E}{\insrsid12989836 nvironment for }{\ul\insrsid12989836 A}{\insrsid12989836 ctive }{\ul\insrsid12989836 C}{\insrsid12989836 ollaboration with }{\ul\insrsid12989836 H}{\insrsid12989836 
ypermedia. BEACH provides the software infrastru}{\insrsid12989836 c}{\insrsid12989836 ture for environments supporting 
synchronous collaboration with many different devices. It offers a user interface that also fits to the needs of devices that have no mouse or keyboard, and which require new forms of human-computer and team-computer interaction. To allow synchronous...
aboration BEACH builds on shared documents accessible via multiple interaction devices concu}{\insrsid12989836 r}{\insrsid12989836 rently.
\par During the development, BEACH was restructured and refactored ({\field{\*\fldinst { HYPERLINK \\l RefactorySmalltalk}}{\fldrslt {Roberts {\i et al.}, 1997}}}; {\field{\*\fldinst { HYPERLINK \\l JacobsenSoftwareModelling}}{\fldrslt {Jacobsen, 200...
 was needed to guide developers of ubiquitous computing applications. This led us to the work presented here. Parts of BEACH emerged into a software framework with an architecture that is structured according to the conceptual model for syn
chronous ubiquitous computing applications proposed in this paper. The model aims at offering both flexibility and extensibility for different devices that are part of ubiquitous computing environments.
\par {\*\bkmkstart sContributingAreas}{\*\bkmkstart _Toc19764383}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.1\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 Involved Research Areas{\*\bkmkend sContributingAreas}
{\*\bkmkend _Toc19764383}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Due to the nature of collabor
ative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. }{\field{\*\fldinst {\insrsid12989836 
 REF fContributingAreas \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b020000000800000013000000660043006f006e0074007200690062007500740069006e006700410072006500610073000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989...
}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 ):}{\cs31\super\insrsid12989836 \chftn {\footnote \pard\plain \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  Of course, this is a simplified view on the research areas, focussing on their contributions relevant within the context of this paper.}}}...
\insrsid12989836 
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f236\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Human-Computer Interaction (HCI) deals with user interfaces and interaction tec}{\insrsid12989836 h}{\insrsid1298...
niques.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous intera}{\insrsid12989836 c}{\insrsid12989836 tion with distributed computers.
\par {\pntext\pard\plain\s61 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s61\qj \fi-227\li227\ri0\sa120\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f236\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Software development techniques are needed to ensure extensibility and reusability.
\par }\pard\plain \s29\qc \li0\ri0\sb220\sa220\keepn\nowidctlpar\faauto\rin0\lin0\itap0 \f236\fs20\lang1031\langfe1033\cgrid\langnp1031\langfenp1033 {\insrsid12989836 {\pict{\*\picprop\shplid1025{\sp{\sn shapeType}{\sv 75}}{\sp{\sn fFlipH}{\sv 0}}
{\sp{\sn fFlipV}{\sv 0}}{\sp{\sn fLockAspectRatio}{\sv 1}}{\sp{\sn fillColor}{\sv 268435473}}{\sp{\sn fFilled}{\sv 0}}{\sp{\sn fLine}{\sv 0}}{\sp{\sn fLayoutInCell}{\sv 1}}}\picscalex34\picscaley34\piccropl0\piccropr0\piccropt0\piccropb0
\picw26264\pich13141\picwgoal14890\pichgoal7450\wmetafile8\bliptag-1236891099\blipupi-29{\*\blipuid b6468a25a3265f559acf25026407e277}
0100090000037b04000007002500000000001100000026060f001800ffffffff000010003effffffde01000082160000820d00000900000026060f000800ffff
ffff020000001700000026060f002300ffffffff04001b00544e5050140070f000300000000014000000440d07010000000000000a00000026060f000a00544e
505000000200f4030900000026060f000800ffffffff030000000f00000026060f001400544e505004000c00010000000100000000000000050000000b02de01
3eff050000000c02a40b44170500000004010d00000007000000fc020000eaeaea000000040000002d01000008000000fa020500010000000000000004000000
2d010100040000002d010000090000001d062100f000a00b4017e00140ff040000002d01000007000000fc020000ffffff000000040000002d01020004000000

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

\insrsid12989836 
\par }\pard\plain \s23\qj \li278\ri374\sa200\widctlpar\aspalpha\aspnum\faauto\adjustright\rin374\lin278\itap0 \f4\fs18\lang1033\langfe1033\langnp1033\langfenp1033 {\insrsid12989836 Figure {\*\bkmkstart fContributingAreas}}{\field{\*\fldinst {\insrsid...
 STYLEREF 1 \\s }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 \_}{\field{\*\fldinst {\insrsid12989836  SEQ Figure \\* ARABIC \\s 1 }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 
{\*\bkmkend fContributingAreas}.}{\lang1024\langfe1024\noproof\insrsid12989836  Conttibuting research areas for the design of collaborative ubiquitous computing applications.}{\insrsid12989836 
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
\par {\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.2\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 Outline of the Paper
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 In the following section, requirements for the software infrastructure of a ubi...
 computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following to illustrate the application of the BEACH model and framework. Based on the identified requi
rements, the proposed conceptual application model has been designed, which is presented next. The succeeding section presents the architecture of the BEACH software framework, which has been developed according to the structure suggested by the conc...
l model. The software design of the Passage system is explained as a sample application of the BEACH model and framework. To position the BEACH model against other approaches, the next section co}{\insrsid12989836 m}{\insrsid12989836 
pares the proposed model with related work. The paper closes with a discussion of the conceptual model and ideas for f}{\insrsid12989836 u}{\insrsid12989836 ture work.
\par }{\insrsid7697605 {\b {\i <<…. Bla bla bla … some stuff removed …>>}}
\par {\*\bkmkstart cConceptualModel}{\*\bkmkstart _Toc2659654}{\*\bkmkstart _Toc2659760}{\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpa...
\jclisttab\tx432\hyphpar0\aspalpha\aspnum\faauto\ls128\outlinelevel0\adjustright\rin0\lin432\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A Conceptual Model for Ubiquitous Computing Applications
{\*\bkmkend cConceptualModel}{\*\bkmkend _Toc2659654}{\*\bkmkend _Toc2659760}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A conceptual model defines the very high-level structure of an application ({\f...
 the definition by {\field{\*\fldinst { HYPERLINK \\l NowackStructuresInteractions}}{\fldrslt {Nowack (1999)}}} a \'93co}{\insrsid12989836 n}{\insrsid12989836 
ceptual model describes a conceptual understanding of something, and it is based on concept formation in terms of classification, generalization and aggregation. Hence, conceptual modeling implies abstra}{\insrsid12989836 c}{\insrsid12989836 tion\'94...

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

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

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

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

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

{{\*\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
{{\*\bkmkstart BEACHConnecTables}{Tandler, P., Prante, T., Müller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Sympos...
{\*\bkmkend BEACHConnecTables}}\par
{{\*\bkmkstart AMFFWPatternSyncGW}{Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp.\~225\endash 242. {\field{\*\fl...
{\*\bkmkend AMFFWPatternSyncGW}}\par
{{\*\bkmkstart Chiron2Architecture}{Taylor, R. N., Medvidovic, N., and et al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22\~(6), 390\endash 406.}
{\*\bkmkend Chiron2Architecture}}\par
{{\*\bkmkstart PlasticityFrameworkAgenda}{Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp.\~110\endash 117.}
{\*\bkmkend PlasticityFrameworkAgenda}}\par
{{\*\bkmkstart ClockArchitecture}{Urnes, T. and Graham, T. N., 1999. Flexibly Mapping Synchronous Groupware Architectures to Distributed Implementations. In: Proceedings of Design, Specification and Verification of Interactive Systems (DSV-IS'99), Sp...
{\*\bkmkend ClockArchitecture}}\par
{{\*\bkmkstart VisualWorksUsersGuide}{{\i VisualWorks User's Guide}. ParcPlace-Digitalk, Inc., 999 East Arques Avenue, Sunnyvale, CA, Revision 2.0 (Software Release 2.5), 1995.}
{\*\bkmkend VisualWorksUsersGuide}}\par
{{\*\bkmkstart UbiCompIssues}{Weiser, M., 1993. Some Computer Science Issues In Ubiquitous Computing, Communications of the ACM 36\~(7), 75\endash 84.}

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

The BEACH Application Model and Software Framework for Synchronous Collaboration in Ubiquitous Computing Environments
Peter Tandler
FhG – Fraunhofer Gesellschaft e.V.
IPSI – Integrated Publication and Information Systems Institute
AMBIENTE – Workspaces of the Future
http://ipsi.fraunhofer.de/ambiente/ 
Abstract
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situations, it is desirable to take advantage of their properties for synchronous collaboration. Besides offer...
In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software framework that is the basis for the software i...
Keywords
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, i-LAND, roomware components
1Introduction
Ubiquitous computing environments offer a wide range of devices coming in many different sizes and shapes (Weiser, 1993). Being often occupied by multiple users simultaneously, ubiquitous computing environments must support synchronous work with info...
Current operation systems provide no support for handling this heterogeneity. Synchronous collaboration can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, but these systems have...
Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and Information Systems Institute in Darmstadt (Germany), in the context of the i-LAND project on support for synchronous collaboration with roomware compon...
The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called "BEACH", the Basic Environment for Active Collaboration with Hy...
During the development, BEACH was restructured and refactored (Roberts et al., 1997; Jacobsen, 2000) several times. It became obvious that a conceptual model was needed to guide developers of ubiquitous computing applications. This led us to the work...
1.1Involved Research Areas
Due to the nature of collaborative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. 1-1.1):1
Human-Computer Interaction (HCI) deals with user interfaces and interaction techniques.
Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous interaction with distributed computers.
Software development techniques are needed to ensure extensibility and reusability.

Figure 1-1.1. Conttibuting research areas for the design of collaborative ubiquitous computing applications.
A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
1.2Outline of the Paper
In the following section, requirements for the software infrastructure of a ubiquitous computing environment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following t...
<<…. Bla bla bla … some stuff removed …>>
2A Conceptual Model for Ubiquitous Computing Applications
A conceptual model defines the very high-level structure of an application (Phillips, 1999; Coutaz, 1997). By using this structure for applications, basic components are identified that have a clear separation of concerns, thus supporting their indep...
In this section, a conceptual model for ubiquitous computing applications is presented. Organized by three major design dimensions, which are identified first, its properties are discussed.
2.1Design Dimensions
In order to identify the design dimensions for a conceptual model, results of all contributing research areas (identified in section 1.1) have to be considered. Looking at these four areas, contributions for a conceptual model can be identified (fig....
Human-Computer Interaction (HCI) is concerned with user interface & interaction.
CSCW has identified different degrees of coupling and different mechanisms for sharing.
Ubiquitous computing (UbiComp) has to deal with device heterogeneity and their relation to the environment in which they are used.
And, finally, separating specific concerns and defining levels of abstraction are very important software modeling techniques.

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

The Passage system is an example of how to react upon changes in the physical environment. As mentioned, 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 ...
Besides the physical environment, other contextual information – such as the current task, project, or presence of co-workers – could influence the behavior of the software, so long as this information is available to the application. This part refer...
Software with functionality depending on physical objects and their properties, or other aspects of the user's environment (req. ) is called context-aware (Salber et al., 1999). There is a strong need for context-aware applications in ubiquitous comp...
Interaction Model: Presentation and Interaction
To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with the "i...
As shown in figure 4-2.2, 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 accessed by the user. For example, a data object ...
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 ada...
Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (se...
2.3Second Dimension: Coupling and Sharing
Whenever multiple devices are involved in a software system, the 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 application code and its state. While distributin...
Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupling th...
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 available interaction devices, has to...
As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identified, De...
Depending on how much state is shared, the degree of coupling 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 c...
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 possible to provide awareness information in the ...
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 environment model can be used to give environmental awareness.
This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that "sharing" can be implemented in many different ways. In the case of collaborating devices with quite varying properties – e...
Sharing the Data Model: Collaborative Data Access
In order to access and work collaboratively with shared data (req. ), it is widely agreed that a shared model for documents reduces the complexity in dealing with distributed applications. While there are well-established models defining a shared dat...
Most popular toolkits and frameworks for computer-supported cooperative work provide some mechanism to manage a shared-object space. In toolkits with a centralized architecture (Patterson, 1991), the document is necessarily shared. Replicated (or sem...
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 straightforward access to data objects from diffe...
Sharing the Application Model: Workspace Awareness & Degree of Coupling
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 (Schuckmann et al., 1999). Sharing the editing state gives the ability t...
By changing the state of the application model, the degree of coupling or other possible work modes can be controlled (req. ). Users working with the same application model can work tightly coupled with rich awareness information (Schuckmann et al., ...
Again, the application designer has to decide whether or not a tightly coupled work mode should be supported or how much awareness information is advantageous. As already mentioned, the Passage system allows transporting both data and current editing...
Sharing the User Interface Model: Distributed & Coupled User Interfaces
If one user interacts with different devices at the same time (req. ), it is desirable that their user interfaces are coordinated. This is only possible, if the information about the currently used user interface elements is accessible to all involve...
In addition, some devices actually have several embedded computers (req. ). When a visual interaction area crosses the borders between displays that are physically placed next to each other, but connected to different machines, it is necessary that t...
However, for the Passage system, a shared user interface model is not necessary. It is sufficient that the virtual part of the bridge runs as an application local to each computer equipped with a bridge. Nevertheless, if the user interface is shared,...
Sharing the Environment Model: Environmental Awareness

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

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 Working IEEE/IFIP Conference on So...
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-167.
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 the CHI 99 conference on Human f...
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 Computing Systems (CHI'02), ACM Press, New...
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 European Conference on Computer-S...
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, J. A. (ed.), Human-Computer Interaction...
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 Frameworks: Object-Oriented Foundations of Fra...
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 Systems (CHI'92), ACM Press, pp. 50...
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.), Proceedings of UbiComp'01: Ubiquitous Computing,...
Tandler, P., Prante, T., Müller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Symposium on User Interface and Software...
Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp. 225-242. http://citeseer.nj.nec.com/439075.html.
Taylor, R. N., Medvidovic, N., and et al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22 (6), 390-406.
Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp. 110-117.
Urnes, T. and Graham, T. N., 1999. Flexibly Mapping Synchronous Groupware Architectures to Distributed Implementations. In: Proceedings of Design, Specification and Verification of Interactive Systems (DSV-IS'99), Springer, Heidelberg, New York, pp. ...
VisualWorks User's Guide. ParcPlace-Digitalk, Inc., 999 East Arques Avenue, Sunnyvale, CA, Revision 2.0 (Software Release 2.5), 1995.
Weiser, M., 1993. Some Computer Science Issues In Ubiquitous Computing, Communications of the ACM 36 (7), 75-84.
Winograd, T. and Guimbretière, F., 1999. Visual Instruments for an Interactive Mural. In: Proceeding of the CHI 99 conference on Human factors in computing systems (CHI'99) extended abstracts, ACM Press, New York, NY, pp. 234-235. http://graphics.sta...

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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<article lang="en-US">
<para>The BEACH Application Model and Software Framework for Synchronous Collaboration in Ubiquitous Computing Environments</para>
<para>Peter Tandler</para>
<para>FhG â€“ Fraunhofer Gesellschaft e.V.IPSI â€“ Integrated Publication and Information Systems InstituteAMBIENTE â€“ Workspaces of the Future<ulink url="http://ipsi.fraunhofer.de/ambiente/">http://ipsi.fraunhofer.de/ambiente/</ulink> </para>
<para>Abstract</para>
<para>The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situations, it is desirable to take advantage of their properties for synchronous collaboration. Besides...
<para>In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software framework that is the basis for the soft...
<para>Keywords</para>
<para>Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, i-LAND, roomware components</para><sect1><title>Introduction</title>
<para>Ubiquitous computing environments offer a wide range of devices coming in many different sizes and shapes (Weiser, 1993). Being often occupied by multiple users simultaneously, ubiquitous computing environments must support synchronous work wit...
<para>Current operation systems provide no support for handling this heterogeneity. Synchronous collaboration can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, but these system...
<para>Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and Information Systems Institute in Darmstadt (Germany), in the context of the i-LAND project on support for synchronous collaboration with roomware ...
<para>The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called â€œBEACHâ€, the Basic Environment for Active Collaborati...
<para>During the development, BEACH was restructured and refactored (Roberts et al., 1997; Jacobsen, 2000) several times. It became obvious that a conceptual model was needed to guide developers of ubiquitous computing applications. This led us to th...
<para>Due to the nature of collaborative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. 1-1.1...
      <para>Of course, this is a simplified view on the research areas, focussing on their contributions relevant within the context of this paper.</para>
</footnote>
</para>
<itemizedlist>
   <listitem>
    <para>Human-Computer Interaction (HCI) deals with user interfaces and interaction techniques.</para>
   </listitem>
   <listitem>
    <para>Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.</para>
   </listitem>
   <listitem>
    <para>Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous interaction with distributed computers.</para>
   </listitem>
   <listitem>
    <para>Software development techniques are needed to ensure extensibility and reusability.</para>
   </listitem>
  </itemizedlist>
<para>
<inlinegraphic width="" fileref=""/>
</para>
<para>Figure 1â€‘1.1. Conttibuting research areas for the design of collaborative ubiquitous computing applications.</para>
<para>A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.</para></sect2><sect2><title>Outline of the Paper</title>
<para>In the following section, requirements for the software infrastructure of a ubiquitous computing environment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the follo...
<para><<â€¦. Bla bla bla â€¦ some stuff removed â€¦>></para></sect2></sect1><sect1><title>A Conceptual Model for Ubiquitous Computing Applications</title>
<para>A conceptual model defines the very high-level structure of an application (Phillips, 1999; Coutaz, 1997). By using this structure for applications, basic components are identified that have a clear separation of concerns, thus supporting their...
<para>In this section, a conceptual model for ubiquitous computing applications is presented. Organized by three major design dimensions, which are identified first, its properties are discussed.</para><sect2><title>Design Dimensions</title>
<para>In order to identify the design dimensions for a conceptual model, results of all contributing research areas (identified in section 1.1) have to be considered. Looking at these four areas, contributions for a conceptual model can be identified...
<itemizedlist>
   <listitem>
    <para>Human-Computer Interaction (HCI) is concerned with user interface & interaction.</para>
   </listitem>
   <listitem>
    <para>CSCW has identified different degrees of coupling and different mechanisms for sharing.</para>

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

<para>Besides the physical environment, other contextual information â€“ such as the current task, project, or presence of co-workers â€“ could influence the behavior of the software, so long as this information is available to the application. This ...
<para>Software with functionality depending on physical objects and their properties, or other aspects of the userâ€™s environment (req. ) is called context-aware (Salber et al., 1999). There is a strong need for context-aware applications in ubiquit...
      <para>However, using detected context to trigger functionality always has the danger of relying on misinterpreted information, which can be very annoying for users.</para>
</footnote> Therefore, the environment model must be capable of expressing relevant information, such as spatial relationships between physical objects.</para>
<para>Interaction Model: Presentation and Interaction</para>
<para>To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with ...
<para>As shown in figure 4-2.2, 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 accessed by the user. For example, a data o...
<para>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, ...
<para>Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction mod...
<para>Whenever multiple devices are involved in a software system, the 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 application code and its state. While distr...
<para>Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupl...
<para>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 available interaction devices, ...
<para>As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identifi...
<para>Depending on how much state is shared, the degree of coupling 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 loo...
<para>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 possible to provide awareness information i...
<para>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 environment model can be used to give environmental awareness...
<para>This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that â€œsharingâ€ can be implemented in many different ways. In the case of collaborating devices with quite varying prop...
<para>Sharing the Data Model: Collaborative Data Access</para>
<para>In order to access and work collaboratively with shared data (req. ), it is widely agreed that a shared model for documents reduces the complexity in dealing with distributed applications. While there are well-established models defining a shar...
<para>Most popular toolkits and frameworks for computer-supported cooperative work provide some mechanism to manage a shared-object space. In toolkits with a centralized architecture (Patterson, 1991), the document is necessarily shared. Replicated (...
<para>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 straightforward access to data objects from...
<para>Sharing the Application Model: Workspace Awareness & Degree of Coupling</para>
<para>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 (Schuckmann et al., 1999). Sharing the editing state gives the abi...
<para>By changing the state of the application model, the degree of coupling or other possible work modes can be controlled (req. ). Users working with the same application model can work tightly coupled with rich awareness information (Schuckmann et...
<para>Again, the application designer has to decide whether or not a tightly coupled work mode should be supported or how much awareness information is advantageous. As already mentioned, the Passage system allows transporting both data and current e...
<para>Sharing the User Interface Model: Distributed & Coupled User Interfaces</para>
<para>If one user interacts with different devices at the same time (req. ), it is desirable that their user interfaces are coordinated. This is only possible, if the information about the currently used user interface elements is accessible to all i...
<para>In addition, some devices actually have several embedded computers (req. ). When a visual interaction area crosses the borders between displays that are physically placed next to each other, but connected to different machines, it is necessary ...
<para>However, for the Passage system, a shared user interface model is not necessary. It is sufficient that the virtual part of the bridge runs as an application local to each computer equipped with a bridge. Nevertheless, if the user interface is s...
<para>Sharing the Environment Model: Environmental Awareness</para>

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

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 Working IEEE/IFIP Conference on So...
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-167.
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 the CHI 99 conference on Human...
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 Computing Systems (CHI'02), ACM Press, Ne...
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 European Conference on Computer-S...
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, J. A. (ed.), Human-Computer Interactio...
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 Frameworks: Object-Oriented Foundations of Fra...
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 Systems (CHI'92), ACM Press, pp. 50...
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.), Proceedings of UbiComp'01: Ubiquitous Computing,...
Tandler, P., Prante, T., MÃ¼ller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Symposium on User Interface and Softwar...
Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp. 225-242. http://citeseer.nj.nec.com/439075.html.
Taylor, R. N., Medvidovic, N., and etÂ al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22 (6), 390-406.
Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp. 110-117.
Urnes, T. and Graham, T. N., 1999. Flexibly Mapping Synchronous Groupware Architectures to Distributed Implementations. In: Proceedings of Design, Specification and Verification of Interactive Systems (DSV-IS'99), Springer, Heidelberg, New York, pp. ...
VisualWorks User's Guide. ParcPlace-Digitalk, Inc., 999 East Arques Avenue, Sunnyvale, CA, Revision 2.0 (Software Release 2.5), 1995.
Weiser, M., 1993. Some Computer Science Issues In Ubiquitous Computing, Communications of the ACM 36 (7), 75-84.
Winograd, T. and GuimbretiÃ¨re, F., 1999. Visual Instruments for an Interactive Mural. In: Proceeding of the CHI 99 conference on Human factors in computing systems (CHI'99) extended abstracts, ACM Press, New York, NY, pp. 234-235. http://graphics.st...

t/sample.bib view on Meta::CPAN

@article{Dijkstra-THE-structure,
   author = {Edsger W. Dijkstra},
   title = {The structure of the "THE"-multiprogramming system},
   journal = {Communications of the ACM},
   volume = {11},
   number = {5},
   pages = {341--346},
   publisher = {ACM Press},
   month = may,
   year = {1968},
   keywords = {cooperating sequential processes, multiprocessing, multiprogramming, multiprogramming system, operating system, processor sharing, program verification, real-time debugging, synchronizing primitives, system hierarchy, system levels, sy...
   issn = {0001-0782},
   url = {http://doi.acm.org/10.1145/363095.363143},
   doi = {http://doi.acm.org/10.1145/363095.363143},
   BibDate = {Wed May 29 13:22:34 2002},
   Category = {SW.Model},
   ExportDate = {2003-06-16 11:44:53},
   Identifier = {Dijkstra68}
}

@inproceedings{Manifold-Architecture,

t/sample.bib view on Meta::CPAN

   Recommendation = {\#\#\#},
   Category = {HCI.PostWIMP},
   ExportDate = {2003-06-16 11:44:53},
   BibDate = {2003-06-16 11:44:53},
   PBibNote = {CHI'00, CHI Letters 2(1), pp. 446-453},
   Identifier = {Beaudouin-Lafon 2000}
}

@inproceedings{AMF-FW+PatternSyncGW,
   author = {F. Tarpin-Bernard and B. David and P. Primet},
   title = {Frameworks and patterns for synchronous groupware: AMF-C approach},
   booktitle = {IFIP Working Conference on Engineering for HCI: EHCI'98},
   location = {Greece},
   pages = {225-242},
   publisher = {$\lbrace$$\rbrace$},
   month = {Sep.},
   year = {1998},
   url = {http://citeseer.nj.nec.com/439075.html},
   Category = {CSCW.SW.Model},
   Identifier = {Tarpin-Bernard98},
   ExportDate = {2003-06-16 11:44:53}

t/sample.bib view on Meta::CPAN

@article{GroupKit-RealTime,
   author = {Mark Roseman and Saul Greenberg},
   title = {Building Real Time Groupware with GroupKit, A Groupware Toolkit},
   booktitle = {ACM-ToCHI96},
   journal = {ACM Transactions on Computer-Human Interaction},
   volume = {3},
   number = {1},
   pages = {66-106},
   month = {Mar.},
   year = {1996},
   keywords = {synchronous groupware},
   BibDate = {2003-06-16 11:44:53},
   PBibNote = {ToCHI ca. 96, original submission is available as Tech Rep. \#95/560/12 (Dept. CS, Univ. Calgary, Apr. '95)},
   Recommendation = {+},
   Category = {CSCW.SW},
   Identifier = {Roseman1996},
   ExportDate = {2003-06-16 11:44:53}
}

@inproceedings{XWeb-JoinCapture,
   author = {/Dan R.//Olsen/Jr./ and S. Travis Nielsen and David Parslow},

t/sample.html view on Meta::CPAN

e.V.<BR>IPSI &ndash; Integrated Publication and Information Systems
Institute<BR>AMBIENTE &ndash; Workspaces of the
Future<BR><FONT COLOR="#000000"><I><SPAN STYLE="text-decoration: none"><A CLASS="western" HREF="http://ipsi.fraunhofer.de/ambiente/">http://ipsi.fraunhofer.de/ambiente/</A></SPAN></I></FONT><I>
</I></FONT>
</P>
<H1 CLASS="heading-1*-western">Abstract</H1>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">The devices
available in ubiquitous computing environments offer new
possibilities for interaction. In the context of meetings and
teamwork situations, it is desirable to take advantage of their
properties for synchronous collaboration. Besides offering an adapted
user interface, this requires that the software infrastructure is
designed for <I>synchronous access</I> to shared information objects
using <I>heterogeneous devices</I> with <I>different interaction</I>
characteristics. As this field is still emerging and no mature
standards are at hand, it is necessary to provide guidance for
UbiComp developers how to model their applications to ensure both
extensibility for future developments and reusability in new
contexts.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">In this paper, a
conceptual model for synchronous applications in ubiquitous computing
environments is proposed. To test its applicability, it was used to
structure the architecture of the BEACH software framework that is
the basis for the software infrastructure of <SPAN LANG="">i-LAND</SPAN>
(the ubiquitous computing environment at FhG-IPSI). The BEACH
framework provides the functionality for synchronous cooperation and
interaction with roomware components, i.e. room elements with
integrated information technology. To show how the BEACH model and
framework can be applied, the design of a sample application is
explained. Also, the BEACH model is positioned against related work.
In conclusion, we provide our experiences with the current
implementation.</P>
<H2 CLASS="heading-2*-western">Keywords</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Synchronous
collaboration, heterogeneous devices, software architecture,
conceptual model, BEACH application model and framework, <SPAN LANG="">i-LAND</SPAN>,
roomware components</P>
<H1 CLASS="western">1Introduction</H1>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Ubiquitous computing
environments offer a wide range of devices coming in many different
sizes and shapes [[UbiComp-Issues]]. Being often occupied by multiple
users simultaneously, ubiquitous computing environments must support
synchronous work with information that is shared among all present
devices. Due to the heterogeneous nature of ubiquitous computing
devices, their software infrastructure must enable user interfaces
taking advantage of their different properties. In addition, it must
enable tight collaboration of users working with different devices or
sharing the same device.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Current operation
systems provide no support for handling this heterogeneity.
Synchronous collaboration can be handled by several
computer-supported cooperative work frameworks, groupware systems, or
middleware infrastructures, but these systems have no support for
heterogeneous devices. There are research prototypes aimed at
managing devices with different interaction capabilities, but these
projects mainly deal with interfaces for and discovery of simple
services and lack support for tight collaboration. There is a need
for a software infrastructure designed for handling heterogeneous
environments, providing adequate interaction styles and user
interface concepts, as well as offering capabilities for synchronous
collaboration. As this kind of infrastructure is built on top of
current operating systems, which handle the interaction with the
specific hardware, it can be referred to as &ldquo;meta-operating
system&rdquo; [[Gaia-GaiaOS]].</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Over the last five
years, we have been working at IPSI, the Fraunhofer Integrated
Publication and Information Systems Institute in Darmstadt (Germany),
in the context of the <SPAN LANG="">i-LAND</SPAN> project on support
for synchronous collaboration with roomware components
[[Roomware-Matters], [Roomware-i-LAND], [Roomware-NextGeneration],
[Roomware-SecondGeneration]]. &ldquo;Roomware&rdquo; is a term we
coined to refer to room elements with integrated information
technology such as interactive tables, walls, or chairs.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">The work presented
here was originally triggered by the need to create a software
infrastructure for this roomware environment. This led to the
development of a software prototype called &ldquo;BEACH&rdquo;, the
<U>B</U>asic <U>E</U>nvironment for <U>A</U>ctive <U>C</U>ollaboration
with <U>H</U>ypermedia. BEACH provides the software infrastructure
for environments supporting synchronous collaboration with many
different devices. It offers a user interface that also fits to the
needs of devices that have no mouse or keyboard, and which require
new forms of human-computer and team-computer interaction. To allow
synchronous collaboration BEACH builds on shared documents accessible
via multiple interaction devices concurrently.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">During the
development, BEACH was restructured and refactored
[[Refactory-Smalltalk], [Jacobsen-SoftwareModelling]] several times.
It became obvious that a <I>conceptual model</I> was needed to guide
developers of ubiquitous computing applications. This led us to the
work presented here. Parts of BEACH emerged into a software framework
with an architecture that is structured according to the conceptual
model for synchronous ubiquitous computing applications proposed in
this paper. The model aims at offering both flexibility and
extensibility for different devices that are part of ubiquitous
computing environments.</P>
<H2 CLASS="western"><A NAME="sContributingAreas"></A>1.1Involved
Research Areas</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Due to the nature of
collaborative ubiquitous computing environments, the results of
several related research areas have to be combined to gain an
integrated application model that covers all aspects of interaction
and collaboration (fig. 1-1.1):<SUP><A CLASS="sdfootnoteanc" NAME="sdfootnote1anc" HREF="#sdfootnote1sym"><SUP>1</SUP></A></SUP></P>
<UL>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Human-Computer
	Interaction (HCI) deals with user interfaces and interaction
	techniques.</FONT></P>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Ubiquitous
	computing (UbiComp) explores dynamic environments with heterogeneous
	devices.</FONT></P>
	<LI><P STYLE="margin-bottom: 0cm"><FONT FACE="Times, serif">Computer-Supported
	Cooperative Work (CSCW) offers techniques to handle synchronous
	interaction with distributed computers.</FONT></P>
	<LI><P><FONT FACE="Times, serif">Software development techniques are
	needed to ensure extensibility and reusability.</FONT></P>
</UL>
<P LANG="de-DE" ALIGN=CENTER STYLE="margin-top: 0.39cm; margin-bottom: 0.39cm; widows: 0; orphans: 0; page-break-after: avoid">
<IMG SRC="sample_html_49014637.gif" NAME="Graphic1" ALIGN=BOTTOM WIDTH=342 HEIGHT=172 BORDER=0></P>
<P STYLE="margin-left: 0.49cm; margin-right: 0.66cm; margin-bottom: 0.35cm"><A NAME="fContributingAreas"></A>
<FONT FACE="Helvetica, sans-serif"><FONT SIZE=2 STYLE="font-size: 9pt">Figure
<SPAN LANG="">1</SPAN>&nbsp;1.1.<SPAN LANG=""> Conttibuting research
areas for the design of collaborative ubiquitous computing
applications.</SPAN></FONT></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">A successful model
for collaborative ubiquitous computing applications must combine the
results of all involved research areas.</P>
<H2 CLASS="western">1.2Outline of the Paper</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">In the following
section, requirements for the software infrastructure of a ubiquitous
computing environment to support synchronous collaboration are
discussed. A sample application, the Passage system, is introduced,
which is used in the following to illustrate the application of the
BEACH model and framework. Based on the identified requirements, the
proposed conceptual application model has been designed, which is
presented next. The succeeding section presents the architecture of
the BEACH software framework, which has been developed according to
the structure suggested by the conceptual model. The software design
of the Passage system is explained as a sample application of the
BEACH model and framework. To position the BEACH model against other
approaches, the next section compares the proposed model with related

t/sample.html view on Meta::CPAN

Dimension: Coupling and Sharing</H2>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Whenever multiple
devices are involved in a software system, the 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 application code and
its state. While <I>distributing code</I> among devices is a
technical question unique to every application, <I>sharing state</I>
has conceptual implications, which this section addresses.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Today, many
applications still run entirely local to a single computer, or access
only data that is distributed over a network. Aiming at synchronous
collaboration, crucial aspects of traditional CSCW systems are <I>access
to shared data</I> and <I>coupling the applications </I>of
collaborating users [[Suite-CouplingUIs]]. Therefore, coupling has to
be applied to both the data and the application model
[[COAST-Model]].</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">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 available
interaction devices, has to be exchanged by different devices and

t/sample.html view on Meta::CPAN

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 modifications at a fine
granularity.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">Most popular
toolkits and frameworks for computer-supported cooperative work
provide some mechanism to manage a shared-object space. In toolkits
with a centralized architecture [[Rendezvous-Demands]], the document
is necessarily shared. Replicated (or semi-replicated
[[Groupware-Architectures]]) systems create a shared-object space by
synchronizing the replicated objects [[Clock-Architecture],
[Dragonfly-Architecture], [COAST-ooSyncGroupware]]. In later versions
of GroupKit [[GroupKit-CSCW92], [GroupKit-RealTime]] shared
&ldquo;environments&rdquo; have been introduced as shared data
structures that can trigger callbacks upon changes.</P>
<P CLASS="western" STYLE="margin-bottom: 0.11cm">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 straightforward
access to data objects from different computers, which is necessary
when a passenger is transferred to another roomware component.</P>

t/sample.rtf view on Meta::CPAN

\par }\pard\plain \s18\qj \li0\ri0\sb120\sa120\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Peter Tandler
\par }\pard\plain \s50\ql \li0\ri0\sa360\keep\keepn\nowidctlpar\hyphpar0\faauto\rin0\lin0\itap0 \f236\fs20\lang1024\langfe1024\cgrid\noproof\langnp1033\langfenp1033 {\insrsid12989836 FhG \endash  Fraunhofer Gesellschaft e.V.\line IPSI \endash 
 Integrated Publication and Information Systems Institute\line AMBIENTE \endash  Workspaces of }{\insrsid9272531 the Future}{\insrsid14965794 \line }{\field\fldedit{\*\fldinst {\insrsid14965794 HYPERLINK "http://ipsi.fraunhofer.de/ambiente/"}{
\insrsid12989836 {\*\datafield 
00d0c9ea79f9bace118c8200aa004ba90b0200000003000000e0c9ea79f9bace118c8200aa004ba90b4800000068007400740070003a002f002f0069007000730069002e0066007200610075006e0068006f006600650072002e00640065002f0061006d006200690065006e00740065002f000000}}}{\fldrslt {
\cs51\i\insrsid14965794 http://ipsi.fraunhofer.de/ambiente/}}}{\i\insrsid9272531  }{\i\insrsid12989836 
\par }\pard\plain \s34\ql \li0\ri0\sb240\sa240\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc265...
Abstract{\*\bkmkend _Toc2659586}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situatio
ns, it is desirable to take advantage of their properties for synchronous collaboration. Besides offering an adapted user interface, this requires that the software infrastructure is designed for }{\i\insrsid12989836 synchronous access}{\insrsid12989...
 to shared information objects using }{\i\insrsid12989836 heterogeneous devices}{\insrsid12989836  with }{\i\insrsid12989836 different interaction}{\insrsid12989836 
 characteristics. As this field is still emerging and no mature standards are at hand, it is necessary to provide guidance for UbiComp developers how to model their applic}{\insrsid12989836 a}{\insrsid12989836 tions to ensure both extensibility for f...
ture developments and reusability in new contexts.
\par In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software f
ramework that is the basis for the software infrastructure of }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  (the ubiquitous computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment at FhG-IPSI). The BEACH framework provides the functionality for synchronous cooperation and interaction with roomware components, i.e. room elements
 with integrated information technology. To show how the BEACH model and framework can be applied, the design of a sample application is explained. Also, the BEACH model is positioned against related work. In conclusion, we provide our experiences wi...
e current implementation.
\par }\pard\plain \s52\ql \fi-576\li576\ri0\sb120\sa60\keep\keepn\widctlpar\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\outlinelevel1\adjustright\rin0\lin576\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Keywo...
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836 , roo}{\insrsid12989836 m}{\insrsid12989836...
ware components
\par {\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1\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 Introduction
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Ubiquitous computing environments offer a wide rang
e of devices coming in many different sizes and shapes [[UbiComp-Issues]]. Being often occupied by multiple users simultaneously, ubiquitous co}{\insrsid12989836 m}{\insrsid12989836 
puting environments must support synchronous work with information that is shared among all present devices. Due
 to the heterogeneous nature of ubiquitous computing devices, their software infrastructure must enable user interfaces taking advantage of their different properties. In addition, it must enable tight collaboration of users working with different d}...
\insrsid12989836 e}{\insrsid12989836 vices or sharing the same device.
\par Current operation systems provide no support for handling this heterogeneity. Synchronous collabor}{\insrsid12989836 a}{\insrsid12989836 
tion can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, 
but these systems have no support for heterogeneous devices. There are research prototypes aimed at managing devices with different interaction capabilities, but these projects mainly deal with interfaces for and discovery of simple services and lack...
ort for tight collabor}{\insrsid12989836 a}{\insrsid12989836 
tion. There is a need for a software infrastructure designed for handling heterogeneous environments, providing adequate interaction styles and user interface concepts, as well as offering capabilities for synchronous collaboration. A
s this kind of infrastructure is built on top of current operating systems, which handle the interaction with the specific hardware, it can be referred to as \'93meta-operating sy}{\insrsid12989836 s}{\insrsid12989836 tem\'94 [[Gaia-GaiaOS]].
\par Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and I}{\insrsid12989836 n}{\insrsid12989836 formation Systems Institute in Darmstadt (Germany), in the context of the }{
\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  project on support for synchronous collaboration with roomware components [[Roomware-Matters], [Roomware-i-LAND], [Roomware-NextGeneration], [Roomware-SecondGeneration]]. \'9...
Roomware\'94 is a term we coined to refer to room elements with integrated information technology such as interactive tables, walls, or chairs.
\par The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called \'93BEACH\'94, the }{\ul\insrsid12989836 B}{\insrsid129898...
\insrsid12989836 sic }{\ul\insrsid12989836 E}{\insrsid12989836 nvironment for }{\ul\insrsid12989836 A}{\insrsid12989836 ctive }{\ul\insrsid12989836 C}{\insrsid12989836 ollaboration with }{\ul\insrsid12989836 H}{\insrsid12989836 
ypermedia. BEACH provides the software infrastru}{\insrsid12989836 c}{\insrsid12989836 ture for environments supporting 
synchronous collaboration with many different devices. It offers a user interface that also fits to the needs of devices that have no mouse or keyboard, and which require new forms of human-computer and team-computer interaction. To allow synchronous...
aboration BEACH builds on shared documents accessible via multiple interaction devices concu}{\insrsid12989836 r}{\insrsid12989836 rently.
\par During the development, BEACH was restructured and refactored [[Refactory-Smalltalk], [Jacobsen-SoftwareModelling]] several times. It became obvious that a }{\i\insrsid12989836 conceptual model}{\insrsid12989836 
 was needed to guide developers of ubiquitous computing applications. This led us to the work presented here. Parts of BEACH emerged into a software framework with an architecture that is structured according to the conceptual model for syn
chronous ubiquitous computing applications proposed in this paper. The model aims at offering both flexibility and extensibility for different devices that are part of ubiquitous computing environments.
\par {\*\bkmkstart sContributingAreas}{\*\bkmkstart _Toc19764383}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.1\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 Involved Research Areas{\*\bkmkend sContributingAreas}
{\*\bkmkend _Toc19764383}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Due to the nature of collabor
ative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. }{\field{\*\fldinst {\insrsid12989836 
 REF fContributingAreas \\h }{\insrsid12989836 {\*\datafield 08d0c9ea79f9bace118c8200aa004ba90b020000000800000013000000660043006f006e0074007200690062007500740069006e006700410072006500610073000000}}}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989...
}{\insrsid12989836 \_}{\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 ):}{\cs31\super\insrsid12989836 \chftn {\footnote \pard\plain \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  Of course, this is a simplified view on the research areas, focussing on their contributions relevant within the context of this paper.}}}...
\insrsid12989836 
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f236\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Human-Computer Interaction (HCI) deals with user interfaces and interaction tec}{\insrsid12989836 h}{\insrsid1298...
niques.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous intera}{\insrsid12989836 c}{\insrsid12989836 tion with distributed computers.
\par {\pntext\pard\plain\s61 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s61\qj \fi-227\li227\ri0\sa120\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f236\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Software development techniques are needed to ensure extensibility and reusability.
\par }\pard\plain \s29\qc \li0\ri0\sb220\sa220\keepn\nowidctlpar\faauto\rin0\lin0\itap0 \f236\fs20\lang1031\langfe1033\cgrid\langnp1031\langfenp1033 {\insrsid12989836 {\pict{\*\picprop\shplid1025{\sp{\sn shapeType}{\sv 75}}{\sp{\sn fFlipH}{\sv 0}}
{\sp{\sn fFlipV}{\sv 0}}{\sp{\sn fLockAspectRatio}{\sv 1}}{\sp{\sn fillColor}{\sv 268435473}}{\sp{\sn fFilled}{\sv 0}}{\sp{\sn fLine}{\sv 0}}{\sp{\sn fLayoutInCell}{\sv 1}}}\picscalex34\picscaley34\piccropl0\piccropr0\piccropt0\piccropb0
\picw26264\pich13141\picwgoal14890\pichgoal7450\wmetafile8\bliptag-1236891099\blipupi-29{\*\blipuid b6468a25a3265f559acf25026407e277}
0100090000037b04000007002500000000001100000026060f001800ffffffff000010003effffffde01000082160000820d00000900000026060f000800ffff
ffff020000001700000026060f002300ffffffff04001b00544e5050140070f000300000000014000000440d07010000000000000a00000026060f000a00544e
505000000200f4030900000026060f000800ffffffff030000000f00000026060f001400544e505004000c00010000000100000000000000050000000b02de01
3eff050000000c02a40b44170500000004010d00000007000000fc020000eaeaea000000040000002d01000008000000fa020500010000000000000004000000
2d010100040000002d010000090000001d062100f000a00b4017e00140ff040000002d01000007000000fc020000ffffff000000040000002d01020004000000

t/sample.rtf view on Meta::CPAN

\insrsid12989836 
\par }\pard\plain \s23\qj \li278\ri374\sa200\widctlpar\aspalpha\aspnum\faauto\adjustright\rin374\lin278\itap0 \f4\fs18\lang1033\langfe1033\langnp1033\langfenp1033 {\insrsid12989836 Figure {\*\bkmkstart fContributingAreas}}{\field{\*\fldinst {\insrsid...
 STYLEREF 1 \\s }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 \_}{\field{\*\fldinst {\insrsid12989836  SEQ Figure \\* ARABIC \\s 1 }}{\fldrslt {\lang1024\langfe1024\noproof\insrsid12989836 1}}}{\insrsid12989836 
{\*\bkmkend fContributingAreas}.}{\lang1024\langfe1024\noproof\insrsid12989836  Conttibuting research areas for the design of collaborative ubiquitous computing applications.}{\insrsid12989836 
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
\par {\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.2\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 Outline of the Paper
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 In the following section, requirements for the software infrastructure of a ubi...
 computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following to illustrate the application of the BEACH model and framework. Based on the identified requi
rements, the proposed conceptual application model has been designed, which is presented next. The succeeding section presents the architecture of the BEACH software framework, which has been developed according to the structure suggested by the conc...
l model. The software design of the Passage system is explained as a sample application of the BEACH model and framework. To position the BEACH model against other approaches, the next section co}{\insrsid12989836 m}{\insrsid12989836 
pares the proposed model with related work. The paper closes with a discussion of the conceptual model and ideas for f}{\insrsid12989836 u}{\insrsid12989836 ture work.
\par }{\insrsid7697605 [# \'85. Bla bla bla \'85 some stuff removed \'85 #]
\par {\*\bkmkstart cConceptualModel}{\*\bkmkstart _Toc2659654}{\*\bkmkstart _Toc2659760}{\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpa...
\jclisttab\tx432\hyphpar0\aspalpha\aspnum\faauto\ls128\outlinelevel0\adjustright\rin0\lin432\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A Conceptual Model for Ubiquitous Computing Applications
{\*\bkmkend cConceptualModel}{\*\bkmkend _Toc2659654}{\*\bkmkend _Toc2659760}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 A conceptual model defines the very high-level structure of an application [[Gr...
-Architectures], [PAC-UI-Architecture]]. By using this structure for applications, basic components are identified that have a clear separation of concerns, thus supporting their independence and increasing their flexibility and adaptability. Accordi...
 the definition by [ :inline | [Nowack-Structures+Interactions]] a \'93co}{\insrsid12989836 n}{\insrsid12989836

t/sample.rtf view on Meta::CPAN

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 [[Suite-CouplingUIs]]. Therefore, coupling has to be applied to both the data and the application model [[COAST-Model]].
\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 [[Dewan-FlexibleUICoupling]] can be refined. Coupling can now be defined as }{\i\insrsid12989836 
sharing the same interaction, user interface, or editing (application) state}{\insrsid12989836

t/sample.rtf view on Meta::CPAN

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 [[Rendezvous-Demands]], the document is necessarily shared. Replicated (or semi-replicated
 [[Groupware-Architectures]]) systems create a shared-object space by synchronizing the replicated objects [[Clock-Architecture], [Dragonfly-Architecture], [COAST-ooSyncGroupware]]. In later versions of GroupKit [[GroupKit-CSCW92], [GroupKit-RealTime...
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 [[COAST-Model]]. Sharing the editing state gives the ability to
 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

t/sample.txt view on Meta::CPAN

The BEACH Application Model and Software Framework for Synchronous Collaboration in Ubiquitous Computing Environments
Peter Tandler
FhG – Fraunhofer Gesellschaft e.V.
IPSI – Integrated Publication and Information Systems Institute
AMBIENTE – Workspaces of the Future
http://ipsi.fraunhofer.de/ambiente/ 
Abstract
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situations, it is desirable to take advantage of their properties for synchronous collaboration. Besides offer...
In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software framework that is the basis for the software i...
Keywords
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, i-LAND, roomware components
1Introduction
Ubiquitous computing environments offer a wide range of devices coming in many different sizes and shapes [[UbiComp-Issues]]. Being often occupied by multiple users simultaneously, ubiquitous computing environments must support synchronous work with ...
Current operation systems provide no support for handling this heterogeneity. Synchronous collaboration can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, but these systems have...
Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and Information Systems Institute in Darmstadt (Germany), in the context of the i-LAND project on support for synchronous collaboration with roomware compon...
The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called "BEACH", the Basic Environment for Active Collaboration with Hy...
During the development, BEACH was restructured and refactored [[Refactory-Smalltalk], [Jacobsen-SoftwareModelling]] several times. It became obvious that a conceptual model was needed to guide developers of ubiquitous computing applications. This led...
1.1Involved Research Areas
Due to the nature of collaborative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. 1-1.1):1
Human-Computer Interaction (HCI) deals with user interfaces and interaction techniques.
Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous interaction with distributed computers.
Software development techniques are needed to ensure extensibility and reusability.

Figure 1-1.1. Conttibuting research areas for the design of collaborative ubiquitous computing applications.
A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
1.2Outline of the Paper
In the following section, requirements for the software infrastructure of a ubiquitous computing environment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following t...
[# …. Bla bla bla … some stuff removed … #]
2A Conceptual Model for Ubiquitous Computing Applications
A conceptual model defines the very high-level structure of an application [[Groupware-Architectures], [PAC-UI-Architecture]]. By using this structure for applications, basic components are identified that have a clear separation of concerns, thus su...
In this section, a conceptual model for ubiquitous computing applications is presented. Organized by three major design dimensions, which are identified first, its properties are discussed.
2.1Design Dimensions
In order to identify the design dimensions for a conceptual model, results of all contributing research areas (identified in section 1.1) have to be considered. Looking at these four areas, contributions for a conceptual model can be identified (fig....
Human-Computer Interaction (HCI) is concerned with user interface & interaction.
CSCW has identified different degrees of coupling and different mechanisms for sharing.
Ubiquitous computing (UbiComp) has to deal with device heterogeneity and their relation to the environment in which they are used.
And, finally, separating specific concerns and defining levels of abstraction are very important software modeling techniques.

t/sample.txt view on Meta::CPAN

The Passage system is an example of how to react upon changes in the physical environment. As mentioned, 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 ...
Besides the physical environment, other contextual information – such as the current task, project, or presence of co-workers – could influence the behavior of the software, so long as this information is available to the application. This part refer...
Software with functionality depending on physical objects and their properties, or other aspects of the user's environment (req. ) is called context-aware [[ContextToolkit-AppDevelopment]]. There is a strong need for context-aware applications in ubi...
Interaction Model: Presentation and Interaction
To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with the "i...
As shown in figure 4-2.2, 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 accessed by the user. For example, a data object ...
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 ada...
Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction model (se...
2.3Second Dimension: Coupling and Sharing
Whenever multiple devices are involved in a software system, the 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 application code and its state. While distributin...
Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupling th...
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 available interaction devices, has to...
As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identified, De...
Depending on how much state is shared, the degree of coupling 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 c...
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 possible to provide awareness information in the ...
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 environment model can be used to give environmental awareness.
This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that "sharing" can be implemented in many different ways. In the case of collaborating devices with quite varying properties – e...
Sharing the Data Model: Collaborative Data Access
In order to access and work collaboratively with shared data (req. ), it is widely agreed that a shared model for documents reduces the complexity in dealing with distributed applications. While there are well-established models defining a shared dat...
Most popular toolkits and frameworks for computer-supported cooperative work provide some mechanism to manage a shared-object space. In toolkits with a centralized architecture [[Rendezvous-Demands]], the document is necessarily shared. Replicated (o...
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 straightforward access to data objects from diffe...
Sharing the Application Model: Workspace Awareness & Degree of Coupling
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 [[COAST-Model]]. Sharing the editing state gives the ability to provide ...
By changing the state of the application model, the degree of coupling or other possible work modes can be controlled (req. ). Users working with the same application model can work tightly coupled with rich awareness information [[COAST-Model]]. Tig...
Again, the application designer has to decide whether or not a tightly coupled work mode should be supported or how much awareness information is advantageous. As already mentioned, the Passage system allows transporting both data and current editing...
Sharing the User Interface Model: Distributed & Coupled User Interfaces
If one user interacts with different devices at the same time (req. ), it is desirable that their user interfaces are coordinated. This is only possible, if the information about the currently used user interface elements is accessible to all involve...
In addition, some devices actually have several embedded computers (req. ). When a visual interaction area crosses the borders between displays that are physically placed next to each other, but connected to different machines, it is necessary that t...
However, for the Passage system, a shared user interface model is not necessary. It is sufficient that the virtual part of the bridge runs as an application local to each computer equipped with a bridge. Nevertheless, if the user interface is shared,...
Sharing the Environment Model: Environmental Awareness

t/sample.xml view on Meta::CPAN

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<article lang="en-US">
<para>The BEACH Application Model and Software Framework for Synchronous Collaboration in Ubiquitous Computing Environments</para>
<para>Peter Tandler</para>
<para>FhG â€“ Fraunhofer Gesellschaft e.V.IPSI â€“ Integrated Publication and Information Systems InstituteAMBIENTE â€“ Workspaces of the Future<ulink url="http://ipsi.fraunhofer.de/ambiente/">http://ipsi.fraunhofer.de/ambiente/</ulink> </para>
<para>Abstract</para>
<para>The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situations, it is desirable to take advantage of their properties for synchronous collaboration. Besides...
<para>In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software framework that is the basis for the soft...
<para>Keywords</para>
<para>Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, i-LAND, roomware components</para><sect1><title>Introduction</title>
<para>Ubiquitous computing environments offer a wide range of devices coming in many different sizes and shapes [[UbiComp-Issues]]. Being often occupied by multiple users simultaneously, ubiquitous computing environments must support synchronous work...
<para>Current operation systems provide no support for handling this heterogeneity. Synchronous collaboration can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, but these system...
<para>Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and Information Systems Institute in Darmstadt (Germany), in the context of the i-LAND project on support for synchronous collaboration with roomware ...
<para>The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called â€œBEACHâ€, the Basic Environment for Active Collaborati...
<para>During the development, BEACH was restructured and refactored [[Refactory-Smalltalk], [Jacobsen-SoftwareModelling]] several times. It became obvious that a conceptual model was needed to guide developers of ubiquitous computing applications. Th...
<para>Due to the nature of collaborative ubiquitous computing environments, the results of several related research areas have to be combined to gain an integrated application model that covers all aspects of interaction and collaboration (fig. 1-1.1...
      <para>Of course, this is a simplified view on the research areas, focussing on their contributions relevant within the context of this paper.</para>
</footnote>
</para>
<itemizedlist>
   <listitem>
    <para>Human-Computer Interaction (HCI) deals with user interfaces and interaction techniques.</para>
   </listitem>
   <listitem>
    <para>Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.</para>
   </listitem>
   <listitem>
    <para>Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous interaction with distributed computers.</para>
   </listitem>
   <listitem>
    <para>Software development techniques are needed to ensure extensibility and reusability.</para>
   </listitem>
  </itemizedlist>
<para>
<inlinegraphic fileref="" width=""/>
</para>
<para>Figure 1â€‘1.1. Conttibuting research areas for the design of collaborative ubiquitous computing applications.</para>
<para>A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.</para></sect2><sect2><title>Outline of the Paper</title>
<para>In the following section, requirements for the software infrastructure of a ubiquitous computing environment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the follo...
<para>[# â€¦. Bla bla bla â€¦ some stuff removed â€¦ #]</para></sect2></sect1><sect1><title>A Conceptual Model for Ubiquitous Computing Applications</title>
<para>A conceptual model defines the very high-level structure of an application [[Groupware-Architectures], [PAC-UI-Architecture]]. By using this structure for applications, basic components are identified that have a clear separation of concerns, t...
<para>In this section, a conceptual model for ubiquitous computing applications is presented. Organized by three major design dimensions, which are identified first, its properties are discussed.</para><sect2><title>Design Dimensions</title>
<para>In order to identify the design dimensions for a conceptual model, results of all contributing research areas (identified in section 1.1) have to be considered. Looking at these four areas, contributions for a conceptual model can be identified...
<itemizedlist>
   <listitem>
    <para>Human-Computer Interaction (HCI) is concerned with user interface &amp; interaction.</para>
   </listitem>
   <listitem>
    <para>CSCW has identified different degrees of coupling and different mechanisms for sharing.</para>

t/sample.xml view on Meta::CPAN

<para>Besides the physical environment, other contextual information â€“ such as the current task, project, or presence of co-workers â€“ could influence the behavior of the software, so long as this information is available to the application. This ...
<para>Software with functionality depending on physical objects and their properties, or other aspects of the userâ€™s environment (req. ) is called context-aware [[ContextToolkit-AppDevelopment]]. There is a strong need for context-aware application...
      <para>However, using detected context to trigger functionality always has the danger of relying on misinterpreted information, which can be very annoying for users.</para>
</footnote> Therefore, the environment model must be capable of expressing relevant information, such as spatial relationships between physical objects.</para>
<para>Interaction Model: Presentation and Interaction</para>
<para>To be able to support different styles of interaction (req. , ), the interaction model specifies how different interaction styles can be defined. The term used here describes a part of the software architecture, and should not be confused with ...
<para>As shown in figure 4-2.2, 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 accessed by the user. For example, a data o...
<para>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, ...
<para>Passage defines an interactive visual representation (for the virtual part of the bridge) and physical actions as input (placing objects on the physical part of the bridge). Consequently, its interaction model uses both a visual interaction mod...
<para>Whenever multiple devices are involved in a software system, the 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 application code and its state. While distr...
<para>Today, many applications still run entirely local to a single computer, or access only data that is distributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW systems are access to shared data and coupl...
<para>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 available interaction devices, ...
<para>As discussed above, in a ubiquitous computing environment elements of the user interface can be distributed among several machines (req. ) or among different devices (req. ). Based on the separation of concerns that has been previously identifi...
<para>Depending on how much state is shared, the degree of coupling 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 loo...
<para>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 possible to provide awareness information i...
<para>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 environment model can be used to give environmental awareness...
<para>This section discusses the aspects of sharing the basic models. Before starting a detailed discussion, it has to be noted that â€œsharingâ€ can be implemented in many different ways. In the case of collaborating devices with quite varying prop...
<para>Sharing the Data Model: Collaborative Data Access</para>
<para>In order to access and work collaboratively with shared data (req. ), it is widely agreed that a shared model for documents reduces the complexity in dealing with distributed applications. While there are well-established models defining a shar...
<para>Most popular toolkits and frameworks for computer-supported cooperative work provide some mechanism to manage a shared-object space. In toolkits with a centralized architecture [[Rendezvous-Demands]], the document is necessarily shared. Replica...
<para>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 straightforward access to data objects from...
<para>Sharing the Application Model: Workspace Awareness &amp; Degree of Coupling</para>
<para>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 [[COAST-Model]]. Sharing the editing state gives the ability to pr...
<para>By changing the state of the application model, the degree of coupling or other possible work modes can be controlled (req. ). Users working with the same application model can work tightly coupled with rich awareness information [[COAST-Model]...
<para>Again, the application designer has to decide whether or not a tightly coupled work mode should be supported or how much awareness information is advantageous. As already mentioned, the Passage system allows transporting both data and current e...
<para>Sharing the User Interface Model: Distributed &amp; Coupled User Interfaces</para>
<para>If one user interacts with different devices at the same time (req. ), it is desirable that their user interfaces are coordinated. This is only possible, if the information about the currently used user interface elements is accessible to all i...
<para>In addition, some devices actually have several embedded computers (req. ). When a visual interaction area crosses the borders between displays that are physically placed next to each other, but connected to different machines, it is necessary ...
<para>However, for the Passage system, a shared user interface model is not necessary. It is sufficient that the virtual part of the bridge runs as an application local to each computer equipped with a bridge. Nevertheless, if the user interface is s...
<para>Sharing the Environment Model: Environmental Awareness</para>

( run in 0.306 second using v1.01-cache-2.11-cpan-0d8aa00de5b )