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 3 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 2006 2 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 2006 3 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 2006 4 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 2006 5 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 2006 6 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 2006 7 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 2006 8 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 2006 9 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
Progress on MISRA C++ DARP workshop, York, 18 th April 2007 Chris TappKeylevel Consultants Ltd. Dr C H PygottQinetiQ.
QinetiQ Proprietary AN ISO standard for high integrity software.
© 2007 Carnegie Mellon University Secure Coding Initiative Jason A. Rafail Monday, May 14 th, 2007.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
10 th January QinetiQ in confidence © Copyright QinetiQ 1.
1 Certification Chapter 14, Storey. 2 Topics What is certification? Various forms of certification The process of system certification (the planning.
SOFTWARE QUALITY ASSURANCE SOFTWARE QUALITY ASSURANCE DEFINITIONS OF SQA SOFTWARE STANDARDS Process Quality Assurance Product Quality Assurance.
Workshop on Accreditation of Bodies Certifying Medical Devices Kiev, November 2014.
Project VIABLE: Behavioral Specificity and Wording Impact on DBR Accuracy Teresa J. LeBel 1, Amy M. Briesch 1, Stephen P. Kilgus 1, T. Chris Riley-Tillman.
OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.
COUNTER: improving usage statistics Peter Shepherd Director COUNTER December 2006.
Team Crutch. Vision Statement Team crutch aims to develop portable, inexpensive, user-friendly software for the Android platform that mitigates communication.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
OBP Research Oy for simpler creation of embedded systems.
1/16/2016Engr. Ali Ahmed1 Software Requirements Specification (SRS) Engr. Ali Ahmed C&SE Department BUKC.
B. Sharma, S.D. Dhodapkar, S. Ramesh 1 Assertion Checking Environment (ACE) for Formal Verification of C Programs Babita Sharma, S.D.Dhodapkar RCnD, BARC,
INSE lecture 17 Standards Quality. SE-related Standards Why? Who? What?
RQF Trials and the Newcastle Experience Barney Glover.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Quality Management in the Finland’s Greenhouse Gas Inventory Leena Raittinen, Statistics Finland UNFCCC Workshop on National Systems April 2005 Bonn,
Use of Fieldbus in safety related systems, an evaluation study of WorldFIP according to proven-in-use concept of IEC Jean Pierre Froidevaux WorldFIP.
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
CSEN 5314 Quiz 1. A data model is a collection of concepts that can be used to describe the ___________ of a database. a. structure b. extension c. state.
Usage statistics in context - panel discussion on understanding usage, measuring success Peter Shepherd Project Director COUNTER AAP/PSP 9 February 2005.
National Aeronautics and Space Administration Checklists and Testing Systems.
Chapter 24 - Quality Management 1Chapter 24 Quality management.
Acting Section Head, Regulatory Activities Section, NSNI, IAEA
Software Requirements Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn Lecture 4 & 5.
Assistance - Savita Kini November 15, Software Quality Assurance - Outline ä What is Software Quality assurance(SQA)? ä Quality Concepts. ä Software.
No: 1 CEMSIS wp6_beg037_v0_2_fisa 2003 slides.ppt CEMSIS FIKS-CT Cost-Effective Modernisation of Systems Important to Safety Deryk Pavey, Deryk.
Software Quality Assurance (SQA) Monitor the methods and standards used during the software development and verify their correct usage. What is Quality?
Hospital Accreditation Documentation Process & Standard Requirements
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
ISO STANDARDS TRAINING & CONSULTING
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Prepared by: Hussein Alhashimi. This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
L To identify the services that the customer requires from a system and the constraints under which it operates and is developed.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
Lawson Global Support Our Support Partnership Andrew Stephenson Lawson Global Support Working with Support Copyright ©
Page 1 | Proprietary and Copyrighted Information Safeguards Gary Hannaford, Task Force Chair IESBA CAG Meeting New York, USA September 14, 2015.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
Page 1 | Proprietary and Copyrighted Information Structure of the Code Don Thomson, Task Force Chair IESBA Meeting New York, USA November 30 – December.
Smart Home Technologies System Engineering. System Engineering in Intelligent Environments Intelligent Environments are complex systems consisting of.
© 2017 SlidePlayer.com Inc. All rights reserved.