Table 2 Key concepts in CFDSD
From: CFDSD: a Communication Framework for Distributed Software Development
ID | Concept | How CFDSD approach |
|---|---|---|
1 | Site | Teams, home-office and crowdsourcing, branches, |
offshore | ||
2 | Software process | Abstraction. Create a link between message and project |
activity. | ||
3 | Tools | Software engineering tools and communications tools |
(including bots). | ||
4 | Physical distance | Site Geocoordinate. |
5 | Temporal distance | Work-schedule and time-zone. |
6 | Media | Only computer-mediated communication (content |
and logs) | ||
7 | Computer-mediated communication | Synchronous and asynchronous interaction of |
any CMC tool. | ||
8 | Interaction | Unidirectional stream of communication, initiated by |
a sender and delivered to one or more receivers. | ||
9 | Conveyance | Only record-generating interactions and does |
not address face-to-face communication. | ||
10 | Convergence | Evaluation based on artifacts. |
11 | Synchronism | Site communication synchronism. It does not address |
the synchrony between individuals (face-a-face). | ||
12 | Feedback | Specific unilateral interaction. |
13 | Communication frequency | Based on the send time. |
14 | Communication turn-taking | Switching among talkers (dyadic or not) and identify |
the communication purpose. | ||
15 | Parallelism | Record date/time and create a unique id per interaction. |
16 | Rehearsability | Not applied by the CFDSD. |
17 | Reprocessability | Store all interaction, but does not look if receiver |
reprocesses the message. | ||
18 | Appropriation | Not applied by the CFDSD. |
19 | Symbol set | CFDSD encapsulates any set of symbols, but it cannot |
parse them in this work. |