The role of deferred requirements in a longitudinal study of emailing

Our group has taken a clinical approach to doing requirements engineering for a specific domain: delivering email tools to the cognitively impaired population. The clinical view suggests a process that first gathers an individual's goals, assesses the individual's abilities, delivers a tailored system, and finally, monitors usage over time to look for adaptation needs. One concept that has arisen from our project is the notion of a deferred requirement (or deferred goal). Professional clinicians ask an individual to think broadly of the goals they have, and think about not only goals that are achievable today, but ones that might be striven for and become achieved in the future. We discuss this idea of deferred requirements in terms of a longitudinal study working with nine participants over a two year period. We also report on initial attempts to build automated tools around deferred requirements, monitoring, and system adaptation.

[1]  Gerhard Fischer,et al.  User Modeling in Human–Computer Interaction , 2001, User Modeling and User-Adapted Interaction.

[2]  M.S. Feather,et al.  Reconciling system requirements and runtime behavior , 1998, Proceedings Ninth International Workshop on Software Specification and Design.

[3]  Stephen Fickas,et al.  A pilot study exploring electronic (or e-mail) mail in users with acquired cognitive-linguistic impairments , 2003, Brain injury.

[4]  William N. Robinson,et al.  Implementing Rule-Based Monitors within a Framework for Continuous Requirements Monitoring , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[5]  John Mylopoulos,et al.  Requirements analysis for customizable software: a goals-skills-preferences framework , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[6]  Stephen Fickas,et al.  The longitudinal effects of accessible email for individuals with severe cognitive impairments , 2005 .

[7]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[8]  D. Norman Emotional design : why we love (or hate) everyday things , 2004 .

[9]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[10]  William N. Robinson,et al.  Managing Requirements Inconsistency with Development Goal Monitors , 1999, IEEE Trans. Software Eng..

[11]  Martin S. Feather,et al.  Requirements monitoring in dynamic environments , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[12]  Colin Potts,et al.  ScenIC: a strategy for inquiry-driven requirements determination , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[13]  George S. Avrunin,et al.  Patterns in property specifications for finite-state verification , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[14]  A. Mihailidis,et al.  Assistive technology for cognitive rehabilitation: State of the art , 2004 .

[15]  A. Sutcliffe User-Centered Requirements Engineering , 2002 .