Test-Driven Development: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
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. This appears to be synonymous with [[Concurrent Engineering]]. | 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. This appears to be synonymous with [[Concurrent Engineering]]. | ||
=Test Driven Iterations= | |||
<html><iframe src="https://docs.google.com/presentation/d/1YH4BHfyPbEUv1HSPqm5NVupav2ErisjSWUZxQ3JzW2g/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="749" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html> | |||
[https://docs.google.com/presentation/d/1YH4BHfyPbEUv1HSPqm5NVupav2ErisjSWUZxQ3JzW2g/ edit] | |||
Revision as of 20:36, 23 November 2016
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. This appears to be synonymous with Concurrent Engineering.
Test Driven Iterations