Session 4.6 - Design Reviews & TSPi Design Scripts

Chapter 7: Designing with Teams | Duration: 1 hr

Learning Objectives

By the end of this session, you will be able to:

  • Run effective design inspections using INS script
  • Describe DES1/DESn steps and entry/exit criteria
  • Allocate design work into the SDS and secure commitments
  • Plan integration tests alongside design and baseline results

Introduction

Design quality is secured through inspection and disciplined scripts. Chapter 7 walks through DES1/DESn, emphasizing inspected SDS and integration test plans before moving to implementation.

Design Reviews & Inspections

  • Need well-documented design; analyze interfaces, loops, states.
  • INS script: moderation, defect logging (LOGD), follow-up fixes.
  • More reviewers find more issues; balance yield vs. time.

DES1/DESn Overview

Entry Criteria
  • Completed strategy and plan
  • Design standards documented; glossary set
  • Completed and inspected SRS (updated for DESn)
Main Steps
  • Decide overall product structure
  • Name components and allocate functions
  • Produce external specs; allocate use cases
  • Identify design tasks; build SDS

Component Allocation & SDS

Use STRAT form and traceability table to map functions to components and cycles (Table 7.4 example). Then divide SDS sections among team members based on skills and availability; secure commitments.

Integration Test Plan

Create integration test plan alongside the SDS to exercise all interfaces. Inspect it with the SDS—planning tests often reveals interface defects earlier than coding.

Baseline & Exit Criteria

  • Fix inspection defects; recheck critical changes.
  • Support manager baselines the SDS (changes via CCR only).
  • Exit with: inspected SDS, inspected integration test plan, standards/glossary, INS forms, updated SUMP/SUMQ, time/size/defect data in tool, notebook copies.

Summary

  • Inspections improve design quality and shared understanding.
  • DES1/DESn enforce entry criteria, structured design steps, and documented outputs.
  • Traceability tables clarify component/function allocation and cycle content.
  • Baseline SDS and integration tests before implementation to control change.