1. Anyone interested in this approach ? Over the past couple of years, I have developed PiVoT software to support the Agile development process. It emphasises the testing of the evolving executables throughout the development process. The approach, and supporting PiVoT software, was originally developed to help our final–year students to tackle a full-blown real-world database-centric business application using UML and the Agile philosophy. However, as it has evolved, it has become apparent that it would be just as useful and relevant to professional developers as it has been to our students. It is a work-in–progress, about 80% complete. The remaining 20% relates to providing web support to the client applications. Is anyone interested in getting on board with this?

2. PiVoT software has been developed and supplied to provide students with 3-Tier OO support (and a chance to complete their Major Project within the time allowed)

3. Twelve principles underpin the Agile Manifesto : 1.Customer satisfaction by rapid delivery of useful software 2.Welcome changing requirements, even late in development. 3.Working software is delivered frequently (weeks rather than months) 4.Working software is the principal measure of progress 5.Sustainable development, able to maintain a constant pace 6.Close, daily cooperation between businesspeople and developers 7.Face-to-face conversation is the best form of communication (co-location) 8.Projects are built around motivated individuals, who should be trusted 9.Continuous attention to technical excellence and good design 10.Simplicity 11.Self-organizing teams 12.Regular adaptation to changing circumstances The Agile OO Development Process using PiVoT Software

4. The Executables The PiVoT-Supported Development Process Design Time Run Time Interface-Generated Data form the Interface is used to Populate the Prototype and to provide test data

5. Enter … the PiVoT Approach to Support Evolving Executables Executables 1. Use Prototype Screens to Generate Demo Data 2. Use Screen- Generated Data to Populate & Demonstrate Prototype 3. Use Interface to Generate Test Data 4. Use Test Data to Test Interface, Business Object code and Business Rules Launch Application The Evolving Executables are Central to the Development Process ( not just a result of it ) Persisted Business Object Code

6. With PiVoT, Application Testing is an Integral Part of the Development Process Executables Status Testing Support Prototype with No Business Objects UI Data Type Verification Prototype with Unpersisted Business Objects Business Object Property Verification Pre-Release Executables with Persisted Business Objects Business Rules and Specific Processing Logic Verification ( plus standard load, stress etc. testing ) … with the Test Data Banks being Created Using the User Interface itself … with the Test Data Banks being Created Using the User Interface itself