In this article they discuss how their techniques allow for the creation of code that can easily handle new requirements. There are different types of formal methods that have totally different purposes. Formaly methods do permit more percise specifications and support earlier error detection. Jonathan Bowen and Michael Hinchey propose ten guidelines that should help software development teams use formal methods in a more effective manner. This article is an exciting and interesting introduction to formal methods that takes a positive outlook on the impact that the discipline will have on software engineering profession.
Testing is a process that can be conducted in a manual or an automated fashion.
Brian Marick has developed some rules of thumb that help us to determine when we should automate a test. Mr. Marick provides us with some ideas to better help us to determine when a test should be automated. Coverage is an exciting topic and it is often used to help us gauge the adequacy of the tests that we develop. Brian Marick describes code coverage and explains some guidelines for the appropriate situations in which it should be used.