User Stories Research Articles

Improving Ontology Requirements Engineering with OntoChat and Participatory Prompting

Past ontology requirements engineering (ORE) has primarily relied on manual methods, such as interviews and collaborative forums, to gather user requirements from domain experts, especially in large projects. Current OntoChat offers a framework for ORE that utilises large language models (LLMs) to streamline the process through four key functions: user story creation, competency question (CQ) extraction, CQ filtration and analysis, and ontology testing support. In OntoChat, users are expected to prompt the chatbot to generate user stories. However, preliminary evaluations revealed that they struggle to do this effectively. To address this issue, we experimented with a research method called participatory prompting, which involves researcher-mediated interactions to help users without deep knowledge of LLMs use the chatbot more effectively. The participatory prompting user study produces pre-defined prompt templates based on user query, focusing on creating and refining personas, goals, scenarios, sample data, and data resources for user story. These refined user stories will subsequently be converted into CQs.

AAT4IRS: automated acceptance testing for industrial robotic systems.

Industrial robotic systems (IRS) consist of industrial robots that automate industrial processes. They accurately perform repetitive tasks, replacing or assisting with dangerous jobs like assembly in the automotive and chemical industries. Failures in these systems can be catastrophic, so it is important to ensure their quality and safety before using them. One way to do this is by applying a software testing process to find faults before they become failures. However, software testing in industrial robotic systems has some challenges. These include differences in perspectives on software testing from people with diverse backgrounds, coordinating and collaborating with diverse teams, and performing software testing within the complex integration inherent in industrial environments. In traditional systems, a well-known development process uses simple, structured sentences in English to facilitate communication between project team members and business stakeholders. This process is called behavior-driven development (BDD), and one of its pillars is the use of templates to write user stories, scenarios, and automated acceptance tests. We propose a software testing (ST) approach called automated acceptance testing for industrial robotic systems (AAT4IRS) that uses natural language to write the features and scenarios to be tested. We evaluated our ST approach through a proof-of-concept, performing a pick-and-place process and applying mutation testing to measure its effectiveness. The results show that the test suites implemented using AAT4IRS were highly effective, with 79% of the generated mutants detected, thus instilling confidence in the robustness of our approach.

Evolution of Requirements Engineering in Agile Methodology – Literature Review

Requirements Agile approaches have transformed engineering. This paper shows how RE in Agile software development has evolved from documentation-heavy to collaborative, adaptable, and customer-focused. Agile was born in the mid-1990s when the industry realized it needed to respond to changing client needs and market volatility. This evolution includes iterative development, client interaction, and emphasizing communication above documentation, as discussed in the paper. By comparing conventional and Agile RE approaches, we demonstrate the benefits of adapting to change, working with customers, and delivering functional software faster. This analysis provides a persuasive description of Agile RE implementation methodologies and resources through a detailed literature review and real-world experiences. User stories and backlog refinement are notable techniques. The research finishes by exploring how these techniques affect team dynamics, project success, and customer satisfaction. RE's Agile difficulties and opportunities are also examined. The findings illuminate RE methods' successful adaptation to Agile projects' dynamic character. Software development is more responsive and effective due to this adaptation.

The Development of Marketing Plan for a Virtual Cycling Application: A Case Study of China (Beijing)

Background and Aims: Due to the COVID-19 pandemic, people's social activities have been greatly affected, so online activities have seen rapid development and user growth. become the norm. In cycling, the China Cycling Association canceled or postponed several races, affecting cyclists across the country. This is because the mass gatherings and high crowd density associated with such events increase the risk of virus transmission. Because of this, bicycle virtual riding software has developed rapidly, and users have increased rapidly. In addition, the evolving metaverse concept has prompted increased investment in bicycle virtual riding software development. This study explores and analyzes the operation plan of bicycle virtual riding software in China (Beijing) and analyzes the specific needs of Chinese people. Methodology: The main research methods include SWOT analysis, user stories, and population research. Use competitive product analysis such as SWOT analysis to study the specific reasons why other products cannot be promoted and popular in China (Beijing). Collect the main channels for users to obtain information and determine product promotion plans. And conduct user demand research, establish user portraits, and finally propose feasible solutions. Results: The main findings are the difficulties in promoting virtual bicycle riding software in Beijing, China, the reasons why the currently popular software is difficult to promote, the travel habits and consumption willingness of residents, and a complete promotion plan. Conclusion: The study sheds light on factors impeding the adoption of popular software already in use and clarifies the travel habits and consumption attitudes of the locals in Beijing, China. It also highlights challenges in promoting virtual bicycle riding software in Beijing. It provides insights into creating a strong promotion strategy to overcome the obstacles found and increase the adoption of virtual bicycle riding technology through in-depth analysis.

