< Back
Page 3 of 3
This chapter is from the book
Summary
Executable Design is a method for driving the implementation of software functionality. It focuses on the following principles:
- The way we design can always be improved.
- We'll get it "right" the third time.
- We will not get it "right" the first time.
- Design and construct for change rather than longevity.
- Lower the threshold of pain.
Going beyond how we write automated tests, Executable Design also involves how they are structured inside projects, how they are executed in different environments, and a way to think about what the next test should be. When we answer the question "What should the software do next for the intended user?" our programmer tests will be more directly focused on delivery of value to the user. Using transparent code analysis, team members can get feedback on the health of the code as they implement in an incremental fashion.
< Back
Page 3 of 3