Changes

It will be described with the help of an example that represents a typical scenario: the company needs to interact with an external partner such as an outsourcee to carry out a design. The DAVE R&D team sits at the heart of the system. Let's say that one of its members, Bob, starts the new design according to the product's requirements. He takes care of part of the schematics and sets up the PCB project by choosing the number of layers, manufacturing technologies, dimensions, etc.

At first, Bob saves the project files on a local storage device that is part on the DAVE's internal IT infrastructure. Later on, he needs to share the project with Mallory, an external contractor located in the UK who helps Bob to speed up the design. The project is shared through Altium 365. Upon starting to work on the project, Mallory receives a snapshot of the DAVE database library (DBL) as well. If necessary, this snapshot allows him to instantiate additional components in the project by picking them up from the DBL. What if Mallory needs to instantiate a component that is not available in the DBL, however? Within the project, he creates an ''[https://www.altium.com/documentation/altium-designer/building-maintaining-components-libraries-overview integrated library]'' in which the new component is temporarily stored. At this stage, the new component is not yet fully qualified, but this does not prevent Mallory from continuing with his task. Although component's fields such as ''DAVE code'' and ''manufacturer'' are still not populated, the component is totally usable: as long as Mallory has designed its schematic symbol and PCB footprint according to DAVE Embedded Systems requirements, he can proceed with no worries.

Periodically, Mallory pushes the modifications to the repository on the 365 platform. On DAVE side, Bob does the same so that they can keep synchronized each other. If Mallory put puts new components in into the project's integrated library, a member of the DAVE R&D team , let's say Alice, takes care of completing their definition/qualification processusing schematic/PCB symbols created by Mallory as starting point. After this step, the new components will end up to be available * in the DAVE ERP database* in the DAVE master database library. Interestingly, TBDupdating the ERP database and the master database library is a process '''that leverages the same tools DAVE Embedded Systems adopted several years ago for the software development/maintenance''': [https://gitlab.com/ GitLab] along with its [https://docs.gitlab.com/ee/ci/ CI/CD module].