Personal Software Process

International Conference on Emerging Practices in Software Process & Architecture (SOFTPA 2022) is an emerging practice in Software Development life cycle adopted by various software organizations to develop an environment of continuous deployment and delivery within time. There are several software development processes that practice the concept of continuous improvement and automation to maintain the operational stability and smooth flow of software delivery.

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...

Over the years software quality is becoming more and more important in software engineering. Like in other engineering disciplines where quality is already a commodity, software engineering is moving into these stages. The Team Software Process (TSP) was created by the Software Engineering Institute (SEI) with the main objective of helping software engineers and teams to ensure high-quality software products and improve process management in the organization. This paper presents a methodology for ...

The Constructive Cost Model COCOMO II and the PROxy Based Estimating model PROBE, were validated and calibrated based on short-term software projects developed by twenty one organizations at four cities in the central-west Colombian region, Manizales, Pereira, Armenia y Cali. The software development was embedded within a workshop based on the Personal Software Process PSP that last four weeks and includes work in class and work outside class. The COCOMO II statistical analysis includes the validation of the existing COCOMO II 1997 and 2000 calibrations, and the calibration of COCOMO II 2000 using CALICO. The PROBE statistical analysis produces object categories for Java and Php programming languages, regarding function and size, but cannot validate existing categories for Object Pascal and C++.

Many software development organizations struggle to make informed decisions when investing in new software technologies. The authors' experimental framework can help companies evaluate a new software technology by examining its features in relation to its peers and competitors through a systematic approach that includes modeling experiments

High-maturity software development processes, making intensive use of metrics and quantitative methods, such as the Personal Software Process (PSP) and the Team Software Process (TSP), can generate a significant amount of data that can be periodically analyzed to identify performance problems, determine their root causes and devise improvement actions. Currently, there are several tools that automate data collection and produce performance charts for manual analysis in the context of the PSP/TSP, but practically no tool support exists for automating the data analysis and the recommendation of improvement actions. Manual analysis of this performance data is problematic because of the large amount of data to analyze and the time and expertise required. Hence, we propose in this paper a performance model and a tool (named PSP PAIR) to automate the analysis of performance data produced in the context of the PSP, namely, identify performance problems and their root causes, and recommend improvement actions. The work presented is limited to the analysis of the time estimation performance of PSP developers, but is extensible to other performance indicators and development processes.

Measures represent important data in all engineering disciplines. This data allows engineers to understand how things work and how to make changes to produce desired results. In software engineering, it is difficult to collect useful measures because developers do not consider it an important activity, compared to coding. Moreover, manual collected data is often affected by errors, making it unusable. The shortage of automated tools for collecting and analyzing measures does not contribute to the evolution of software engineering. We present PROM (PRO Metrics), an automated tool for collecting and analyzing software metrics as well as personal software process (PSP) data. The tool uses an architecture based on plug-ins that automatically collects data from development tools.

Improvement of the business cycle plays a very significant role in the product growth, rendering it successful for production teams, and utilizing the same collection of activities[1]. SPI is a really major task for companies to survive in a dynamic world to understand different changing functionalities such as developments in the market, shifts in the organizational level to unplanned adjustments, and eventually enhance product quality[3]. Improvement of the software platform is not introduced at a single point, but is a continuous and iterative method over the development cycle that allows to reach a high degree of maturity[4].

(U) This paper is an overview of the process improvement efforts of the Naval Air Systems Command’s (NAVAIR) Air 4.0, Research and Engineering Competency. It focuses on 24 software engineering teams within the U.S., and specifically on the six teams that were early adopters: the AV-8B Joint System Support Activity; the E-2C, EA-6B, P-3C, and Tactical Aircraft Electronic Warfare Software Support Activities; and the F/A-18 Software Development Task Team. These teams ranged in size from less than 10, to more than 70 NAVAIR software engineers and support contractors. The process improvement efforts described in this paper began in the 1990s and early 2000s. Their process improvement tool sets included the Capability Maturity Model, the Capability Maturity Model (CMM)® Integration, the Personal Software Process (PSP), the Team Software Process (TSP), the Earned Value Management System (EVMS), the High Performance Organization, and the Team Software Process for Multiple Teams (TSPm)SM. 

(U) By 2005, the early adopters had achieved impressive results: the first CMM Level 5 rating in the Navy, the second EVMS certification in the Federal Government, two teams achieving CMM Level 4 in less than half the normal time, reductions in software defect densities between 22 and 48%, reductions in the variances of the actual cost and schedule to within 10% of the estimates, and two TSP software teams realizing a net combined savings of $2.746 million with the conclusion of their first TSP software development projects. These cost savings were six times the cost of AV-8B’s and P-3C’s investment in training and startup of PSP and TSP. 

