Skip to main content
v2026.11,986 entries · CC-BY 4.0

Spacecraft Design: Lifecycle Phases, Reviews and Subsystems

How spacecraft design proceeds through NASA’s lifecycle phases and PDR/CDR reviews, and where each subsystem and design driver is covered.

Written and maintained by CASRAI Editorial Board

Published

On this page

Spacecraft design is the engineering process that turns a mission concept into a vehicle: it defines requirements, then develops and integrates the structure, thermal control, power, propulsion, guidance and control, avionics and communications subsystems so that the whole system meets the mission within cost and schedule limits. NASA frames this as a staged life cycle with formal reviews, not a single act of drawing a vehicle.

Short answer

In NASA’s Systems Engineering Handbook (NASA/SP-2016-6105 Rev2), a project moves from Pre-Phase A concept studies through Phases A to F, and the design work itself is concentrated in Phases A to C. Each phase produces defined outcomes, and design reviews decide whether the project may proceed. The Preliminary Design Review (PDR) tests whether the preliminary design meets all system requirements with acceptable risk, and the Critical Design Review (CDR) tests whether the design is mature enough to proceed to full-scale fabrication, assembly, integration and test. The data table below compares the phases.

Definition and scope

Spacecraft design sits inside the wider discipline of aerospace engineering and applies the methods of systems engineering: the spacecraft is treated as an integrated system of subsystems whose requirements, interfaces and verification are managed together. European practice uses the same idea. ECSS-E-ST-10C Rev.1 (15 February 2017) states that it “specifies the system engineering implementation requirements for space systems and space products development”, lists among its objectives specifying “the essential system engineering tasks, their objectives and outputs”, and adds that depending on the product category its application needs to be checked and, if needed, tailored. It cancels and replaces the 2009 issue.

Two points about scope are worth keeping straight. First, the NASA handbook describes itself as top-level guidance and states that it is not intended in any way to be a directive, so it is a reference for how to structure the work, not a compliance checklist. Second, the design of the spacecraft is only part of a mission: launch, operations, ground data systems and end-of-life disposal are all treated as parts of the same life cycle.

How design proceeds in practice

The handbook organises a project into formulation (Pre-Phase A through Phase B) and implementation (Phase C through Phase F). The data table below sets out every phase with its purpose and typical outcomes as the handbook gives them in its life cycle table.

Concept studies and requirements

Pre-Phase A is a broad survey of ideas and feasibility that produces draft system-level requirements, with outcomes such as simulations, studies, models and mock-ups. Phase A narrows this to a final mission concept, system-level requirements and the technologies the mission needs, and it defines the trade studies that compare alternatives. The handbook also recommends developing a concept of operations early; it notes that a concept of operations can serve as a check in identifying missing or conflicting requirements. Technology maturity is often tracked with technology readiness levels.

Preliminary and final design

Phase B, Preliminary Design and Technology Completion, establishes an initial baseline and a preliminary design for each end product. Typical outcomes include mock-ups, trade study results, specification and interface documents and prototypes. The PDR closes this phase. Phase C, Final Design and Fabrication, completes the detailed design, fabricates hardware and codes software, and the CDR is the gate that demonstrates the maturity of the design is appropriate for full-scale fabrication, assembly, integration and test.

Integration, operations and closeout

Phase D covers system assembly, integration and test, and launch. Phase E covers operations and sustainment. Phase F is closeout, which includes decommissioning and disposal. Seen this way, the work usually called spacecraft design is front-loaded: the decisions that fix the architecture are made in Pre-Phase A through Phase C, while Phases D to F test, fly and retire what was designed.

Trade studies: how design choices get made

The handbook says trade studies exist to ensure that the system architecture, the intended operations and design decisions move toward the best solution achievable with the available resources. It lists four basic steps: devise alternative means of meeting the functional requirements (in early phases this means system architectures, in later phases system designs); evaluate the alternatives against measures of performance and system life cycle cost, with mathematical models helping to force recognition of the relationships among outcome variables; rank the alternatives against appropriate selection criteria; and drop the less promising alternatives, proceeding to the next level of resolution if needed.

It adds that the process should be done openly and inclusively, with systems engineers, design engineers, crosscutting specialty engineers, analysts, end users, maintainers, operators and project managers cooperating. Quantitative techniques are used, but the handbook is explicit that subjectivity also plays a significant role, and that assumptions, models and results should be documented in the project archives. For researchers writing a proposal around a spacecraft or payload, this documentation habit is useful evidence that a design choice was compared against alternatives, not assumed.

The same handbook observes that when alternatives reduce cost without reducing effectiveness, or raise effectiveness without raising cost, the decision is easy, and that decisions become harder when an alternative trades cost for effectiveness. It also notes that the life cycle costs of a program or project tend to get locked in early in design and development, which is why the early phases carry so much weight.

Requirements and the System Requirements Review

The handbook describes requirements as being validated to be clear, correct, complete and achievable, agreed with the customer and key stakeholders, and then baselined and placed under configuration control. Typically a System Requirements Review (SRR) is held so that comments on needed changes can be gathered and agreement reached on the set of requirements before it is baselined. In practice this means the design that PDR examines is measured against a requirements set that was already reviewed and frozen, which is part of why PDR can ask a precise question about whether the preliminary design meets all system requirements.

