S/W Design Review

(before CDR)

V0.1

Definition

The objectives of the Design Review for Software held before the project CDR are as follows:

  1. Review and validate the detailed design of the S/W from technical standpoint
  2. Ensure that the detailed design of S/W meets all project requirements
  3. Clearly identify the risks related to S/W and possible contingencies
  4. Approve proposed schedule for S/W implementation work to be conducted during Implementation Stage

Questions

Technical assessment

  • Is the detailed design of S/W appropriate?
  • Does the detailed design of S/W meet the product specifications?
  • Are the implementation trade-offs proposed for S/W appropriate for the project?
  • Are the algorithms appropriate?
  • Have the key risks related to S/W been correctly identified and evaluated?
  • What contingencies can we propose against those risks?
  • Are the R&D test programs for S/W (Unit, Integration) appropriate?
  • What are the open issues which need to be addressed regarding S/W?

Cross-functional check

  • Does the S/W detailed design support the Serviceability requirements?
  • Does the S/W detailed design support the Test requirements?ASICS schedule and resources

S/W schedule and resources

  • Is the proposed schedule for S/W implementation work appropriate?
  • Are the corresponding resources appropriate (# of people, type of skills)?
  • Have we identified additional S/W risks (technical, cost, schedule basis)?
  • From a S/W standpoint, are we ready to proceed to the Implementation stage?

Input

Marketing

  • MRD (remains a living document after the Planning & Specification Stage Review but with limited changes expected)

Service

  • Serviceability objectives
  • Product Service Plan

R&D

System Architecture

  • Architecture reference model

ASIC Design

  • Model definition
  • Model diagram
  • Pinout
  • Programmer reference model
  • Block diagrams
  • Pseudo code
  • Simulation results

ASIC Verification

  • All 4 stages of verification ready
  • Results of before-tape-out unit and integration testing
  • List of bugs

H/W design

  • Interface between H/W - H/W, H/W - S/W, H/W - ASICs, H/W - system
  • 95% Jedec files completed
  • Electrical schematics ready
  • Timing, thermal (70% of work only) and performance analysis
  • Mechanical drawings
  • Preliminary placement
  • BOM
  • Layout recommendations (size, # of layers, special line, list of critical signal files)
  • Utilities for testing
  • Board programmer reference model
  • Quality reliability and compliance
  • Design documentation (95%)

S/W design

  • SRS
  • S/W design document (for each block)
  • Management interfaces specifications (MIBs and relevant NMS application, LMA)
  • Detailed performance estimations
  • S/W integration and module test plan
  • Updated S/W development plan
  • S/W configuration management tool and usage methodology ready

Engineering Prototypes

  • Build plans for prototypes
  • Usage plans for prototypes (R&D, Manufacturing, Safety regulations)

R&D Test

  • Final Unit / Integration Test programs
  • Final Engineering Test programs
  • Engineering Test tools and equipment list
  • Initial System and Alpha Test procedures
  • Test environment set-up, external labs ordered

Manufacturing

  • Test Vehicle results and required action items
  • Progress report on DFX activities (completed and remaining)
  • Manufacturing costs, NREs and GM analysis
  • Material Flow
  • Updated Manufacturing Plan (Gantt chart)

Manufacturing Test

  • Final placement of test points
  • Updated Test equipment availability plan
  • Frame of S/W testing

Materials

  • List of qualified vendors

Finance

  • Estimates of product GM in production (on a per component basis)

Deliverables

S/W detailed design validated

List of open issues related to S/W detailed design

Updated S/W schedule for Implementation Stage

Additional S/W resources for Implementation Stage identified (if any)