software quality assurance and its functional safety€¦ · 7 functional safety sqa imo’s work...
TRANSCRIPT
Seojeong Lee / Prof. Marine IT division
Software Quality Assurance and
its Functional Safety
- vital for increasing level of autonomy
2
Functional Safety
SQAAgenda
2
1. Autonomous technology in maritime area
– 4th industrial revolution technologies
– Expected benefits and challenges
2. E-navigation Software Quality guideline
– Guideline on SQA and HCD for e-navigation
(IMO MSC Circ.1512)
3. Software Functional Safety
– Safety vs. Security
– Software Safety related experiences of other industries
and S.Korea
4. Concluding remarks
3
Functional Safety
SQA4th industrial revolution technology in maritime
1. Autonomous technology in maritime area
Operating
Monitoring and Diagnosis
Manufacturing
“ Software Quality and
its Functional Safety”
(Source: Rolls Royce)
Machine Learning
Virtual Reality
IoT
4
Functional Safety
SQAExpected benefits of autonomous technology
• A survey related to autonomous shipping by Nautilus Federation
– almost 900 maritime professionals from 12 different countries
were participated.
• More than 60% consider technology could be used to improve safety and automation offers the potential to deliver improved operational performance.
• 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.
1. Autonomous technology in maritime area
“If higher automation releases ships’ staff to monitor more
effectively what is happening aboard their vessels, that
should be an advantage since crews on many types of ship
are overworked and tired, making poor decisions and
accidents more likely.”
5
Functional Safety
SQAChallenges to overcome
1. Autonomous technology in maritime area
(Source: “Future proofed?”, Nautilus Federation)
scale 1-10
1 CYBER-SECURITY 8.16
2 Reliability of communications and the data exchange link 7.96
3 Legal and liability issues 7.81
4 Quality of software 7.62
5 Risk assessment and public acceptance 7.5
6 Opposition from seafarers and their unions 7.43
7 Regulatory issues 7.09
8 Technical feasibility 6.52
9 Training and reskilling 5.77
10 Economic feasibility 5.65
• Concerns by the survey participants:
6
Functional Safety
SQAIMO’s work on Software Quality
2. E-navigation Software Quality guideline
Guideline on SQA and HCD for e-navigation (IMO MSC Circ.1512)
7
Functional Safety
SQAIMO’s work on Software Quality – SQA process
2. E-navigation Software Quality guideline
Activity 5Software operation and
maintenance
Activity 2 System requirement
analysis
Activity 1Stakeholder and System
requirements definition
Preliminary hazard analysis
Analysis Operational System Feedback
Stage 1: Concept development
Activity 3System architectural design
and integration Activity 4
Software testing, installation and acceptance
Stage 2: Planning and Analysis
Stage 3: DesignStage 4: Integration and Testing
Stage 5: Operation
Verification of Conformance
FeedbackLoop
Activity 6Software Disposal
Strategy
Disposal
PrototypeSystem readiness
Stakeholder and System Requirements
Reuse
Reuse
Reuse
Maintenance and Operational Requirements
Optimised set of the requirements
8
Functional Safety
SQAIMO’s work on Software Quality – Software quality in use
2. E-navigation Software Quality guideline
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.
Context coverage
Context completeness
Flexibility
Effectiveness to use software
Efficiency to use software
Satisfaction
Effectiveness
Efficiency
Freedom from risk
Usefulness, Trust, Pleasure, Comfort
Economic risk, Health and safety riskEnvironmental risk mitigation
Software Quality in Use
9
Functional Safety
SQASoftware Functional Safety
3. Software Functional Safety
“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
10
Functional Safety
SQASafety and Security
3. Software Functional Safety
• 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.
11
Functional Safety
SQAWhat information is available in the maritime field on Software related Safety and Security?
3. Software Functional Safety
• Guidelines on cyber risk management IMO
– Led by BIMCO Baltic and International Maritime Council (2017)
• Guidelines on Cyber Security Onboard Ships
12
Functional Safety
SQAClassification societies also provide information on software related safety
3. Software Functional Safety
(Source: American Bureau of Shipping)
13
Functional Safety
SQAOther industries’ efforts on software functional safety
3. Software Functional Safety
Maritime industry?
Why?
Where?
(source: http://www.aispro.com/)
14
Functional Safety
SQAS.Korea’s efforts – Software Functional Safety guideline
ScarFS process
Assigning responsibility5
Finding solutions4
Analyzing hazards3
Identifying Hazards2
Scoping target SW1
Risk Analysis
SW requirementAnalysis
SW Design
SW Implementation
SW Integration
SW Maintenance
Verification
and
Validation
• Supported by NIPA
– National IT Industry Promotion
Agency, 2016-2017
• To help small SW companies in
railway, medical and maritime
areas
• ScarFS (Software to be Careful
about Functional Safety)
process and usable templates
for maritime area
• Free of charge
3. Software Functional Safety
15
Functional Safety
SQASoftware safety opportunity in Autonomous vessels
3. Software Functional Safety
• 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.
16
Functional Safety
SQAConcluding 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: http://mylifeatsea.blogspot.kr,http://www.crewtoo.com, lunamarina/wikipedia.org )
감사합니다.[Gamsa-hab-nida]