| |||||||||||||||
ASSURE 2019 : 7th International Workshop on Assurance Cases for Software-intensive Systems | |||||||||||||||
Link: http://www.es.mdh.se/assure2019/ | |||||||||||||||
| |||||||||||||||
Call For Papers | |||||||||||||||
*************************************************************************************************
CALL FOR PAPERS ************************************************************************************************* 7th International Workshop on Assurance Cases for Software-intensive Systems ASSURE 2019 Turku, Finland, September 10, 2019 In conjunction with the International Conference on Computer Safety, Reliability and Security SAFECOMP ************************************************************************************************* IMPORTANT DATES ************************************************************************************************* Paper submission: May 22nd, 2019 (Extended Deadline) Notification to authors: June 3rd, 2019 Camera-ready version: June 10th, 2019 ASSURE 2019 Workshop: September 10th, 2019 ************************************************************************************************* Visit the workshop website for more information: http://www.es.mdh.se/assure2019/ ************************************************************************************************* Software plays a key role in high-risk systems, e.g., safety and security-critical systems. A number of 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 2019 Workshop on Assurance Cases for Software-intensive Systems (ASSURE 2019) are to: (a) explore techniques for creating/assessing assurance cases for software-intensive systems, admitting a variety of mechanisms for their creation including structured argumentation, graphical notations, narrative forms, etc. (b) examine the role of assurance cases in the engineering lifecycle of critical systems; (c) identify the dimensions of effective practice in the development and evaluation of assurance cases; (d) investigate the relationship between dependability techniques and assurance cases; and, (e) identify critical research directions, define a roadmap for future development, and formulate challenge problems. 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 describing the experience of an organization in developing assurance cases are particularly welcome. 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., autonomous and AI-based systems, including self-driving cars, unmanned aircraft systems, complex health care and decision making systems, continuous software integration, etc. - Standards: Industry guidelines and standards are increasingly requiring the development of assurance cases, e.g., the automotive standard ISO 26262, the FDA guidance on the total product life cycle for infusion pumps and the OMG standard on argumentation (Structured Assurance Case Metamodel, SACM). - 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 J3062 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. More generally, the role of formal verification in the wider context of assurance. - 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. ************************************************************************************************* SUBMISSION GUIDELINES ************************************************************************************************* Papers will be peer-reviewed by at least 3 program committee members, and accepted papers will be published in the SAFECOMP 2019 Workshop proceedings, to be published by Springer in the Lecture Notes in Computer Science (LNCS) series. 1. All papers must be original work not published, or in submission, elsewhere. 2. Papers should be submitted in PDF only. Please verify that papers can be reliably printed and viewed on screen before submission. 3. Papers should conform to the SAFECOMP paper formatting guidelines. 4. Regular (Research/Tools/Experience) papers can be no more than 10 pages long, including figures, references, and any appendices. Note that accepted tool papers will be expected to a give a tool demonstration at the workshop, i.e., no screenshots. 5. Position papers (relating to ongoing work or proposed aspects of challenge problems) will be limited to 6 pages, including figures, references, and any appendices. 6. Submission is via EasyChair: https://easychair.org/conferences/?conf=assure2019 ************************************************************************************************* WORKSHOP ORGANIZERS ************************************************************************************************* Ewen Denney, SGT / NASA Ames Research Center, USA Ibrahim Habli, University of York, UK Irfan Sljivo, Mälardalen University, Sweden Ganesh Pai, SGT / NASA Ames Research Center, USA |
|