Since many different - very complicated - steps are required for electronics development, we would like to explain the project planning process in the area of electronic prototypes in a simplified manner. The basis of every development is the specification book. The specification book contains the planned requirements for the design. Frequently, the specifications are also part of the contracts, so it must be ensured that the specifications are complete and correct.
During the development phase, the areas of electronics, mechanics, hardware and software work together, and the respective work is divided into two large areas: the circuit diagram or schematic and the PCB layout. The circuit diagram and schematic usually represent all electrical connections.
Here, the individual components listed in the circuit diagrams are usually represented with simplified symbols, but the ways in which they are represented can differ. It is interesting to know that the PCB layout and the circuit diagram are often created by different people. Therefore, studying the data sheet during the development phase is not only a great advantage, but also an existential necessity. The enclosures are then usually created using CAD software for dimensional drawings and 3D models. Based on these drawings and additional information, production can then begin.
Sometimes 3D printers come into play here, with which a prototype can be printed in advance to avoid mistakes. Because sometimes incorrectness is overlooked on the screen. The requirements specification, another important part of electronics development, is drawn up during the development phase. All important points of the development phase and how they were implemented are recorded here.
The requirements specification can be compared to the specification sheet, but here usually more details are noted, so that it clearly exceeds the scope of the specification sheet. Finally, everything that was part of the project planning is recorded in the requirements specification. For example: technical details, circuit diagrams, PCB layouts and CAD drawings. This means that not only the "what" of the implementation is important, but also the "how" of the implementation. The requirements specification, like the specifications, is therefore a very important part of the development phase.
Because it must be possible to trace at any time what was changed when and also by whom during the development time.