Towards a Non-Functional Requirements Discovery Approach for Persuasive Systems

[Abstract] A number of software systems that attempt to help people achieve behavior change have been proposed in various domains such as health and wellness. However, sometimes, such systems have failed to provide a satisfactory or sustainable User Experience (UX), as it is observed when users may be reluctant to respond to the activation of the systems' changing demands. Moreover, a negative User Experience (UX) can be exposed by Behavior Change Support Systems (BCSS) if designers do not have clear understanding of the requirements that factually help changing the user behavior that accomplishes a sustainability goal. We first explored the Persuasive System Design (PSD) model that should be considered in UX assessment of BCSSs. Then, we propose a requirements discovery process that can be considered to redesign a software interactive system based on negative UX.This work has received partial support by the projects FEDER-UE CSI ED431G/01, ED43C 2018/29, accreditation 2016-2019 ED431G/08, KUSISQA supported by N° 014-2019-FONDECYT-BM-INC.INV, NOVA LINCS UID/CEC/04516/2019, MICINN IJC2018-037522-I, RTI2018-099646-B-I00Xunta de Galicia; ED431G/01Xunta de Galicia; ED43C 2018/29Xunta de Galicia; ED431G/08Gobierno de Chile; 014-2019-FONDECYTBM-INC.INVRepública Portuguesa. Fundação para a Ciência e a Tecnologia; UID/CEC/04516/201

Creative Information Exploration in Journalism

Existing digital tools used by journalists such as content management systems and search engines focus on helping journalists find relevant information and organize their creative work; they do not provide support for discovering creative angles to investigate. To meet this need in journalism, we have researched new creative search algorithms that manipulate the journalist’s primary medium – written information – and developed an innovative creativity and productivity support tool deliberately for use by journalists. In this paper, we analyse the creative tasks journalists perform when developing new stories, we provide an overview of requirements, which have been addressed by the INJECT digital creativity support tool for journalists. Further, we explain the intended use of the system using a walkthrough scenario and present our early experiences from deploying the tool in journalist’s working environments

Knowns and Unknowns: An Experience Report on Discovering Tacit Knowledge of Maritime Surveyors

Context: Requirements elicitation is an essential activity to ensure that systems provide the necessary functionality to users, and that they are fit for purpose. In addition to traditional `reductionist' techniques, the use of observations and ethnography-style techniques have been proposed to identify requirements. Research Problem: One frequently heard issue with observational techniques is that they are costly to use, as developers would lose considerable time to partake, and also depend on luck in identifying requirements. Very few experience reports exist to evaluate observational techniques in practice. Results: In this experience report, we draw on several data sources, covering insights from both developers and users. The data were collected through 9 interviews with users and developers, and over 80 hours of observation of prospective users in the maritime domain. We capture `knowns' and `unknowns' from both developers and users, and highlight the importance of observational studies. Contribution: While observational techniques are costly to use, we conclude that essential information is uncovered, which is key for developers to understand system users and their concerns.Comment: Accepted to the International Working Conference on Requirements Engineering: Foundation for Software Quality. Springer, Cham, 2023. Barcelona, 17.-20. Apri

Refining Vision Videos

[Context and motivation] Complex software-based systems involve several stakeholders, their activities and interactions with the system. Vision videos are used during the early phases of a project to complement textual representations. They visualize previously abstract visions of the product and its use. By creating, elaborating, and discussing vision videos, stakeholders and developers gain an improved shared understanding of how those abstract visions could translate into concrete scenarios and requirements to which individuals can relate. [Question/problem] In this paper, we investigate two aspects of refining vision videos: (1) Refining the vision by providing alternative answers to previously open issues about the system to be built. (2) A refined understanding of the camera perspective in vision videos. The impact of using a subjective (or "ego") perspective is compared to the usual third-person perspective. [Methodology] We use shopping in rural areas as a real-world application domain for refining vision videos. Both aspects of refining vision videos were investigated in an experiment with 20 participants. [Contribution] Subjects made a significant number of additional contributions when they had received not only video or text but also both - even with very short text and short video clips. Subjective video elements were rated as positive. However, there was no significant preference for either subjective or non-subjective videos in general.Comment: 15 pages, 25th International Working Conference on Requirements Engineering: Foundation for Software Quality 201

CONSTRUCTING A REFINED MODEL TRANSITION SYSTEMS IN DATABASE USING TRIGGERED SCENARIOS

