Test Driven Design: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
Test driven design refers to a design process that performs tests and rapid prototypes on an early and ongoing business. This can be done in various ways:
Test driven design refers to a design process that performs tests and rapid prototypes on an early and ongoing basis. This can be done in various ways:


#Partial Prototypes - Building out small components at a time instead of a whole machine at a time.
#Partial Prototypes - Building out small components at a time instead of a whole machine at a time.
Line 5: Line 5:
#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
#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
#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
See analogue in software - http://en.wikipedia.org/wiki/Test-driven_development

Revision as of 08:19, 2 February 2015

Test driven design refers to a design process that performs tests and rapid prototypes on an early and ongoing basis. This can be done in various ways:

  1. Partial Prototypes - Building out small components at a time instead of a whole machine at a time.
  2. Module Based Design - Breaking artifict into smaller modules and prototyping individual modules
  3. 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
  4. Doing extra calculations or simulations in software or in Hardware-in-Loop systems
  5. Visualizations, 3D renderings, motion analysis

See analogue in software - http://en.wikipedia.org/wiki/Test-driven_development