Assure 2017

ASSURE 2017 has successfully concluded.

UPDATES

  • 2017-10-01: ASSURE 2017 concluded successfully. The accepted papers appear in the SAFECOMP 2017 Workshop Proceedings. Thank you for attending! See you in 2018.
  • 2017-08-28: The ASSURE 2017 Program has been announced. The final program is contingent on registration. If you haven't already done so, please register for ASSURE 2017 via SAFECOMP 2017.
  • 2017-08-27: ASSURE 2017 will be held on Tuesday, Sep. 12, 2017. The accepted papers and program will be posted here soon.
  • 2017-06-02: Authors of accepted papers have been notified. The final, camera-ready version and a signed copyright release form are due on June 12, 2017. Instructions on submitting both the final version and the copyright form also have been posted.
  • 2017-05-24: Paper submission deadlines have passed. Submission is now closed.
  • 2016-05-16: ASSURE deadlines have been extended by a week, to May 24, 2017.
  • 2017-03-27: Dr. Simon Burton, Chief Expert Safety, Reliability and Availability at Robert Bosch GmbH Central Research Division, Germany, has generously accepted to give an invited keynote talk! Watch this space for the topic and abstract for the talk.
  • 2017-03-22: The deadline to submit papers to ASSURE 2017 is May 17, 2017. Submit a paper now!
  • 2017-03-01: The ASSURE 2017 website is live!

Introduction

The 5th International Workshop on Assurance Cases for Software-intensive Systems (ASSURE 2017) is being collocated this year with SAFECOMP 2017, and aims to provide an international forum for high-quality contributions on the application of assurance case principles and techniques to provide assurance that the dependability properties of critical, software-intensive systems have been met.

The main goals of the workshop are to:

  • Explore techniques for the creation and assessment of assurance cases for software-intensive systems
  • Examine the role of assurance cases in the engineering lifecycle of critical systems
  • Identify the dimension of effective practice in the development and evaluation of assurance cases
  • Investigate the relationship between dependability techniques and assurance cases
  • Identify critical research challenges and define a roadmap for future development

We invite original, high-quality research, practice, tools and position papers that have not been published/submitted elsewhere. See the full Call for Papers, for more details on topics. Also view the submission deadlines, and guidelines.

Program

ASSURE 2017 Program

September 12, 2017, from 08:00 – 17:30

08:00 – 09:00 Registration

09:00 – 11:00 Session 1. Welcome, Introduction, Keynote and Assurance Case Frameworks

09:00 – 09:05 Welcome and Introduction, ASSURE 2017 Organizers

09:05 – 10:00 Keynote Talk: Making the Case for Safety of Machine Learning in Highly Automated Driving, Simon Burton (with Lydia Gauerhof and Christian Heinzemann)

10:00 – 10:30 A Thought Experiment on Evolution of Assurance Cases – from a Logical Aspect, Y. Kinoshita and S. Kinoshita

10:30 – 11:00 Morning Coffee/Tea Break

11:00 – 12:30 Session 2. Assurance Case Tool Support

11:00 – 11:30 Uniform Model Interface for Assurance Case Integration with System Models, A. Wardziński and P. Jones

11:30 – 12:00 ExplicitCase: Integrated Model-based Development of System and Safety Cases, C. Cârlan, S. Barner, A. Diewald, A. Tsalidis and S. Voss

12:00 – 12:30 D-Case Communicator: A Web-Based GSN Editor for Multiple Stakeholders, Y. Matsuno

12:30 – 13:30 Lunch Break

13:30 – 15:30 Session 3. Assurance Cases for Security

13:30 – 14:00 Reconciling Systems-Theoretic and Component-Centric Methods for Safety and Security Co-Analysis, W. Temple, Y. Wu, B. Chen and Z. Kalbarczyk

14:00 – 14:30 Towards combined safety and security constraints analysis, D. Pereira, C. Hirata, R. Pagliares and S. Nadjm-Tehrani

14:30 – 15:00 Attack Modeling for System Security Analysis and Assurance Case, A. Altawairqi and M. Maarek

