An integrative approach to requirements analysis: How task models support requirements reuse in a user-centric design framework

Montabert, Cyril; McCrickard, D. Scott; Winchester, Woodrow W.; Pérez-Quiñones, Manuel A.

doi:10.1016/j.intcom.2009.06.003

Cited by 11 publications

(4 citation statements)

References 47 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In contrast to the activity-centric scenario and other approaches (Oliver et al 2006;Dragunov et al 2005;Dredze et al 2006;Montabert et al 2009), here, activity labeling is a subjective matter. Because activities are corrected and labeled by the owner of the data, i.e., the user him-or herself, this user-provided ground truth data is used to train the system and a test is performed later on the activity data of the same user.…”

Section: Window Captionmentioning

confidence: 96%

A Study on Automatic Classification of Users’ Desktop Interactions

Mirza

Chen

Hussain

et al. 2015

Cybernetics and Systems

View full text Add to dashboard Cite

Knowledge workers frequently change activities, either by choice or through interruptions. With an increasing number of activities and activity switches, it is becoming more and more difficult for knowledge workers to keep track of their desktop activities. This article presents our efforts to achieve activity awareness through automatic classification of user's everyday desktop activities. For getting a deeper understanding, we investigate performance of various classifiers with respect to discriminative power of time-, interaction-, and content-based feature sets for different work scenarios and users. Specifically, by viewing an activity as a sequence of desktop interactions we present (1) a methodology for translating a user's desktop interactions into activities, (2) evaluation of the discriminative power of different activity features and feature types, and (3) analysis of supervised classification models for classifying desktop activity under two different scenarios, i.e., an activity-centric scenario and a user-centric scenario. The experiments are carried out on a real-world dataset, and the results show satisfactory accuracy using relatively few and simple types of features.

show abstract

Section: Window Captionmentioning

confidence: 96%

A Study on Automatic Classification of Users’ Desktop Interactions

Mirza

Chen

Hussain

et al. 2015

Cybernetics and Systems

View full text Add to dashboard Cite

show abstract

“…In a study employing integrative approach to requirements analysis in a usercentric design framework, [5] pointed out the lack of consistency among designers could be an important reason leading to the limited usefulness of the designed system. There exist many reasons that may possibly lead to the illdefined usability/UX requirements, such as constantly changing instructions, vague user needs, budget concerns, and time constraints.…”

Section: Introductionmentioning

confidence: 99%

“…Research has shown that the major causes of project failure are requirements inconsistencies and missing user involvement ( [1], [6], [9]). As [1], [5] and [7] stressed, user involvement is a critical factor in the product development process. We should get users involved from the very beginning of the project until the end of it: getting their ideas to better understand their requirements and needs before we design the product, getting their experience of the prototype, and asking them to test the final product and give us their feedback.…”

Section: Introductionmentioning

confidence: 99%

Improving User Experience through Task Design and Evaluation Metrics in Research Projects

Yuan

2015

Schriften Aus Der Fakultät Wirtschaftsinformatik Und Angewandte Informatik Der Otto-Friedrich-Universität Bamberg

View full text Add to dashboard Cite

In UX requirement practice and research, it has been widely acknowledged that usability and user experience should be addressed in every aspect of the product development process. However, challenges exist on how to consistently and explicitly conduct the usability evaluation and improve user experience. In this paper, I will present how we have tried to improve user experience with interactive information systems by employing a consistent task design and a set of evaluation metrics. An integrated interactive information retrieval system is introduced as an example. Task design and user experience metrics used in a user-centered experiment evaluating this system are described. The task design scheme and user experience metrics have been applied in other user experiments to test the effectiveness of some other information systems and they have been proved effective. Successful experience and lessons learned are discussed. Some further thoughts and suggestions on future work are also presented.

show abstract

“…Conventionally conducting a requirements analysis was an early step in the waterfall approach to software development [3,4,5]. However, "agile" approaches which include user and stakeholder involvement throughout development [6] and recognise the need for flexibility and change [7] have been used more and also combined with the waterfall approach.…”

Section: Introductionmentioning

confidence: 99%

Business Process Modelling is an Essential Part of a Requirements Analysis

Lusignan¹,

Krause²,

Michalakidis³

et al. 2012

Yearb Med Inform

View full text Add to dashboard Cite

SummaryObjectives: To perform a requirements analysis of the barriers to conducting research linking of primary care, genetic and cancer data. Methods: We extended our initial data-centric approach to include socio-cultural and business requirements. We created reference models of core data requirements common to most studies using unified modelling language (UML), dataflow diagrams (DFD) and business process modelling notation (BPMN). We conducted a stakeholder analysis and constructed DFD and UML diagrams for use cases based on simulated research studies. We used research output as a sensitivity analysis. Results: Differences between the reference model and use cases identified study specific data requirements. The stakeholder analysis identified: tensions, changes in specification, some indifference from data providers and enthusiastic informaticians urging inclusion of socio-cultural context. We identified requirements to collect information at three levels: micro-data items, which need to be semantically interoperable, meso-the medical record and data extraction, and macro-the health system and socio-cultural issues. BPMN clarified complex business requirements among data providers and vendors; and additional geographical requirements for patients to be represented in both linked datasets. High quality research output was the norm for most repositories. Conclusions: Reference models provide high-level schemata of the core data requirements. However, business requirements' modelling identifies stakeholder issues and identifies what needs to be addressed to enable participation.

show abstract

An integrative approach to requirements analysis: How task models support requirements reuse in a user-centric design framework

Cited by 11 publications

References 47 publications

A Study on Automatic Classification of Users’ Desktop Interactions

A Study on Automatic Classification of Users’ Desktop Interactions

Improving User Experience through Task Design and Evaluation Metrics in Research Projects

Business Process Modelling is an Essential Part of a Requirements Analysis

Contact Info

Product

Resources

About