The Personal Software Process-SM (PSP-SM) Body of Knowledge, Version 1.0

Pomeroy-Huff, Marsha; Mullaney, Julia; Cannon, Robert; Seburn, Mark

doi:10.21236/ada636411

Cited by 11 publications

(18 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The PQI takes into account five components [5]: − The ratio of design time to coding time (Design to Code Ratio), which provides an indication of design quality, and is recommended to be at least 100%; − The ratio of design review time to design time (Design Review to Design Ratio), which provides an indication of design review quality, and is recommended to be at least 50%; − The ratio of code review time to coding time (Code Review to Code Ratio), which provides an indication of code review quality, and is recommended to be at least 50%; − The ratio of compile defects to a size measure (Defect Density in Compile), which provides an indication of code quality, and is recommended to be less than 10 defects/KLOC; − The ratio of unit test defects to a size measure (Defect Density in Unit Test), which provides an indication of program quality, and is recommended to be less than 5 defects/KLOC.…”

Section: Qualitymentioning

confidence: 99%

“…In these cases, benchmarkbased thresholds were first computed based on rounded terciles and subsequently cross-checked and refined by comparison with literature. For example, according to [5], DDUT should be less than 5 defects/KLOC for high performance, but only 20% of the data points lays in the [0, 5] range, so we considered a wider [0, 10] 'green' range instead, containing 31% of the data points.…”

Section: Derivation Of Performance Rangesmentioning

confidence: 99%

“…The Team Software Process (TSP) and the accompanying Personal Software Process (PSP) are examples of methodologies that can help individuals and teams improve their performance and produce virtually defect free software on time and budget [2] [3] [4], addressing current software development challenges. One of the pillars of the TSP/PSP is its measurement framework: based on four simple measures -effort, schedule, size and defects -it supports several quantitative methods for project management, quality management and process improvement [5].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A model for analyzing estimation, productivity, and quality performance in the personal software process

Raza

Faria

2014

Proceedings of the 2014 International Conference on Software and System Process

View full text Add to dashboard Cite

High-maturity software development processes, making intensive use of metrics and quantitative methods, such as the TSP/PSP, can generate large amounts of data that can be periodically analyzed to identify performance problems, determine their root causes and devise improvement actions. However, there is a lack of tool support for automating that type of analysis, and hence diminish the manual effort and expert knowledge required. So, we propose in this paper a comprehensive performance model, addressing time estimation accuracy, quality and productivity, to enable the automated (tool based) analysis of performance data produced in the context of the PSP, namely, identify performance problems and their root causes, and subsequently recommend improvement actions. Performance ranges and dependencies in the model were calibrated and validated, respectively, based on a large PSP data set referring to more than 30,000 finished projects.

show abstract

Section: Qualitymentioning

confidence: 99%

Section: Derivation Of Performance Rangesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A model for analyzing estimation, productivity, and quality performance in the personal software process

Raza

Faria

2014

Proceedings of the 2014 International Conference on Software and System Process

View full text Add to dashboard Cite

show abstract

“…On the other hand, the introduced content of PSP0 in Table 1 is divided into 23 contents based on the grading checklists. This introduced content † † also corresponds largely to the key concepts and key skills defined in PSP BOK [18]. Table 4 gives factors that represent the state of the motivation process and the state sets of factors.…”

Section: Factors and State Sets In The Psp Coursementioning

confidence: 99%

Motivation Process Formalization and Its Application to Education Improvement for the Personal Software Process Course

Umeda

Katamine

Ishibashi

et al. 2014

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

Masanobu UMEDA†a) , Nonmember, Keiichi KATAMINE †b) , Member, Keiichi ISHIBASHI † †c) , Nonmember, Masaaki HASHIMOTO †d) , Fellow, and Takaichi YOSHIDA †e) , Nonmember SUMMARY Software engineering education at universities plays an increasingly important role as software quality is becoming essential in realizing a safe and dependable society. This paper proposes a practical state transition model (Practical-STM) based on the Organizational Expectancy Model for the improvement of software process education based on the Personal Software Process (PSP) from a motivation point of view. The Practical-STM treats an individual trainee of the PSP course as a state machine, and formalizes a motivation process of a trainee using a set of states represented by factors regarding motivation and a set of operations carried out by course instructors. The state transition function of this model represents the features or characteristics of a trainee in terms of motivation. The model allows a formal description of the states of a trainee in terms of motivation and the educational actions of the instructors in the PSP course. The instructors are able to decide effective and efficient actions to take toward the trainees objectively by presuming a state and a state transition function of the trainees formally. Typical patterns of state transitions from an initial state to a final state, which is called a scenario, are useful for inferring possible transitions of a trainee and taking proactive operations from a motivation point of view. Therefore, the model is useful not only for improving the educational effect of the PSP course, but also for the standardization of the course management and the quality management of the instructors. key words: personal software process, motivation, state transition model, organizational expectancy model, education improvement IntroductionSociety depends on many devices and services realized by software. Software defects can lead to not only inconvenience and the loss of business opportunity but also problems relating to information security and safety. Software quality is essential to business success and a safe and dependable society.The Personal Software Process (PSP) [1], [2] developed by Watts S. Humphrey is a self-improvement process that a software engineer can employ to manage his/her own development process by him/herself and to improve his/her software quality using his/her own process data. To sat- * , significantly improved during the course. These results show that it is possible for graduate students to acquire knowledge and skills required for the improvement of software quality, and reveal that the PSP is an effective tool for such purpose. However, not all trainees were able to complete the course [10]. For example, only about 20 percent of the trainees completed the course in recent school years, while it is said that about 50 percent of experienced software engineers in industries complete. The low completion rate of the course is undesirable in terms of not only the inefficiency...