Modeling contextual goals and detecting context conflicts from BDD-based user stories

Behavior-Driven Development (BDD) user stories are widely used in agile methods for capturing user requirements and acceptance criteria due to their simplicity and clarity. However, the concise structure of BDD-based user stories prevents capturing contextual information and connections between them, which help stakeholders understand requirements and uncover potential issues. The contextual goal models (CGMs) can provide explicit relationships between goals and contexts, but manually constructing models is effort-intensive. This paper proposes an automated approach called BUS2C to model contextual goals and detect context conflicts from BDD-based user stories. The aim is to improve requirements analysis by systematically eliciting goals and dependencies. BUS2C approach involves: (1) mapping BDD-based user story elements to CGMs, and (2) merging related models based on similarity. The context conflict detection algorithm checks if contexts associated with different goals are compatible using natural language metrics. We evaluated BUS2C approach through three experiments. First, we showed the effectiveness in merging scattered CGMs with common features. Second, we demonstrated the capability to construct CGMs from BDD-based user stories quickly, assisting modelers. Our merging method also produced models closer to manually built ones versus without merging. Third, we validated that the context conflict detection can successfully identify inconsistencies in small datasets, enhancing requirements quality. Further validation on larger datasets is needed. In conclusion, this work contributes automated techniques to systematically model and analyze contextual goals from BDD-based user stories. By providing unified goal understanding and detecting issues like conflicts, BUS2C approach aims to improve requirements analysis and support adaptive systems development.

Human BioMolecular Atlas Program (HuBMAP): 3D Human Reference Atlas Construction and Usage.

