Test Driven Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
See analogue in software - http://en.wikipedia.org/wiki/Test-driven_development | See analogue in software - http://en.wikipedia.org/wiki/Test-driven_development | ||
=Test-Driven Development= | |||
Test-Driven Development is design based on a rapid ability to iterate by designing partial implementations of a final product to test various assumptions and working principles. |
Revision as of 21:45, 25 November 2015
Test driven design refers to a design process that performs tests and rapid prototypes on an early and ongoing basis - prior to an actual build. This can be done in various ways:
- Subject Matter Expert review
- Review via a social network
- Partial Prototypes - Building out small components at a time instead of a whole machine at a time.
- Module Based Design - Breaking artifict into smaller modules and prototyping individual modules
- Scale models - this may be done by wood, paper, or other models - such as 3D printing, laser cutting for folded (LifeTrac tubing) or stacked (architecture) paper pieces, or many other models
- Doing extra calculations or simulations in software or in Hardware-in-Loop systems
- Visualizations, 3D renderings, motion analysis
See analogue in software - http://en.wikipedia.org/wiki/Test-driven_development
Test-Driven Development
Test-Driven Development is design based on a rapid ability to iterate by designing partial implementations of a final product to test various assumptions and working principles.