IEEE Transactions on Software Engineering - Special issue on computer security and privacy
A theory of diagnosis from first principles
Artificial Intelligence
Data Diversity: An Approach to Software Fault Tolerance
IEEE Transactions on Computers - Fault-Tolerant Computing
On the synthesis of a reactive module
POPL '89 Proceedings of the 16th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
ICSE '94 Proceedings of the 16th international conference on Software engineering
ACM Transactions on Information and System Security (TISSEC)
Dynamically Discovering Likely Program Invariants to Support Program Evolution
IEEE Transactions on Software Engineering - Special issue on 1999 international conference on software engineering
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Using Simplicity to Control Complexity
IEEE Software
Recovery blocks in action: A system supporting high reliability
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Intrusion Detection via Static Analysis
SP '01 Proceedings of the 2001 IEEE Symposium on Security and Privacy
Workshop on Assurance Cases: Best Practices, Possible Obstacles, and Future Opportunities
DSN '04 Proceedings of the 2004 International Conference on Dependable Systems and Networks
Efficient monitoring of safety properties
International Journal on Software Tools for Technology Transfer (STTT) - Special section on tools and algorithms for the construction and analysis of systems
Structured Assurance Cases: Three Common Standards
HASE '05 Proceedings of the Ninth IEEE International Symposium on High-Assurance Systems Engineering
Model-based runtime analysis of distributed reactive systems
ASWEC '06 Proceedings of the Australian Software Engineering Conference
Cooperative Bug Isolation: Winning Thesis of the 2005 ACM Doctoral Dissertation Competition (Lecture Notes in Computer Science)
Redundancy in Data Structures: Improving Software Fault Tolerance
IEEE Transactions on Software Engineering
Software for Dependable Systems: Sufficient Evidence?
Software for Dependable Systems: Sufficient Evidence?
Rule systems for run-time monitoring: from eagle to ruler
RV'07 Proceedings of the 7th international conference on Runtime verification
An Empirical Evaluation of Structured Argumentation Using the Toulmin Argument Formalism
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
Workflow-driven tool integration using model transformations
Graph transformations and model-driven engineering
When the requirements for adaptation and high integrity meet
Proceedings of the 8th workshop on Assurances for self-adaptive systems
Challenges in the regulatory approval of medical cyber-physical systems
EMSOFT '11 Proceedings of the ninth ACM international conference on Embedded software
Self-adaptive software needs quantitative verification at runtime
Communications of the ACM
Towards certified runtime verification
ICFEM'12 Proceedings of the 14th international conference on Formal Engineering Methods: formal methods and software engineering
Conditional Safety Certification of Open Adaptive Systems
ACM Transactions on Autonomous and Adaptive Systems (TAAS)
A methodology and supporting techniques for the quantitative assessment of insider threats
Proceedings of the 2nd International Workshop on Dependability Issues in Cloud Computing
Copilot: monitoring embedded systems
Innovations in Systems and Software Engineering
Software health management with Bayesian networks
Innovations in Systems and Software Engineering
| Hi-index | 0.02 |
Software often must be certified for safety, security, or other critical properties. Traditional approaches to certification require the software, its systems context, and all their associated assurance artifacts to be available for scrutiny in their final, completed forms. But modern development practices often postpone the determination of final system configuration from design time to integration time, load time, or even runtime. Adaptive systems go beyond this and modify or synthesize functions at runtime. Developments such as these require an overhaul to the basic framework for certification, so that some of its responsibilities also may be discharged at integration-, load- or runtime. We outline a suitable framework, in which the basis for certification is changed from compliance with standards to the construction of explicit goals, evidence, and arguments (generally called an "assurance case"). We describe how runtime verification can be used within this framework, thereby allowing certification partially to be performed at runtime or, more provocatively, enabling "runtime certification."