search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
5.10 Software Integrity


5.10.1 Functional Objective. For any activity that relies on the integrated use of equipment or sub-systems that include software, the risks associated with software and its integration into the equipment or sub-system are properly managed and that the software is safe to use. A failure or unspecified behaviour of the software shall not result in:


n an event that escalates to a hazard; or n impairment of the mitigation of a hazard; and n impairment of recovery from a hazard.


5.10.2 Performance Requirements. The way software could be a stimulus event to a hazard, or impair the mitigation of a hazard, or impair recovery following such a hazardous event, shall be communicated to the appropriate parties.


5.10.3 The production of software shall be managed so that the safety risks arising from the software production are reduced to an acceptable level.


5.10.4 Provision shall be made to protect systems against:


n intentional or unintentional viruses or unauthorised code; n unauthorised installation, change, or deletion of software or associated data; n the installation or use of unauthorised software, (e.g. running games or office applications); n modification of the software function by additional or modified physical devices.


5.10.5 The system safety justification shall be developed to include the risks posed by the use of software and how those risks are reduced to an acceptable level. Any function of a MASS should be adequately validated in accordance with its consequence to safety and performance of the MASS, and any software implementation of this function adequately verified.


5.10.6 The configuration status of the software on each platform shall be captured and recorded, and the record main- tained up-to-date for the life of the platform.


5.10.7 The development and testing of changes to the software and data, including specific arrangements for on-board testing, shall be managed so that the safety of the system, sub-system or equipment is not compromised.


5.10.8 The retention and release of earlier versions of software shall be managed to enable restoration of a previous known and trusted state when necessary.


5.10.9 The release and installation of software to each platform shall be appropriately and actively managed so that changes to software are controlled. The installation process shall include a strategy for managing a failed installation.


5.11 In-service Requirements


5.11.1 Independent verification should be undertaken to provide assurance that the MASS complies in all respects with the provisions of this Code and remains compliant throughout its life.


Maritime Autonomous Surface Ships up to and including 24 metres in length


25


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84