Application of the interface analysis template for delivering system requirements

yesThis paper presents a structured approach for systems requirements analysis that integrates use case modelling with a coherent flows based approach for describing interface exchanges based on the Interface Analysis Template. The approach is discussed in the context of current frameworks for requirements elicitation from the engineering design and systems engineering domains, and it is illustrated with an automotive case study. This illustrates the strength of the framework to support structured multi-domain and multi-disciplinary analysis of requirements for complex systems

Collaborative Verification-Driven Engineering of Hybrid Systems

Hybrid systems with both discrete and continuous dynamics are an important model for real-world cyber-physical systems. The key challenge is to ensure their correct functioning w.r.t. safety requirements. Promising techniques to ensure safety seem to be model-driven engineering to develop hybrid systems in a well-defined and traceable manner, and formal verification to prove their correctness. Their combination forms the vision of verification-driven engineering. Often, hybrid systems are rather complex in that they require expertise from many domains (e.g., robotics, control systems, computer science, software engineering, and mechanical engineering). Moreover, despite the remarkable progress in automating formal verification of hybrid systems, the construction of proofs of complex systems often requires nontrivial human guidance, since hybrid systems verification tools solve undecidable problems. It is, thus, not uncommon for development and verification teams to consist of many players with diverse expertise. This paper introduces a verification-driven engineering toolset that extends our previous work on hybrid and arithmetic verification with tools for (i) graphical (UML) and textual modeling of hybrid systems, (ii) exchanging and comparing models and proofs, and (iii) managing verification tasks. This toolset makes it easier to tackle large-scale verification tasks

Identifying Conflicting Requirements in Systems of Systems

A System of Systems (SoS) is an arrangement of useful and independent sub-systems, which are integrated into a larger system. Examples are found in transport systems, nutritional systems, smart homes and smart cities. The composition of component sub-systems into an SoS enables support for complex functionalities that cannot be provided by individual sub-systems on their own. However, to realize the benefits of these functionalities it is necessary to address several software engineering challenges including, but not limited to, the specification, design, construction, deployment, and management of an SoS. The various component sub-systems in an SoS environment are often concerned with distinct domains; are developed by different stake-holders under different circumstances and time; provide distinct functionalities; and are used by different stakeholders, which allow for the existence of conflicting requirements. In this paper, we present a framework to support management of emerging conflicting requirements in an SoS. In particular, we describe an approach to support identification of conflicts between resource-based requirements (i.e. requirements concerned with the consumption of different resources). In order to illustrate and evaluate the work, we use an example of a pilot study of an IoT SoS ecosystem designed to support food security at different levels of granularity, namely individuals, groups, cities, and nations

Data-driven agile requirements elicitation through the lenses of situational method engineering

