SOLIDWORKS Design Approach · Part 01
SOLIDWORKS as a design system, not a software program
Most CAD training teaches menus. This series teaches decisions. It treats a modern parametric modeller as an engineering system whose commands are only the visible surface of a much deeper set of geometric, dimensional and manufacturing choices.
Executive summary
Why the approach matters more than the syntax
A designer who knows every command in a CAD system and nothing about design intent will produce models that break the first time a dimension changes. A designer who understands topology, parametrics, tolerance behaviour and manufacturing constraint will produce robust models in almost any system, because the concepts transfer and the keystrokes do not.
That is the organising principle of this series. Each part starts with an engineering task and works backwards to the modelling technique that serves it, rather than starting with a toolbar and looking for something to apply it to. SOLIDWORKS is used throughout as the reference implementation because its feature tree makes modelling decisions unusually visible — the tree is a readable record of how a designer chose to build a part.
Position
The design-system view
Four claims sit underneath every page that follows.
Modelling is a plan, not a sequence of clicks
Before any sketch is drawn, a part can be read for geometric clues: is it an extrusion, a revolve, a composite, or genuinely free-form? Is it symmetric? Does it contain patterns? Those clues determine the fastest build, the most editable build, and the build that matches how the part will actually be made. Those three are not always the same, and choosing between them is an engineering judgement.
Parameters precede dimensions
Parametric modelling separates the shape from its size. A sketch is a set of parameters and relations; dimensions are simply the values currently assigned to them. Once that distinction is internalised, a designer stops treating a model as a drawing and starts treating it as a small, editable program that produces geometry.
Design intent is recorded in the build order
The feature tree is documentation whether or not anyone intends it to be. The order in which features are created, the references they are attached to and the relations that lock their sketches encode the reasoning behind the design. Well-built models absorb change; poorly built models fail on it.
Every model is a manufacturing proposition
Geometry that cannot be machined, moulded, bent or printed is not a design, it is a picture. Tolerances, draft, wall thickness, tool access and material selection belong in the modelling conversation from the beginning, not in a review after the model is finished.
Structure
How the pathway is organised
Five stages, each building on the last. The first two establish the language; the remaining three extend it into geometry, verification and production.
CAD fundamentals
Process context, the working environment, model topology, parametrics, sketching discipline and design intent — the conceptual base that makes everything else legible.
Part and product modelling
Features, automation, drawings, assemblies and visual communication: the day-to-day production work of a design office.
Advanced geometry
Curves, surfaces, sheet metal, weldments and sustainable design — where mathematics and material behaviour enter the model.
Development and analysis
Tolerancing, data exchange and analysis tools: proving that a design will function, transfer and be inspectable before anything is cut.
Manufacture
Rapid prototyping, numerical control machining and injection moulding — the routes from a validated model to a physical part.
The pathway is designed to be read in sequence, but the later stages are largely self-contained. A reader who already models confidently can begin at Part 11 (curves) or Part 15 (tolerances) without loss. Parts 02 to 05 are the exception: almost everything later assumes the vocabulary they establish.
Framework
Three modes, one model
Nearly all mainstream parametric systems present the same three document types. Understanding what each one owns removes most beginner confusion.
The three are associative: a change made in one propagates to the others. That associativity is the single most valuable property of a parametric system and the single most common casualty of careless modelling. Much of this series is, in effect, about protecting it.
Audience and scope
Who this is written for
Design engineers
Practitioners who model daily and want a firmer conceptual footing under their habits, particularly around tolerance behaviour and manufacturability.
Draftspersons and detailers
Anyone producing drawings to ASME or ISO conventions who needs the reasoning behind the drafting rules rather than a list of them.
Students and career changers
Readers building CAD literacy from the ground up, including those preparing for vendor certification.
Metric units lead throughout, with imperial equivalents where industry practice still favours them — sheet gauge and many machining conventions, for example. Australian English is used for all narrative text; software command names, standard designations and code words are reproduced in their published form.
What to carry into Part 02
- CAD competence is the ability to choose a build, not the ability to recall a command path.
- A parametric model is a program that emits geometry; treat edits as changes to that program.
- The feature tree is the primary artefact of design intent and should be readable by someone else.
- Manufacturability is a modelling input, not a downstream review gate.
- Part, assembly and drawing are three views of one associative definition, and associativity is worth protecting.
Series
Continue the pathway
The SOLIDWORKS Design Approach series works through computer aided design as an engineering discipline, from first principles to manufacture.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review SOLIDWORKS as a Design System: Series Overview. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Apply SOLIDWORKS as a Design System: Series Overview by beginning with the duty, not the component or software command. Convert the key ideas—design, solidworks, system, series, overview—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.
Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.
Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.
Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.
Step-by-step operating method
- Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
- Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
- Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
- Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
- Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.
Illustrative design review record
Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.
| Evidence class | Question | Release expectation |
|---|---|---|
| Requirement | What must the design do and under which conditions? | Approved and traceable |
| Input | Where did the load, property, tolerance or process limit come from? | Source, unit and revision recorded |
| Analysis | Which model and assumptions connect input to result? | Checkable calculation or simulation |
| Verification | How will conformity be demonstrated? | Method and acceptance criterion agreed |
| Validation | Will the solution work for intended users and conditions? | Representative use evidence |
Common failure modes and recovery actions
1. Watch for
Starting detailed design before interfaces and operating limits are agreed.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Using catalogue or typical values as though they were certified project inputs.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Confusing verification of requirements with validation of user need.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Releasing drawings or procedures without configuration, inspection and change controls.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- What function and failure consequence govern this decision?
- Which inputs are measured, specified, assumed or illustrative?
- How will conformity be demonstrated and recorded?
- What change would invalidate the current evidence?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying SOLIDWORKS as a Design System: Series Overview?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about design would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- SOLIDWORKS Design Help — Dassault Systèmes SOLIDWORKS. Used for feature-based CAD, sketches, structures and manufacturing outputs. Accessed 2026-08-13.
- NASA Systems Engineering Handbook — NASA. Used for requirements, design, verification, validation and technical management. Accessed 2026-08-13.