Rapid prototyping of embedded hardware/software systems

Prototyping of embedded hardware/software systems is increasingly important because the difference in the product relies mainly on the variations of software and system features. Nonfunctional and software requirements must be explored together with the user. It is important to integrate the user into the specification process because more and more customers expect solutions and services tailored exactly to their needs. Therefore, the consumer must be integrated in the process of definition and evaluation of soft and working prototypes. Modern techniques such as conjoint analysis and quality function deployment (QFD). must be used for data analysis as base for data-interpretation. Most important to the user is the overall performance of the system. Often the true performance of an embedded hardware/software system cannot be observed or determined by simulation or even emulation. Since the subsystem is hidden and can not be tested in isolation, a working prototype must be built to determine bottlenecks and to validate the design either directly or through the analysis of recorded data. System prototyping of embedded subsystems in the target environment has many advantages. Especially the technique of design interpretation in which a special prototyper that records all input/output actions at runtime is most useful. Recorded data can later be used to analyze the system behavior under test and operating conditions. Critical sequences can be used for fine-tuning and debugging the system.