[SystemSafety] Call for Papers. ASSURE 2016
SPRIGGS, John J
John.SPRIGGS at nats.co.uk
Tue Apr 5 10:42:39 CEST 2016
Although UK CAA’s CAP760 does indeed provide some guidance on development of assurance cases, their CAP670 (in Part B Section 3 “SW01”) would be a better place to start if you have ‘software intensive systems’.
John
http://publicapps.caa.co.uk/docs/33/CAP760.pdf
http://publicapps.caa.co.uk/docs/33/CAP%20670%2023%20May%202014.pdf
[NATS]
John Spriggs
Head of Legacy, Infrastructure & Software Assurance
D: 01489 615371
e: john.spriggs at nats.co.uk<mailto:john.spriggs at nats.co.uk>
NATS
4000 Parkway, Whiteley,
Fareham, Hants PO15 7FL
www.nats.co.uk<http://www.nats.co.uk/>
From: systemsafety [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of Ganesh J. Pai
Sent: 04 April 2016 23:40
To: systemsafety at techfak.uni-bielefeld.de
Subject: [SystemSafety] Call for Papers. ASSURE 2016
Dear System Safety List Members,
Please consider submitting a research / position / tools / industrial practice paper to the 4th International Workshop on Assurance Cases for Software-Intensive Systems (ASSURE 2016), which will be collocated this year with SAFECOMP 2016, in Trondheim, Norway.
The Call for Papers is included below. More details on the workshop are available on the ASSURE 2016 website: http://ti.arc.nasa.gov/events/assure2016/
*************************************************************
CALL FOR PAPERS
*************************************************************
ASSURE 2016
The 4th International Workshop on Assurance Cases
for Software-intensive Systems
September 20, 2016
Trondheim, Norway.
Collocated with SAFECOMP 2016
*************************************************************
http://ti.arc.nasa.gov/events/assure2016
*************************************************************
Software plays a key role in high-risk systems, e.g.,
safety-, security-, and mission-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 and the FAA's operational approval guidance
for unmanned aircraft systems), automotive (ISO 26262), and
healthcare (FDA total product lifecycle guidance for
infusion pumps). As such, there is a need to develop models,
tools, and techniques 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:
(a) explore techniques for creating/assessing assurance
cases for software-intensive systems;
(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 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.
- Modeling and meta modeling: 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.
- Other topics, including the exploration of relevant
techniques for assurance cases for real-time, concurrent,
and distributed systems; and the connections between the
Goal Structuring Notation for assurance cases and
goal-orientation from the requirements engineering
community.
************************************************************
SUBMISSION GUIDELINES
************************************************************
1. All papers must be original work not published, or in
submission, elsewhere.
2. All papers should be submitted only in PDF. Please
verify that papers can be reliably printed and viewed on
screen before submitting.
3. Papers should conform to the LNCS paper formatting
guidelines. See the ASSURE 2016 website (below) for
details.
4. Regular (research, or practice) papers can be up to 12
pages long including figures, references, and any
appendices.
5. Tools papers can be up to 10 pages long including
figures, references and any appendices. Note: Authors of
accepted tools papers will be expected to give a
demonstration of the tool(s) at the workshop, i.e., no
screenshots.
6. Position papers can be between 4 and 6 pages long,
including figures, references, and any appendices.
6. Submit your paper electronically by May 17, 2015 through
the workshop website:
http://ti.arc.nasa.gov/events/assure2016/
Papers will be peer-reviewed by at least three program
committee members. Accepted papers will be published in
the SAFECOMP 2016 Workshop Proceedings, to be published by
Springer, in the Lecture Notes in Computer Science (LNCS)
Series.
************************************************************
IMPORTANT DATES
************************************************************
Workshop papers due : May 17, 2016
Author notification : June 7, 2016
Camera ready papers : June 20, 2016
ASSURE 2016 Workshop : September 20, 2016
SAFECOMP 2016 : September 20 - 23, 2016
************************************************************
WORKSHOP ORGANIZERS
************************************************************
Ewen Denney, SGT / NASA Ames Research Center, USA
Ibrahim Habli, University of York, UK
Ganesh Pai, SGT / NASA Ames Research Center, USA
************************************************************
PROGRAM COMMITTEE
************************************************************
To be confirmed. See the ASSURE 2016 Website.
http://ti.arc.nasa.gov/events/assure2016/
************************************************************
***************************************************************************
If you are not the intended recipient, please notify our Help Desk at Email information.solutions at nats.co.uk
immediately. You should not copy or use this email or attachment(s) for any purpose nor disclose
their contents to any other person.
NATS computer systems may be monitored and communications carried on them recorded, to
secure the effective operation of the system.
Please note that neither NATS nor the sender accepts any responsibility for viruses or any losses
caused as a result of viruses and it is your responsibility to scan or otherwise check this email
and any attachments.
NATS means NATS (En Route) plc (company number: 4129273), NATS (Services) Ltd
(company number 4129270), NATSNAV Ltd (company number: 4164590)
or NATS Ltd (company number 3155567) or NATS Holdings Ltd (company number 4138218).
All companies are registered in England and their registered office is at 4000 Parkway,
Whiteley, Fareham, Hampshire, PO15 7FL.
***************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20160405/fa548a6c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 619 bytes
Desc: image001.gif
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20160405/fa548a6c/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 167 bytes
Desc: image004.png
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20160405/fa548a6c/attachment-0001.png>
More information about the systemsafety
mailing list