managing systems and software reliability

12
managing systems and software reliability DNV SERVING THE ENERGY AND MARITIME INDUSTRIES integrated software dependent systems IMPROVE SYSTEM PERFORMANCE THE POWER TO

Upload: dnv-gl-old-account

Post on 24-Mar-2016

216 views

Category:

Documents


1 download

DESCRIPTION

Software and systems used in the energy and maritime environments are becoming increasingly complex as they evolve to meet more demanding operational, regulatory and technological requirements. The energy and maritime industries are also facing great product innovation with more embedded software forming part of the safety and business critical systems. DNV has extensive experience working with these industries and with this experience we have identified software and systems development standards and best practices and brought them together to produce a new recommended practice, DNV RP-D201, and an offshore standard, OS-D203 – a new class notation for Integrated Software Dependent Systems (ISDS).

TRANSCRIPT

Page 1: Managing systems and software reliability

managing systems and software reliability

DNV SERVING THE ENERGy aND maRITImE INDUSTRIESintegrated software dependent systems

Improvesystemperformance

the power to

Page 2: Managing systems and software reliability

GLOBAL SERVICES TO THE ENERGY AND MARITIME INDUSTRIES

■■ Safety, health and environmental risk management ■■ Enterprise risk management ■■ IT risk management■■ asset risk management

■■ Technology qualification ■■ Verification ■■ Ship classification ■■ Offshore classification

02 I ENERGy aND maRITImE I integrated software dependent systems I

Page 3: Managing systems and software reliability

CONTENTS

I integrated software dependent systems I ENERGy aND maRITImE I 03

04 Introducing the world’s first class notation for systems and software reliability06 Reducing software-related downtime for Seadrill08 measuring the quality of software source code

02 I ENERGy aND maRITImE I integrated software dependent systems I

Software and systems used in the energy and maritime environments are becoming increasingly complex as they evolve to meet more demanding operational, regulatory and technological requirements. The energy and maritime industries are also facing great product innovation with more embedded software forming part of the safety and business critical systems.

DNV has extensive experience working with these industries and with this experience we have identified software and systems development standards and best practices and brought them together to produce a new recommended practice, DNV RP-D201, and an offshore standard, OS-D203 – a new class notation for Integrated Software Dependent Systems (ISDS).

tHe poWer to Improve system performance

©is

tock

Page 4: Managing systems and software reliability

IntroducIng tHe World’s fIrst class notatIon for systems and softWare relIabIlIty

04 I ENERGy aND maRITImE I integrated software dependent systems I

DNV’s optional ISDS notation has been developed in response to industry demand for improved management of risks associated with software malfunctions. ISDS is based on a proven methodology to ensure software integrity from the newbuilding process throughout the lifetime of the unit. Through specific process requirements, ISDS helps prevent software issues that may result in costly delays at the yard, and it helps owners and operators to avoid downtime during operations.

MILLIONS OF LINES OF CODECritical systems onboard offshore units contain high vol-umes of software code. Dynamic positioning and drilling control systems typically contain about 500,000 lines of programming each. In comparison, an Airbus A380 com-mercial airplane has about one million lines of code. In terms of software, offshore units tend to be far more com-plex than airplanes, yet the software on these units is not by far subject to the same controls and testing as seen in the aviation industry. The system components onboard offshore units are manufactured by different suppliers and are inte-grated at the yard. It is typically during this process that compatibility issues that compromise unit performance are detected.

Software is also upgraded more frequently than hardware, introducing a need for well-defined change management processes that can be used through the entire life cycle of the unit.

SOFTWARE BUSINESS RISKSoftware delays at the yard can last for months, and for units

in operation, downtime is a significant business risk. With rigs getting day rates of up to USD 500,000, waiting around to repair code or re-boot systems after upgrades or malfunc-tions is unacceptable.

Safe, predictable and profitable operations depend on the development of reliable components, successful integration of these components into systems, and good management and coordination of components and system requirements.The entire software value chain, including development, procurement, testing, validation, integration, commission-ing, configuration and operation have to be considered, in order to reduce delays and non-productive time.

WORKING TOWARD AN INDUSTRY STANDARDDNV has developed the ISDS methodology to give benefits to all parties involved in a project; owners, operators, yards and suppliers. While reduced risk for delays and downtime are the key benefits for the owners and operators, lasting improvements in system integration capabilities and early finding of potential problems are the key benefits for yards and suppliers. Some of the world-leading yards and suppli-ers have already expressed that they see ISDS as means to increase their competitive strength.

DNV’S TRACK RECORD IN SOFTWARE INTEGRITYDNV has a long history working with software dependent systems. In 1982, DNV became the first class society to issue a classification note on Computer Based Systems, and today DNV has extensive in-house software competence and spe-cialists with experience also from the automotive, telecom and aerospace industries. In 2008, DNV released a

