Martin Fowler
Software development teams find life can be much easier if they integrate their work as often as they can. They also find it valuable to release frequently into production. But teams don’t want to expose half-developed features to their users. A useful technique to deal with this tension is to build all the back-end code, integrate, but don’t build the user-interface. The feature can be integrated and tested, but the UI is held back until the end until, like a keystone, it’s added to complete the feature, revealing it to the users.
A simple example of this technique might be to give a customer the option of a rush order. Such an order needs to be priced, depending on where the customer lives and what delivery companies operate there. The nature of the goods involved affects the picking approach used in the warehouse. Certain customers may qualify to have rush
To read the full article click on the 'post' link at the top.