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

Finding and Resolving Security Misusability with Misusability Cases

Although widely used for both security and usability concerns, scenarios used in security design may not necessarily inform the design of usability, and vice- versa. One way of using scenarios to bridge security and usability involves explicitly describing how design deci- sions can lead to users inadvertently exploiting vulnera- bilities to carry out their production tasks. This paper describes how misusability cases, scenarios that describe how design decisions may lead to usability problems sub- sequently leading to system misuse, address this problem. We describe the related work upon which misusability cases are based before presenting the approach, and illus- trating its application using a case study example. Finally, we describe some findings from this approach that further inform the design of usable and secure systems

Behaviour Driven Development for Multi-Agent Systems

This paper presents a testing methodology to apply Behaviour Driven Development (BDD) techniques while developing Multi-Agent Systems (MAS), so called BEhavioural Agent Simple Testing (BEAST) methodology. It is supported by the developed open source framework (BEAST Tool) which automatically generates test cases skeletons from BDD scenarios specifications. The developed framework allows testing MASs based on JADE or JADEX platforms and offers a set of configurable Mock Agents which allow the execution of tests while the system is under development. BEAST tool has been validated in the development of a MAS for fault diagnosis in FTTH (Fiber To The Home) networks

Quantitative Verification: Formal Guarantees for Timeliness, Reliability and Performance

Computerised systems appear in almost all aspects of our daily lives, often in safety-critical scenarios such as embedded control systems in cars and aircraft or medical devices such as pacemakers and sensors. We are thus increasingly reliant on these systems working correctly, despite often operating in unpredictable or unreliable environments. Designers of such devices need ways to guarantee that they will operate in a reliable and efficient manner. Quantitative verification is a technique for analysing quantitative aspects of a system's design, such as timeliness, reliability or performance. It applies formal methods, based on a rigorous analysis of a mathematical model of the system, to automatically prove certain precisely specified properties, e.g. ``the airbag will always deploy within 20 milliseconds after a crash'' or ``the probability of both sensors failing simultaneously is less than 0.001''. The ability to formally guarantee quantitative properties of this kind is beneficial across a wide range of application domains. For example, in safety-critical systems, it may be essential to establish credible bounds on the probability with which certain failures or combinations of failures can occur. In embedded control systems, it is often important to comply with strict constraints on timing or resources. More generally, being able to derive guarantees on precisely specified levels of performance or efficiency is a valuable tool in the design of, for example, wireless networking protocols, robotic systems or power management algorithms, to name but a few. This report gives a short introduction to quantitative verification, focusing in particular on a widely used technique called model checking, and its generalisation to the analysis of quantitative aspects of a system such as timing, probabilistic behaviour or resource usage. The intended audience is industrial designers and developers of systems such as those highlighted above who could benefit from the application of quantitative verification,but lack expertise in formal verification or modelling

Requirements engineering related usability techniques adopted in agile development processes

Over the last decade there has been a growing interest in the integration of agile software development process (ASDP) and user-centred design (UCD). However, there are no papers that study which usability techniques related to requirements engineering are being adopted in the ASDP, and there are no formalized proposals for their adoption. Objective: Identify which techniques related to requirements engineering activities are being adopted in the ASDP and determine how they are being adopted. Method: We have conducted a systematic mapping study (SMS) to retrieve the literature reporting the application of usability techniques in the ASDP. We analysed these techniques using a catalogue of techniques compiled by software engineering researchers. We then determined the manner in which the techniques that are being used in the ASDP were adopted. Results: The agile community is very much interested in adopting usability techniques. The most used techniques are Personas, contextual inquiry and prototyping. Conclusions: This research offers an overview of the adoption of usability techniques related to requirements engineering in ASDPs and reports how they are being adopted. We found that some of the techniques are being adapted for adoption.This research was funded by the Spanish Ministry of Education, Culture and Sports FLEXOR and “Realizando Experimentos en la Industria del Software: Comprensión del Paso de Laboratorio a la Realidad” projects (TIN2014-52129-R and TIN2014-60490-P, respectively) and the eMadrid-CM “Investigación y Desarrollo de Tecnologías Educativas en la Comunidad de Madrid” project (S2013/ICE-2715

Effective and efficient requirement traceability in the software development and Information Technology industry

Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices

A Requirements Specification Template for Temperature Calibration System

Calibration laboratories follow a set of standards and these standards change all the time. The ISO17025 standard concerns calibration laboratories and have recently got a new version. This new version mainly adds the requirement for traceability in the calibration process. The company in question is creating a new temperature calibration software, due to the adaptation of a new version of the ISO17025. This thesis concentrates on the creation of the software requirements specification for this new software system. Calibration theory and software requirements theory are topics that are researched in this thesis. The goal of this thesis is to create a new template for internal software products software requirements specification and utilize it in the project. In the first part of the thesis, we will learn about the different key elements in this project, information that the reader must know to understand the subject. We will learn about calibration theory and temperature calibration in particular. Then we will jump straight into the theory of software requirements, a part of good practices in software requirements specification that can be helpful in the different stages. The development process plays also a part in the creation and management of the requirements, so this aspect is also looked at. Then we will utilize the gathered information in the creation of a new internal software requirements specification and functional design specification. The new software requirements specification template for internal software systems is more suitable for this type of software system than the already existing template. Additionally, the functional design specification is included in the same document, which results in a smaller number of project-related documents. This results in a reduction of the amount of work required by the process. By reducing the number of documents into one larger document, makes requirement engineering tasks easier and allows for a deeper integration between requirements and implementation.The name of the company where this project took place has been censored on the behalf of the company's integrity

An agile business process improvement methodology

Adoption of business process improvement strategies are now a concern of most organisations. Organisations are still facing challenges and finding transient solutions to immediate problems. The misalignment between IT solutions and organisational aspects evolves across space and time showing discrepancies. Unfortunately, existing business process approaches are not according with continuous business process improvement involving business stakeholders. Considering this limitation in well-known Business Process (BP) methodologies, this paper presents a comparative study of some approaches and introduces agility in the Business Process and Practice Alignment Methodology (BPPAM). Our intention is to present observed problems in existing approaches and introduce agility in our proposal to address features, like the alignment between daily work practices and business process descriptions, in a simple and agile way. (C) 2017 The Authors. Published by Elsevier B.V

An ontology of agile aspect oriented software development

Both agile methods and aspect oriented programming (AOP) have emerged in recent years as new paradigms in software development. Both promise to free the process of building software systems from some of the constraints of more traditional approaches. As a software engineering approach on the one hand, and a software development tool on the other, there is the potential for them to be used in conjunction. However, thus far, there has been little interplay between the two. Nevertheless, there is some evidence that there may be untapped synergies that may be exploited, if the appropriate approach is taken to integrating AOP with agile methods. This paper takes an ontological approach to supporting this integration, proposing ontology enabled development based on an analysis of existing ontologies of aspect oriented programming, a proposed ontology of agile methods, and a derived ontology of agile aspect oriented development

An Abstract Formal Basis for Digital Crowds

Crowdsourcing, together with its related approaches, has become very popular in recent years. All crowdsourcing processes involve the participation of a digital crowd, a large number of people that access a single Internet platform or shared service. In this paper we explore the possibility of applying formal methods, typically used for the verification of software and hardware systems, in analysing the behaviour of a digital crowd. More precisely, we provide a formal description language for specifying digital crowds. We represent digital crowds in which the agents do not directly communicate with each other. We further show how this specification can provide the basis for sophisticated formal methods, in particular formal verification.Comment: 32 pages, 4 figure