The increasing complexity of onboard software dependent systems represents a significant safety and business risk for owners and operators of advanced offshore units. With renewed industry focus on this critical, but often poorly managed, operational component, DNV has developed the world’s first class notation for Integrated Software Dependent Systems (ISDS).

Page 5: Managing systems and software reliability

I integrated software dependent systems I ENERGy aND maRITImE I 0504 I ENERGy aND maRITImE I integrated software dependent systems I

Recommended Practice for Integrated Software Dependent Systems (DNV-RP-D201).

The ISDS methodology has been built on DNV’s decades of experience working with software integrity for embedded systems, and the methodology represents the industry’s most comprehensive and effective software-related risk manage-

ment tool to date. After piloting ISDS in more than 10 off-shore projects, the Recommended Practice was promoted to a tentative Offshore Standard in 2010 (DNV-OS-D203). In 2011, the Offshore Standard, and the belonging class nota-tion, are released in their final version ready to be applied in projects globally.

Page 6: Managing systems and software reliability

06 I ENERGy aND maRITImE I integrated software dependent systems I

reducIng softWare-related doWntIme for seadrIll

Seadrill undertook a pilot project, applying DNV’s recom-mended practices retrospectively to a recent newbuild to determine if the practices would have covered the gaps they felt occurred in the software integration process. DNV’s software engineering team in Houston met with Seadrill staff and evaluated procedures and documentation. Although many of the units in Seadrill’s fleet are not classed by DNV, this software integration task falls outside the scope of mandatory class rules and could be supported without conflict by DNV.

Seadrill and DNV addressed commissioning, change man-agement, crew competence and transparency issues. After a period of on-site collaboration, Seadrill and DNV planned and delivered recommended practice training, performed gap analysis and risk analysis to prioritise their findings and developed an action plan. Ten major action areas were identified, seven relating to on-going operation and three to future newbuilds. Importantly, external support helped Seadrill to keep the initiative moving so that new practices were implemented and the company was better prepared for future newbuilds.

PROJECT FINDINGSThe project addressed typical integration problems such as limited local vendor support and long downtimes.

One finding was that the rig crew had little or no involve-ment in the integration testing processes that could have built up their competence to support the system, and they relied on service engineers flown in from overseas. Naturally, it was also recognised that not all the expertise necessary to maintain every system can be kept continuously available onboard every rig.

Another finding was that the lack of technical documenta-tion limited the understanding of what was being tested, and there was no good means of feedback when equipment design or functionality did not meet operational requirements.

It was also difficult to assign problems to a particular vendor as some machines can have up to five vendor control systems involved in their operation. Some equipment manufacturers offered poor training and did not follow up to ensure their equipment was working as designed, and inadequate soft-ware revision control led to downtime and the loss of impor-tant upgrades. Documentation for fixes and upgrades gener-ally lacked detail on what was being changed, why and how it should be tested.

BENEFITS OF ISDSIn undertaking the pilot project and by applying the meth-odologies of ISDS, several benefits were highlighted. These include:■■ the class notation provides a well-defined framework for the industry on how to work systematically with quality and performance assurance for software dependent systems

■■ in collaboration with DNV specialists, the owner can assess suppliers to ensure they have the pre-requisites for deliver-ing good quality software

■■ owners are able to address potential problems earlier in the project, at a time when it is much cheaper to resolve any problems without causing critical delays

■■ the methodology is not only applicable for the develop-ment of the project and commissioning – it is also applica-ble during operation in order to manage changes throughout the lifetime of the rig/vessel.

Seadrill is an offshore deepwater drilling company that operates a fleet of 41 units including drillships, jackup rigs, semisubmersible rigs and tender rigs. Their latest generation newbuilds are highly automated and when software is integrated, care must be taken to ensure that the movements of components such as pipe handlers do not clash with other, equally-automated components.

Ref: The full story of this project was published in Offshore Engineer, Oct 2010

Page 7: Managing systems and software reliability

I integrated software dependent systems I ENERGy aND maRITImE I 0706 I ENERGy aND maRITImE I integrated software dependent systems I

“ISDS is a great tool to help guide us through new systems and optimisations and we’ll definitely use it going forward.”Steve O’Leary, Technical Services Director at Seadrill

© P

hoto

: Sea

drill

Page 8: Managing systems and software reliability

08 I ENERGy aND maRITImE I integrated software dependent systems I

measurIng tHe QualIty of softWare source code

QUALITY COUNTSSoftware quality includes both external and internalaspects.■■ External quality is defined by functionality, usability, amount of faults and performance, usually addressed and under control

■■ Internal quality is about testability, reusability, maintain-ability and changeability. This is often overlooked since it is less visible, harder to measure and has a long term impact on the life cycle cost.

