[et_pb_section fb_built=\u201d1\u2033 admin_label=\u201dsection\u201d _builder_version=\u201d4.16\u2033 custom_padding=\u201d40px|||||\u201d da_disable_devices="off|off|off" global_colors_info="{}" theme_builder_area="post_content" da_is_popup="off" da_exit_intent="off" da_has_close="on" da_alt_close="off" da_dark_close="off" da_not_modal="on" da_is_singular="off" da_with_loader=\u201doff\u201d da_has_shadow=\u201don\u201d][et_pb_row admin_label=\u201drow\u201d _builder_version=\u201d4.16\u2033 background_size=\u201dinitial\u201d background_position=\u201dtop_left\u201d background_repeat=\u201drepeat\u201d 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="{}" custom_padding__hover="|||" theme_builder_area=\u201dpost_content\u201d][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 custom_padding=\u201d||0px|||\u201d global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
Functional safety standards require the development of a safety-critical product to be done according to the V-model of system development. Fig. 1 shows this V-model in the form that underlies the autoConform\u00ae methodology and software.<\/p>\n
[\/et_pb_text][et_pb_image src=\u201chttps:\/\/autoconformance.com\/wp-content\/uploads\/2025\/04\/V-Modell.png\u201c title_text=\u201cV-Modell\u201c _builder_version=\u201c4.27.3\u2033 _module_preset=\u201cdefault\u201c global_colors_info=\u201c{}\u201c theme_builder_area=\u201dpost_content\u201d][\/et_pb_image][et_pb_text _builder_version=\u201d4.27.3\u2033 _module_preset=\u201ddefault\u201d custom_padding=\u201d||0px|||\u201d global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
Fig. 1: System development V-model of the autoConform\u00ae methodology and software<\/p>\n
<\/p>\n
This article is about how the content and the order of the work products (i.e. the documents) of the V-model can be defined in such a way that an iteration-free creation of all work products is possible.<\/p>\n
An iteration-free V-model workflow has two decisive advantages.<\/p>\n
In other words:<\/p>\n
is much easier to carry out if the work products documenting the product development follow an iteration-free V-model.<\/p>\n
Section 2 describes the iteration-free V-model workflow. Section 3 summarizes the prerequisites for an iteration-free V-model workflow.<\/p>\n
The iteration-free V-model process is shown in Fig. 2.<\/p>\n
[\/et_pb_text][et_pb_image src=\u201chttps:\/\/autoconformance.com\/wp-content\/uploads\/2025\/04\/Iteration-free-V-model-workflow-scaled.png\u201d title_text=\u201cIteration-free V-model workflow\u201d show_in_lightbox=\u201con\u201d _builder_version=\u201c4.27.3\u2033 _module_preset=\u201ddefault\u201d global_colors_info=\u201d{}\u201d theme_builder_area=\u201dpost_content\u201d][\/et_pb_image][et_pb_text _builder_version=\u201d4.27.3\u2033 _module_preset=\u201ddefault\u201d custom_padding=\u201d3px|||||\u201d global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
Fig. 2: Iteration-free V-model workflow<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=\u201c4.27.3\u2033 _module_preset=\u201cdefault\u201d custom_margin=\u201c||-32px|||\u201c global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
\u00a0Fig. 2 shows the V-model process for a product whose product architecture consists of<\/p>\n
Fig. 2 thus shows that there can basically be any number of system, hardware and software levels in a product architecture. At its simplest, the product architecture of an electronic product with embedded software contains only one E\/E hardware level and two software levels (namely, the level of the entire software and one software detailed design level). All other system, hardware and software levels may exist, but don\u2018t have to exist.<\/p>\n
In Fig. 2, the V-model workflow is indicated by green arrows. The workflow begins in the upper-left corner at the work products \"Item Definition\" and \"External System Interface Specification\". These two work products are closely related to each other and should be created together.<\/p>\n
The same applies to the safety analyses \"(A)SIL allocation\", \"FTA\", \"DFMEA\" and \"DFA\" at each product architecture level and the safety requirements created from these analyses: these work products are also closely related to each other and should therefore be created together.<\/p>\n
In Fig. 2, there are bidirectional arrows only between<\/p>\n
These bidirectional arrows indicate that,<\/p>\n
It cannot be concluded from Fig. 2 that the iteration-free V-model workflow is uniquely defined. For instance, it is (theoretically) possible to first edit the leftmost block column (design and interface specifications) in Fig. 2 from top to bottom, subsequently the second block column from the left (safety analyses) from top to bottom, then the third block column (requirements) from top to bottom, and finally the fourth block column (test specifications).<\/p>\n
However, the usual and most practical workflow is from left to right, level by level, starting at the top level.<\/p>\n
<\/p>\n
[\/et_pb_text][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 custom_padding=\u201d0px||0px|||\u201d global_colors_info="{}" theme_builder_area="post_content"]<\/p>\n
An iteration-free V-model can be applied whenever all requirement, design, and test specifications can be related to a hierarchical product architecture in which all physical hardware and software elements and their respective functions have been defined by top-down decomposition.<\/p>\n
In addition, the expected content of each V-model work product must be defined such that it presupposes only content contained or defined in one of the upstream work products.<\/p>\n
The work product templates of the autoConform\u00ae methodology and software are designed to meet both of these requirements. Making the V-model workflow iteration-free is key for speeding up the product development process significantly.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>","protected":false},"excerpt":{"rendered":"
The iteration-free V-Model process is one of the essential keys to significantly accelerating the product development process. Learn how to define such an iteration-free process and what the prerequisites are.<\/p>","protected":false},"author":2,"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-1809","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemein"],"yoast_head":"\n