Аналитическая связь между магнитными аномалиями и формой рельефа местности

In this chapter, we investigate some opportunities and challenges for requirements engineering resulting from major changes in the technical context in which ICT systems operate, in particular from the continuous trend towards information and communication technology convergence. We illustrate these challenges with two major examples, one concerning requirements monitoring as a self-governance mechanism in Internet-based social networks, the other concerning the role of requirements modeling as a mediator between different cultures in embedded systems engineering for the automotive industry. Starting from a brief re-iteration of Thomas Friedman's argument on standards evolution, we finally discuss platform strategies as an important emerging challenge for organizational RE

Enhancing the EAST-ADL error model with HiP-HOPS semantics

EAST-ADL is a domain-specific modelling language for the engineering of automotive embedded systems. The language has abstractions that enable engineers to capture a variety of information about design in the course of the lifecycle — from requirements to detailed design of hardware and software architectures. The specification of the EAST-ADL language includes an error model extension which documents language structures that allow potential failures of design elements to be specified locally. The effects of these failures are then later assessed in the context of the architecture design. To provide this type of useful assessment, a language and a specification are not enough; a compiler-like tool that can read and operate on a system specification together with its error model is needed. In this paper we integrate the error model of EAST-ADL with the precise semantics of HiP-HOPS — a state-of-the-art tool that enables dependability analysis and optimization of design models. We present the integration concept between EAST-ADL structure and HiP-HOPS error propagation logic and its transformation into the HiP-HOPS model. Source and destination models are represented using the corresponding XML formats. The connection of these two models at tool level enables practical EAST-ADL designs of embedded automotive systems to be analysed in terms of dependability, i.e. safety, reliability and availability. In addition, the information encoded in the error model can be re-used across different contexts of application with the associated benefits for cost reduction, simplification, and rationalisation of dependability assessments in complex engineering designs

Uml-based modeling of non-functional requirements in telecommunication systems. In:

Abstract-Successful design of real-time embedded systems relies heavily on the successful satisfaction of their non-functional requirements. Model-driven engineering is a promising approach for coping with the design complexity of embedded systems. However, when it comes to modeling non-functional requirements and covering specific aspects of different domains and types of embedded systems, general modeling languages for real-time embedded systems may not be able to cover all of these aspects. One solution is to use a combination of modeling languages for modeling different non-functional requirements as is done in the definition of EAST-ADL modeling language for automotive domain. In this paper, we propose a UML-based solution, consisting of different modeling languages, to model non-functional requirements in telecommunication domain, and discuss different challenges and issues in the design of telecommunication systems that are related to these requirements

Model Style Guidelines for Embedded Code Generation

International audienceEmbedded systems are increasingly being developed using models. These models may have started with the system engineer or algorithm developer as an executable specification or algorithm description. However, these models also now serve as the entry point for software engineering, thanks to automatic embedded code generation. As a result, software engineers want to take advantage of these same models, adding constraints on system behavior; describing characteristics that are needed for implementation, such as fixed-point details; or linking components in the design to relevant parts of requirements and specification documents. This paper describes model style guidelines for automatically generating fixed-point and floating-point code for embedded systems. The guidelines are based on best practices and techniques derived from actual industry examples in aerospace and automotive companies worldwide

Automotive embedded systems software reprogramming

This thesis was submitted for the degree of Doctor of Philosophy and was awarded by Brunel UniversityThe exponential growth of computer power is no longer limited to stand alone computing systems but applies to all areas of commercial embedded computing systems. The ongoing rapid growth in intelligent embedded systems is visible in the commercial automotive area, where a modern car today implements up to 80 different electronic control units (ECUs) and their total memory size has been increased to several hundreds of megabyte. This growth in the commercial mass production world has led to new challenges, even within the automotive industry but also in other business areas where cost pressure is high. The need to drive cost down means that every cent spent on recurring engineering costs needs to be justified. A conflict between functional requirements (functionality, system reliability, production and manufacturing aspects etc.), testing and maintainability aspects is given. Software reprogramming, as a key issue within the automotive industry, solve that given conflict partly in the past. Software Reprogramming for in-field service and maintenance in the after sales markets provides a strong method to fix previously not identified software errors. But the increasing software sizes and therefore the increasing software reprogramming times will reduce the benefits. Especially if ECU’s software size growth faster than vehicle’s onboard infrastructure can be adjusted. The thesis result enables cost prediction of embedded systems’ software reprogramming by generating an effective and reliable model for reprogramming time for different existing and new technologies. This model and additional research results contribute to a timeline for short term, mid term and long term solutions which will solve the currently given problems as well as future challenges, especially for the automotive industry but also for all other business areas where cost pressure is high and software reprogramming is a key issue during products life cycle