Ubiquitous digitalization has led to the continuous generation of large amounts of digital data, both in organizations and in society at large. In the requirements engineering community, there has been a growing interest in considering digital data as new sources for requirements elicitation, in addition to stake-holders. The volume, dynamics, and variety of data makes iterative requirements elicitation increasingly continuous, but also unstructured and complex, which current agile methods are unable to consider and manage in a systematic and efficient manner. There is also the need to support software evolution by enabling a synergy of stakeholder-driven requirements elicitation and management with data-driven approaches. In this study, we propose extension of agile requirements elicitation by applying situational method engineering. The research is grounded on two studies in the business domains of video games and online banking.The work presented in this paper is partially funded by the DOGO4ML Spanish research project, PID2020-117191RB-I00.Peer ReviewedPostprint (author's final draft

Are your lights off? Using problem frames to diagnose system failures

This paper reports on our experience of investigating the role of software systems in the power blackout that affected parts of the United States and Canada on 14 August 2003. Based on a detailed study of the official report on the blackout, our investigation has aimed to bring out requirements engineering lessons that can inform development practices for dependable software systems. Since the causes of failures are typically rooted in the complex structures of software systems and their world contexts, we have deployed and evaluated a framework that looks beyond the scope of software and into its physical context, directing attention to places in the system structures where failures are likely to occur. We report that (i) Problem Frames were effective in diagnosing the causes of failures and documenting the causes in a schematic and accessible way, and (ii) errors in addressing the concerns of biddable domains, model building problems, and monitoring problems had contributed to the blackout

Towards a Taxonomy for Eliciting Design-Operation Continuum Requirements of Cyber-Physical Systems

Software systems that are embedded in autonomous Cyber-Physical Systems (CPSs) usually have a large life-cycle, both during its development and in maintenance. This software evolves during its life-cycle in order to incorporate new requirements, bug fixes, and to deal with hardware obsolescence. The current process for developing and maintaining this software is very fragmented, which makes developing new software versions and deploying them in the CPSs extremely expensive. In other domains, such as web engineering, the phases of development and operation are tightly connected, making it possible to easily perform software updates of the system, and to obtain operational data that can be analyzed by engineers at development time. However, in spite of the rise of new communication technologies (e.g., 5G) providing an opportunity to acquire Design-Operation Continuum Engineering methods in the context of CPSs, there are still many complex issues that need to be addressed, such as the ones related with hardware-software co-design. Therefore, the process of Design-Operation Continuum Engineering for CPSs requires substantial changes with respect to the current fragmented software development process. In this paper, we build a taxonomy for Design-Operation Continuum Engineering of CPSs based on case studies from two different industrial domains involving CPSs (elevation and railway). This taxonomy is later used to elicit requirements from these two case studies in order to present a blueprint on adopting Design-Operation Continuum Engineering in any organization developing CPSs

Seamless Integration of Multirequirements in Complex Systems

Requirements are the keystone of complex systems development. In order to reduce inconsistencies, requirements analysis is an important issue of systems engineering. In this context, there is a need for conciliating views of several stakeholders from different domains and for tracing these requirements from specification to realization. The computerization of analysis, with the help of a clearly defined semantics linked to a non-specialist readable language, should lead to overcome this major issue. Several works already go into this direction. The most popular ones are dealing with natural language, easily understandable but with few semantics. Other approaches propose more formal notations, with stronger semantics but then being less affordable by stakeholders. In this paper, we propose a preliminary work that should drive us to define a language dedicated to requirements which combine the best of both worlds in order to ease requirements analysis throughout the system lifecycle

Journal tendering for societies: a brief guide

Hundreds of societies publish journals in collaboration with publishers. Some may be considering how and whether to renegotiate or go out to tender. Some may be considering whether they can/should/wish to change the business model of the journal (e.g. by a move to Open Access). Other societies may be considering using an external publisher for the first time. This guide, based on our experience, is written for all of these. In their negotiations with publishers learned societies – especially smaller ones – may have difficulty articulating their requirements and assessing the publishers’ offerings. This is true where they wish to compare the newer models with typical "conventional" models, or simply compare different conventional offerings. The reasons are complex and include: * lack of knowledge of the publishing industry on the part of the society's executive staff (who cannot always find the time to acquire the knowledge); * the "author/research funder pays" models, which, whilst becoming more prevalent in the domains of science, technology, engineering and mathematics (STEM), appear (but may not actually be) rather less feasible in other domains. This guide draws on the experience of one learned society, the Association for Learning Technology (ALT), in reviewing the publishing arrangements for its journal Research in Learning Technology, between September and December 2010

Review of Systems Engineering (SE) Methods and Their Application to Wave Energy Technology Development

The design of effective and economically viable wave energy devices involves complex decision-making about the product based on conceptual design information, including stakeholder requirements, functions, components and technical parameters. The great diversity of concepts makes it extremely difficult to create fair comparisons of the relative merits of the many different designs. Conventional design approaches have proved insufficient to guarantee wave energy technologies meet their technical and economic goals. Systems engineering can provide a suitable framework to overcome the obstacles towards a successful wave energy technology. The main objective of this work is to review the well-established systems engineering approaches that have been successfully implemented in complex engineering problems and to what extent they have been applied to wave energy technology development. The paper first reviews how system information can be organised in different design domains to guide the synthesis and analysis activities and the definition of requirements and metrics, as well as the search for solutions and decision-making. Then, an exhaustive literature review on the application of systems engineering approaches to wave energy development is presented per design domain. Finally, a set of conclusions is drawn, along with some suggestions for improving the effectiveness of wave energy technology development.Authors would like to thank the Basque Government through the research groups IT1314‐19 and GIU19/276 and the Scottish Government for the support of Wave Energy Scotland