Browsing by Author "Schneider, Kevin"

Now showing 1 - 3 of 3
  • No Thumbnail Available
    ItemMetadata only
    Augmenting Emotional Requirements with Emotion Markers and Emotion Prototypes
    (IEEE, 2009) Callele, David; Neufeld, Eric; Schneider, Kevin
    A production-phase weakness in emotional requirements was identified and resolved during a follow-up study. The definition of emotional requirements was extended to include emotion prototypes and emotion markers. Improved practices for identifying media assets for emotional requirements were developed, enhancing their utility to the production process.
  • No Thumbnail Available
    ItemMetadata only
    An Introduction to Experience Requirements
    (IEEE, 2010) Callele, David; Neufeld, Eric; Schneider, Kevin
    We consider the application of requirements engineering principles and techniques to the elicitation, capture, and representation of the output of the user experience design process. A stimulus-perception-response model is used to motivate experience requirements, defined as descriptions of user experiences that must be met (functional experiences) or are satisfaction goals (non-functional experiences). We identify potential benefits and look at experience requirements in video games.
  • No Thumbnail Available
    ItemMetadata only
    UI traces: Supporting the maintenance of interactive software
    (IEEE, 2009) Sutherland, Andrew; Schneider, Kevin
    We propose a method to support the maintenance of interactive software systems with user interface traces, that involves: (1) collecting execution traces of an interactive system, (2) segmenting execution traces into user interface traces according to user interface activity, and (3) mapping the user interface activity to the implementation activity. To support our approach, we developed a tool that uses aspect-oriented programming and load-time weaving to collect user interface traces from an interactive system. The tool allows us to browse the user interface traces and view user interface related data such as: user input, display updates, and thread activity. Using our tool, we demonstrate how developers can orient themselves and identify the slice of code relevant to performing common software maintenance tasks.