Software Quality Assurance and its Functional Safety - vital for increasing level of autonomy

Transcription

1 Software Quality Assurance and its - vital for increasing level of autonomy Seojeong Lee / Prof. Marine IT division

2 Agenda 1. Autonomous technology in maritime area 4 th industrial revolution technologies Expected benefits and challenges 2. E-navigation Software Quality guideline Guideline on and HCD for e-navigation (IMO MSC Circ.1512) 3. Software Safety vs. Security Software Safety related experiences of other industries and S.Korea 4. Concluding remarks 2 2

3 1. Autonomous technology in maritime area 4th industrial revolution technology in maritime Software Quality and its Machine Learning Manufacturing Operating Monitoring and Diagnosis Virtual Reality IoT (Source: Rolls Royce) 3

4 1. Autonomous technology in maritime area Expected benefits of autonomous technology A survey related to autonomous shipping by Nautilus Federation If higher automation releases ships staff to monitor more effectively what is happening aboard their vessels, that almost 900 maritime professionals from 12 different countries were participated. should be an advantage since crews on many types of ship More than 60% consider technology could be used to improve safety accidents and automation more likely. offers the potential to deliver improved operational performance. are overworked and tired, making poor decisions and Benefits to use new equipment and systems to: reduce workloads, ease administrative burdens, eliminate dirty and dangerous work in enclosed spaces, and assist with predictive and preventive maintenance. 4

5 1. Autonomous technology in maritime area Challenges to overcome Concerns by the survey participants: scale CYBER-SECURITY Reliability of communications and the data exchange link Legal and liability issues Quality of software Risk assessment and public acceptance Opposition from seafarers and their unions Regulatory issues Technical feasibility Training and reskilling Economic feasibility 5.65 (Source: Future proofed?, Nautilus Federation) 5

6 2. E-navigation Software Quality guideline IMO s work on Software Quality Guideline on and HCD for e-navigation (IMO MSC Circ.1512) 6

7 2. E-navigation Software Quality guideline IMO s work on Software Quality process Disposal Activity 6 Software Disposal Strategy Analysis Operational System Feedback Preliminary hazard analysis Feedback Loop Stakeholder and System Requirements Stage 1: Concept development Activity 1 Stakeholder and System requirements definition Maintenance and Operational Requirements Stage 5: Operation Activity 5 Software operation and maintenance Reuse Stage 2: Planning and Analysis Activity 2 System requirement analysis Reuse Optimised set of the requirements Verification of Conformance Stage 4: Integration and Testing Activity 4 Software testing, installation and acceptance Stage 3: Design Activity 3 System architectural design and integration Reuse System readiness Prototype 7

8 2. E-navigation Software Quality guideline IMO s work on Software Quality Software quality in use Software Quality in Use Capability of a software product to enable specific users to achieve specific goals with effectiveness, productivity, safety and satisfaction in specific contexts of use. Software Quality in Use Effectiveness Efficiency Satisfaction Effectiveness to use software Efficiency to use software Usefulness, Trust, Pleasure, Comfort Freedom from risk Context coverage Economic risk, Health and safety risk Environmental risk mitigation Context completeness Flexibility 8

9 3. Software Software Functional safety, defined as the absence of unacceptable risks due to hazards caused by the malfunction behavior of electric or electronic systems, is quickly becoming a key factor in the development of modern vehicles. by FEV Motorentechnik GmbH 9

10 3. Software Safety and Security Safety The prevention of accidents which may or may not involve human agents, but are in any case not intentional. Safety can also refer to protecting against things like users making dumb mistakes. performing dangerous options using computer, we prompt the user with a confirmation box, to increase overall safety. Security The prevention of malicious activities by human such as mugging, burglary, robbery, terrorist activities. The prevention of unauthorized actions such as changing settings for prevented and/or not allowed data. 10

11 3. Software What information is available in the maritime field on Software related Safety and Security? Guidelines on cyber risk management IMO Led by BIMCO Baltic and International Maritime Council (2017) Guidelines on Cyber Security Onboard Ships 11

12 3. Software Classification societies also provide information on software related safety (Source: American Bureau of Shipping) 12

13 3. Software Other industries efforts on software functional safety Maritime industry? Why? Where? (source: 13

14 3. Software S.Korea s efforts Software guideline Supported by NIPA National IT Industry Promotion Agency, To help small SW companies in railway, medical and maritime areas ScarFS (Software to be Careful about ) process and usable templates for maritime area Free of charge Scoping target SW Identifying Hazards Analyzing hazards Finding solutions 5Assigning responsibility Verification and Validation ScarFS process Risk Analysis SW requirement Analysis SW Design SW Implementation SW Integration SW Maintenance 14

15 3. Software Software safety opportunity in Autonomous vessels Terminologies Smart ships, ships' connectivity, remote ships, and digital twin etc. Summary of IMO MSC's discussions on autonomous ships The scoping exercise of "autonomous ship" should include: the full range of human element factors within different levels of autonomy for both shipboard and shore-based personnel; the reliability, robustness, resiliency and redundancy of the underlying technical, communications, software and engineering systems; consideration of conducting a Formal Safety Assessment or gap analysis as to the safety, technical, human element and operational aspects of autonomous remotely controlled or unmanned ships. 15

16 Concluding remarks Autonomy will come sooner if providing at a low cost Software will become a growing feature more and more - Software quality and Software functional safety as part of overall maritime safety Proactive and preemptive actions are needed To improve the level of safety and efficiency in maritime area To improve the seafarers work life (Source: lunamarina/wikipedia.org ) 16

17 감사합니다. [Gamsa-hab-nida]