File preview
Software Certification Consortium
Meeting #11 May 5 - 6, 2013
Welcome & Introductions
• Alan Wassyng • Brad Martin • Workshop Participants • Remote Participants
2
Scope & Deliverables
3
Regulations Regulations Engineer Experience
Engineer
Methods
Experience
Certifier
Certifier Tools Standards Methods
Tools
Research & Development Education Little Little Coordination Coordination Research & Development
Standards
Education
SCC Coordination
Overall SCC Outcomes
1) Theoretical Basis For System & Software Engineering Practices & Certification
3) Evidence Based Standards for Certified Software
6) Education & Skills Development Capability
Tolerable Risk from Systems Containing Software
2) System & Software Engineering, and Certification Methods And Tools
4) Certification & Regulatory Requirements
5) Demonstrate, Monitor & Track the Efficacy Of Methods and Tools
5
Workshop Theme
Competencies and Education
Required for
Development and Certification of Systems Containing Software
6
Agenda
SUNDAY 11:30 – 12:30 12:30 – 13:00 13:00 – 13:30 13:30 – 14:00 14:00 – 14:45 14:45 – 15:00 15:00 – 16:30 16:30 – 17:00 Lunch Welcome and Introductions Dick Fairley – Colorado Technical University / IEEE Computer Society "Bodies of Knowledge and Competency Models for Software and Systems Engineering" Phil Laplante – Pennsylvania State University “Licensing of Professional Software Engineers” Discussion 1 Coffee Breakout #1 – Bodies of Knowledge Report back from Breakouts
17:30 – 19:00
19:00 – 21:00
Social at Drummer’s Lot Pub
SCC Dinner at Treaty of Paris
7
Agenda
MONDAY 08:30 – 09:00 Anura Fernando – Underwriters Laboratories & John Hatcliff – Kansas State University “Challenges in Developing a Safety Standard for Medical Application Platforms” Steve Arndt – US Nuclear Regulatory Commission “Competencies Required for Engineering of Digital Systems in Nuclear Power Plants” Discussion 2 Coffee Ramesh S – General Motors “Competency Requirements for Engineering of Software Based Automotive Systems” Alan Wassyng – McMaster University “The Educational Value of Challenge Problems” Discussion 3 Lunch Medical Device Challenges – Overview and Options (Research & Education) Example PCA Pump Requirements Document PCA Pump Hardware Platform PCA Pump Challenge Potential Work Plan Intro to Insulin Pump Challenge & Work Plan Update on Pacemaker Challenge Coffee Discussion 4 Breakout #2 – Challenge Problems Report back from Breakout Actions and Wrap-up
8
09:00 – 09:30
09:30 – 10:15 10:15 – 10:30 10:30 – 11:00 11:00 – 11:30 11:30 – 12:15 12:15 – 13:15 13:15 – 13:25 13:25 – 13:40 13:40 – 13:50 13:50 – 14:00 14:00 – 14:10 14:10 – 14:20 14:20 – 14:30 14:30 – 15:00 15:00 – 16:30 16:30 – 17:15 17:15 – 17:30
Breakout #1 - BoKs
1. What Body of Knowledge do Developers & Certifiers of Safety Critical Systems Containing Software Need to Know? How can Developers & Certifiers Gain This Knowledge? How can the Software Certification Consortium Contribute to the Development of the Body of Knowledge, and the Availability of Education & Training That Encompass the BoK? Is there a system and software engineering process (based on an existing standard) that can be adopted to organize the BoK, educational and training material? Beyond educational and training material, is there a need for a comprehensive set of procedures that capture effective methods for development and certification of safety critical systems containing software? If needed, what role can SCC play in getting the procedures developed in an open access manner? What measures/metrics are available now for arguing the adequacy of software quality? Which domains should SCC address first? (medical devices, nuclear power, automotive, aviation, financial, other)
9
2. 3.
4.
5.
6.
7. 8.
Breakout #2 – Challenge Problems
1. Goals: research, education, regulatory, practice
2. SCC’s role in the challenges
3. How do we implement a certification regime for the challenges? 4. Rules for the challenges
5. Timeline – publications, competition, educational materials 6. Work plans for the PCA and/or insulin pump challenge problem
10
Action Items
11
Meeting #11 May 5 - 6, 2013
Welcome & Introductions
• Alan Wassyng • Brad Martin • Workshop Participants • Remote Participants
2
Scope & Deliverables
3
Regulations Regulations Engineer Experience
Engineer
Methods
Experience
Certifier
Certifier Tools Standards Methods
Tools
Research & Development Education Little Little Coordination Coordination Research & Development
Standards
Education
SCC Coordination
Overall SCC Outcomes
1) Theoretical Basis For System & Software Engineering Practices & Certification
3) Evidence Based Standards for Certified Software
6) Education & Skills Development Capability
Tolerable Risk from Systems Containing Software
2) System & Software Engineering, and Certification Methods And Tools
4) Certification & Regulatory Requirements
5) Demonstrate, Monitor & Track the Efficacy Of Methods and Tools
5
Workshop Theme
Competencies and Education
Required for
Development and Certification of Systems Containing Software
6
Agenda
SUNDAY 11:30 – 12:30 12:30 – 13:00 13:00 – 13:30 13:30 – 14:00 14:00 – 14:45 14:45 – 15:00 15:00 – 16:30 16:30 – 17:00 Lunch Welcome and Introductions Dick Fairley – Colorado Technical University / IEEE Computer Society "Bodies of Knowledge and Competency Models for Software and Systems Engineering" Phil Laplante – Pennsylvania State University “Licensing of Professional Software Engineers” Discussion 1 Coffee Breakout #1 – Bodies of Knowledge Report back from Breakouts
17:30 – 19:00
19:00 – 21:00
Social at Drummer’s Lot Pub
SCC Dinner at Treaty of Paris
7
Agenda
MONDAY 08:30 – 09:00 Anura Fernando – Underwriters Laboratories & John Hatcliff – Kansas State University “Challenges in Developing a Safety Standard for Medical Application Platforms” Steve Arndt – US Nuclear Regulatory Commission “Competencies Required for Engineering of Digital Systems in Nuclear Power Plants” Discussion 2 Coffee Ramesh S – General Motors “Competency Requirements for Engineering of Software Based Automotive Systems” Alan Wassyng – McMaster University “The Educational Value of Challenge Problems” Discussion 3 Lunch Medical Device Challenges – Overview and Options (Research & Education) Example PCA Pump Requirements Document PCA Pump Hardware Platform PCA Pump Challenge Potential Work Plan Intro to Insulin Pump Challenge & Work Plan Update on Pacemaker Challenge Coffee Discussion 4 Breakout #2 – Challenge Problems Report back from Breakout Actions and Wrap-up
8
09:00 – 09:30
09:30 – 10:15 10:15 – 10:30 10:30 – 11:00 11:00 – 11:30 11:30 – 12:15 12:15 – 13:15 13:15 – 13:25 13:25 – 13:40 13:40 – 13:50 13:50 – 14:00 14:00 – 14:10 14:10 – 14:20 14:20 – 14:30 14:30 – 15:00 15:00 – 16:30 16:30 – 17:15 17:15 – 17:30
Breakout #1 - BoKs
1. What Body of Knowledge do Developers & Certifiers of Safety Critical Systems Containing Software Need to Know? How can Developers & Certifiers Gain This Knowledge? How can the Software Certification Consortium Contribute to the Development of the Body of Knowledge, and the Availability of Education & Training That Encompass the BoK? Is there a system and software engineering process (based on an existing standard) that can be adopted to organize the BoK, educational and training material? Beyond educational and training material, is there a need for a comprehensive set of procedures that capture effective methods for development and certification of safety critical systems containing software? If needed, what role can SCC play in getting the procedures developed in an open access manner? What measures/metrics are available now for arguing the adequacy of software quality? Which domains should SCC address first? (medical devices, nuclear power, automotive, aviation, financial, other)
9
2. 3.
4.
5.
6.
7. 8.
Breakout #2 – Challenge Problems
1. Goals: research, education, regulatory, practice
2. SCC’s role in the challenges
3. How do we implement a certification regime for the challenges? 4. Rules for the challenges
5. Timeline – publications, competition, educational materials 6. Work plans for the PCA and/or insulin pump challenge problem
10
Action Items
11