(U) The successes that NAVAIR’s Air 4.0, Research and Engineering Competency, enjoyed helped to create a culture that is both interested in the continued pursuit and advancement of process improvement within its ranks, and desiring to spread process improvement to the larger organization.

This research covers the technical and soft skills required in  software  development,  a  globally  in-demand  activity.  These  skills  are  required  to  efficiently  perform  in  a  very globalized,  competitive  field.  Previous  studies  show  the existence  of  a  gap  between  industry  and  academia.  Training  centers  provide  professionals  with  technical  skills, but as of late, the need for soft skills has become apparent,  making  it  important  to  study  and  find  ways  to embed them into the professionals who join the industry. The  application  of  Personal  Software  Process  (PSP) methodology  helps  students  to  strengthen  their  skills  in  the software development process, however, the method is not widespread in academia nor industry.  This article shows  the  importance  of  soft  skills,  according  to  Latin  American companies, and how PSP can reduce the skills gap

In considering how the concept of Clean Code 1 could be summarised in a few words, the acronym SAD (Simple, Attractive, Dependable) was formed to suggest that code should be simple, well written and reliable. SAD isn't really specific as with some acronyms e.g. DRY (Don't Repeat Yourself), as you can look for repeated literals or code within a project and categorically say if it is WET (Write Everything Twice) or DRY. Like beauty, SAD is in the eye of the beholder. However, another acronym FURST was devised to fill this void to ensure that code is Fit for purpose, Unit tested, Reviewed, Standardised and Timely. This goes further than SAD in that it gives some more tangible expressions which can be checked or measured. FURST is not a complete end to end process but sets out what needs to be done rather than how to do it (in this regard like SCRUM). However, from it, checklists can be devised to be used at certain points within the development cycle and could be automated to some extent using toolchains.

TxP was created by NAVAIR to help non-software teams define their own customized team processes, similar to the TSP process enjoyed by software teams. It takes time for a team to define a customized team process, and during this time, postmortem analysis needs to evolve as the team’s customized process evolves. These postmortems will give the team the insight required to see where it has improved, and where it needs to focus its future improvement efforts on its way to standing up its customized team process.

This paper applies Personal Software Process (PSP) for software development activities, and uses PSP scripts to follow the activities in software development. In particular, we have adapted a development script in order to enable automatic traceability. The script is the cyclical process that is designed for developing a large program in a sequence of small incremental steps. Moreover, we have extended an XTraQue tool to enable an automatic traceability during using PSP. This enables the completeness of traceability during using PSP. The Part-of-Speech (POS) embedded XML-based templates of software artefacts for PSP-based development, that is, functional requirements (FR), use case, and class diagram are defined. We perform an explanatory case study in order to evaluate the effectiveness between manual and automatic traceability during the personal software process (PSP). In particular, the causal links between software artefacts created during software development are so-called traceability relations. The result evaluation are concerned with precision and recall measures on the creation of traceability relations.

This paper describes experiences over ten academic terms in teaching a course on software development processes. Significant lessons learned include: (1) supplementing general information on processes with a hands-on in-class process (personal software process, in this case); (2) using a tool to assist in collecting and managing process data to meet the learning needs (Excel spreadsheets, in this case); and (3) using the process data obtained in the course as a means of supporting accreditation objectives

The International Journal of Software Engineering & Applications (IJSEA) is a bi-monthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas.

This work describes a service oriented architecture of a software application that facilitates the implementation of the Personal Software Process by a development team or an organization. Some of the characteristics of this software and which are important to mention are extensibility and technical environment independence. These characteristics facilitate the process of adding new tools to the software development process integrating them to the Personal Software Process independently of the operating systems and programming languages being used. The implemented software undertakes the data collection necessary to the Personal Software Process almost automatically, since the administrator must only classify the errors that may occur when a particular programming language is used, among other small tasks. This ease of use approach helps to make the implementation of the Personal Software Process a success, requiring a low effort by the software development team members.

Personal Software Process (PSP) ultimately provides software en gineers an excellent framework and practice that can help them to improve the quality of their work, by analyzing their performance statistically and helping them to achieve realistic goals set by them. Besides, PSP offers many benefits to software engineers. However, through findings and studies, it is found that the Personal Software