(1) Project LEAP: A “Personal Information Environment” for Software Engineers Philip Johnson Cam Moore Collaborative Software Development Laboratory University.

Slides:



Advertisements
Similar presentations
1.Explain the nature and importance of capital investment analysis. 2.Evaluate capital investment proposals, using the following methods: average rate.
Advertisements

Software Development Life Cycle
Metrics for Process and Projects
Software Construction
Money Management and Financial Planning
The Experience Factory May 2004 Leonardo Vaccaro.
Systems Analysis and Design
SE 450 Software Processes & Product Metrics Reliability: An Introduction.
Fundamentals of Information Systems, Second Edition
A Case Study of HPC Metrics Collection and Analysis Philip Johnson and Michael Paulding, University of Hawaii, Honolulu, Hawaii. Goals of the case study.
Managing Quality and Performance
Swami NatarajanJuly 14, 2015 RIT Software Engineering Reliability: Introduction.
1 Chapter 1 Introduction: Enterprise Resource Planning.
Click here to advance to the next slide.
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Kapoor Dlabay Hughes 6e © The McGraw-Hill Companies, Inc.,2001. All Rights Reserved. P ERSONAL F INANCE Irwin/McGraw-Hill.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
7 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Introduction to High-Level Language Programming
ISERN-Meeting, Honolulu, Hawaii 09 October 2000 Slide 0 Using Experiments to Teach Software Engineering Using Experiments to Teach Software Engineering.
(1) Experimental Software Engineering in Internet Startups: An Oxymoron? Philip Johnson Collaborative Software Development Laboratory Information and Computer.
  We listened to your comments, needs, and concerns in using WEAVEonline for the past three years  We searched for an alternative to WEAVEonline.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Software Project Management
Chapter 4 Components of the Software Quality Assurance System
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Software System Engineering: A tutorial
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
Software Estimation and Function Point Analysis Presented by Craig Myers MBA 731 November 12, 2007.
Chapter 6 : Software Metrics
Money Management Skills
Project Coordinators: Eduardo Santana de Almeida Silvio Romero de Lemos Meira Federal University of Pernambuco Informatics Center Recife Center for Advanced.
Hour 1 February/18/14 Eric Weber Career Tech Found.
ISO17799 Maturity. Confidentiality Confidentiality relates to the protection of sensitive data from unauthorized use and distribution. Examples include:
Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition.
06/16/101 Software Project Management (SPM) Lecture 9 Software Quality Management Dr. Daniel Keret.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
6.3 Your Budget Worksheet. Section 6.3 Your Budget Worksheet  Goals: Identify steps you should take to create a budget worksheet. Explain common problems.
Lecture 4 Software Metrics
1 Presentation Template: Instructor Comments u The following template presents a guideline for preparing a Six Sigma presentation. An effective presentation.
SE-280 Dr. Mark L. Hornick 1 SE-280 Software Engineering Process Dr. Mark L. Hornick web: myweb.msoe.edu/hornick SE280 info syllabus,
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
ANKITHA CHOWDARY GARAPATI
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
SPRAE A Framework for Teaching Software Testing Edward L. Jones Florida A&M University.
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
(1) Cam Moore Collaborative Software Development Laboratory Communication & Information Sciences University of Hawaii, Manoa
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Company Confidential Leverage Your E-Business Suite as Part of Your Sales Performance Management Strategy January 17, 2008.
CS5103 Software Engineering Lecture 02 More on Software Process Models.
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
(1) Cam Moore Collaborative Software Development Laboratory Communication & Information Sciences University of Hawaii, Manoa
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Chapter 43 Budgeting Techniques. Budget The main purposes are to help you. –Live within your income. –Achieve your financial goals. –Buy wisely. –Avoid.
Personal Finance Chapter 6
CSC444F'07Lecture 41 CSC444 Software Engineering Top 10 Practices.
My career choices Game designer, Software designer, Engineer.
1 - 1 Chapter 1 Managerial Accounting & The Business Organization.
Chapter 1 Assuming the Role of the Systems Analyst.
Building Comfort With MATLAB
Systems Analysis and Design
Fundamentals of Information Systems, Sixth Edition
This presentation uses a free template provided by FPPT.com Computer Name: Ojen Shrestha Class: XI Section: G 1 Date:
Software Development Life Cycle
Software metrics.
Chapter 2. Problem Solving and Software Engineering
Systems Development An Overview of Systems Development
Presentation transcript:

(1) Project LEAP: A “Personal Information Environment” for Software Engineers Philip Johnson Cam Moore Collaborative Software Development Laboratory University of Hawaii

(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) 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) 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) Quicken supports the classic improvement cycle Observe the activity Collect data Evaluate the activity Analyze the data Modify the activity Observe Evaluate Modify

(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) Leap Examples: Observation Collecting time data Collecting defect data using checklists Computing the size of a Java program Observe Evaluate Modify

(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) Leap Examples: Modification Plan a new project Modify a checklist Observe Evaluate Modify

(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) 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)