SysML Safety Requirements Modeling for Faster Tailoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The arcane language of safety requirements and safety specific expressions hinder comprehension and collaboration between safety and design engineers, leading to delays and inefficiencies in system development, and existing methods for specifying generic safety requirements are time-consuming and costly.
Innovation Solution
A model-based approach using Systems Modeling Language (SysML) to integrate generic safety requirements, including a custom stereotype and safety extension generalization, enabling concise, complete, and non-ambiguous requirements representation and facilitating collaboration through a model-based glossary and reports.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional document-based methods (PDF, Word, Excel) are used to specify generic safety requirements, then comprehensive safety coverage can be achieved, but the process becomes time-consuming and costly due to manual searching, copying, and adjudication
Solution Approach 1:
The patent replaces manual mechanical processes (searching PDF/Word files, copying to Excel, manual adjudication meetings) with an automated model-based system. The SysML model automatically searches for applicable generic safety requirements, extracts them, and presents them for review, eliminating the time-consuming manual document handling while maintaining comprehensive safety coverage
Solution Approach 2:
The patent creates a digital model copy of safety requirements within the SysML environment rather than working with physical or traditional digital documents. This model-based copy allows automated processing, validation, and integration with system design models, reducing the need for repetitive manual copying and adjudication
2Manufacturing precision
If safety engineers use arcane safety-specific language and expressions, then precise safety requirements can be defined, but design engineers find it difficult to comprehend, leading to adjudication delays
Solution Approach 1:
The patent introduces a model-based glossary as an intermediary between safety engineers and design engineers. The glossary provides standardized definitions and contextual explanations of safety terms within the SysML model, allowing design engineers to comprehend safety requirements without losing precision. The model itself acts as a mediator by structuring requirements in a way that is both technically precise and accessible
Solution Approach 2:
The SysML model serves multiple functions simultaneously: it maintains precise safety definitions for safety engineers while providing contextualized, comprehensible representations for design engineers. The model-based approach unifies the communication medium, allowing both groups to work from the same structured representation rather than translating between different document formats and languages
3Reliability
If a blanket approach is used to apply all generic safety requirements to all systems, then comprehensive safety coverage is ensured, but cost increases due to applying unnecessary requirements to systems of varying size, shape, use, and complexity
Solution Approach 1:
The patent applies local quality by tailoring safety requirements to specific system characteristics. The SysML model enables selective application of generic safety requirements based on the particular system's size, shape, use, and complexity. Each system receives only the safety requirements relevant to its specific context, maintaining comprehensive coverage where needed while avoiding unnecessary requirements elsewhere
Solution Approach 2:
The patent introduces dynamics by making the safety requirement application process adaptive rather than static. The model-based system can dynamically determine which generic safety requirements apply to each specific system configuration, allowing the safety approach to flex and adapt to varying system characteristics rather than applying a rigid blanket approach
Data Source
AI summary
A method for analyzing system safety requirements. The method includes parsing a plurality system and/or software specific requirements, and filtering the plurality system and/or software specific requirements using a generic system safety requirements (GSSR) model to generate a matched generic safety requirement in pre-set tables.