1. Problem Tracking: A closed-loop tracking systemmust be deployed

1. Software Safety Planning: The safety plan outlines therequired components to deliver a safe product and thesafety assessment has to be performed for each softwareacquisition, development, and maintenance activity.2. Personnel Training: The safety plan must incorporatethe required training and qualifications each personnelmust have to work with a certain component of the system.

3. Resources: Which resources are allocated to whichsoftware safety tasks must be specified in process planningdocuments.4. Software Life Cycles: Software safety has to be performedthrough all the phases of the development lifecycleeven after the system is operational.5. Documentation Requirements: The documentationmust include safety plan, project management plan, configurationmanagement plan, quality assurance plan, requirementsspecification, design documentation, verificationand validation plan, safety analysis reports andmaintenance plan.6.

Best services for writing your paper according to Trustpilot

Premium Partner
From $18.00 per page
4,8 / 5
4,80
Writers Experience
4,80
Delivery
4,90
Support
4,70
Price
Recommended Service
From $13.90 per page
4,6 / 5
4,70
Writers Experience
4,70
Delivery
4,60
Support
4,60
Price
From $20.00 per page
4,5 / 5
4,80
Writers Experience
4,50
Delivery
4,40
Support
4,10
Price
* All Partners were chosen among 50+ writing services by our Customer Satisfaction Team

Traceability: Tracing system must incorporate a link tosystem-level hazard tracking system so that it becomeseasier to monitor the risky states of the system.7. Problem Tracking: A closed-loop tracking systemmust be deployed for tracking failures which will belinked to system-level hazard tracking system so that itcan be ensured that a minor error does not lead to systemcollapse.8. Configuration Management Acivities: A configuration management system must include all the designcode, simulators, test plan, procedures etc. to providea strict control over configuration changes. Any configurationchanges made must be in alignment with systemsafety criteria set in place.

9. Software Assurance Activities: Acceptance of anysystem-level hazards related to software must be dependenton the successful conclusion of all assurance activitieslinked to its associated software safety requirements.10.

COTS Software Components: COTS componentsmust undergo safety analysis and their interaction withthe rest of the system must be evaluated at a system levelas well.11. Certification Process: An official certification processhas to be established in which mission assurance softwaresafety personnel participate. They cumulativelyevaluate the hazards, mitigations, requirement fulfillment,verifications and validations performed in the system8.