Hardware requirements start at the system level and provide hardware architectural details that begin to shape the answers to how the solution will work. It starts with a decomposition of system level requirements into hardware and software implementable requirements. The hardware requirements provide structure to tangible real-world interfaces and action. These are the high-level questions Pi uses to drive a hardware requirements session:
• What are the system interfaces of the hardware element?
• How does the hardware element control other elements on the system level?
• What are the intended operating conditions (temperature, vibration, voltage ranges, etc.)?
Proof of Concept Development
In most projects, a proof of concept is valuable to confirm that a new design is effective. This type of rapid, informal prototyping often reveals the most important considerations and sensitivities of a new design. Pi creates proof of concept hardware and software that can be tested in a prototype vehicle, or with prototype bench test environments, in order to preview the capability and performance of the new design. Pi’s internal use of the our existing OpenECU hardware and software designs greatly accelerates this prototyping stage.