Cybersecurity threat analysis, risk assessment and design patterns for automotive networked embedded systems: A case study

Cybersecurity has become a crucial challenge in the automotive sector. At the current stage, the framework described by the ISO/SAE 21434 is insufficient to derive concrete methods for the design of secure automotive networked embedded systems on the supplier level. This article describes a case study with actionable steps for designing secure systems and systematically eliciting traceable cybersecurity requirements to address this gap. The case study is aligned with the ISO/SAE 21434 standard and can provide the basis for integrating cybersecurity engineering into company-specific processes and practice specifications.Web of Science27884983

A Comprehensive Safety Engineering Approach for Software-Intensive Systems Based on STPA

Formal verification and testing are complementary approaches which are used in the development process to verify the functional correctness of software. However, the correctness of software cannot ensure the safe operation of safety-critical software systems. The software must be verified against its safety requirements which are identified by safety analysis, to ensure that potential hazardous causes cannot occur. The complexity of software makes defining appropriate software safety requirements with traditional safety analysis techniques difficult. STPA (Systems-Theoretic Processes Analysis) is a unique safety analysis approach that has been developed to identify system hazards, including the software-related hazards. This paper presents a comprehensive safety engineering approach based on STPA, including software testing and model checking approaches for the purpose of developing safe software. The proposed approach can be embedded within a defined software engineering process or applied to existing software systems, allow software and safety engineers integrate the analysis of software risks with their verification. The application of the proposed approach is illustrated with an automotive software controller

SysML for embedded automotive systems: SysCARS methodology

International audienceThis paper gives an overview of the years of Valeo experience in deploying a Model Based System Engineering (MBSE) approach for mechatronic automotive embedded systems and products. The different stages are described initial studies, language and tool benchmarking up to the last returns of experience on industrial projects. Particular emphasis is put on describing the SysCARS methodology which gives, not only a precise mapping of System Engineering work items to SysML artefacts, but also the sequence of modeling activities to be performed. It is shown how the SySCARS methodology has been implemented as a SysML profile, based on a powerful "workflow driven" mechanism, which helps the user during the modeling process. Finally it is presented how interoperability is ensured with the tools already in place for requirements management and control design

Test Automation Framework for Embedded Systems

Embedded systems are everywhere! Electronic systems in just about every engineering market segment are classified as embedded systems, consumer electronics, medical, automotive, avionics, etc. Embedded systems differ from more conventional systems, such as computers, because they are limited to the embedded hardware, are designed to perform a dedicated function and have high quality and reliability requirements. Due to these characteristics, this type of system is strongly related to critical systems. Critical systems are systems that in the event of a failure can cause damage to living beings or the environment. Thus, it is necessary to ensure a high level of correctness in this type of systems. One way to increase the correctness of a system is through the process of testing. However, testing embedded systems presents a degree of difficulty because they are typically closed systems and work with real-time data that is difficult to reproduce and are non-deterministic. In this way, and with the collaboration of Altran Portugal, we intend to solve this problem by developing a framework that allows test automation for embedded systems. Automating the test data creation and execution of test case increases the quality of these systems by identifying defects to be fixed in a more efficient way. To this end, a survey of automation tools is done and each tool evaluated according to a set of criteria defined when designing the solution. The selected tool is Robot Framework, which is a widely used tool in the web and desktop application. Thus, integrating such a proficient tool in the embedded environment elevates the test automation in the embedded systems context. Then, we test the concept developed in this dissertation by executing functional tests in embedded systems that follow a model-driven development approach

Towards the Model-Driven Engineering of Secure yet Safe Embedded Systems

We introduce SysML-Sec, a SysML-based Model-Driven Engineering environment aimed at fostering the collaboration between system designers and security experts at all methodological stages of the development of an embedded system. A central issue in the design of an embedded system is the definition of the hardware/software partitioning of the architecture of the system, which should take place as early as possible. SysML-Sec aims to extend the relevance of this analysis through the integration of security requirements and threats. In particular, we propose an agile methodology whose aim is to assess early on the impact of the security requirements and of the security mechanisms designed to satisfy them over the safety of the system. Security concerns are captured in a component-centric manner through existing SysML diagrams with only minimal extensions. After the requirements captured are derived into security and cryptographic mechanisms, security properties can be formally verified over this design. To perform the latter, model transformation techniques are implemented in the SysML-Sec toolchain in order to derive a ProVerif specification from the SysML models. An automotive firmware flashing procedure serves as a guiding example throughout our presentation.Comment: In Proceedings GraMSec 2014, arXiv:1404.163