Notes
Slide Show
Outline
1
The Engineering Process at CEPD
  • Updated 11/30/2007
2
Project Quality Plan
  • Initial Research
  • Project Requirements Review
  • Develop a Proposal
  • Project Definition
  • System and/or Subsystem Architecture
  • Design Phases
  • Unit Test
  • Integration and Verification Test
  • Release and Approval
  • Other Deliverables
3
Initial Research
  • Feasibility of concept is determined.
  • Appropriate and available or potential technologies are identified.
  • Necessary tools are identified.
    • Software packages and compilers.
    • Test equipment.
4
Project Requirements Review
  • Review for thoroughness:
    • Electrical characteristics.
    • Mechanical characteristics/packaging.
    • Environmental limits.
    • User interface/control.
    • Communications protocols, both internal and external to the product.
    • Regulatory compliance (FCC, CE, RoHS, UL).
5
Develop a Proposal
  • Initial Materials costs and the necessary development tools are researched.
  • Deliverables are itemized.
  • A task list is created.
  • Labor time/cost is estimated and a preliminary schedule is created.
  • The proposal is written by an Engineer.
  • Proposal is reviewed by a CEPD owner before release to a potential client.
    • If the client accepts the proposal, a PO must be received before work begins.
6
Project Definition
  • The requirements must be determined before the system and/or subsystem architecture is completed.
  • Applicable industry standards are referenced.
  • Electrical designs:
    • interfaces timing, environmental, etc. requirements are specified.
  • Software designs:
    • MIPS, memory, interrupts and desired peripherals, etc., are specified.
  • Layout:
    • Includes the expected number of layers, critical routing, critical component and connector placement, physical dimensions of chassis or board, etc.
7
 System and/or Subsystem Architecture
  • This step has as its output any block diagrams, state machine diagrams, data flow diagrams, bubble diagrams and detailed subsystem interfaces and protocols necessary to begin the detailed design.
  • At this point, the preliminary design review occurs with the client, covering the requirements and architecture.
8
Design Phase 1:
Electronics and Software
  • Software and Firmware Design:
    • Coding, compiling, and linking.
  • Electrical/Electronic Design:
    • Acquiring datasheets, creating HDL code and/or schematics, netlist and BOM, specifying board outline, controlled impedance traces, guarded areas, trace widths, test points and critical component placement, wiring harness designs and connector selection.
  • For all aspects of electronic and software design:
    • Design and rules checking occurs.
    • Errors and warning messages are eliminated.
    • Critical section verification including simulation or test occurs at this time.
    • A theory of operation is written.
    • A detailed design review occurs when this phase is completed.
9
Design Phase 2: The Layout process
  • The layout process has two review milestones.
    • The initial review occurs after the board outline, component footprints and component placement is completed.
    • The second and final review of the board occurs after routing and design or rules checking, prior to fabrication of the circuit board.
      • The final review includes checking of the gerbers files.  Schematics and layout files will be archived and the revision numbers incremented each time a board is fabricated with changes.
    • A redlined version showing changes or rework is archived.
10
Unit Test
  • The hardware and software unit and system test plans and procedures are written.
  • Prototypes are constructed.
  • The hardware and software modules and subsystems are tested individually.
  • Unit tests verify that all of the requirements are met.
  • Test results are documented, preferably electronically.
11
 Integration and Verification Test
  • The hardware and software modules and subsystems are combined and debugged at this time.
  • The test results are reviewed to determine whether adequate coverage of the requirements has occurred and whether the overall system test passes.
  • Test results are documented, preferably electronically.
12
Release and Approval
  • If necessary, any hardware rework is imbedded, software is revised if impacted by the hardware revisions, and the boards and/or wiring are fabricated again.
  • The hardware and software are verified again prior to manufacturing release.
  • The client approves the release (acceptance of design, in writing).
13
Other Deliverables
  • Other deliverables may also be required.
    • Weekly status reports to the client are required.
    • Documentation can also include:
      • User’s guides (Installation, use, etc.).
      • Troubleshooting/maintenance guides.
      • Other documentation as specified in the project requirements.
    • Regulatory approvals:
      • FCC, EMI, UL, CE, RoHS, etc.
14
Consequences of not Following this Process
  • Work quality suffers.
  • Uncontrolled “scope creep” occurs.
    • Requirements change over time.
    • Deliverables become impossible to meet.
    • This can be managed through an ECO process.
  • Projects go over budget and behind schedule.