Subsystems and where each is covered

NASA’s State-of-the-Art of Small Spacecraft Technology report is updated yearly and organises small spacecraft technology into 13 chapters. It presents itself as a general overview, not a comprehensive survey, but its chapter list is a convenient map of the subsystem and support topics a design team has to address.

Design topic Chapter in the 2026 State-of-the-Art report
Whole-vehicle buses Complete Spacecraft Platforms
Electrical power Power
Propulsion In-Space Propulsion
Attitude and trajectory control GNC
Load-bearing structure and moving parts Structures, Materials, and Mechanisms
Temperature management Thermal Control
Onboard computing and electronics Avionics
Radio links Communications
Getting to orbit and release Integration, Launch, and Deployment
Operating the spacecraft Ground Data Systems and Mission Operations
Knowing where the spacecraft is Identification and Tracking
End of life Deorbit Systems

The orbit and attitude behaviour that drives several of these chapters is covered in our guides to flight mechanics and guidance, navigation and control. The report also has an introductory chapter, making 13 in total.

Mechanical and thermal design drivers

NASA’s Small Spacecraft Systems Virtual Institute (S3VI) knowledge base describes mechanical design for small spacecraft as primarily driven by the dynamic and static structural loads experienced during launch. Thermal design is driven by the temperature ratings of components and by worst-case hot and cold states, which depend on factors such as electronics dissipation and on-orbit radiation. On small satellites the two are tightly coupled, so a structural choice (a bracket, a panel, a bolted joint) changes the heat path, and a thermal choice (a conductive interface) changes the loads on fasteners.

The same S3VI page gives several practical points that a design team can act on:

  • Thermal interface materials need compression, so bolt size, preload and finish should be set with margin.
  • CubeSats are typically constrained by volume rather than by mass.
  • Design for manufacturing and reusable component libraries reduce rework.
  • Reduced-fidelity thermal and structural analysis should start early, before the detailed design exists.

It also points designers to NASA-STD-6016C for materials and processes for spacecraft and to the GSFC-X-673-64-1F drawing standards manual, alongside ASME Y14.100. For passive thermal hardware, see our guide to multi-layer insulation.

Where it matters for labs and facilities

Because the handbook ties each phase to physical outcomes such as mock-ups, prototypes and test-ready hardware, the design process generates demand for laboratory and test capacity well before launch: thermal and structural analysis early, fabricated hardware in Phase C and integration and test in Phase D. The S3VI page notes that early reduced-fidelity analysis is intended to inform the design before detailed models are available. Research offices and facility managers can use the phase table to see which stage a project is in and what kind of artefact it will need next.

Common misunderstandings

  • “The handbook is a mandatory procedure.” The handbook states that it is top-level guidance and not a directive. ECSS-E-ST-10C likewise expects tailoring to the product category.
  • “PDR and CDR are the same review at different times.” They answer different questions. PDR asks whether the preliminary design meets all system requirements with acceptable risk and within cost and schedule constraints, which sets the basis for detailed design. CDR asks whether the design is mature enough to proceed to full-scale fabrication, assembly, integration and test.
  • “Small spacecraft are always limited by mass.” The S3VI page says CubeSats are typically volume-constrained rather than mass-constrained.
  • “Mechanical and thermal design can be done separately.” On small satellites the two are tightly coupled, as described above.
  • “Design ends at launch.” The handbook’s phases continue through operations (Phase E) and closeout including disposal (Phase F), and the State-of-the-Art report includes a chapter on deorbit systems.

Sources

Data: NASA project life cycle phases and typical design outcomes

Compiled from the life cycle phase table of the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev2): each phase's name, whether it belongs to formulation or implementation, its purpose and typical outcomes, with the PDR and CDR gates noted where the handbook places them.

NASA project life cycle phases and typical design outcomes
PhasePhase nameLife cycle stagePurposeTypical outcomes
Pre-Phase AConcept StudiesFormulationBroad spectrum of ideas and feasibility; draft system-level requirementsSimulations, studies, models, mock-ups
Phase AConcept and Technology DevelopmentFormulationFinal mission concept, system-level requirements, technology needsTrade study definition
Phase BPreliminary Design and Technology CompletionFormulationInitial baseline; preliminary design of each end product (closes with PDR)Mock-ups, trade study results, specification and interface documents, prototypes
Phase CFinal Design and FabricationImplementationDetailed design; fabricate hardware and code software (closes with CDR)Hardware fabricated and software coded
Phase DSystem Assembly, Integration and Test, LaunchImplementationAssemble, integrate and test the system, then launchSystem assembled, integrated and tested, then launched
Phase EOperations and SustainmentImplementationOperate and sustain the systemNot itemised in the handbook life cycle table
Phase FCloseoutImplementationDecommissioning and disposalNot itemised in the handbook life cycle table

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Spacecraft Design: Lifecycle Phases, Reviews and Subsystems

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →