Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 7,522 papers for “Personal software process”

Personal Software Process Technology:

Iraj Hirmanpour, Soheil Khajenoori · 2015

Process improvements within software development occur at three different levels: the organizational level, the project/team level, and at the individual engineer-- or personal-- level. The Software Engineering Institute (SEI) of Carnegie Mellon University has developed process improvement models tailored to each of these levels. The Capability Maturity Model (CMM)3 deals with organization issues, the Team Software Process (TSP)1, currently under validation testing, address improvements in project or team development processes, and the Personal Software Process (PSP)1. The focus of this paper is on individual software engineer’s issues addressed by the PSP. The Personal Software Process (PSP) provides a framework that individual software engineers can use to define, instrument, and continuously improve their individual processes. After five years of experience in teaching PSP in both academic and industry settings, we have gained some insights into the challenges and rewards of transitioning this technology into an organization’s software development practices. Our industrial experiences included work with the Motorola Paging Products Group; Boeing Corporation’s Space Division and the Naval Oceanographic Office (NAVO). In this paper, we will relate our experiences with the transition of PSP technology into these three organizations. We will describe various approaches taken with industrial PSP training, and report data to validate the benefits of PSP. We will further describe some barriers to PSP training, the challenges of post-training activities, and offer conclusions about the transition process.

Cited by 0

Personal software improvement process

Bjarnason, Ebru Gunaydin · American University Research Archive · 2023

This thesis work documents the results of a study which examines the impact of the Personal Software Process (PSP) on the performance of software engineers, the methodology (Barker's method) employed throughout the development of the automated PSP prototype, and significance of engaging in Web technology. It describes the effects of PSP on key performance dimensions of engineers, including their ability to estimate and plan their work, their work process and productivity. An automated Intranet application to support PSP approach was developed as a prototype in this thesis work by utilizing Barker's method throughout the system development life cycle. This body of work examines the feasibility and benefits provided by Intranet technology, and integration of Intranet technology with database applications. As a means of evaluation, the prototype was compared and contrasted with a manual PSP system.

Cited by 0Open access

Personal software process (PSP) assistant

Raymund Sison · 2005

The personal software process (PSP) is a process and performance improvement method aimed at individual software engineers. The use of PSP has been shown to result in benefits such as improved estimation accuracy and reduced defect density of individuals. However, the experience of our institute and of several others is that recording various size and defect data can be onerous, which in, turn can lead to adoption and data quality problems. This paper describes a system that we have developed that performs automatic size and defect recording, aside from providing facilities for viewing and editing the usual PSP logs and reports. Moreover, the system automatically classifies and ranks defects, and then consolidates schedules and defect lists of individual developers into a schedule and defect library for the developers' team.

Cited by 27

Personal Software Process (PSP) Scriber

Heng-Jui Tsao · CSUSB ScholarWorks (California State University, San Bernardino) · 2002

Personal Software Process (PSP) Scriber is a Web-based software engineering tool designed to implement an automatic system for performing PSP. The basis of this strategy is a set of tools to facilitate collection and analysis of development data. By analyzing the collected data, the developer can make informed, accurate decisions about their individual development effort.

Cited by 0Open access

Software defect detection and process improvement using personal software process data

M. Gopichand, V. Swetha, A. Ananda Rao · 2010

Statistical evidence has shown that programmers perform better when following a defined, repeatable process such as the Personal Software Process (PSP).Anecdotal and qualitative evidence from industry indicates that two programmers working side-by-side at one computer, collaborating on the same design, algorithm, code, or test, perform substantially better than the two working alone i.e. pair programming. Bringing these two ideas together, a new Software Process has been formulated. The Hybrid Personal Software Process (HPSP) is a defined, repeatable process for two programmers working collaboratively. The development time and cost of the product are reduced in HPSP when compared with PSP programming.

Cited by 4

The personal process in software engineering

Watts S. Humphrey · 2002

The personal software process (PSP) provides software engineers a way to improve the quality, predictability, and productivity of their work. It is designed to address the improvement needs of individual engineers and small software organizations. A graduate level PSP course has been taught at six universities and the PSP is being introduced by three industrial software organizations. The PSP provides a defined sequence of process improvement steps coupled with performance feedback at each step. This helps engineers to understand the quality of their work and to appreciate the effectiveness of the methods they use. Early experience with the PSP shows that average test defect rate improvements of ten times and average productivity improvements of 25% or more are typical.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

Cited by 7

Factors influencing a personal software process

Zhong, Xiaoming, 1971- · eScholarship@McGill (McGill) · 1999

Following the development of Personal Software Process (PSP) by Humphrey, a number of efforts have been made to study the impact of PSP on the improvement of software quality and productivity. However, most of such studies have focused on the results of the execution of PSP. Little attention has been paid to the underlying factors that influence the output of the execution of PSP. By investigating which factors influence the output, and how, we would have an improved understanding of PSP, which, in turn, could lead to improvement of the design of PSP and hence of personal software process.

Cited by 0Open access

Introduction to the Personal Software Process

Watts S. Humphrey · CERN Document Server (European Organization for Nuclear Research) · 1996

This newest book from Watts Humphrey is a hands-on introduction to basic disciplines of software engineering. Designed as a workbook companion to any introductory programming or software-engineering text, Humphrey provides here the practical means to integrate his highly regarded Personal Software Process (PSP) into college and university curricula. The book may also be adapted for use in industrial training or for self-improvement by practicing software engineers.Applying the book's exercises to their course assignments, students learn both to manage their time effectively and to monitor the quality of their work, good practices they will need to be successful in their future careers. The book is supported by its own electronic supplement, which includes spreadsheets for data entry and analysis. A complete instructor's package is also available.By mastering PSP techniques early in their studies, students can avoid--or overcome--the popular hacker ethic that leads to so many bad habits. Employers will appreciate new hires prepared to do competent professional work without, as now is common, expensive retraining and years of experience.

Cited by 420

AUTOMATING A MODIFIED PERSONAL SOFTWARE PROCESS

Mohd Hairul, Nizam Md. Nasir, Azwina M. Yusof · 2015

Personal Software Process (PSP) is a defined software development framework that includes defined operations, measurement and analysis techniques to assist software engineers to understand and build their own skills in order to improve their own personal performance. Even though several published studies have suggested that adopting PSP results in improved size and time estimation, and improved numbers of defects found in the compiled and test phases of software development, nevertheless not every software engineer adopts PSP in the process of software development.This paper attempts to clarify the issues that influence the adoption of PSP and explain how an automated tool can address these problems. The PSP adoption issue has been identified to be due to four reasons; 1) overhead in data collection and analysis, 2) excessive use of forms combined with a lack of a fully automated tool, 3) freezing of process definition, and 4) privacy issue. This paper describes an automated web based application tool to support the adoption of PSP in software development, called PSP.NET. This fully-automated tool can simplify both data collection and analysis to make this discipline more manageable and organized, with added features to make it more flexible, such as anti freezing of process definition, privacy support and collaborative sharing of defect information.

