1. (1) Project LEAP: A “Personal Information Environment” for Software Engineers Philip Johnson Cam Moore Collaborative Software Development Laboratory University of Hawaii http://csdl.ics.hawaii.edu/

2. (2) Personal Information Quiz Recreational Sports: Do you know your handicap? What is the weakest part of your game? Personal Finance: Do you know your yearly income? What is your weakest financial asset? Software development: Do you know your average development rate? What defects do you make most frequently?

3. (3) Leap Toolkit Objectives Help the average developer in an average company obtain low-cost answers to software development questions like: What is my development rate? How much effort will this project need? How big do I expect this work product to be? How much time do I actually spend “working”? What kinds of errors do I make repeatedly? The tricky parts: “average” developer “average” company “low-cost” answers

4. (4) Lessons from “Quicken™” Quicken provides average people with low-cost answers to simple financial questions: How much money do I have? How fast do I spend it? Where does my money go? Access to this information leads naturally to goal- setting and monitoring: How much money do I want to have in 10 years? How fast do I want to spend my current income? What do I want (and not want) to spend it on? Am I achieving these goals?

5. (5) Quicken supports the classic improvement cycle Observe the activity Collect data Evaluate the activity Analyze the data Modify the activity Observe Evaluate Modify

6. (6) If Intuit designed a SE tool... Quicken “SE” would: Be useful with partial data Allow minimal and flexible “process” Apply to different work products Automate data collection and analysis Be portable across jobs Keep your data private Quicken “SE” would not require: Quicken “SE” Maturity Model Corporate Quicken “SE” Improvement Group Personal Quicken “SE” Process ISO Quicken “SE” 9000 certification

7. (7) Leap Examples: Observation Collecting time data Collecting defect data using checklists Computing the size of a Java program Observe Evaluate Modify

8. (8) Leap Examples: Evaluation What errors do I make most frequently? What are my direct hours? What is my development rate? Observe Evaluate Modify

9. (9) Leap Examples: Modification Plan a new project Modify a checklist Observe Evaluate Modify

10. (10) Future Directions Experimentation: Evaluation of alternative estimation methods Adoption case studies Enhancements: Voice-based input Enhanced review support Web-based, “obfuscated” data repository Documentation (6 of 15 chapters to go) Open source development model

11. (11) True Confessions Tech Reports: Average words/hr:304 Most common defect: Passive voice Average planned time error:35% Lisp code: Average LOC/hour:10 Average fns/hour:0.8 Most costly defect:AND/OR/NOT Java code: Average LOC/hour:13 Average methods/hour:1.1 Most costly defect:Loop initialization

12. (12)