1 PSP4a Introduction to the Personal Software Process Watts Humphrey Addison Wesley Longman c1997.

Slides:



Advertisements
Similar presentations
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Advertisements

Software Engineering Lab Session Session 1 – Introduction to the practicum © Jorge Aranda, 2005.
Team Software Process By: Bryan Peterson. Presentation Topics History Brief overview of the Team Software Process (TSP) TSP Team Launch Team-working Conclusion.
The Personal Software Process (PSP) Lecture #1 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Tutorial: Using PSP0 Personal Software Process for Engineers: Part I
Urchin & Website Usability. Usability Study Usability study is a repetitive process that involves testing a site and then using the test results to change.
PRO2 - 1 Introduction to the Personal Software Process SWENET PRO2 Module Developed with support from the National Science Foundation.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 7.
Copyright © 1997 Carnegie Mellon University Introduction to the Personal Software Process - Lecture 1 1 Introduction to the Personal Software Process Lecture.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
CS 325: Software Engineering April 7, 2015 Software Configuration Management Task Scheduling & Prioritization Reporting Project Progress Configuration.
Important concepts in software engineering The tools to make it “easy to apply common sense”!
Important concepts in software engineering The tools to make it easy to apply common sense!
Personal Software Process
The Software Process Strategy The Software Process Strategy Part III.
Aplicaciones de Ingeniería de Software
CS351 © 2003 Ray S. Babcock PSP Personal Software Process ● This material based on the book: ● “Introduction to the Personal Software Process” by Watts.
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Planning. SDLC Planning Analysis Design Implementation.
Personal software process Mohammed ahmed ali. What is psp The personal software process (psp) is a structured set of process descriptions, measurements.
Personal Software Process Overview CIS 376 Bruce R. Maxim UM-Dearborn.
Project Management and Scheduling
Your Interactive Guide to the Digital World Discovering Computers 2012.
 Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of.
Metody statystyczne Copyright, 2001 © Jerzy R. Nawrocki Doskonalenie Procesów Programowych.
Chapter 15 Projecting Defects( 缺陷预测 ). 山东大学齐鲁软件学院 2 outline  Analyze and use your defect data to help improve both planning accuracy and product quality.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 8.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
CS 350: Introduction to Software Engineering Slide Set 1 C. M. Overstreet Old Dominion University Fall 2005.
SE-280 Dr. Mark L. Hornick 1 In software engineering, we sometimes distinguish between "practice" and "process". By "practice", we mean "what" software.
Chapter 3: Completing the Problem- Solving Process and Getting Started with C++ Introduction to Programming with C++ Fourth Edition.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 6.
Program Development Life Cycle (PDLC)
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Lecture: The Personal Software Process. 2 Overview  Personal Software Process assumptions process stages measures and quality strategy results.
© 1998 Carnegie Mellon UniversityTutorial The Personal Software Process (PSP) The overview of the PSP that follows has been built from material made.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Software Engineering Prof. Dr. Bertrand Meyer March–June 2007 Chair of Software Engineering Lecture 2: The Personal Software Process.
From Quality Control to Quality Assurance…and Beyond Alan Page Microsoft.
Time Management Personal and Project. Why is it important Time management is directly relevant to Project Management If we cannot manage our own time.
1 PSP4a Introduction to the Personal Software Process Watts Humphrey Addison Wesley Longman c1997.
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
SE-280 Dr. Mark L. Hornick 1 SE-280 Software Engineering Process Dr. Mark L. Hornick web: myweb.msoe.edu/hornick SE280 info syllabus,
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
Module 1 – Lesson 6 Ms. Tracy. Bell Ringer What is the typical useful life for a personal computer?
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
The Personal Software Process Alan Kelon Oliveira de Moraes May 15, Recife.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 11.
Program Development Cycle
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
Advanced Software Engineering Lecture 4: Process & Project Metrics.
Personal Design and Development Software Process PD 2 SP “The unexamined life is not worth living.” Plato.
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
CompuTimeClock ComputTimeClock is a Windows-based software that replaces your mechanical time clock and more. What is CompuTimeClock?
CSC 480 Software Engineering PSP Project 1 August 20, 2004.
Stock Market Game - Wrap-up Computer Information Technology.
CS 350, slide set 4 M. Overstreet Old Dominion University Spring 2005.
CSC 205 Programming II Lecture 1 PSP. The Importance of High-Quality Work Three aspects to doing an effective software engineering job producing quality.
Debuggers. Errors in Computer Code Errors in computer programs are commonly known as bugs. Three types of errors in computer programs –Syntax errors –Runtime.
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
Starting to use it with the ACM problems
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
A possible solution: Personal Software Process (PSP)
Laboratory Documentation & Notebooks
Introduction to Wikis.
Presentation transcript:

1 PSP4a Introduction to the Personal Software Process Watts Humphrey Addison Wesley Longman c1997

2 PSP4a Humphrey on PSP  “a guide to using disciplined personal practices to do superior software engineering”  “The PSP will show you how to plan and track your work and how to consistently produce high-quality software.”

3 PSP4a Software Development  Do you know how many lines of code you write per day? (or function points? or modules?)  Do you know how many errors you make?  Watts Humphrey knows how many LOC/day he writes and how many errors/KLOC he makes!

4 PSP4a Measurement  Could a person train for running an olympic event without timing their performance?  Would an archer train by shooting at a target but not seeing if the arrows hit the target?

5 PSP4a Time Log

6 PSP4a Time Log Entries  Date  Start - time in hours:minutes  Stop - time in hours:minutes  Interrupt - time of each interruption in minutes  Delta - start - stop - interrupt  Activity - category

7 PSP4a Engineering Notebook  Record all activities related to class  Post on web page – update semi- weekly

8 PSP4a Class Discussion  What can we learn from a programming time log?  What are different uses of any knowledge gained from a time log?

9 PSP4a Possible Categories  Drawing and revising object model  Writing code  Compiling and correcting syntax errors  Testing code (no currently known errors)  Debugging logic errors (that is, there is an error and you are trying to locate and correct the error - note)

10 PSP4a C2 time log  This is a time log that I kept while design a programming problem and producing a solution  My values

11 PSP4a Class Discussion  Where my categories good?  What would have been better categories?  Any knowledge from this time log?

12 PSP4a Process Improvement  1. Measure  2. Evaluate  3. Modify  Repeat steps 1-3

13 PSP4a Planning is essential  You can estimate the effort required for your next project  Accurate estimation comes only with practice.  Estimate the next and then keep log to evaluate and improve estimates

14 PSP4a Personal Estimation  The past is the best estimate of the future  Find some size measure of the product –e.g. loc, number of classes, number of functions –determine your productivity based on size –estimate size of next task –calculate effort estimate

15 PSP4a Group Discussion  How can we manage our time more effectively?  How can we manage our team members’ time more effectively?  How can we use PSP to improve our team members’ performance?

16 PSP4a Class Discussion  What can we learn from a time log of our studying?  What categories would be good for studying?

17 PSP4a L4aS17 time log  Keep a time log of your class work for the next week – 6/19 to 6/26  Develop an extensive set of categories  Summary including pie charts and productivity  Turn in your log and an evaluation, summary on 6/27 (on and off)