Verification & validation systematics

Engineering departments are under continuous pressure to develop and produce technologically complex products quickly, flexibly, adaptably and cost-effectively. To provide proof of the required performance and the corresponding quality, all product design requirements must be tested and subsequently documented. Since development work is increasingly globalised and also interdisciplinary (interaction of mechanics, electronics, software), transparent, uniform testing systems are becoming increasingly important. Only then can the following challenges be overcome:

1. Shorter development cycles due to cost and time pressure
2. Lack of a testing forecast for detailed and cost-efficient planning
3. Lack of KPI systems for targeted control of testing and, if necessary, initiation of countermeasures
4. Decreasing efficiency due to the liaison between international development sites
5. Increasing product complexity with stagnating scaling of knowledge
6. Unclear testing objectives and impact of technical changes
7. Proof and documentation of product compliance

The newboxes product verification and validation approach addresses these challenges in the overall context of systems engineering.

‍

Our approach

The newboxes approach is based on the use of systems engineering and the V-model. These include the methodological and procedural framework from requirements management to system verification and validation.  

We define with you all necessary tests and their verification and ensure the progress monitoring and documentation of all verification and validation activities (V&V) within the testing of products. This is based, among other things, on the DVP&R (Design Verification Plan and Report) methodology.

Our approach consists of a generic master level and a specific project level. On the one hand, these describe the safeguarding of specific products within development projects. On the other, they structure, manage and scale the knowledge generated in projects. By combining the two, the full potential of our approach unfolds. Your R&D processes receive an enormous boost in efficiency.    

‍

‍

Specific product development (project)

During scoping, the system to be tested is mapped in the form of a product structure. In the case of application developments, this ranges from individual functions and components to be tested to overall system testing for new product developments. Based on this and the project timeline, the responsible employees for the testing are determined.

The "DVP definition" covers the inclusion of the necessary test standards:

• Which characteristic and/or function must be safeguarded at which level of the system structure to meet which requirements?
• What acceptance criteria must be met for a successful test?  
• How will the testing be conducted?  

In addition, the time by which a test must be completed (e.g. quality gate) is specified.

In the Test Planning phase, a precise timeline and the necessary resources, including test benches, are defined for conducting the complete testing program. Redundancies are identified and minimised during planning, which significantly increases test efficiency.

Next, the implementation and tracking of the previously planned tests take place.  Our approach makes it possible to see at any time how far advanced the testing is and thereby the level of product maturity. Both are automatically processed in the form of a KPI monitoring system and a corresponding reporting system is derived. Changes and deviations from the planned scope of testing and their reasons are documented. This provides the project leaders and management with full transparency regarding potential cost increases or delays and thereby provides proactive control of the overall verification.

Following execution, evaluation and documentation of all tests, the experts and responsible employees (e.g. component, module or system responsible) release the system elements and functions from the development point of view in the "DVP&R Release" phase by means of a standardised release process – first the individual components as well as subsystems and finally the entire product.

‍

Generic knowledge (Master)

The generic part of the verification and validation systematics is composed of the following elements:

1. Generic / Master product structure
2. Master tests (DVPs) to describe what needs to be tested.
3. Test standards describing the uniform execution of the tests – the "how".

The structured, documented know-how is based on the previous experience of experts as well as from development projects, robust design analyses, audits and quality findings from the field and production. This makes it clear to all employees involved which tests are mandatory for certain components, modules or (sub-) systems and how the testing should be conducted.  

Every project undertaken adds new knowledge, enabling the generic knowledge to be updated and scaled.

‍

Interaction of both worlds

In order to unleash the full potential of the knowledge documented in the Master World in your organisation and in the development projects, this is very closely interlinked with project-specific testing. At the start of a project, the specific product structure for the project is derived from the generic master, and with it the associated tests and test standards. Immediate evaluation of the generic scope required specifically for the project as well as the addition of further DVP content allows the generation of an almost complete picture of the testing scope and program at an early stage.

In the planning and implementation of the tests, the findings in the test standards stored in the master can be used with regard to exact test execution and duration. This makes it easier to avoid errors and failures that have already occurred in the past, results are comparable across projects and products, and time estimates are more consistent.

‍

Our Solutions

Set course for complete verification and validation of your products within systems engineering with newboxes. Our processes, methods and tools help you with the following tasks:

• Introduction of a verification and validation systematic for new product developments
• Standardisation of verification and validation systematics, e.g. mechanics, electronics and software, from different business units and locations as well as in the context of cooperations
• Establishment of knowledge management in the V&V department
• Task force to resolve testing roadblocks  
• Digitisation of testing processes and documentation
• Introduction of a KPI system to visualise the progress  
• Documentation and proof for authorities and customers (e.g. homologation)
• Fulfilment of product compliance