Cited by 0

The Personal Software Process (PSP) tutorial

Watts S. Humphrey, Jim Over · 2003

The PSP paradigm is based on process improvement principles. Practitioners establish personal process goals. They define the methods that they will use. They measure their work and analyse the results. Based on these analyses, they adjust their methods to better meet their personal goals.

Cited by 3

Amalgamation of Personal Software Process in Software Development Practice

AK Khan · Science Technology and Arts Research Journal · 2013

Today, concern for quality has become an international movement. Eventhough most industrial organizations have now adopted modern qualityprinciples, the software community has continued to rely on testing as theprincipal quality management method. Different decades have different trends in software engineering. The Personal Software Process (PSP) is anevolutionary series of personal software engineering techniques that an engineer learns and practices. A software process is nothing without theindividual programmer. PSP a data driven process customized to teaching individuals about their programming styles, helping software engineers further develop their skills in developing quality software. Apart from discussing about PSP as a framework of techniques to help engineers and their organizations to improve their performance while simultaneously increasing product quality, in this paper, the Personal Software Process definition, principles, design, advantages and opportunities are explained focusing on the incorporation of PSP concepts in software development practice.

Cited by 2Open access

The Personal Software Process in Undergraduate Software Engineering Education

A. L. Brown, M. J. Oudshoorn, K.J. Maciunas · 1997

The Personal Software Process, PSP, was developed at Carnegie Mellon University&amp;apos;s Software Engineering Institute as a personal version of the Capability Maturity Model. The intention of the PSP is to educate individual software engineers in the processes they follow in completing a programming task with a view to improving the quality of future work. At each level of the PSP more and more useful personal statistics are kept. This starts with simple time keeping and error reporting statistics, and is later augmented by recording code size and self-improvement plans. At its deepest level, the process involves evolving a personalised version of the PSP. It is estimated to take 400 hours to complete the entire PSP course at the graduate level. Clearly, this would impose an extreme burden on an undergraduate curriculum if it was taught as a whole. Indeed the PSP is aimed at practising software engineers and in its more sophisticated forms would be beyond the scope of an undergraduate degree...

Cited by 0

Towards an Integrated Personal Software Process and Team Software Process Supporting Tool

Ho-Jin Choi, Sang-Hun Lee, Syed Ahsan Fahmi et al. · IGI Global eBooks · 2013

Personal Software Process (PSP) and Team Software Process (TSP) have been developed and used to help individual developers and teams make high-quality products through improving their personal and team software development processes. For the PSP and TSP practices, data collection and analysis of software metrics need to be done at fine-grained levels. These tasks are not trivial, requiring tool support. This chapter aims to discuss issues to building such a tool, and introduce our on-going endeavor towards an integrated PSP and TSP supporting tool. In particular, features of sensor-based automated data collection for PSP, utilization of Six Sigma techniques into PSP and TSP activities, and incorporation of electronic process guide will be paid attention.

Cited by 0