2004
DOI: 10.1504/ijcat.2004.004071
|View full text |Cite
|
Sign up to set email alerts
|

Shared data modeling with UML-G

Abstract: Groupware is explicitly designed to support the cooperation among group members. The implementation of cooperation-aware groupware is supported by several object-oriented toolkits and frameworks, but there is no unified way to model applications built on top of these. We have proposed UML-G as an extensible UML profile for modeling groupware and are in the process of turning it into a community effort. In this article, we identify modeling needs specific to shared data modeling. Shared data is a prerequisite t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0
4

Year Published

2006
2006
2018
2018

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 15 publications
(10 citation statements)
references
References 24 publications
0
6
0
4
Order By: Relevance
“…In our study, we focus on task-based specification of the user interface and we do not cover the UI generation aspects. Therefore we do not consider UML-based notations, such as UML-G [24], which are best suited for software implementation and UI generation or transformation.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In our study, we focus on task-based specification of the user interface and we do not cover the UI generation aspects. Therefore we do not consider UML-based notations, such as UML-G [24], which are best suited for software implementation and UI generation or transformation.…”
Section: Related Workmentioning
confidence: 99%
“…As pointed out in [33], task analysis is used in various steps of the development process and we focus here on the specification of a system to be then developed. In a previous study [10], we have reviewed several task-based notations, such as CTT [17], GTA [32,33], MABTA [13], CUA [21] or UML-G [24] and we have highlighted the lack of support to describe the multimodal aspects of a multi-user interface. Addressing this issue, we present a notation, named COMM, that enables the designer to specify collaborative and multimodal aspects of an interactive system.…”
Section: Introductionmentioning
confidence: 99%
“…Depending on the application requirements choose an appropriate SHARING INTERFACE 3.4 that allows decoupling the SHARING MODEL 3.4 from the DISTRIBUTION SCHEME 3.4 as well as mechanisms for PERSISTENCY 3.4 and TIME-DEPENDENCY 3.4 . When specifying the SHARING MODEL 3.4 , start with the TYPE OF SHARED DATA 3.4 that determines 'what' needs to be shared and may vary according to the application requirements (Rubart and Dawabi, 2004). As a good starting point one can look at the components identified in the FUNCTIONAL DECOMPOSITION MODEL 3.3 .…”
Section: Forcesmentioning
confidence: 99%
“…There are some proposals for conceptual modelling notations of aspects of group work. Among these notations may be mentioned: a) APM (Action Port Model) focused on modeling the workflows developed by groups [6]; b) PROCLETS that proposes a notation for interaction processes associated with managing multiple workflows [7]; c) AMENITIES, that proposes extensions of UML notation (COMO-UML) for groupware modelling with emphasis on the modelling of dynamic aspects [8]; and d) UML-G, also focuses on the modelling of groupware but with emphasis on data modelling [9], [10].…”
Section: Introductionmentioning
confidence: 99%