show abstract

“…En la actualidad, la industria dispone de modelos ampliamente aceptados como elementos de apoyo en el ejercicio de mejoramiento continuo de fábricas de software, tales como el Modelo Integrado de Capacidad y Madurez (CMMI) en su versión Development (CMMI Product Team, 2010), y los procesos Personal Software Process (PSP) (Pomeroy-Huff et al, 2009) y Team Software Process (TSP) (Humphrey et al, 2010). Todos ellos han evolucionado con la preocupación por definir procesos dedicados al componente de ingeniería inherente a las fábricas de software (herramientas, tecnologías, metodologías, entre otros).…”

Section: Introductionunclassified

Modelo de Relacionamiento Estratégico entre Factores Organizacionales y Técnicos en Fábricas de Software Colombianas

Cerón

Arboleda

2018

Inf. tecnol.

View full text Add to dashboard Cite

_____________________________________________________________________________________________________________________________________ ResumenSe presenta un modelo para conciliar la gestión del desarrollo de software y la gestión organizacional mediante el relacionamiento de factores asociados a la producción en fábricas de software y factores administrativos, alineando métricas de operación con los objetivos estratégicos de las fábricas. Otros autores han propuesto modelos tales como el Integrado de Capacidad de Madurez (CMMI), el de Procesos de Software Personal (PSP), o el Proceso de Software para Equipos (TSP), para apoyar el mejoramiento continuo de fábricas de software. De manera paralela, la gestión organizacional ha consolidado el desarrollo misional de empresas en diferentes sectores, a través del ejercicio de planeación estratégica y su despliegue. La propuesta presentada en este artículo proporciona una herramienta, complementaria a aquellas que sirven como soporte para desarrollo y despliegue de planeación estratégica destinada al apoyo de ejecutivos de fábricas de software. El resultado de esta propuesta fue validado en cuatro fábricas de software con diferentes niveles de madurez. AbstractA model is presented to reconcile the management of software development and organizational management through the relationship of factors associated with production in software factories and administrative factors, aligning operational metrics with the strategic objectives of the factories. Other authors have proposed models such as the Integrated Maturity Capability (CMMI), the Personal Software Processes (PSP), or the Software for Equipment (TSP), to support the continuous improvement of software factories. In parallel, the organizational management has consolidated the missionary development of companies in different sectors, through the exercise of strategic planning and its deployment. The proposal presented in this article provides a tool, complementary to those that serve as support for the development and deployment of strategic planning for the convenience of executives of software factories. The result of this proposal was validated in four software factories with different levels of maturity.

show abstract

The Personal Software Process-SM (PSP-SM) Body of Knowledge, Version 1.0

Cited by 11 publications

References 1 publication

A model for analyzing estimation, productivity, and quality performance in the personal software process

A model for analyzing estimation, productivity, and quality performance in the personal software process

Motivation Process Formalization and Its Application to Education Improvement for the Personal Software Process Course

Modelo de Relacionamiento Estratégico entre Factores Organizacionales y Técnicos en Fábricas de Software Colombianas

Contact Info

Product

Resources

About