The tuition is aligned with a traditional industry ‘V’ model development cycle, but also considers the assurance of Agile methods. Industry good practice standards are discussed including IEC61508, RTCA DO178C / DO254 and the UK MoD standard 00:055.

Lead Tutor

Mr Richard Maguire CEng FIMechE, MBCS, MSaRS

Software and Safety Assurance Consultant – Rail Systems, Aerospace & Defence

Richard is a valuable associate for Wilde Analysis Ltd. He has a first degree in Mechanical Engineering, MSc in Technology Management and post-grad in Software Engineering. His company RS2A Limited was set up in 2006 after his work in Automotive, Petrochemical and Defence industries.

Richard now has 15 years of direct engineering, management and assurance experience in safety critical industries, helping companies construct their assurance arguments for certification and accreditation programmes.

Richard has been guest lecturer at Queen Mary College London University and was also a Teaching Fellow at University of York on their renowned MSc in System Safety. He has presented internationally and published many conference papers on software and risk issues over 20 years.

Who Should Attend?

This is at the introductory level of software assessment and would be suitable for Managers, Designers, Supervisors, Operators, Trainees and Graduates.

Prerequisites

The course does not assume any prior knowledge on the subject of Reliability or Safety Engineering, with fundamental concepts and terminology being introduced.

Duration

1 Day

The course commences at 9:00am and finishes at approximately 5:00pm.

Course Fee

From £525, including lunch and refreshments.

Delegates will receive a certificate of attendance.

Sessions

• Introduction
  • Key definitions
  • Industry practice
  • Software assurance policies
• Standard Approaches
  • Avoiding Errors
  • Finding Errors
  • Integrity Levels
• Requirements
  • Decomposition from Users to Code
  • Standard approaches
• Traceability
  • Requirements traceability
  • Test traceability
• Assurance
  • Absence of vulnerabilities
  • Residual risk
  • Reporting and Communication
• Testing
  • Checklists; Static Analysis
  • Dynamic Verification
• Software Safety
  • Failure Modes
  • Hazards
• Software Security
  • Threats
  • Attacks
  • Protection
• Worked Example
  • Our example follows the development of an engine control function from User Requirement to Code Testing, with all the things that can go well and not so well in between.