Automatic Acceptance Test Case Generation From Essential Use Cases

Requirements validation is a crucial process to determine whether client-stakeholders’ needs and expectations of a product are sufficiently correct and complete. Various requirements validation techniques have been used to evaluate the correctness and quality of requirements, but most of these techniques are tedious, expensive and time consuming. Accordingly, most project members are reluctant to invest their time and efforts in the requirements validation process.Moreover, automated tool supports that promote effective collaboration between the client-stakeholders and the engineers are still lacking. In this paper, we describe a novel approach that combines prototyping and test-based requirements techniques to improve the requirements validation process and promote better communication and collaboration between requirements engineers and clientstakeholders. To justify the potential of this prototype tool, we also present three types of evaluation conducted on the prototpye tool, which are the usability survey, 3-tool comparison analysis and expert reviews

Applying Model-Driven Paradigm for the Improvement of Web Requirement Validation

This paper proposes an approach for Web requirements validation by applying the model-driven paradigm in classical requirements validation techniques. In particular, we present how the Navigational Development Techniques (NDT) approach exploits the model-driven paradigm to improve its requirements validation task by exploring tool cases that systematize or even automate the application of requirements validation techniques. Our solution is validated by applying it in a real industrial environment. The results and the learned lessons are presented accordingly

Tracing the Scenarios in Scenario-Based Product Design: a study to support scenario generation

Scenario-based design originates from the human-computer interaction and\ud software engineering disciplines, and continues to be adapted for product development. Product development differs from software development in the former’s more varied context of use, broader characteristics of users and more tangible solutions. The possible use of scenarios in product design is therefore broader and more challenging. Existing design methods that involve scenarios can be employed in many different stages of the product design process. However, there is no proficient overview that discusses a\ud scenario-based product design process in its full extent. The purposes of creating scenarios and the evolution of scenarios from their original design data are often not obvious, although the results from using scenarios are clearly visible. Therefore, this paper proposes to classify possible scenario uses with their purpose, characteristics and supporting design methods. The classification makes explicit different types of scenarios and their relation to one another. Furthermore, novel scenario uses can be referred or added to the classification to develop it in parallel with the scenario-based design\ud practice. Eventually, a scenario-based product design process could take inspiration for creating scenarios from the classification because it provides detailed characteristics of the scenario

Human Activity Modelling in the Specification of Operational Requirements: Work in Progress

This paper describes our experience of integrating HCI concepts and techniques into a concurrent requirements engineering process called RESCUE. We focus on the use of a model of current human activity to inform specification of a future system. We show how human activity descriptions, written using a specially designed template, can facilitate the authoring of use case descriptions to be used in the elicitation of requirements for complex socio-technical systems. We describe our experience of using descriptions of human activity, written using the template, to support specification of operational requirements for DMAN, a system to support air traffic controllers in managing the departure of aircraft from airports. We end with a discussion of lessons learnt from our experience and present some ideas for future development of work in this area

Integrating design thinking into extreme programming

© 2018, Springer-Verlag GmbH Germany, part of Springer Nature. The increased demand for information systems drives businesses to rethink their customer needs to a greater extent and undertake innovation to compete in the marketplace. The design thinking (DT) is a human-centered methodology leads to creativity and innovation. The agile applications development such as extreme programming (XP) as a rapid application development approach tends to focus on perfecting functionality requirement and technical implementation. However, it causes significant challenges to building software/applications to meet the needs of end-user. This study integrates DT practices into XP methodology to improve the quality of software product for the end-users and enable businesses to achieve creativity and innovation. The proposed integrated DT@XP framework presents the various DT practices (empathy, define, persona, DT user stories) are adapted into XP exploration phase, prototyping and usability evaluation into XP planning phase. Our work demonstrates the applicability of DT concepts to analyze customer/user involvement in XP projects