Personal software process: Difference between revisions

Revision as of 19:36, 2 August 2023

Latest revision as of 09:25, 5 February 2025

(3 intermediate revisions by 3 users not shown)

Line 1:

{{Short description|Process to improve programming quality}}

{{More footnotes needed|date=August 2023}}

{{Software development process}}

[[File:PSP_Task_Overview_form_(image).png|thumb|Image of a PSP Task Overview form.]]

The '''Personal Software Process''' ('''PSP''') is a structured [[software development]] process that is designed to help [[software engineer]]s better understand and improve their performance by bringing discipline to the way they develop software and tracking their predicted and actual development of the code. It clearly shows developers how to manage the quality of their products, how to make a sound plan, and how to make commitments. It also offers them the data to justify their plans. They can evaluate their work and suggest improvement direction by analyzing and reviewing development time, defects, and size data. The PSP was created by [[Watts Humphrey]] to apply the underlying principles of the [[Software Engineering Institute]]'s (SEI) [[Capability Maturity Model]] (CMM) to the software development practices of a single developer. It claims to give software engineers the process skills necessary to work on a [[team software process]] (TSP) team.

Line 21 ⟶ 23:

;PSP0, PSP0.1 (Introduces process discipline and measurement)

PSP0 has 3 phases: planning, development (design, code, compile, test) and a post mortem.

A baseline is established offor current process measuring: time spent on programming, faults injected/removed, and size of a program.

In a post mortem, the engineer ensures all data for the projects has been properly recorded and analysed.

PSP0.1 advances the process by adding a coding standard, a size measurement and the development of a personal process improvement plan (PIP). In the PIP, the engineer records ideas for improving his own process.

Line 125 ⟶ 127:

==Certification==

A certification covering PSP is offered by the SEI at Carnegie Mellon University. The steps to becoming an SEI-Certified PSP Developer are: learn the PSP; take the certification exam; maintain credentials.

The PSP Developer examination is based on concepts found in the PSP Body of Knowledge.<ref name=PSP-BOKv2>{{cite book|last1=Pomeroy-Huff|first1=Marsha|last2=Cannon|first2=Robert|last3=Chick|first3=Timothy A.|last4=Mullaney|first4=Julia|last5=Nichols|first5=William|title=The Personal Software Process (PSP) Body of Knowledge, Version 2.0|date=2009|publisher=[[Software Engineering Institute]], [[Carnegie Mellon University]]|___location=Pittsburgh, Pennsylvania|url=http://resources.sei.cmu.edu/asset_files/SpecialReport/2009_003_001_15029.pdf|access-date=17 November 2014}} Freely downloadable Special Report CMU/SEI-2009-SR-018, 2009</ref> The SEI maintains an [[FAQ]]<ref name=":0">{{cite web | title=SEI-Certified PSP Developer: Frequently Asked Questions | work=[http://www.sei.cmu.edu/training/ SEI Training] | publisher=[[Software Engineering Institute]], [[Carnegie Mellon University]] | ___location=Pittsburgh, Pennsylvania | url=http://seicertification.clearmodel.com/get-certified/software-development/become-an-sei-certified-psp-developer/sei-certified-psp-developer-frequently-asked-questions/ | access-date=17 November 2014 | url-status=dead | archive-url=https://web.archive.org/web/20141129020408/http://seicertification.clearmodel.com/get-certified/software-development/become-an-sei-certified-psp-developer/sei-certified-psp-developer-frequently-asked-questions/ | archive-date=29 November 2014 }}</ref> on certification.

==See also==