1 / 32

Introduction to PSP

Personal Software Process Lecture 1. Introduction to PSP. Liubo Ouyang ouyangliubo@126.com http://ss.hnu.cn/oylb/psp/. Plan of the lecture. Introduction SPI CMM PSP Organisation of the course Summary. About Ireland. Population: ~ 4.0 million Second largest exporter of software

dwight
Télécharger la présentation

Introduction to PSP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Personal Software Process Lecture 1 Introduction to PSP Liubo Ouyang ouyangliubo@126.com http://ss.hnu.cn/oylb/psp/

  2. Plan of the lecture • Introduction • SPI • CMM • PSP • Organisation of the course • Summary

  3. About Ireland • Population: ~ 4.0 million • Second largest exporter of software • ~every global IT company has its branch in Dublin area • Revenue per IT worker: ~120 000 USD • Profit per IT worker: ~13 000 USD • Advantages of Ireland: English, cheap work force, on the edge of Europe, taxes

  4. Plan of the lecture • Introduction • SPI • CMM • PSP • Organisation of the course • Summary

  5. Software crisis OOP symptoms: Over time Over budget Poor quality Beginning: late 60’s Examples: OS 360, POLTAX, KSI ZUS ...

  6. Software Process Improvement • Structure vs. process • Business process improvement • ISO 9000, BPI  SPI • SPI: identify processes, define them, and improve them • Processes are like habits: difficult to introduce and even harder to break

  7. Plan of the lecture • Introduction • SPI • CMM • PSP • Organisation of the course • Summary

  8. What is CMM ? CMM = Capability Maturity Model CMM: a “way for organizations to determine the capabilities of their current processes and to establish priorities for improvement.” Software Engineering Institute (SEI), 1989-1993

  9. Levels of CMM 5. Optimising 3. Defined 4. Managed 2. Repeatable CMM 1. Initial

  10. Level 1 - Initial • Jazz and mess • A group of individuals instead of a team • Can be bad, can be great - depends on the fate CMM

  11. Level 2 - Repeatable • Requirements management • Software configuration management • Software quality assurance • Software project planning and oversight • Software project tracking • Software subcontract management CMM

  12. Level 3 - Defined • Peer reviews • Inter-group co-ordination • Software product eng. • Integrated software management • Training program • Software process definition • Software process focus CMM

  13. Level 4 - Managed • Quality management • Quantitative process management CMM

  14. Level 5 - Optimising • Process change management • Technology change management • Defect prevention CMM

  15. Plan of the lecture • Introduction • SPI • CMM • PSP • Organisation of the course • Summary

  16. What is PSP about ? PSP = PersonalSoftware Process PSP: self-improvement PSP: how to make and meet commitments PSP: forms + guidelines + procedures Watts Humphrey, SEI, 1995

  17. Levels of PSP 3. Cyclic personal process 2. Personal Quality Mgmnt 1. Personal Planning Process PSP 0. Baseline Personal Process

  18. Baseline Personal Process PSP0 • Current process • Time recording • Defect recording • Defect type standard PSP

  19. Baseline Personal Process PSP0.1 • Size measurement • Coding standard • Process improvement proposal PSP

  20. Personal Planning Process PSP1: • Size estimating • Test report PSP1.1: • Task planning • Schedule planning PSP

  21. Personal Quality Management PSP2: • Code reviews • Design reviews PSP2.1: • Design templates PSP

  22. Cyclic Personal Process Large projects (10 KLOC) Divide an conquer An incremental approach: 1. A base module 2. Enhancements (iterative cycles) Each iteration is a PSP2 PSP

  23. CMM and PSP PSP CMM

  24. What is PSP not about ? • Risk management? • Requirements analysis and specification? • Software configuration management? • Software modelling?

  25. Team Software Process (TSP) Large software and short time Too many details and interrelationships The habituation problem TSP: support from your peers (e.g. reviews)

  26. Plan of the lecture • Introduction • SPI • CMM • PSP • Organisation of the course • Summary

  27. Organization of the course The goal: to create a software organization (SDS) of CMM level 2. Requirements management Configuration management Quality assurance Project planning Project tracking & oversight

  28. Scope of the course (1) • Introduction to PSP • Developing an effective personality • Risk management • Software quality assurance (-) • Requirements management • Software configuration management • The baseline PSP (PSP 0 & 0.1) • Estimating software size (PSP 1)

  29. Scope of the course (2) • Time and schedule estimating (PSP 1.1) • Function points and COCOMO II • Project tracking and oversight • Software design (PSP 2.1) • Design and code reviews (PSP 2) • Software testing • Quality management and SPI

  30. Summary PSP is a self-improvement method PSP deals with: • Project planning • Software quality

  31. Further readings • W.S. Humphrey, A Discipline for Software Engineering, Addison-Wesley, 1995 • www.cmu.edu

  32. Quality assessment • What is your general impression ? (1 - 6) • Was it too slow or too fast ? • Did you learn something important to you ? • What to improve and how ?

More Related