Download Summary
Transcript
SOFT3103.DOC Page 2 of 38 Spiral Model • • • Development no longer sequential but form a cycle that keeps coming around Testing critical, results fed back into development cycle Develop systems incrementally Extreme Programming • • • • • • • Form of RAD Development cycle takes place over a single day Testing is central to this model and products can not be released unless all tests are passes Core Practices o On-site customer o Small releases o Planning o Metaphor o Simple design o Pair programming o Collective ownership o Continuous Integration o Coding standards o Testing – constant o Re factoring – changing code you have written o Forty hour week – never left along to work after hours Can get different testing frameworks for different languages Unit testing o Unit tests are developed prior to the actual coding of the unit o Debugging is undertaken by adding tests to the unit tests Acceptance Testing o Requirements integrated in each release should be acceptance tested in that release o Because customer is on site, this actual happens as the project is being developed o Often done with the customer to confirm they are getting what they want Clean Room • • • • • • • • Where you mathematically prove the program is correct Formal methods Programmers are not allowed to compile and run your code Build code and formally verify it Return status on how reliable the system is Functional specification o Entire product specified in an appropriate mathematical formalism o Specification is subject to inspection to reduce errors Design and verification o Stepwise abstraction – prove implementation is what you specified o Correctness conditions Role of review and testing o Heavily dependent on inspection Course Summary ~ Robert Whitaker