The Human BioMolecular Atlas Program (HuBMAP) aims to construct a reference 3D structural, cellular, and molecular atlas of the healthy adult human body. The HuBMAP Data Portal (https://portal.hubmapconsortium.org) serves experimental datasets and supports data processing, search, filtering, and visualization. The Human Reference Atlas (HRA) Portal (https://humanatlas.io) provides open access to atlas data, code, procedures, and instructional materials. Experts from more than 20 consortia are collaborating to construct the HRA's Common Coordinate Framework (CCF), knowledge graphs, and tools that describe the multiscale structure of the human body (from organs and tissues down to cells, genes, and biomarkers) and to use the HRA to understand changes that occur at each of these levels with aging, disease, and other perturbations. The 6th release of the HRA v2.0 covers 36 organs with 4,499 unique anatomical structures, 1,195 cell types, and 2,089 biomarkers (e.g., genes, proteins, lipids) linked to ontologies and 2D/3D reference objects. New experimental data can be mapped into the HRA using (1) three cell type annotation tools (e.g., Azimuth) or (2) validated antibody panels (OMAPs), or (3) by registering tissue data spatially. This paper describes the HRA user stories, terminology, data formats, ontology validation, unified analysis workflows, user interfaces, instructional materials, application programming interface (APIs), flexible hybrid cloud infrastructure, and previews atlas usage applications.

An exploratory study on the USARP method: improving the usability requirements elicitation and specification

USARP (USAbility Requirements with Personas and User stories) is a method for eliciting and specifying usability requirements using personas, user stories, and usability guidelines organized as cards. USARP suggests brainstorming sessions to discuss usability requirements oriented by its cards. We conducted an exploratory study in an academic environment to analyze the useof USARP in projects developed by undergraduate students acting as software engineers. We noted difficulties in selecting cards to use during the USARP adoption. Thus, this study proposes to evolve USARP to provide a more effective way to elicit and specify usability requirements. We reviewed the cards, removing redundant content and combining cards with similar content. Also, weproposed a checklist and a board to guide the selection of the cards according to users and system characteristics. Finally, the process suggested for adopting USARP was updated to reflect the use of the new artifacts. In this extended version, we provide an example of USARP in practice. We expect these improvements could guide the customization of the brainstorming sessions to be more effective and efficient.

Identifying strategies and related principles supporting a co-design approach in an assistive device service delivery and research platform.

Possibilities Project Plus (PPPlus) is a free assistive device (AD) marketplace and research platform for persons with disabilities. The overall aim of PPPlus is to increase access to ADs through an integration of service, research and education. To maximize positive outcomes and reflect community needs a co-design approach informed by guiding principles of Integrated Knowledge Translation (IKT) was adopted, with examination of methods related to Experience Based Co-design. The integrated nature of PPPlus benefits from the use of specific engagement strategies that align with IKT principles to meet project objectives. The extent to which partnership and engagement strategies are specified in the rehabilitation research literature vary greatly and studies that provide information on specific strategies used to operationalize principles are limited. The objective of this manuscript is to provide a description of the co-design approach and the specific strategies that strive to achieve meaningful user engagement. By reflecting on these processes we also report on limitations and strategies for improvement. The co-design approach is highlighted through specific project activities including a representative governance structure, ongoing environmental scan and iterative Health Equity Impact Assessments (HEIA). The inherent engagement strategies that align with IKT and co-design principles are described. The most impactful engagement strategies included early engagement of partners throughout all phases, ensuring project relevance across partners through alignment of objectives with complementary aims, using HEIAs to promote equitable outcomes from diverse stakeholders, the representative governance structure beyond individuals with disabilities and caregivers, and the use of experiences and stories to inform development. This examination of specific strategies related to co-design focused on partnership engagement and informed targets for enhancement of the PPPlus initiative. These include being more intentional in developing a more rigorous process for evaluation that includes an assessment of strategies and their impact-especially as related to partner engagement. In addition, ongoing and enhanced efforts will focus on developing knowledge products that bring to life the most salient experience-based user stories emerging from the environmental scan with these being used to drive distinct co-creation events as well as serve other knowledge mobilization purposes (i.e., supporting policy change).

Establishing Metrics to Encourage Broader Use of Atomic Requirements - A Call for Exchange and Experimentation

There are seemingly many advantages to being able to identify, document, test, and trace single or "atomic" requirements during system development and maintenance. Ongoing work with Agile development has focused on "user stories" that can capture individual features for implementation. However, it is still difficult to evaluate the quality of such requirements and teaching their creation is difficult. Based on a working definition of atomic requirement, this paper proposes a set of metrics for their evaluation. Ten metrics designed to measure atomic requirements are presented here: five used on individual requirements statements and five applied to a requirements document or set of requirement statements. Example metrics for individual requirements include Requirement Atomic Completeness and Requirement Atomic Verifiability. Requirement Traceability is a proposed metric for a set of atomic requirements (such as a traditional requirements specification document.) Further work is needed to make the suggested metrics more consistent and precise, including exploring the use of tools that may automate some of the measures. However, a first step is to refine the metrics themselves and ensure they adequately measure atomic requirement quality. Hence this note shares the proposed metrics to encourage discussion and to recommend experimentation. The author is applying the metrics in software engineering courses doing team software development. The goal is the eventual acceptance of a set of requirements metrics specifically designed to evaluate atomic requirements. Better metric definitions may lead to wider utilization of atomic requirements and improved requirements engineering in general.

Stakeholder Analysis using Fuzzy Logic Operations for Integrated User Story Prioritisation Approach in Agile-Scrum Method

Effective prioritisation of user stories in Agile-Scrum projects is pivotal to ensuring optimal allocation of resources and meeting both user and system requirements. The process of prioritising user stories requires careful stakeholder analysis to determine their influence, the significance of their story, and the value it adds to the project. Common challenges, such as conflicting views, stakeholder exclusion, requirements overflow, insufficient stakeholder input, and incorrect prioritisation of user stories, are typical. This study presents an innovative approach to user story prioritisation by integrating stakeholder analysis as part of the user story prioritisation process in the Agile-Scrum method. The analysis employs fuzzy logic operations to rank stakeholders based on selected parameters, facilitating a more comprehensive understanding of their contributions and concerns. The study’s application focuses on the context of an ATM system’s requirements and associated user stories. Feedback was gathered from software experts well-versed in practising the Agile methodology within their respective organisations. Results from this study highlight the positive impact of stakeholder analysis during the prioritisation process. At the same time, the software experts praised the approach’s ability to integrate functional and non-functional user stories during the prioritisation process. By systematically addressing stakeholder perspectives, this approach ensures a balanced consideration of diverse user needs and system requirements, ultimately enhancing the accuracy and efficacy of user story prioritisation within Agile-Scrum projects.

SimAC: simulating agile collaboration to generate acceptance criteria in user story elaboration

SimAC: simulating agile collaboration to generate acceptance criteria in user story elaboration

Automatic user story generation: a comprehensive systematic literature review

Automatic user story generation: a comprehensive systematic literature review

Transforming clinical clerkship processes with integrated information systems

There are still many manual administrative processes involved in clinical clerkships. However, digital technologies and software solutions can significantly improve medical education. This paper aims to utilize extreme programming (XP) as a methodology for developing the information system. A total of 23 user stories have been planned for completion. The priority of each requirement stated in the user stories is determined using the MoSCoW prioritization technique. The results indicate that the software successfully passed all tests among the 23 black box testing scenarios. Developing an integrated information system to streamline clinical clerkships has been successfully achieved. The user experience questionnaire (UEQ) is utilized to gather the perspectives of hospital management and medical faculty members regarding the information system. The average scores for each category are as follows: 1.93 for attractiveness, 2.04 for perspicuity, 2.20 for efficiency, 2.06 for dependability, 2.14 for stimulation, and 1.85 for novelty. Therefore, it can be concluded that all existing user experience scales exhibit an outstanding degree of user satisfaction.

A Comparison of Transforming the User Stories and Functional Requirements into UML Use Case Diagram

A Comparison of Transforming the User Stories and Functional Requirements into UML Use Case Diagram

Code Simulator with Real-Time Conferencing and Considerable Users

Abstract: The Multiuser Live Text Editor represents a dynamic platform fostering collaborative coding endeavors, enabling users to engage in real-time interaction while collectively crafting code. Boasting compatibility with prominent programming languages such as C++, Java, and Python, this innovative tool is founded upon the notion of adaptive functionality, a cornerstone of its shared editing capabilities. At its core lies pair programming, an agile methodology originating from Extreme Programming (XP), wherein two developers synergistically collaborate on a single computing environment. Tasked with jointly conceiving, implementing, and validating user stories, these pairs operate in tandem, leveraging their complementary skills to achieve shared objectives. Notably, this collaborative process thrives on the diversity of the paired developers' systems, with each individual allocated equal time at the keyboard.

FAST a Digital Sales Transformation Software for the Real Estate Industry

Nowadays, organisations are encountering ever-more challenging demands, and those that do not adapt risk closure. This trend is particularly notable in small and medium-sized enterprises, where deficits in technology adoption are often particularly conspicuous. Companies that succeed in streamlining their sales process are more likely to enjoy better outcomes, underlining the crucial requirement of implementing technical solutions to tackle these problems with optimal efficiency. Therefore, the aim of this investigation is to deploy a web-based system for the purpose of enhancing sales management in a company operating in the field of real estate and construction. The system was constructed utilising Extreme Programming XP methodology, consisting of four phases: planning (user stories), design (system outline), coding (system programming) and testing (testing). The introduction of a web-based system highly streamlined the company’s sales process, reducing information search times by 64% and decreasing time spent on recording sales data by 62%. The system enabled greater sales activity during the day, resulting in a 72% increase in task performance. It also aided the accounting department in streamlining revenue reporting. This demonstrates that the system is an efficient tool for enhancing the sales process, reducing yearly tasks, and minimizing recording time.

ProCoMon: A Web-based Project Procurement Management Plan (PPMP) Consolidation and Monitoring System for Nueva Vizcaya State University

The major purpose of this study is to design and develop a web-based consolidation and monitoring system that can handle the delayed submission of a university's Annual Procurement Plan, which is managed by Nueva Vizcaya State University's Procurement Management Office. As a result of the identification of requirements and specifications, there is a need to design and develop a web-based system wherein research interviews, observations, and user stories are used to identify and analyze the study's methods, issues, and concerns. The Agile Unified Process was used as the research methodology, which managed changing user needs and involved the user in the software development process. AUP includes processes for each of the four phases: inception, elaboration, construction, and transition. As a result, the study lends a better consolidation and monitoring system that is more efficient and accurate in the formulation of an Annual Procurement Plan for the university.

Improving Inventory Control Through a Web-Based System in a Retail Company

Background Currently, retail companies that fail to digitise their logistics processes experience difficulties in controlling stock, resulting in inaccuracies in the quantity of products and excess amounts in the warehouse. Consequently, the aim was to introduce a web-based system to enhance inventory control in retail firms within the city of Huaraz. Methods The Extreme Programming methodology was implemented in four phases. During the planning phase, roles and user stories were established. In the coding phase, Hypertext Preprocessor and JavaScript programming languages were utilised alongside the MySQL database management system. The testing phase involved evaluating each interface’s functionality to ensure that it was a part of the web system. The objective of this was to develop the web system and utilise it as an inventory control tool. Results The utilization of the web-based system within the logistics sector led to enhanced indicators, as seen through a 52.94% increase in inventory precision rate and 91.94% rise in the stock turnover rate. Conclusions The web system facilitates the minimisation of input errors in product quantity records while also enabling visualisation of such data. It further provides an illustrated representation, in the form of a bar graph, of each product’s indicator behaviour.

Exploring issues of story-based effort estimation in Agile Software Development (ASD)

ContextEffort estimation based on user stories plays a pivotal role in agile software development, where accurate predictions of project efforts are vital for success. While various supervised ML tools attempt to estimate effort, the prevalence of estimation errors presents significant challenges, as evidenced by the CHAOS report by the Standish Group, which highlights incorrect estimations contributing to a substantial percentage of failed agile projects. ObjectivesThis research delves into the domain of user story-based effort estimation in agile software development, aiming to explore the issues arising from inaccurate estimations. The primary goal is to uncover these issues comprehensively and propose potential solutions, thus enhancing the efficacy of the user story-based estimation method. MethodsTo achieve the research objectives, a systematic literature review (SLR) is conducted, surveying a wide range of sources to gather insights into issues surrounding user story-based effort estimation. The review encompasses diverse estimation methods, user story attributes, and the array of challenges that can result from inaccurate estimations. ResultsThe SLR reveals a spectrum of issues undermining the accuracy of user story-based effort estimation. It identifies internal factors like communication, team expertise, and composition as crucial determinants of estimation reliability. Consistency in user stories, technical complexities, and task engineering practices also emerge as significant contributors to estimation inaccuracies. The study underscores the interconnectedness of these issues, emphasizing the need for a standardized protocol to minimize inaccuracies and enhance estimation precision. ConclusionIn light of the findings, it becomes evident that addressing the multi-dimensional factors influencing user story-based effort estimation is imperative for successful agile software development. The study underscores the interplay of various aspects, such as team dynamics, task complexity, and requirement engineering, in achieving accurate estimations. By recognizing these challenges and implementing recommended solutions, software development processes can avoid failures and enhance their prospects of success in the agile paradigm.

Agile methodologies in digital banking: Theoretical underpinnings and implications for customer satisfaction

This paper delves into the theoretical underpinnings of agile methodologies and investigates their potential to enhance customer satisfaction in digital banking. Theoretical foundations of agile methodologies draw on several key theoretical frameworks complexity theory, complex systems, like digital banking ecosystems, exhibit emergent properties. Traditional linear approaches struggle to predict these. Agile embraces iterative development cycles and adaptability to changing requirements, acknowledging this complexity lean thinking, derived from manufacturing, lean thinking prioritizes eliminating waste and maximizing customer value. Agile translates this by focusing on short development sprints, prioritizing features with the highest customer impact, and minimizing unnecessary functionalities customer co-creation, traditional models often distance customers from the development process. Agile emphasizes customer co-creation, actively involving them in design and testing. This fosters a deeper understanding of customer needs and leads to more relevant and satisfying digital banking experiences. Agile practices in digital banking. Agile methodologies encompass diverse practices. This visual management system focuses on workflow optimization. Promoting a continuous flow of work from development to deployment user stories and acceptance criteria, User Acceptance criteria define the specific conditions a feature must meet for user approval. These practices ensure features align with customer needs and expectations. Agile methodologies hold significant promise for enhancing customer satisfaction in digit banking. Agile development allows banks to deliver new features and functionalities faster, keeping pace with evolving customer demands. Customers benefit from quicker access to innovative solutions that address their financial needs. This results in digital banking experiences that are intuitive, efficient, and cater to specific user needs. Increased Innovation, The iterative nature of agile fosters continuous learning and experimentation. Banks can test new features, gather customer feedback, and rapidly iterate upon them, leading to a more innovative and dynamic digital banking experience. Improved transparency and trust, agile practices promote open communication and collaboration between development teams and customers. Customers are kept informed of updates and have a voice in shaping the development process, fostering trust and a sense of ownership.