Hazard management method based on database model

Abstract

The invention provides a hazard management method based on a database model. The hazard management method comprises the following steps: performing domain analysis on a conceptual model of a hazard log, establishing a hazard management model, establishing a database according to the hazard management model, importing data into the database to form entries for management, and automatically checking whether the data accords with database constraints in the importing process; calculating an entry state, a change state and a confirmation state of each piece of imported data, and performing multi-state management; carrying out hazard management on imported data, confirming closing of conformity items, adding evidence to non-conformity items to complete closing, carrying out automatic management on states of all items, and automatically completing hazard change influence analysis on the non-conformity items; and for the hazard and mitigation measures which cannot be closed, associating with the SRAC, and checking the source and integrity of the SRAC. According to the method, informatization management of the hazard logs can be realized through constraint of a database model and card control on software, and the efficiency and quality of hazard management are improved.

Description

technical field [0001] The invention relates to the field of safety critical systems, in particular to a hazard management method based on a database model. Background technique [0002] The domain of safety-critical systems refers to systems whose failure may result in loss of personal safety, loss of important property, or damage to the environment. Safety-critical systems involve many fields such as aerospace, rail transit, nuclear power, and chemical industry. According to the technical requirements of relevant standards in the field of safety-critical systems, the use of hazard logging technology is highly recommended. The hazard log needs to fully record the hazards identified during the entire life cycle of the system, the risk assessment level, and the mitigation measures for the hazards, and maintain and manage the entire life cycle. When the system, subsystem or component changes, the hazard log shall be updated and maintained synchronously. To ensure that all s...

AI Technical Summary

Problems solved by technology

However, its support for importing external items is poor, and the import format is single

The system cannot well support the operation of importing hazard analysis results from other tools

[0010] 2. It is impossible to establish a hazard management model intuitively

However, according to the design principles of requirements management tools, items can be arbitrarily associated in the tool, which cannot reflect the relationship between hazards and sub-hazards, hazards and mitigation measures, and cannot intuitively reflect the composition and status of hazards

[0013] 3. There are shortcomings in version management and change impact management

When the system is relatively large and the functions are relatively complex, a large amount of work will be added to trace the impact of hazards

[0016] 4. Lack of application rule management of hazard logs

[0018] Although the state management of the requirements management tool is an enumerated variable, there is no closed logic card control between multiple levels. When the mitigation measures for the hazard are not closed / output, the hazard can be closed at will, resulting in insufficient risk control.

Images