Anais do IHC'2001 - Departamento de Informática e Estatística - UFSC

More documents

Recommendations

Info

66 Anais do IHC’2001 - IV Workshop sobre Fatores Humanos em Sistemas Computacionais As pointed out by Beyer and Holtzblatt [3], all artifacts even the most informal, have structure and content (information that the artifact carries). In designing the artifact, the designer establishes a conversation with the design medium, in the sense explained by Schon [24]. This level of communication is also part of the process and thus should be considered. A fractal communication model, proposed in [21], [22] captures the nature of the communication process involved in software design, while stresses the fact that, in order to design the primary message (the interface), other fractionated messages must carefully be designed and appropriate channels must be chosen to convey them. Figure 2 illustrates the main concepts of the fractal model of communication. A Figure 2: The fractal model of communication In this diagram, nodes represent the communication agents (A and A’) and channels (C and C’). The arrows are bi-directional, which means that an agent sends and receives messages. Nodes C’ represent the fractal nature of communication. Different foci of the design process can be highlighted: the designer-user communication (A-A’) using the interface as message, in a first level, as the interface is the unity- message conveyed by the computer (which is the first channel). The designer-artefact communication (A-C), and the usercomputer communication (C-A’) are represented in a second level of the fractal, having C’ as special channels. An inner level could be opened for analysis, showing a third level of the fractal structure, as illustrated by Figure 3. Usability engineers, for example, communicate with users using a usability test as channel. In designing the test, usability engineers communicate with the emergent artefact (the test) through a checklist as channel, for example. In this model, the interface is understood as a unity-message that reflects what was grasped through the fractionated messages. So, the interface as a unity-message is directly affected by the choice of channels and messages used to compose the fractionated messages during the design process. This means that, in designing the interface, or the unity message, many fractionated messages are being exchanged. Each one of those messages is also being designed and should be carefully designed to make the designer-user communication through the unity-message smoother. As both senders and receivers in this communication process, designers and users change turns and cooperate on the development of the interface. C c’ c’ A’
Anais do IHC’2001 - IV Workshop sobre Fatores Humanos em Sistemas Computacionais 67 Task list Check list Usability engineers Usability test Figure 3. An instance of the fractal inner level Users This model reflects the authors’ understandings about design. This structure can better reflect the potential contributions of each part in the whole process. Also, in designing the interface, designers should also design other messages and choose appropriate channels to send them. The design of the fractionated messages is highly influenced by the development context [9] and the particular characteristics of each project. The conversational process (first level) and the designers and users communication with the emerging artefact (second level) are made explicit in the proposed model as we consider them fundamental aspects to improve the quality of the communication in the first level. 4. Meta-Modelling a Product Development Cycle: A Case Study The meta-model was applied in a major software design company, given the pseudonym here “ORG”, which employs leading professionals in all areas involved with the creation of commercial applications also called off-the-shelf software. The main groups identified as agents of the communication process were marketing people, program managers, designers, usability engineers, developers, testers, and support. Customers, clients, betausers and users are four types of external agents called “users”: clients are people who have already bought the product and receive the service of the support team for problems with the product. Customers represent the market: people who are identified by the marketing as a potential client. Users are the subjects recruited by the usability team to participate in the usability tests. Actually, these three categories of persons are potential end-users for the product. Figure 3 illustrates the meta-model applied to the product development cycle of this particular organisation. An overview of the communication among the groups is showed in a simplified way, with two levels of the fractal structure.
Page 1 and 2:
De 15 a 17 de outubro de 2001 Flori
Page 3 and 4:
Sumário Apresentação............
Page 5 and 6:
Análise Ergonômica do Estado da A
Page 7 and 8:
de formidável coesão, denominado
Page 9 and 10:
Sociedade Brasileira de Computaçã
Page 11:
Fund. Educacional de Criciúma - FU
Page 15 and 16:
Palestras Internacionais Online Com
Page 17:
Objetivos: O objetivo deste mini-cu
Page 21 and 22:
Anais do IHC’2001 - IV Workshop s
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36: Anais do IHC’2001 - IV Workshop s
Page 85: Anais do IHC’2001 - IV Workshop s
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289:
IV Workshop sobre Fatores Humanos e
Page 292 and 293:
272 Anais do IHC’2001 - IV Worksh
Page 294 and 295:
274 4. Considerações Finais Anais
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
314 Artigos Anais do IHC’2001 - I
show all

Anais do IHC'2001 - Departamento de Informática e Estatística - UFSC

Create successful ePaper yourself

Delete template?

Save as template?