Executable Documentation

Why is so much project documentation outdated and worthless? Simply put, the real value is in the final product; so, that’s where the money goes. Wouldn't it be nice if your documentation actually reflected the functionality in the system? One way to do this is to create executable documentation, also known as executable specifications. Join David Hussman for this class if you are struggling with ambiguous requirements, lack of collaboration with users, or a lack of communication among developers, business stakeholders, and testers. Although David uses open source Fit as a vehicle for demonstrating executable documentation, the class will teach you how to develop the information you need to make any similar tool serve up meaningful requirements that have two states--red (dead) or green (alive). Starting down the path to executable documentation is a great way to remove waste and more quickly produce better software.