Iterating and testing
This chapter introduces us to show the progress to a customer, and how to do it, because the customer don’t care about our diagrams, classes, or the object oriented tools we used, they only want to see a functional application that solves their problems and more important is doing what is suppose to do, and for this is important to choose a way of development, Feature driven development or Use case driven development.
Feature driven development, you must look at the feature list and work on one single feature at a time, then iterate and doing all the features until the functionality of the application is finished, this works well when the features don’t interconnect a whole lot and systems with lots of disconnected pieces of functionality.
Use case driven development, here you work in a single scenario through a use case, and you work until all the scenarios are completed, this is useful when the application has a lot of scenarios than individual functionalities, you can show bigger pieces of the project to the customer and works well if the system have a large and complicated process.
To show the development of the application to the customer we need to write test scenarios, where is a way to show the customer that the functionality is working well, and is needed to be creative to test the software with every possible usage and for incorrect usage, because this way we can catch errors early, and this is only for one specific thing, a expected output according to the input, and more important to match with the design.
And the chapter concludes with an interesting contract between software and the people that use it for example the frameworks , this details how the software work when certain actions are taken, and to explain the chapter introduces program by contract and defensive programming, where in the first the users are agreeing that the software works in that way, and you trust them that they can handle it, in the other way the second one is when you don’t trust your users, you need to throw errors or how they can handle with the problems.
In conclusion, testing is a very important way to show that our product is doing well and the final user will feel secure that the product is gonna do the right things in every moment.
Photo by Daniel Chou
Newbie Programmer 