Ajax Personal Transporters

1. Ajax Personal Transporters LiveThru the Project Inc. October 7, 2004

2. Greg Silverstein Software Architect Coding Supervisor Daniel Lipsy Project Manager Coder Matt Tasker Coder Tzu-Chieh Wei Documentation Doug Kavendek Testing Supervisor Nicholas Mattiello Coder Tze-Ho Lee (Chi) Tester Marina Fingerman Presentation We are…

3. Assumptions • Maintain original interface • Must not void warranty on old software • Single user environment • Backwards compatible • Deletion of customers indexed by phone number • Java v1.4 or newer is installed on system

4. Demo

5. General Enhancements • Transaction logging • Additions, cancellations, modifications. • Importing old data • Malicious zip code module • Bypassed • New order after deletion • File I/O was inconsistent

6. General Enhancements • Text labels • Initially: text in fields • Consistent field size • No auto-resizing after input • Consistent movement with Tab

7. Input Enhancements • Input limitations • No numeric characters in either name • No non-numeric characters in phone number • Modify order number maximum • Phone number restraints • Min: 4 digits; Max: 15 digits • No negative quantities ordered • “&” and newline characters are now safe

8. Search Enhancements • Column headers • Case-insensitive • No need for strict case sensitivity • Substring search • Exact matches on top • Inexact matches below

9. Other Enhancements • Backlogged order functionality • Orders can be modified • Shutdown tab • Immediate dialogue • Modifications and backlogging • Condensed popups

10. Zip View orders Add Modify Cancel order Shut down Action logging Remove customer Intuitive n/a 4 3 2 n/a n/a n/a n/a Consistent n/a 3 1 2 n/a n/a n/a n/a Efficient n/a 3 3 3 n/a n/a n/a n/a Durable n/a 3 1 1 n/a n/a n/a n/a Thoughtful n/a 4 2 1 n/a n/a n/a n/a ICED-T Analysis:Original system

11. Zip View orders Add Modify Cancel order Shut down Action logging Remove customer Intuitive 4 4 4 5 4 4 5 4 Consistent 4 4 5 4 4 4 5 5 Efficient 4 4 4 4 4 4 5 3 Durable 3 4 4 4 4 4 5 4 Thoughtful 4 4 5 5 4 5 5 4 ICED-T Analysis:Our system

12. Development Methods • RAD • Used To Solve Additional Requirements • Modular Design • Each Feature Developed Independently • Incremental • Insured Each Feature Was Complete and Stable Before Next Step Was Addressed

13. Software Releases -9/5/04 V0.0 Pre Existing Code -9/25/2005 V0.5a Dan’s Modifications -9/27/2004 V0.5b Matt’s Modifications -9/27/2004 V1.0 Error Combined Code -9/28/2004 V1.0a Working Combined Code First Functional Output (Pre Production Alpha) -10/5/2004 V1.1 Working Combined Code With First Set of Revisions -10/6/2004 v1.2 Working Combined Code With Second Set of Revisions -10/6/2004 v1.3 Deliverable Build

14. Testing Procedures • Regression • Use case • Diabolical

15. Action Pre (0.0) Post (1.3) New Order 54 51 View Orders 12 13 Modify Order 1200 + 55 47 Cancel Order 1200 + 21 24 Search Customers 1200 + 23 26 Delete Customers 1200 + 13 22 Time Measurement Figure 1.1: Measured Times in Seconds Functional Time Measure: 4,978SEC 183SEC Difference: 4795SEC in favor new system

16. Action Win2k WinXP Gentoo Linux New Order 1.74 1.82 1.51 View Orders 2.57 2.71 2.44 Modify Order 3.11 3.14 3.06 Cancel Order 1.92 2.01 1.84 Search Customers 2.92 2.84 2.71 Delete Customers 2.84 2.88 2.81 Application Performance Action Times Comparison: Figure 1.2: Action Times Comparison (seconds)

17. Workplace Value • Quantitative Analysis Of System Benefit • 4 Target Areas • Cost • Features Implementation • System Stability • User Productivity • Comparison • Old System Was 13.1% Effective To Goal • New System Was 98.7% Effective To Goal

18. Production Flow 10/7 9/25 Milestones 9/27 10/5 code starting first major build second major build code complete

19. Proposed Future Updates • Verification of addresses • Deletion of customers • Handle multiple entries with same phone number more gracefully • Automate state through zip code

20. Lessons Learned • (you fill in)

21. Questions?