Triggered scenarios are sequence charts that represent interactions between the system agents’. Graphically a triggered scenario comprises several vertical lines labeled by names representing agent’s lifeline. Time is assumed to flow downward. Annoted arrows between these lines correspond to synchronous messages which represent instantaneous events on which both objects synchronize, In this paper, we propose a scenario-based language that supports both existential and universal interpretations for conditional scenarios. Existing model synthesis techniques use traditional two-valued behavior models, such as Labeled Transition Systems. These are not sufficiently expressive to accommodate specification languages with both existential and universal scenarios. We therefore shift the target of synthesis to Modal Transition Systems (MTS), an extension of labeled Transition Systems that can distinguish between required, unknown, and proscribed behavior to capture the semantics of existential and universal scenarios. Modal Transition Systems support elaboration of behavior models through refinement, which complements an incremental elicitation process suitable for specifying behavior with scenario-based notations. The synthesis algorithm that we define constructs a Modal Transition System that uses refinement to characterize all the Labeled Transition Systems models that satisfy a mixed, conditional existential and universal scenario-based specification. We show how this combination of scenario language, synthesis, and Modal Transition Systems supports behavior model elaboration

Exploring how to use scenarios to discover requirements

This paper investigates the effectiveness of different uses of scenarios on requirements discovery using results from requirements processes in two projects. The first specified requirements on a new aircraft management system at a regional UK airport to reduce its environmental impact. The second specified new work-based learning tools to be adopted by a consortium of organizations. In both projects scenarios were walked through both in facilitated workshops and in the stakeholders’ workplaces using different forms of a scenario tool. In the second project, scenarios were also walked through with a software prototype and creativity prompts. Results revealed both qualitative and quantitative differences in discovered requirements that have potential implications for models of scenario-based requirements discovery and the design of scenario tools

When details are difficult to portray: enriching vision videos

The creation of a shared understanding of the project vision of all relevant stakeholders is vital to the requirements engineering process. One way to create such a shared understanding is through the use of vision videos that visualize the project vision at an early project stage. However, not all functional aspects can be presented. For example, the fact that an access code is valid for only a single use can be hard to visualize. One low-effort solution could be the insertion of short texts or short audio clips. In this work, our question is twofold: What effects do short pieces of additional information have in vision videos? What are suitable ways to add this information to vision videos? To answer these research questions, we investigated three different methods of inserting additional information to vision videos in an eye tracking study. We inserted short texts either below the scene or as overlays and also investigated the addition of short audio clips. These methods were evaluated in terms of participants’ video comprehension, visual effort, cognitive load and subjective preference. The results of our study show that the pieces of additional information improve vision comprehension, thereby supporting the creation of a shared understanding. All investigated methods lead to only marginal increases of the viewers’ cognitive load. Based on our results, we derive recommendations on how to insert additional information in vision videos

How Do Business People Rank Requirements Representations for Information Systems?

The research question that summarises the primary research goals is: How do business people rank their intentions to use different requirements representations for information systems? An additional goal of the research is to understand the determinants that contribute to these intentions. Business people in this research are defined as working people who are not in an information systems role. The requirements representations evaluated were Prose Narrative, Image Narrative, Diagram Narrative and Video Narrative. The results of this research show that business people rank their intention to use the requirements representations in the following order: Prose Narrative, Image Narrative, Diagram Narrative and Video Narrative. The determinants that influence the intention to use a representation are: Job Performance, Effort, Attitude to a Representation, Social Influence, Facilitating Conditions, Self-Efficacy, Anxiety, Freedom of Choice, Experience, Age and Gender. This research shows that the influence of each of these determinants on the intention to use a representation is significantly different for each requirements representation

Shared Understanding Within Large Information Systems Projects

This research responds to calls for practice-based research in the field of project management. Undertaken during the development of a sizable public information systems project, it examines the extent to which the professionals engaged in the project shared a common understanding of important matters such as its goals, structure and clients. The literature review examines the history of project management and its methodologies, the reasons that information systems projects fail, the concept of uncertainty and shared understanding, and risk associated with the development of large scale information systems. The fieldwork was conducted in 2010. The research adopts an interpretive position and the methodology centred on two series of structured interviews held some eight months apart. Analysis of responses found a low level of shared understanding about all matters investigated amongst the professionals developing the IS. The overall conclusion of the research is that no evidence was found that the participants in a programme or project have a common, shared understanding of current endeavours and the future envisaged end state. Therefore any project activity that depends on a single shared understanding such as the definition of deliverables and management of the business case, may be ill-founded. Further research into the topic of shared understanding in the context of IS programmes and projects is recommended