Re: [SystemSafety] Call for Papers. ASSURE 2016

From: SPRIGGS, John J < >
Date: Tue, 5 Apr 2016 08:42:39 +0000


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_xxxxxx

NATS
4000 Parkway, Whiteley,
Fareham, Hants PO15 7FL
www.nats.co.uk<http://www.nats.co.uk/>

From: systemsafety [mailto:systemsafety-bounces_at_xxxxxx Sent: 04 April 2016 23:40
To: systemsafety_at_xxxxxx 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:

                   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_xxxxxx 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.






The System Safety Mailing List
systemsafety_at_xxxxxx Received on Tue Apr 05 2016 - 10:43:36 CEST

This archive was generated by hypermail 2.3.0 : Tue Jun 04 2019 - 21:17:08 CEST