Today more than ever, companies are forced to make their products better, faster and more cost-effective, with products all the while becoming ever more complex due to an increase in interdisciplinary challenges.

The systems engineering approaches are used for the market-oriented development of complex technical systems on time and within budget while incorporating the necessary roles and disciplines.

The engineering processes therefore have a particularly high influence on added value in a company.

Concepts (Drafting/Selection)

The development of a technical system usually begins with a concept phase in which the system to be developed is defined in general terms and the basic aims behind the system are determined. Usually, several alternatives for a possible system are developed and discussed before the alternative with the greatest chance of success is chosen.

INVENSITY assists you in this area with methods for systematically generating ideas.

Requirements Engineering

After a project has been commissioned, you begin with compiling the requirements that describe the system and which will enable the system to be implemented during the next step. Requirements engineering is a step-by-step process. The individual process steps - collecting & analyzing, structuring & refining, agreement, verifying and evaluating requirements - can be repeated in several iteration steps within this process.

Thanks to its consultants’ many years of experience in requirements management, INVENSITY can evaluate existing standards, highlight potential for improvement and assist in the implementation of (partially) automated solutions based on existing tools. The development of a holistic concept to manage requirements and the creation of transparency and traceability are significant aspects for INVENSITY in this regard.

Specification

The requirements drawn up are documented at different levels of detail (according to the V-Model, e.g. system level, segment level, component level, module level), and are thus continuously refined.

Architecture Design

The draft of an architecture helps to distribute functions to sub-systems and define the interfaces.

Architecture therefore divides a system into sub-systems where the functions are assigned to the components. The communication interfaces are also defined and described. In this way, the architecture describes how the whole system is constructed.

We are happy to offer our help thanks to the varied experience of the INVENSITY consultants in drafting architectures for a wide range of systems.

Implementation

Implementation aids the realization of the system elements defined by the architecture and their interfaces. The various sub-systems must be realized in each case, i.e. the functions and interfaces specified by the architecture must be implemented.

The latter does not necessarily mean implementation in terms of software, as electrical, mechanical or wholly different systems must also be implemented.

Integration

Integration serves to bring together the individual parts and to bring the whole system into operation.

Verification and Validation

Verification is used to check whether the requirements collected have been correctly implemented, i.e. whether the result of development corresponds to the requirements. In doing so, all functional requirements must be verified, which takes place on various levels of the system.

Validation, in contrast, is the documented demonstration that a system fulfils the requirements in practical terms. In practice, validation is often carried out as multi-level testing, beginning with, for example, road-testing through to the long-term test in an actual application environment.
Validation is used to check whether the right thing has been done.
Verification serves to check that the specified tasks have indeed been implemented according to the specification.