We hope that everyone will obtain a better understanding of the overall development process from this book. Instead, we aim to give a minimum set of notions and to show how to use these notions when progressing from a set of requirements to an implementation. Most of what we have written in this book is not true. It is also not false. This is because we are in the prescriptive business.
Software development is a special kind of process.
Algorithms are not true or false. They are appropriate for a task or not. Thus this book should contain a correctness proof that demonstrates that the application of its methods invariably yields a desired system. However, due to space limitations, we have omitted this proof. More seriously, we have tried to decrease the fuzziness that is inherent in prescriptive text by giving precise textual descriptions of the key notions in the respective methods.