Proceedings ACS/IEEE International Conference on Computer Systems and Applications
DOI: 10.1109/aiccsa.2001.934012
|View full text |Cite
|
Sign up to set email alerts
|

Facilitating group formation and role allocation in software engineering groups

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0
1

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(9 citation statements)
references
References 11 publications
0
8
0
1
Order By: Relevance
“…Similarly, in (Winter 2004) it is proposed a group model that combines Belbin's team roles with team members' knowledge, type of task that needs to be done, and group contextual factor (such as localization and time pressures). Other investigations also propose similar models applied to the Software Engineering Area in order to make teams with better performance and efficiency (Dafoulas 2001). In (Aguilar et al 2007) it is proposed an intelligent agent that acts like another team member and takes the needed role in order to balance the team.…”
Section: Observed Interactionsmentioning
confidence: 99%
“…Similarly, in (Winter 2004) it is proposed a group model that combines Belbin's team roles with team members' knowledge, type of task that needs to be done, and group contextual factor (such as localization and time pressures). Other investigations also propose similar models applied to the Software Engineering Area in order to make teams with better performance and efficiency (Dafoulas 2001). In (Aguilar et al 2007) it is proposed an intelligent agent that acts like another team member and takes the needed role in order to balance the team.…”
Section: Observed Interactionsmentioning
confidence: 99%
“…4) A role has meaning only in a role model [47] or has meaning generally [25,49,50]. 5) Roles have [49,50] or have not [81] their own states and behaviors.…”
Section: Roles In Object Modellingmentioning
confidence: 99%
“…Recently, more and more papers that apply roles have been published. Roles are paid more and more attention in different areas relevant to information systems such as modeling [4, 8, 10, 35-39, 47, 49, 50, 56, 67-70, 72-73, 75-77], software design [25,45,47,56,69,88,97], access control [2, 3, 12, 22, 31-33, 46, 65, 76], system administration [54,61,75], agent systems [11, 18-20, 28, 30, 59, 60, 66, 84], database systems [21,62,71], and Computer-Supported Cooperative Work (CSCW) systems [9,29,40,52,74,87,92,94,96].…”
Section: Introductionmentioning
confidence: 99%
“…The proposed role-based collaboration and theory can gain significant applications in group decision support systems (GDS) [5], [32], [36], management [27], [34], personalized interfaces [12], [25], [28], [30], agent systems [2], [7], and software engineering [8], [20], [22], [26], [33].…”
Section: Requirements For Role-based Collaborationmentioning
confidence: 99%
“…By "dynamic" we mean that role assignment and reassignment occur during collaboration. People may be expected to dynamically change their roles according to the needs of the group and organization [8], [22]. Even though some argue that there are benefits from having "fuzzy" role definitions, particularly for more creative or uncertain work areas, there is still a period when the collaborators keep their definite roles and the "fuzzy" state should be resolved by role transitions before operations begin.…”
Section: Requirements For Role-based Collaborationmentioning
confidence: 99%