SMAD stands for Space Mission Analysis and Design. The textbook by that name, first published in 1991 and now in its fifth edition (Space Mission Engineering: The New SMAD), is the closest thing the space industry has to a universal reference. It defines the process of taking a mission concept from initial objectives through detailed design.
The SMAD methodology breaks mission engineering into a structured sequence: define mission objectives, derive requirements, allocate budgets (mass, power, data, thermal, link), assess risks, and verify readiness at each phase gate. Each step feeds the next. Requirements drive budgets. Budgets constrain design trades. Design trades generate new requirements. The process is iterative by nature.
What makes SMAD powerful is not any single analysis. It is the integration. A mass budget without requirements context is just numbers. Requirements without budget margins are just wishes. Phase gates without risk posture are just meetings. The methodology works because it connects these elements into a coherent picture of mission readiness.
Most teams implement SMAD methodology using a collection of disconnected tools: DOORS for requirements, Excel for budgets, PowerPoint for reviews, custom scripts for analysis. The methodology describes an integrated process, but the tools force a fragmented execution. Every review cycle requires manual integration of data from five different sources.
SMAD Portal implements the methodology as software. Requirements, budgets, risks, phase gates, and engineering calculators live in one system. The connections the methodology describes — requirements tracing to budgets, risks linking to requirements, phase gates pulling from all of the above — are maintained automatically. The process the textbook defines becomes the workflow the tool enforces.