Project Scoping
Before starting any project at NER we must determine the scope, constraints, timeline and otherwise the overall definition of the project. This is typically completed by leadership such as the chief engineer, system head, and potential project leads. A project at a high level (general function, budget, timeline) will be defined in FinishLine, and the details regarding actual electrical I/O level decisions may be elaborated on in further meetings and documented in Confluence.
Project Creation
Actually creating the project in Altium Designer to be shared via 365! This is typically done by the project lead and only requires coming up with a project name and filling in some basic parameters.
Details on this can be found here: {link to schematics page, subsection for project creation}
Schematic Design
Design of the actual electronics circuits. This encompasses picking components, digging into their datasheets to learn how to implement them, completing the wiring required, and even simulating when necessary to validate behavior. Critical setup and organization of the schematics should be done by the project lead, and then sub-circuits can be more easily divided between any available team members. Schematics should follow the Vault Guidelines
Details on this can be found here: Schematic Capture
We’ve recently changed that component build-out will not be required until the layout stage rather than during schematic design. For schematics “Draft” components are okay!
Asynchronous Schematic Review
Review of the electrical design of the system. This review will be completed by everyone on the team who can contribute their time! Contents should be the electrical design itself, component choices (function as well as cost and solderability), and general schematic cleanliness & organization.
Details on this can be found here: {link to schematic review checklist}
Component Build-out
{}
PCB Layout Design
Designing the way components and copper are placed on the board. Similar to the schematic design, the project lead will be responsible for critical actions, such as importing the schematics, and organization of efforts across the project team. All members should be able to participate in layout, but it can vary depending on board size and timeline demands. Layouts should follow the Vault Guidelines
Details on this can be found here: PCB Layout (Matt Edition)
Component Review
{}