We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byJohn Crabtree
Modified over 2 years ago
© Copyright QinetiQ limited 2006 Objectives of Coding Standards & MISRA C++ Clive Pygott, Systems Assurance Group, QinetiQ Chris Tapp, Keylevel Consultants & MISRA C++ chair
© Copyright QinetiQ limited DARP Workshop April 2006 Conclusions Predictability: behaviour, time, memory usage A requirement for more precise definition of the language/subset to be used in a high integrity environment A requirement for a more structured and capable means of recording intent and invariants in source code Verification A requirement for a means of collecting data on the effectiveness of any high-integrity guidelines Participants at the last Defence Aerospace Research Partnership C++ workshop were asked: what do you want to see in a generic software vulnerabilities standard
© Copyright QinetiQ limited Reasons for coding standards To avoid undefined behaviour To avoid implementation defined behaviour To improve clarity for review and maintenance To provide a consistent style across a program or set of programs To avoid common programmer errors To incorporate good practice, particularly with regard to future proofing
© Copyright QinetiQ limited Who are MISRA? Motor Industry Software Reliability Association Started in 1990 Mission: to provide assistance to the automotive industry in the creation and application of safe and reliable software in vehicle systems The original project was part of the UK Governments SafeIT programme Now self-supported – and used far outside the automotive industry
© Copyright QinetiQ limited MISRA C++ Extension of MISRA-C No language feature totally barred (except goto – for a better reason than in MISRA-C) Target date for draft for peer review – January 2007 Being developed by a working group including –Software safety consultants/researchers –Tool vendors –Users
© Copyright QinetiQ limited MISRA C++ sources Identification of Issues –QinetiQ Vulnerabilities Report Evaluation of Existing Material –Other Coding Standards MISRA-C JSF++ Medical Systems Transportation Tool Vendors (real world experience). –Other Publications Scott Meyers Stephen Dewhurst Etc.
© Copyright QinetiQ limited MISRA C++ Aims Predictability – mostly functional Portability Clarity for review/maintenance Avoiding common errors Not systematically addressed Predictability – temporal, memory usage Not Consistency of style Good practice/future proofing
© Copyright QinetiQ limited MISRA C++ (&C) rule structure Rule Structure –Rule Number and category (Mandatory…) –Headline Text (should be) precise and testable –Issue and Existing Material References –Explanation of the issue(s) and rule justification. –Examples of non-conforming and, where appropriate, conforming code. –Expected deviations (if appropriate and may include none!)
© Copyright QinetiQ limited MISRA C++ relationship with OWGV? Would hope that this group sets the objectives for high integrity software MISRA C++ would then want to claim compliance
For OWGV Meeting #1, 2006 June, Washington, DC, USA 1D Terms of Reference: ISO/IEC Project , Guidance to Avoiding Vulnerabilities in Programming.
Supporting further and higher education Pedagogic Evaluation Helen Beetham Consultant in Pedagogy JISC e-learning programme.
Health & Safety Management Health & Safety Management for Quarries Topic Four.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 29Slide 1 Chapter 29 Configuration Management.
1 ISO/IEC JTC 1/SC 22/WG 23 ISO working group on Guidance for Avoiding Vulnerabilities through language selection and use John Benito, Convener Jim Moore,
The MAP-ESG project Fiona Crozier Vice-President ENQA Assistant Director, QAA UK.
COUNTER: improving usage statistics Peter Shepherd Director COUNTER December 2006.
Ada's approach to Software Vulnerabilities Stephen Michell Maurya Software Ottawa Canada 25/06/06.
1 Report of Progress of ISO/IEC 24772, Programming Language Vulnerabilities, in ISO/IEC JTC 1/SC 22 John Benito, Convener Jim Moore, Secretary ISO/IEC.
The Role of COUNTER David Sommer JIBS User Group 2009.
Presentation title: 32pt Arial Regular, black Recommended maximum length: 1 line Quality is everything! Tricia Ellis AWHILES Conference 2 nd July 2008.
PLANNING THE AUDIT Individual audits must be properly planned to ensure: Appropriate and sufficient evidence is obtained to support the auditors opinion;
For C Language WG, 2006 March, Berlin 1 A New Standards Project on Avoiding Programming Language Vulnerabilities Jim Moore Liaison Representative from.
For SIGAda Conference, 2005 November, Atlanta 1 A New Standards Project on Avoiding Programming Language Vulnerabilities Jim Moore Liaison Representative.
WMO Standards and Technical Regulations (TR) D. Ivanov (Member of Secretariat TR Editorial Board; DRA-C/ROE) Reduced version (I. Zahumensky; WIGOS-PO)
Regulatory Submission Datasets in the World of Evolving Standards Dave Christiansen, DrPH Christiansen Consulting, CDISC Founding Director Safety and the.
Software Quality Management CIS 376 Bruce R. Maxim UM-Dearborn.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Configuration Management IS301.
Market Reform Forum John Harvie, MRPO Martin Roberts, LMA 25 April 2007.
1 CDASH Initiative: Status Update Bay Area CDISC Implementation Network Meeting - May 29, 2008 Rhonda Facile, Project Director, CDISC Dorothy B. Dorotheo,
Usage statistics in context - panel discussion on understanding usage, measuring success Peter Shepherd Project Director COUNTER AAP/PSP 9 February 2005.
INSE - Lecture 16 Documentation Configuration Management Program Support Environments Choice of Programming Language.
Copyright © Healthcare Quality Quest, Proposed standards for a national clinical audit — How we got involved and what we have learned.
APPLICATION of Various Techniques for HAZARD n A BIOLOGICAL, CHEMICAL OR PHYSICAL AGENT THAT IS REASONABLY LIKELY TO CAUSE ILLNESS OR INJURY IN THE ABSENCE.
Slide 3.1 © The McGraw-Hill Companies, 2007 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach.
How do we keep track of what we do? COUNTER now and in the future? Peter Shepherd Director COUNTER February 2008.
Integrating the gender aspects in research and promoting the participation of women in Life Sciences, Genomics and Biotechnology for Health.
The Project Cycle Management Course presented by Simon Pluess World Alliance of YMCAs.
European Aviation Safety Agency 5 July 2007 EASA Cologne Slide 1.
COUNTER: making statistics useful Peter Shepherd Director COUNTER January 2007.
© 2016 SlidePlayer.com Inc. All rights reserved.