Assure 2016

ASSURE 2016 has successfully concluded.

UPDATES

  • 2016-07-18: Clive Tomsett, Clinical Strategist at the Cerner Corporation, will give an invited keynote talk!
  • 2016-07-18: The ASSURE 2016 Program has been announced. The final program is contingent on registration. If you haven't already done so, please register for ASSURE 2016 via SAFECOMP 2016.
  • 2016-06-08: ASSURE 2016 will be held on Tuesday, Sep. 20, 2016. The accepted papers and program will be posted here soon.
  • 2016-06-07: Authors of accepted papers have been notified. The final, camera-ready version and a signed copyright release form are due on June 20, 2016. Instructions on submitting both the final version and the copyright form have been posted.
  • 2016-05-26: Paper submission deadlines have passed. Submission is now closed.
  • 2016-05-16: ASSURE deadlines have been extended by to May 26, 2016. Submit a paper now!
  • 2016-03-28: The deadline to submit papers to ASSURE 2016 is May 17, 2016.
  • 2016-03-28: The ASSURE 2016 call for papers, and the paper submission guidelines are now available.
  • 2016-03-07: The ASSURE 2016 website is live!

Introduction

The 4th International Workshop on Assurance Cases for Software-intensive Systems (ASSURE 2016) is being collocated this year with SAFECOMP 2016, 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

08:00 – 09:00 Registration

09:00 – 11:00 Session 1. Introduction, Keynote, and Lifecycles

09:00 – 09:10 Welcome and Introduction, ASSURE 2016 Organizers

09:10 – 10:00 Keynote Talk: Rhetoric or Rigor: The Development and Use of Safety Cases in Health IT Clive Tomsett, Cerner Corporation

10:00 – 10:30 The Agile Safety Case, Tor Stålhane and Thor Myklebust

10:30 – 11:00 Towards Faster Maintenance of Safety Cases, Omar Jaradat and Iain Bate

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

11:30 – 13:00 Session 2. Formal Evidence and Tool Support

11:30 – 12:00 On Using Results of Code­-level Bounded Model Checking in Assurance Cases, Carmen Cârlan, Daniel Ratiu, and Bernhard Schätz

12:00 – 12:30 Configuration­-aware Contracts, Irfan Šljivo, Barbara Gallina, Jan Carlson, and Hans Hansson

12:30 – 13:00 Developing SNS tool for Consensus Building on Environmental Safety using Assurance Cases, Yutaka Matsuno, Yang Ishigaki, Koichi Bando, Hiroyuki Kido, and Kenji Tanaka

13:00 – 14:00 Lunch Break

14:00 – 15:30 Session 3. Applications

14:00 – 14:30 The 6W1H Model as a Basis for Systems Assurance Argument, Shuji Kinoshita and Yoshiki Kinoshita

14:30 – 15:00 The Assurance Timeline: Building Assurance Cases for Synthetic Biology, Myra Cohen, Justin Firestone, and Massimiliano Pierobon

15:00 – 15:30 Towards Safety Case Integration with Hazard Analysis for Medical Devices, Andrzej Wardziński and Aleksander Jarzębowicz

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

16:00 – 17:30 Session 4. Panel and Conclusion

16:00 – 17:15 PANEL: Assurance Challenges for Safety-critical Autonomous Systems

Panelists:

– Håkon Olsen, Principal Consultant at Lloyd's Register, Norway

– Jérémie Guiochet, Professor at University of Toulouse, France

– Marialena Vagia, Research Scientist at SINTEF, Norway

– Ovidiu Drugan, Senior Researcher at DNV GL, Norway

17:15 – 17:30 Conclusion and Wrap-Up, ASSURE 2016 Organizers

Important Dates

EVENTDEADLINE
Workshop Papers DueMay 26, 2016
Notification of AcceptanceJune 7, 2016
Camera-ready Copies DueJune 20, 2016
ASSURE 2016 WorkshopSeptember 20, 2016
SAFECOMP 2016September 20 – 23, 2016

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 760, 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 2016 Workshop on Assurance Cases for Software-intensive Systems (ASSURE 2016) 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 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.
  • 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?
  • 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 to create and analyze arguments.
  • Exploration of relevant techniques for assurance cases for real-time, concurrent, and distributed systems.
  • Modeling and Metamodeling: Representation of structured arguments through meta models, such as OMG's Structured Assurance Case Metamodel (SACM).
  • 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.
  • Connections between the Goal Structuring Notation for assurance cases, and goal-orientation from the requirements engineering community.

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.