Lessons Learned in Projects:

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.

A new or modified safety-critical electronic product must be designed and manufactured in such a way that technical product defects that could endanger life and limb or violate legal regulations are excluded. Other product defects with less drastic consequences must be sufficiently improbable. This article describes how product design and manufacturing can be optimized to best avoid these types of product defects.

Configuration and calibration parameters exist not only in the software, but also at all system and hardware levels. We recommend identifying all parameters as such by their parameter names and specifying them in one or a few central parameter documents. Learn more about how you can use these and other measures to ensure consistent and correct parameterization throughout your product development project.

Which work products need to be created on the left side of the V-Model depends on the system architecture. Learn here which work products are essential to meet the quality standards underlying the V-Model.

System analyses, i.e. complexity, safety and security analyses, should be performed as early as possible in the product design process. However, certain prerequisites must be fulfilled before these analyses can be performed. Find out here what these prerequisites are.

Bidirectional traceability of requirements, design decisions and test case specifications in the V-model is required by standards on functional safety. With the help of the autoConform® methodology and software, this traceability can be established in a largely automated manner. Read more about how it works.

A good system or software design has a low structural complexity. In order to be able to evaluate the structural complexity of a given system or software design, the structural complexity must be measurable. Find out here how structural complexity can be measured.

Delays in development projects usually have one of three causes. Find out here what these causes are, how you can identify them and minimize the associated risks.

Once the technical requirements for the product and its elements have been created, the status of the requirement verifications can be used to determine whether the product is ready for the market. Find out here what you need to consider to make this method work.

Safety analyses are typically created manually, are time-consuming and, for reasons of manageability, do not examine the product in every detail. Find out here how comprehensive safety analyses can be created with minimal effort.

The creation of safety analyses in a product development project is required by standards. Find out more about when the best time is for which safety analysis in development projects.

Technical documents that are created semi-automatically and are intended to be complete are often very extensive. Find out more about how you can organize the review and approval of these documents in a time- and cost-saving manner.

It is a challenge to create all the documents needed during product development in a complete and consistent manner. Find out how to overcome this challenge here.

The keys to success are “model-based development” and “semi-automatic creation of all safety analyses and development-related documents”. Find out here what is crucial about these two keys.

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.

The sequence of works to be done and their documentation are defined at the beginning of a product development project. Find out here how to set up a development project so that the number of development loops is minimized.