Mader et al., 2012 - Google Patents
A bridge from system to software development for safety-critical automotive embedded systemsMader et al., 2012
View PDF- Document ID
- 3998803438035306177
- Author
- Mader R
- Grießnig G
- Armengaud E
- Leitner A
- Kreiner C
- Bourrouilh Q
- Steger C
- Weiß R
- Publication year
- Publication venue
- 2012 38th Euromicro Conference on Software Engineering and Advanced Applications
External Links
Snippet
In this paper, we present a tool enhancement that allows an effective transition from the system level development phase to the software level development phase of a tool- supported safety engineering workflow aligned with the automotive functional safety …
- 238000001514 detection method 0 abstract description 7
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/50—Computer-aided design
- G06F17/5009—Computer-aided design using simulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3632—Software debugging of specific synchronisation aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Error detection; Error correction; Monitoring responding to the occurence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
- G06F21/125—Restricting unauthorised execution of programs by manipulating the program code, e.g. source code, compiled code, interpreted code, machine code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformations of program code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F2217/00—Indexing scheme relating to computer aided design [CAD]
- G06F2217/70—Fault tolerant, i.e. transient fault suppression
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for programme control, e.g. control unit
- G06F9/06—Arrangements for programme control, e.g. control unit using stored programme, i.e. using internal store of processing equipment to receive and retain programme
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Nejati et al. | A SysML-based approach to traceability management and design slicing in support of safety certification: Framework, tool support, and case studies | |
Bahig et al. | Formal verification of automotive design in compliance with ISO 26262 design verification guidelines | |
Wotawa et al. | Quality assurance methodologies for automated driving. | |
Weissnegger et al. | Simulation-based verification of automotive safety-critical systems based on EAST-ADL | |
Guissouma et al. | Lifecycle management of automotive safety-critical over the air updates: A systems approach | |
O’Halloran | Automated verification of code automatically generated from Simulink® | |
Mader et al. | A bridge from system to software development for safety-critical automotive embedded systems | |
Ibrahim et al. | State of the Art in Software Tool Qualification with DO-330: A Survey. | |
Mader et al. | OASIS: An automotive analysis and safety engineering instrument | |
Stürmer et al. | Experiences with model and autocode reviews in model-based software development | |
Punnoose et al. | Survey of Existing Tools for Formal Verification. | |
Trindade et al. | Automatically generated safety mechanisms from semi-formal software safety requirements | |
Ferrari et al. | Lessons learnt from the adoption of formal model-based development | |
Gonzalez-de-Aledo et al. | Towards a verification flow across abstraction levels verifying implementations against their formal specification | |
Beine | A model-based reference workflow for the development of safety-critical software | |
Gonschorek et al. | Integrating Safety Design Artifacts into System Development Models Using SafeDeML | |
Hugues et al. | Twinops: Digital twins meets devops | |
Fey et al. | Quality assurance methods for model-based development: A survey and assessment | |
Botham et al. | PICASSOS–Practical applications of automated formal methods to safety related automotive systems | |
Yushtein et al. | System-software co-engineering: Dependability and safety perspective | |
Graf et al. | Dynamic mapping of runtime information models for debugging embedded software | |
Kim et al. | Assessment of high integrity software components for completeness, consistency, fault-tolerance, and reliability | |
Dropmann et al. | A Model-Based Safety Analysis of Dependencies Across Abstraction Layers | |
Graf et al. | Gaining insight into executable models during runtime: Architecture and mappings | |
Khlaif et al. | A Survey on Formal Verification Approaches for Dependable Systems |