User story

About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.

Modeling How to Understand a Target System: Bridging the Gap Between Software Engineers and Usability Experts

Abstract: In order to investigate the reasons why software engineers fail in design activities concerning usability, we devised a method to model the features of how to understand a target system. It is the method to visualize differences of system understanding between a software engineer and a usability expert from three aspects, namely qualitative difference, quantitative difference, and difference in recognition to the understanding. Moreover we devised "three layer model diagram" which consists of "system function layer", "task and workflow layer" and "user practice field layer", for describing system understanding. We conducted the experiment and interview for software engineers and analyzed them applying this method. This analysis revealed that software engineers who failed in the activities have a tendency to understand tasks correspond to functions, in addition to understanding an entire system from functions. These suggested that their function-based understandings and little recognition to "system users" and "user practice in the field" in their everyday design activities are included in their failure reason.

Using behaviour-driven development with hardware-software co-design for autonomous load management

Abstract: The typical approach to designing embedded systems manages the specification and design of the hardware and software separately. HW/SW Co-design is used, in embedded computing, to allow the hardware and the software to be designed and implemented together and make sure that the non-functional properties are met. Behavior-driven development (BDD) is an agile software development approach that spurs collaboration of project stakeholders to ensure the right software is developed to meet their needs. BDD describes the behavior of the system as executable user stories and focuses on how the system behaves for users interact with the system. In this paper, we introduce an approach that integrates BDD with HW/SW Co-design. The approach provides the ability to describe the behavior of the software as executable user stories in a HW/SW Co-design environment. The approach is evaluated using a renewable energy project in collaboration with a private company in Canada to build a system for autonomous load management of self-forming renewable energy nanogrids.

On the Suitability of the Social Web Environment for Agile Requirements Engineering

Abstract: The agile methodologies are part of a shift from predictive to adaptive approach to software development, and are being increasingly deployed in many organizations. This paper views agile requirements engineering as a kind of social engineering, and explores the potential of the Social Web in facilitating it. In doing so, the interplay between stakeholders, salient activities of agile requirements engineering process, and Social Web Applications is illustrated by means of representative examples. The implications towards agile requirements engineering education are highlighted.

Approach to Construction of Common Information Space of Manufacturing Enterprise

Abstract: The development of methodology and support tools of the design process and practical implementation of the manufacturing enterprise common information space (CIS) is considered. The proposed methodology allows top management, analysts, developers and IT specialists to respond quickly to changing organizational and technical conditions of production and impact of the external environment, to clarify and agree on requirements to elements of the enterprise control system, to continuously improve and modernize the CIS during the operation of the enterprise. It is shown that the application of existing methodologies and notations is not enough to ensure consistency at each level of CIS design with the corresponding program documents: business development strategy, functional strategies (including information technology development strategy, digital transformation strategy, etc.), project description and technical tasks for software and hardware development, etc. The proposed methodology involves using IDEF0 notation at the top level with decomposition and business process modeling in BPMN or eEPC notations at the middle level. For modeling and software development at the lower level it is proposed to use flexible development methodologies - the agile methods based on the use of corresponding models: user stories, abstract UML models, block diagrams. The advantages and peculiarities of practical application of the proposed methodology in the design of the CIS and elements of the production executive system of the manufacturing enterprise are considered.