Irvin R. Katz
Has also published under the name of:
"I. R. Katz"
About the author:
No description available of Irvin R. Katz...
Publications by Irvin R. Katz (bibliography)
» 2001 «
Katz, Irvin R., Petre, Marian and Leventhal, Laura Marie (2001): Editorial: Empirical Studies of Programmers. In International Journal of Human-Computer Studies, 54 (2) pp. 185-188
Katz, Irvin R. and Bauer, Malcolm I. (2001): SourceFinder: Course preparation via linguistically targeted web search. In Educational Technology & Society, 4 (3)
» 1995 «
Katz, Irvin R., Mack, Robert L., Marks, Linn, Rosson, Mary Beth and Nielsen, Jakob (eds.) Proceedings of the ACM CHI 95 Human Factors in Computing Systems Conference May 7-11, 1995, Denver, Colorado.
Katz, Irvin R. (1995): FRADS: A System for Facilitating Rapid Prototyping by End Users. In: Proceedings of the Sixth International Conference on Human-Computer Interaction July 9-14, 1995, Tokyo, Japan. pp. 53-58.
While user interface toolkits and managers facilitate prototyping by programmers, few systems allow nonprogrammers to create their own applications. In this paper, we report some techniques that bring prototyping to nonprogramming domain experts, namely professional test developers at Educational Testing Service. The Free-Response Authoring and Delivery System (FRADS) allows professional test developers to create dynamic, working prototypes of computer-based test questions. FRADS was designed to leverage nonprogrammers' experience with commercial graphics packages. Test developers create questions by importing graphics and other user-interface objects, choosing the tools to provide to students in responding to the question, and delineating -- via dialog boxes and specially designed graphical objects -- how the tools and provided interface objects interact. With FRADS, we explore how much "programming power" can be obtained by using direct, graphical specification of applications.
Copyrights may apply
Kaplan, R. M. and Katz, Irvin R. (1995): Designing Interfaces for Computer-Based Assessments. In: Proceedings of the Sixth International Conference on Human-Computer Interaction July 9-14, 1995, Tokyo, Japan. pp. 83-88.
Over the last several years we have developed many new constructed-response items types. Part of our efforts in this process has been to develop, in conjunction with the item types, automatic or semi-automatic means for scoring these items. The development of scoring processes feeds directly back to the interface design process. Because creating complex intelligent applications to analyze a particular item can be time consuming, costly, and result in a process that cannot be generally applied, this approach to scoring these items is not a viable approach. An alternative to this is to constrain the item interface in such a way as to assist the scoring process while at the same time leaving the task realistic. We have shown two item types for which this type of development process took place. The first is a graphical task for architects. Rather than allow an architect to develop a completely open-ended solution, the item interface collects the same information while constraining the activities of the architect. Similarly, the second item, in the domain of writing, constrains the activities of the writer while collecting information like that which would be produced in a completely open-ended writing task.
Copyrights may apply
» 1987 «
Katz, Irvin R. and Anderson, John R. (1987): Debugging: An Analysis of Bug-Location Strategies. In Human-Computer Interaction, 3 (4) pp. 351-399
This article presents a series of four experiments investigating students' debugging of LISP programs. The experiments involve a population of subjects who know LISP reasonably well and whose errors are best classified as slips (Brown & Van Lehn, 1980). That is, students are unlikely to repeat the same errors either within their program or across programs (Experiment 1). The students' understanding of LISP is also reflected in their debugging behavior: They can usually fix a bug once they locate it. Students' difficulties are in locating the erroneous line of code. We observe that students use a variety of bug-location strategies during debugging (Experiment 2) and that the choice of strategy differs depending on whether students are debugging their own programs or other students' programs (Experiment 3). In addition, we observe that although the different bug-location strategies affect which lines of a program are searched, once students decide on a line, their ability to judge whether or not the line is correct and their ability to correct an error are not substantially affected by the strategy being used to locate the line (Experiment 4). Finally, we argue that our results have implications not only for debugging in other computer languages, but for the general processes involved in troubleshooting as well.
Copyrights may apply
SHOW THIS LIST ON YOUR HOMEPAGE
What do YOU think?
Give us your opinion! Do you have any comments/additions
that you would like other visitors to see?
You say:
Mar 18th, 2010
Changes to this page (author)
26 Feb 2010: Enabled abstracts to be shown on Irvin R. Katz's author page.12 Jun 2009: Author was edited (approved by an editor)31 May 2009: Author was edited
29 Jun 2007: Author was added to the bibliography
29 Jun 2007: Author was edited
29 Jun 2007: Author was edited
28 Apr 2003: Added the author to the bibliography