A design pattern for mobile-distributed knowledge spaces

Eßmann, Bernd; Hampel, Thorsten

doi:10.1145/1234324.1234327

Cited by 4 publications

(5 citation statements)

References 42 publications

(42 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are also proposals to deal with coordination services in wireless networks; however such proposals assume signal stability and use centralized components (Essmann and Hampel 2005;Licea 2006). These proposals were designed to support micro-mobility or work in environments completely covered by a wireless network (i.e., using access points).…”

Section: Related Workmentioning

confidence: 99%

A Patterns System to Coordinate Mobile Collaborative Applications

2011

View full text Add to dashboard Cite

Advances in wireless communication technologies and mobile computing devices open new possibilities to carry out computer-supported mobile collaborative work. However this opportunity brings also a number of challenges to designers, since collaborative applications supporting mobile activities involve requirements which are not present in stationary collaboration scenarios. For example, mobile collaborative applications should not use centralized components because it jeopardizes the autonomy required by mobile workers. In order to help designers to deal with these new requirements, this article presents a patterns system focused on the coordination support required for mobile collaborative work. Such patterns represent reusable designs that help reduce design risks, cost and time. The article also presents three mobile collaborative applications in which proposed patterns were included in their respective designs.

show abstract

Section: Related Workmentioning

confidence: 99%

A Patterns System to Coordinate Mobile Collaborative Applications

2011

View full text Add to dashboard Cite

show abstract

“…Autonomy [4,11,13,14,16,17]. Participants in a mobile collaboration process must be able to work autonomously through the system, storing their work in an individual workspace.…”

Section: Requirements To Design Mswmentioning

confidence: 99%

“…However, even if collaboration is tightly coupled, the users' mobility may cause disconnections and changes in group structure, hence applications should also function autonomously. Flexibility [4,13,16,17]. Mobile collaborative systems must support frequent changes in group size and structure, as mobility may cause group participants to connect or disconnect from the group.…”

Section: Requirements To Design Mswmentioning

confidence: 99%

“…Thus, participants will be able to choose their own level of involvement in the collaboration according to their needs and situation. Consistency and Availability [4,14,19]. Frequent disconnections and autonomous work usually cause inconsistencies and unavailability of the resources that are being shared by the group members.…”

Section: Requirements To Design Mswmentioning

confidence: 99%

“…Full replication of data and services is highly recommended in scenarios of mobile collaboration. Connectivity [1,4,8,13,15,16,19,20]. Most work scenarios do not provide wireless communication support; therefore the MSW should function based on a Mobile Ad-hoc Network (MANET).…”

Section: Requirements To Design Mswmentioning

confidence: 99%

See 2 more Smart Citations

General requirements to design mobile shared workspaces

Herskovic

Ochoa

Pino

et al. 2008

2008 12th International Conference on Computer Supported Cooperative Work in Design

View full text Add to dashboard Cite

Traditionally, collaborative systems have been difficult to conceive, design and implement. Although several requirements involved in these products are recurrent, some become invisible to clients and developers because they are part of the product backend. This situation is worse in the case of mobile groupware because the general requirements to support mobile collaboration are still unclear. This paper presents a framework of general requirements that are usually present in mobile shared workspaces. These requirements are not always visible; therefore the framework acts as a checklist helping developers to consider them. Thus, the framework could increase the success probability of mobile shared workspaces.

show abstract