BibSonomy :: publication ::

tag user group author concept BibTeX key search:all search:neilernst

The blue social bookmark and publication sharing system.

(0)

This publication has not been reviewed yet.

rating distribution

average user rating

The average rating is computed over all reviews. However, some of them may be invisible to you due to the visibility setting chosen by the reviewers.

(0.0 of 5.0 based on 0 reviews)

Preserving knowledge in design projects: what designers need to know

by: James D. Herbsleb, and Eiji Kuwana

In: CHI '93: Conference on Human factors in computing systems Amsterdam, The Netherlands: ACM (1993) , p. 7--14.

Resources (URL, PDF, PS...)

URL:	http://portal.acm.org/citation.cfm?doid=169059.169061
DOI:	10.1145/169059.169061
Additional URLs:	blog post on paper URL:text:

In order to inform the design of technology support and new procedural methods for software design, we analyzed the content of real design meetings in three organizations, focusing in particular on the questions the designers ask of each other. We found that most questions concerned the project requirements, particularly what the software was supposed to do and, somewhat less frequently, scenarios of use. Questions about functions to be performed by software components and how these functions were to be realized were also fairly frequent. Rationales for design decisions were seldom asked about. The implications of this research for design tools and methods are discussed.

Description

Preserving knowledge in design projects

BibTeX record

@inproceedings{herbsleb93,
  abstract = {In order to inform the design of technology support and
new procedural methods for software design, we analyzed
the content of real design meetings in three organizations,
focusing in particular on the questions the designers ask of
each other. We found that most questions concerned the
project requirements, particularly what the software was
supposed to do and, somewhat less frequently, scenarios of
use. Questions about functions to be performed by
software components and how these functions were to be
realized were also fairly frequent. Rationales for design
decisions were seldom asked about. The implications of
this research for design tools and methods are discussed.},
  added-at = {2007-12-17T18:15:01.000+0100},
  address = {Amsterdam, The Netherlands},
  author = {Herbsleb, James D. and Kuwana, Eiji},
  biburl = {http://www.bibsonomy.org/bibtex/22fb0378edddebb0c737393f4808e9ab9/neilernst},
  booktitle = {CHI '93: Conference on Human factors in computing systems},
  description = {Preserving knowledge in design projects},
  doi = {http://doi.acm.org/10.1145/169059.169061},
  interhash = {75ce4740d93be6d3589df2453ae725c9},
  intrahash = {2fb0378edddebb0c737393f4808e9ab9},
  isbn = {0-89791-575-5},
  keywords = {design empirical},
  pages = {7--14},
  publisher = {ACM},
  timestamp = {2007-12-17T18:15:01.000+0100},
  title = {Preserving knowledge in design projects: what designers need to know},
  url = {http://portal.acm.org/citation.cfm?doid=169059.169061},
  year = 1993
}

Endnote record

%0 Conference Paper
%1 herbsleb93
%A Herbsleb, James D.
%A Kuwana, Eiji
%B CHI '93: Conference on Human factors in computing systems
%@ 0-89791-575-5
%C Amsterdam, The Netherlands
%D 1993
%I ACM
%K 
%P 7--14
%T Preserving knowledge in design projects: what designers need to know
%R http://doi.acm.org/10.1145/169059.169061
%U http://portal.acm.org/citation.cfm?doid=169059.169061
%X In order to inform the design of technology support and
new procedural methods for software design, we analyzed
the content of real design meetings in three organizations,
focusing in particular on the questions the designers ask of
each other. We found that most questions concerned the
project requirements, particularly what the software was
supposed to do and, somewhat less frequently, scenarios of
use. Questions about functions to be performed by
software components and how these functions were to be
realized were also fairly frequent. Rationales for design
decisions were seldom asked about. The implications of
this research for design tools and methods are discussed.