![]() |
CiteULike | ![]() |
hawkestein's CiteULike | ![]() |
![]() |
|
![]() |
Register | ![]() |
Log in | ![]() |
The Role of Domain Expenence in Software Designby: B. Adelson, E. Soloway
Software Engineering, IEEE Transactions on In Software Engineering, IEEE Transactions on, Vol. SE-11, No. 11. (1985), pp. 1351-1360.
|
Reviews
[Write a review of this article]
Notes for this articleReferenced in: 10.1016/j.infsof.2007.02.010
Find related articles from these CiteULike users
Find related articles with these CiteULike tags
Posting History
AbstractA designer's expertise rests on the knowledge and skills which develop with experience in a domain. As a result, when a designer is designing an object in an unfamiliar domain he will not have the same knowledge and skills available to him as when he is designing an object in a familiar domain. In this paper we look at the software designer's underlying constellation of knowledge and skills, and at the way in which this constellation is dependent upon experience in a domain. What skills drop out, what skills, or interactions of skills come forward as experience with the domain changes? To answer the above question, we studied expert designers in experimentally created design contexts with which they were differentially familiar. In this paper we describe the knowledge and skills we found were central to each of the above contexts and discuss the functional utility of each. In addition to discussing the knowledge and skills we observed in expert designers, we will also compare novice and expert behavior.
BibTeX record
RIS record