[et_pb_section fb_built=\u201d1\u2033 admin_label=\u201dsection\u201d _builder_version=\u201d4.16\u2033 custom_padding=\u201d40px|||||\u201d da_disable_devices=\u201doff|off|off\u201d global_colors_info=\u201d{}\u201d theme_builder_area=\u201dpost_content\u201d da_is_popup=\u201d off\u201d da_exit_intent=\u201doff\u201d da_has_close=\u201don\u201d da_alt_close=\u201doff\u201d da_dark_close=\u201doff\u201d da_not_modal=\u201don\u201d da_is_singular=\u201doff\u201d da_with_loader=\u201doff\u201d da_has_shadow=\u201don\u201d][et_pb_row admin_label=\u201drow\u201d _builder_version=\u201d4.16\u2033 background_size= \u201cinitial\u201d background_position=\u201ctop_left\u201d background_repeat="repeat" custom_padding=\u201d3px||3px|||\u201d global_colors_info=\u201d{}\u201d theme_builder_area=\u201dpost_content\u201d][et_pb_column type=\u201d4_4\u2033 _builder_version=\u201d4.16\u2033 custom_padding=\u201d|||\u201d global_colors_info=\u201d{}\u201d custom_padding__hover= \u201c|||\u201c theme_builder_area="post_content"][et_pb_text admin_label="Text" _builder_version="4.27.3\u2033 background_size="initial" background_position="top_left" background_repeat="repeat" global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
The generation of technical requirements is a central part of every product development project. Especially for safety-critical products, this process must be correct and precise. To this end, a hierarchical approach<\/strong> is taken: at the very beginning, the product is subdivided into product architecture levels<\/strong> Subsequently, design specifications, safety analyses, technical requirements and test specifications are created for each level.<\/p>\n The outcomes of Safety analyses<\/strong> are safety classifications and requirements for safety mechanisms. The latter requirements are incorporated directly into the technical requirements specification of the respective product architecture level. However, many other technical requirements still need to be derived. This is explained in detail in Section 2. Section 3 highlights the advantages of the requirements generation procedure described in this article.<\/p>\n The design specification<\/strong> a product architecture level contains the following information:<\/p>\n The specification of effect chains is carried out by so-called "generalized signals"<\/strong>, which represent the transfer of information, material or energy between elements. These signals can be either intended<\/strong> and unintended<\/strong> with the latter being known as \u201cdisturbances.\u201d<\/p>\n Based on the design specification, requirements are generated using a basic set of requirement templates or boilerplates.<\/strong> An example:<\/p>\n IF EXTERNALLY input_signal_name<\/em> expected_signal_behaviour<\/em>,<\/p>\n THEN THE element_name<\/em> SHALL ENSURE THAT output_signal_name<\/em> expected_signal_behaviour<\/em>.<\/p>\n<\/blockquote>\n These templates can be expanded and adapted to customer needs. Four classes of requirements can be generated for the system to be developed and all its system, hardware and software elements:<\/p>\n [\/et_pb_text][et_pb_image src=\u201dhttps:\/\/autoconformance.com\/wp-content\/uploads\/2024\/11\/automated-conformance-tipps.jpg\u201d title_text=\u201dautomated-conformance-tipps\u201d show_in_lightbox=\u201don\u201d _builder_version =\u201c4.27.3\u2033 _module_preset=\u201cdefault\u201c global_colors_info=\u201d{}\u201d theme_builder_area=\u201dpost_content\u201d][\/et_pb_image][et_pb_text admin_label=\u201dText\u201d _builder_version=\u201d4.27.3\u2033 background_size=\u201dinitial\u201d background_position=\u201dtop_left\u201d background_repeat=\u201drepeat\u201d global_colors_info=\u201d{} \u201c theme_builder_area=\u201dpost_content\u201d]<\/p>\n The benefits of automated requirement generation are impressive:<\/p>\n The partially automated generation of technical requirements not only saves time, but also significantly improves the quality of the requirements documents. With this methodology, requirements are created in a complete, testable and consistent manner across all product architecture levels - an indispensable basis for the successful development of safety-critical products.<\/p>\n [\/et_pb_text][et_pb_image src=\u201dhttps:\/\/autoconformance.com\/wp-content\/uploads\/2024\/11\/developer-team-software.jpg\u201d title_text=\u201ddeveloper-team-software\u201d show_in_lightbox=\u201don\u201d _builder_version =\u201c4.27.3\u2033 _module_preset=\u201cdefault\u201d global_colors_info=\u201c{}\u201c theme_builder_area=\u201cpost_content\u201d][\/et_pb_image][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>","protected":false},"excerpt":{"rendered":" Do you still write the technical requirements by hand, or do you have them generated semi-automatically? Find out here how technical requirements for the product and its elements can be generated semi-automatically.<\/p>","protected":false},"author":1,"featured_media":964,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"\r\n Willkommen bei WordPress. Dies ist dein erster Beitrag. Bearbeite oder l\u00f6sche ihn und beginne mit dem Schreiben!<\/p>\r\n","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-776","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemein"],"yoast_head":"\n2. Semi-automatic generation of technical requirements<\/h2>\n
\n
Example of intended and unintended signals<\/h3>\n
\n
\n
\n
3. Benefits of semi-automated requirement generation<\/h2>\n
\n
4. Summary<\/h2>\n