15:00 – 15:30 Using an Assurance Case Framework to Develop Security Strategy and Policies, R. Bloomfield, P. Bishop, E. Butler and K. Netkachova

15:30 – 16:00 Afternoon Coffee/Tea Break

16:00 – 17:25 Session 4. Guided Discussion

17:25 – 17:30 ASSURE 2017 Conclusion and Wrap-Up

Important Dates

EVENTDEADLINE
Workshop Papers Due24 May 2017
Notification of Acceptance31 May 2017
Camera-ready Copies Due12 June 2017
ASSURE 2017 WorkshopSeptember 12, 2017
SAFECOMP 2017September 13 – 15, 2017

Call for Papers

Software plays a key role in high-risk systems, e.g., safety-, and security-critical systems. Several certification standards/guidelines now recommend and/or mandate the development of assurance cases for software-intensive systems, e.g., defense (UK MoD DS-0056), aviation (CAP 670, FAA's operational approval guidance for unmanned aircraft systems), automotive (ISO 26262), and healthcare (FDA infusion pumps total product lifecycle guidance). As such, there is a need to develop models, techniques and tools that target the development of assurance arguments for software.

The goals of the 2017 Workshop on Assurance Cases for Software-intensive Systems (ASSURE 2017) are to:

  • explore techniques for creating/assessing assurance cases for software-intensive systems;
  • examine the role of assurance cases in the engineering lifecycle of critical systems;
  • identify the dimensions of effective practice in the development and evaluation of assurance cases;
  • investigate the relationship between dependability techniques and assurance cases; and,
  • identify critical research challenges and define a roadmap for future development.

We solicit high-quality contributions: research, practice, tools and position papers on the application of assurance case principles and techniques to assure that the dependability properties of critical software-intensive systems have been met.

Papers should attempt to address the workshop goals in general.

Topics

Topics of interest include, but are not limited to:

  • Assurance issues in emerging paradigms, e.g., adaptive and autonomous systems, including self-driving cars, unmanned aircraft systems, complex health care and decision making systems, etc.
  • Standards: Industry guidelines and standards are increasingly requiring the development of assurance cases, e.g., the automotive standard ISO 26262 and the FDA guidance on the total product lifecycle for infusion pumps.
  • Certification and Regulations: The role and usage of assurance cases in the certification of critical systems, as well as to show compliance to regulations.
  • Empiricism: Empirical assessment of the applicability of assurance cases in different domains and certification regimes.
  • Dependable architectures: How do fault-tolerant architectures and design measures such as diversity and partitioning relate to assurance cases?
  • Dependability analysis: What are the relationships between dependability analysis techniques and the assurance case paradigm?
  • Safety and security co-engineering: What are the impacts of security on safety, particularly safety cases, and how can safety and security cases (e.g., as proposed in ISO 26262 and SAE J 3061 respectively) be reconciled?
  • Tools: Using the output from software engineering tools (testing, formal verification, code generators) as evidence in assurance cases / using tools for the modeling, analysis and management of assurance cases.
  • Application of formal techniques for the creation, analysis, reuse, and modularization of arguments.
  • Exploration of relevant techniques for assurance cases for real-time, concurrent, and distributed systems.
  • Assurance of software quality attributes, e.g., safety, security and maintainability, as well as dependability in general, including tradeoffs, and exploring notions of the quality of assurance cases themselves.
  • Domain-specific assurance issues, in domains such as aerospace, automotive, healthcare, defense and power.
  • Reuse and Modularization: Contracts and patterns for improving the reuse of assurance case structures.
  • Relations between different formalisms and paradigms of assurance and argumentation, such as Goal Structuring Notation, STAMP, IBIS, and goal-oriented formalisms such as KAOS.

Submit

Submission Instructions for Accepted Papers

/Public Release. This material from the originating organization/author(s) might be of the point-in-time nature, and edited for clarity, style and length. Mirage.News does not take institutional positions or sides, and all views, positions, and conclusions expressed herein are solely those of the author(s).View in full here.