SQALESQALE objectively evaluates internal quality in order tounderstand the life cycle costs. SQALE delivers true valueby:■■ assessing and comparing software quality between differ-ent version, subcontractors, applications and sub-systems

■■ strengthening own quality management processes to define and follow-up quality goals

SQALE BRINGS ADDED VALUECode analysis is not new but SQALE delivers resultsthrough:■■ quality model based on a life cycle perspective - quality characteristics are defined and linked to the software life cycle

■■ an analysis model based on a unique aggregation Method - SQALE aggregates all static analysis results in quality indexes based on remediation costs.

ExAMPLES OF SQALE USAGE:■■ efactoring decisions■■ control outsourced product quality■■ improvement activities follow-up■■ evaluate open source projects■■ due diligence■■ choose between two similar products

QUALITY MODELThe Quality Model is made up of six qualitycharacteristics based on the software life cycle.Associated to each quality characteristic is a set ofsub-characteristics. Each sub-characteristic is definedthrough at least one quality checkpoint. Each qualitycheckpoint sets the quality requirement to be satisfied.

ANALYSIS MODELAnalysing the software quality is measuring the gap leftto achieve the quality targets. To measure this gap, aremedy factor is introduced to compensate for thespecific remedy for each checkpoint. This results in anindex that corresponds to the remediation effort to satisfythe quality requirements.

REPORTINGThe SQALE reporting is compact and graphical.Different stakeholders receive relevant information basedon the same data e.g.:■■ management gets feedback on quality characteristics and life cycle costs

■■ developers get feedback on adherence to quality checkpoints.

Comparing the non compliance distribution relatedto Testability between Reused, Modified, newlyCreated, and Outsourced source code files

as a supplement to the ISDS methodology, DNV has SQaLE - a model and tools to assess the quality of software source code. The model is applicable to all programming languages relevant for maritime and offshore control systems.

Page 9: Managing systems and software reliability

I integrated software dependent systems I ENERGy aND maRITImE I 0908 I ENERGy aND maRITImE I integrated software dependent systems I

©N

exan

s

Page 10: Managing systems and software reliability

10 I ENERGy aND maRITImE I integrated software dependent systems I

■■ Safety, health and environmental risk management

■■ Enterprise risk management■■ IT risk management ■■ asset risk management ■■ Technology qualification ■■ Verification ■■ Ship classification ■■ Offshore classification

global servIces to tHe energy and marItIme IndustrIes

Page 11: Managing systems and software reliability

10 I ENERGy aND maRITImE I integrated software dependent systems I I integrated software dependent systems I ENERGy aND maRITImE I 11

maIn offIces

Paris69 rue du Chevaleret75013 ParisFrancePhone: +33 144244010

PerthLevel 5216 St Georges TerracePerth, WaaustraliaPhone: +61 0408 006339

Pusan Namchon 1-dong Suyong-Gu, Pusan 613011, Republic of KoreaPhone: +82 51 610 7700

Rio de JaneiroRua Sete deSetembro,111/12 Floor20050006 Rio de JaneiroBrazilPhone: +55 21 3722 7232

ShanghaiHouse No. 91591 Hong Qiao RoadShanghai 200336ChinaPhone: +86 21 3208 4518

SingaporeDNV Technology Centre10 Science Park DriveSingapore 118224Phone: +65 6508 3750

AberdeenCromarty HouseRegent Quayaberdeen aB11 5aRUnited Kingdom Phone: +44 1224 335 000

Dubai Bur Juman Office Tower, 14th Floor, Trade Center Road, Dubai United arab EmiratesPhone: +971 4 352 6626

Houston1400 Ravello DrKaty, TX 77449USaPhone: +1 281 396 1000

LuandaEdificio monumentalRua major Kanhangulo nº 290, 2º andarangolaPhone: +244 222 391 631

OsloVeritasveien 1NO-1322 HøvikNorwayPhone: +47 67 57 99 00

LondonPalace House3 Cathedral StreetLondon SE1 9DEUnited KingdomPhone: +44 20 7357 6080

Page 12: Managing systems and software reliability

Det NORSke VeRItAS ASNO-1322 Høvik, Norway I Tel: +47 67 57 99 00 I Fax: +47 67 57 99 11www.dnv.com

tHIS IS DNVDNV is a global provider of services for managing risk, helping customers to safely and responsibly improve their business performance. Our core competence is to identify. assess and advise on risk management. DNV is an independent foundation with presence in more than 100 countries.

© Det Norske Veritas aS. Design: Coor Service management/Graphic Services 1104-043. Print: 07 Oslo aS xxx/2011. Frontcover: ©Seadrill

Improvesystem

performance

the power

to