Kim et al., 2003 - Google Patents
Assessment of high integrity software components for completeness, consistency, fault-tolerance, and reliabilityKim et al., 2003
View PDF- Document ID
- 12503522092549280797
- Author
- Kim H
- Jerath K
- Sheldon F
- Publication year
- Publication venue
- Component-Based Software Quality: Methods and Techniques
External Links
Snippet
The use of formal model based (FMB) methods to evaluate the quality of components is an important research area. Except for a growing number of exceptions, FMB methods are still not really used in practice. This chapter presents two case studies that illustrate the value of …
- 230000000694 effects 0 abstract description 44
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
-
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/74—Reverse engineering; Extracting design information from source code
-
- 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/10—Requirements analysis; Specification techniques
-
- 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
- G06F9/44—Arrangements for executing specific programmes
- G06F9/445—Programme loading or initiating
- G06F9/44589—Programme code verification, e.g. Java bytecode verification, proof-carrying code
-
- 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
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
- G06Q10/063—Operations research or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Bahig et al. | Formal verification of automotive design in compliance with ISO 26262 design verification guidelines | |
CN108509336A (en) | A kind of operating system canonical form chemical examination card and test method | |
Dubois et al. | A model for requirements traceability in a heterogeneous model-based design process: Application to automotive embedded systems | |
Elkholy et al. | Model checking intelligent avionics systems for test cases generation using multi-agent systems | |
O’Halloran | Automated verification of code automatically generated from Simulink® | |
Besnard et al. | Unified verification and monitoring of executable UML specifications: a transformation-free approach | |
US20110041116A1 (en) | Formal analysis driven based evolution of requirements specifications | |
Delange et al. | Evaluating and mitigating the impact of complexity in software models | |
Bandara et al. | Identifying software architecture erosion through code comments | |
Sinha et al. | Reliability and availability prediction of embedded systems based on environment modeling and simulation | |
Küster et al. | Incremental development of model transformation chains using automated testing | |
Elmqvist et al. | Safety-oriented design of component assemblies using safety interfaces | |
Kim et al. | Assessment of high integrity software components for completeness, consistency, fault-tolerance, and reliability | |
Michael et al. | The verification and validation of software architecture for systems of systems | |
Cârlan et al. | Arguing on software-level verification techniques appropriateness | |
Beer et al. | Analysis of an Airport Surveillance Radar using the QuantUM approach | |
Bahig et al. | Formal verification framework for automotive UML designs | |
Kim et al. | Assessment of High Integrity Software Components for Completeness, Con-sistency, Fault-Tolerance, and Reliability.............................. | |
Lebioda et al. | Towards Single-System Illusion in Software-Defined Vehicles--Automated, AI-Powered Workflow | |
Blanquart et al. | Software safety-a journey across domains and safety standards | |
Agrawal et al. | Reliability assessment of safety critical intelligent systems: Issues and challenges | |
Filax et al. | Building models we can rely on: requirements traceability for model-based verification techniques | |
Fernández Briones et al. | Application of safety analyses in model driven development | |
Baouya et al. | Toward a context-driven deployment optimization for embedded systems: a product line approach | |
Haberl et al. | Seamless model-driven development put into practice |