Number of co-authors:10
Number of publications with 3 favourite co-authors:Eric Knauss:3Siv Hilde Houmb:1Shareeful Islam:1
Kurt Schneider's 3 most productive colleagues in number of publications:Alexander Repennin..:27Eric Knauss:4Frank Houdek:3
User error: replace user and press any key to continue.
-- Popular computer one-liner
Read the fascinating history of Wearable Computing, told by its father, Steve Mann
Read Steve's chapter !
Publications by Kurt Schneider (bibliography)
Knauss, Eric, Houmb, Siv Hilde, Schneider, Kurt, Islam, Shareeful and Jürjens, Jan (2011): Supporting Requirements Engineers in Recognising Security Issues. In: Berry, Daniel M. and Franch, Xavier (eds.) Requirements Engineering Foundation for Software Quality - 17th International Working Conference, REFSQ 2011, Essen, Germany, March 28-30, 2011. Proceedings 2011. pp. 4-18.
Brill, Olesia, Schneider, Kurt and Knauss, Eric (2010): Videos vs. Use Cases: Can Videos Capture More Requirements under Time Pressure?. In: Wieringa, Roel and Persson, Anne (eds.) Requirements Engineering Foundation for Software Quality, 16th International Working Conference, REFSQ 2010, Essen, Germany, June 30 - July 2, 2010. Proceedings 2010. pp. 30-44.
Knauss, Eric, Schneider, Kurt and Stapel, Kai (2009): Learning to Write Better Requirements through Heuristic Critiques. In: RE 2009, 17th IEEE International Requirements Engineering Conference, Atlanta, Georgia, USA, August 31 - September 4, 2009 2009. pp. 387-388.
Landes, Dieter, Schneider, Kurt and Houdek, Frank (1999): Organizational Learning and Experience Documentation in Industrial Software Projects. In International Journal of Human-Computer Studies, 51 (3) pp. 643-661.
Learning from experiences in the software domain is an important issue for the DaimlerChrysler Corporation. Unfortunately, there are no textbook recipes on how a process of organizational learning can be established. In particular, those types of experiences must be identified that are potentially valuable for reuse. Furthermore, the organization and representation of such experiences must be defined in such a way that they can easily be retrieved and used for the solving of new problems. In this paper, we provide some insights that we gained during the examination of these issues in projects aiming at establishing a so-called experience factory.
© All rights reserved Landes et al. and/or Academic Press
Lindstaedt, Stefanie N. and Schneider, Kurt (1997): Bridging the Gap between Face-to-Face Communication and Long-Term Collaboration. In: Payne, Stephen C. and Prinz, Wolfgang (eds.) Proceedings of the International ACM SIGGROUP Conference on Supporting Group Work 1997 November 11-19, 1997, Phoenix, Arizona, USA. pp. 331-340.
During the different phases of a project, stakeholders have different communication needs and make use of different communication media to satisfy them. A group memory system must be able to support and capture these different communication types. We describe two systems, GIMMe and FOCUS, the integration of which allows us to support and effortlessly capture electronic mail conversations and structural changes in their organizational hierarchy as well as face-to-face demonstrations of software prototypes. As media and style of collaboration change, the emerging group memory goes through a metamorphosis that parallels group members' changing demands. This approach promises low initial effort and the potential to grow in value.
© All rights reserved Lindstaedt and Schneider and/or ACM Press
Schneider, Kurt and Repenning, Alexander (1995): Deceived by Ease of Use -- Using Paradigmatic Applications to Build Visual Design Environments. In: Proceedings of DIS95: Designing Interactive Systems: Processes, Practices, Methods, & Techniques 1995. pp. 177-188.
Application frameworks for visual design environments usually offer a wide range of features and easy-to-use mechanisms to develop applications. We observed that sometimes those features deceive application designers: Tempted by the desire to make rapid progress, designers go into too much detail about easy things too early in the process, like graphical representations. After the easy-to-use mechanisms have been exploited, they find themselves stuck and frustrated. Premature design decisions made during the feature-driven phase can corrupt application system architecture or require abandonment of much work. Extensive rework endangers project success. Paradigmatic applications can help to bridge the gap between application framework features and intended application -- better than manuals or additional features can. As examples and sources for reusable components, this special kind of exemplary applications directs the attention of designers to higher-level building blocks and helps them to avoid premature feature exploitation. We characterize paradigmatic applications and describe their impact on the design process.
© All rights reserved Schneider and Repenning and/or ACM Press
Show this list on your homepage
Join the technology elite and advance:
Changes to this page (author)31 Oct 2011: Added31 Oct 2011: Added
31 Oct 2011: Added
26 Feb 2010: Modified
22 Jun 2007: Added
28 Apr 2003: Added
Page maintainer: The Editorial Team