Process model based development of disassembly tools

Dieser Beitrag ist mit Zustimmung des Rechteinhabers aufgrund einer (DFG geförderten) Allianz- bzw. Nationallizenz frei zugänglich.This publication is with permission of the rights owner freely accessible due to an Alliance licence and a national licence (funded by the DFG, German Research Foundation) respectively.Disassembly processes require flexible tools for loosening and handling operations. Today, disassembly processes demand a great deal of manual labour and a vast variety of tools. Partly destructive tools which generate and use new acting surfaces are able to increase the economic viability owing to their flexibility and their promotion of the reuse of components. This article describes selected methods of acting surface generation and their application for prototypical tools.DFG, SFB 281, Demontagefabriken zur Rückgewinnung von Ressourcen in Produkt- und Materialkreisläufe

Model Based Development of Quality-Aware Software Services

Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing QoS as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring QoS aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of CPU execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. QoS-aware modeling frameworks and QoS-aware runtime management infrastructures require a common evolution to get their integration

Model-based development of MAV altitude control via ground-based equipment

This paper presents the development and demonstration of an automated altitude controller for a very low weight Micro Air Vehicle (MAV) (i.e. less than 15g), via low-cost ground-based equipment, and without the provision of active telemetry data from the airframe: this approach contrasts with current technologies that generally seek to place greater functionality within the airframe itself. It is shown that development of a suitable control algorithm is most efficiently achieved by simultaneous creation of an adequate airframe dynamic model, allowing stable control laws to be developed away from the unpredictable flight-test environment and adequate model development to be closely verified against flight-test data. The methodology is practically demonstrated with a simple commercial-off-the-shelf (COTS) MAV whose internal stabilization controller is not available for modification and has no facility for transmission of airframe parameters to the controlling ground-station

Reusing Test-Cases on Different Levels of Abstraction in a Model Based Development Tool

Seamless model based development aims to use models during all phases of the development process of a system. During the development process in a component-based approach, components of a system are described at qualitatively differing abstraction levels: during requirements engineering component models are rather abstract high-level and underspecified, while during implementation the component models are rather concrete and fully specified in order to enable code generation. An important issue that arises is assuring that the concrete models correspond to abstract models. In this paper, we propose a method to assure that concrete models for system components refine more abstract models for the same components. In particular we advocate a framework for reusing testcases at different abstraction levels. Our approach, even if it cannot completely prove the refinement, can be used to ensure confidence in the development process. In particular we are targeting the refinement of requirements which are represented as very abstract models. Besides a formal model of our approach, we discuss our experiences with the development of an Adaptive Cruise Control (ACC) system in a model driven development process. This uses extensions which we implemented for our model-based development tool and which are briefly presented in this paper.Comment: In Proceedings MBT 2012, arXiv:1202.582

Model-Based Development of Design Process Models

Not only do generic compositional models of design support the analysis of design processes and the development of practical design support systems, they also provide the basic structure for more specific design process models. The generi

Testing Strategies for Model-Based Development

This report presents an approach for testing artifacts generated in a model-based development process. This approach divides the traditional testing process into two parts: requirements-based testing (validation testing) which determines whether the model implements the high-level requirements and model-based testing (conformance testing) which determines whether the code generated from a model is behaviorally equivalent to the model. The goals of the two processes differ significantly and this report explores suitable testing metrics and automation strategies for each. To support requirements-based testing, we define novel objective requirements coverage metrics similar to existing specification and code coverage metrics. For model-based testing, we briefly describe automation strategies and examine the fault-finding capability of different structural coverage metrics using tests automatically generated from the model

A Safety Case Pattern for Model-Based Development Approach

In this paper, a safety case pattern is introduced to facilitate the presentation of a correctness argument for a system implemented using formal methods in the development process. We took advantage of our experience in constructing a safety case for the Patient Controlled Analgesic (PCA) infusion pump, to define this safety case pattern. The proposed pattern is appropriate to be instantiated within the safety cases constructed for systems that are developed by applying model-based approaches

Automatic Safety mechanisms implementation in Software Model-Based Development

International audienceModel Based Development (MBD) is now a common approach for the automotive industry. Using modeling tools to simulate the behavior of a system before developing the corresponding product(s) through automatic code generation has proven its efficiency. The Road vehicles — Functional safety — ISO 26262 standard (Part6 ) [2] identifies MBD as a recommended approach especially for software architecture design with semi-formal notation and software verification with back-to-back testing through Model in the Loop (MIL) , Software in the Loop (SIL) and Processor in the Loop (PIL). Regarding error detection the standard recommends a certain number of monitoring methods such as “Range checks of input and output data”, “Plausibility check”, “Control flow monitoring”, but does not give any concrete recommendation for software implementation of those methods and therefore how to test through fault injection. In the MBD approach, since code is generated automatically, safety mechanisms must be introduced at model level