scholarly journals Persuasive Systems for Energy: Cartography of Design Spaces and Proposition of the UP+ Framework

2021 ◽  
Vol Volume 9, Number 1, Special... (Special Issue...) ◽  
Author(s):  
Van Nguyen ◽  
Yann Laurillau ◽  
Gaëlle Calvary ◽  
Joëlle Coutaz

This article reviews surveys, design spaces, and frameworks related to the design of persuasive interactive systems, with a particular focus on energy. We first propose a cartography of these conceptual tools. Most previous work focuses on persuasion principles but is difficult to apply for the software design and engineering of persuasive interactive systems. As a result, we propose UP+, a new framework that synthetizes and revisits existing surveys, design spaces, and frameworks from the software engineering perspective of persuasive interactive systems. Cet article propose un état de l’art d’espaces de conception et d’études pour les systèmes interactifs persuasifs, en particulier dans le domaine de l’énergie. Nous établissons et proposons une cartographie des principes de persuasion et des caractéristiques des systèmes persuasifs captées par ces outils. Nous observons que la plupart de ces outils sont difficiles à exploiter pour l’ingénierie de ces systèmes. Aussi, à partir de cette cartographie, nous proposons le framework UP+ qui synthétise et revisite ces outils d’un point de vue de l’ingénierie des systèmes interactifs persuasifs.

1989 ◽  
Vol 12 (3) ◽  
pp. 317-356
Author(s):  
David C. Rine

Partitioning and allocating of software components are two important parts of software design in distributed software engineering. This paper presents two general algorithms that can, to a limited extent, be used as tools to assist in partitioning software components represented as objects in a distributed software design environment. One algorithm produces a partition (equivalence classes) of the objects, and a second algorithm allows a minimum amount of redundancy. Only binary relationships of actions (use or non-use) are considered in this paper.


Author(s):  
Andrew M. Olson

The software engineering and human factors communities are seeking ways to integrate their methodologies. This paper outlines an amplified, software engineering methodology that extends beyond requirements gathering to encompass human factors analyses. The methodology employs an object model that is uniform throughout the software project. It involves a procedure that seamlessly transforms a task action grammar model, from HCI theory, directly into a specification model based on user/machine dialog and, thence, into a software design model. The model's object-oriented structure makes it feasible to trace the effects of the user's needs throughout the amplified project life cycle to the final code. A case study documents evidence concerning how effectively the procedure supports the software engineering process. An examination of the extent of metamorphosis the model undergoes in the case study indicates that the transition through the amplified life history is well controlled; in particular, the transition from the software specification to the design model is more controlled than that under traditional methodologies.


2021 ◽  
Vol 10 (1) ◽  
pp. 319-326
Author(s):  
Leanah Alsaber ◽  
Ebtesam Al Elsheikh ◽  
Sarah Aljumah ◽  
Nor Shahida Mohd Jamail

Software engineering is a discipline that is little understood by people. It defines how software is developed and maintained to meet the clients’ requirements. Software engineers follow certain systems and standards in their work to meet the clients’ desires. It is on this background that engineers follow specific models in coming up with the final product. One of the models highly used is scrum, which is one of the agile methodologies. However, despite being highly used, it has inherent flaws that need to be corrected. Those flaws are product owner continues changing; do not accept changes in working scrum, sprint’s release time limitation, finally wasting team time within each sprint. This paper presents a new framework, which is an updated version of the current Scrum, to overcome the scum models mentioned issues. In this study, a new framework is presented in a way that is understandable and needed by software developer’s team upon the collected qualitative and quantitative data. The implementation was by making some changes to the current scrum model leading to the “Scrumbear”, certain flaws can be corrected. One of the presented changes involve adding the control master rule to ensure controlling the requirements changing.


Sign in / Sign up

Export Citation Format

Share Document