2020Unpublished venueOpen access

Software Process: Applying Industrial Strength Methods In Engineering Education

Mark J. Sebern

Open full text 3 citations

Abstract

Improving productivity and quality in software development is one of the major concerns of the software engineering discipline, as software systems grow to millions, and soon billions, of lines of code.Productivity and defect density levels that are considered very good today will be inadequate to keep up with this future growth.As a result, software development professionals and organizations are striving to improve existing processes and to develop new ones.One example of demonstrated benefits from these efforts is the success of the Personal Software Process (PSP) and the Team Software Process (TSP) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University.This paper discusses the structure of the TSP and PSP processes, industry experiences with their application, and their relationship to other process improvement frameworks, including the current version of the SEI's Capability Maturity Model (now known as CMMI).With this background, it reflects on the introduction of the PSP and TSP into software engineering curricula, and reports experiences at the Milwaukee School of Engineering, one of the first four ABET-accredited software engineering programs.

Open-access reader

About this research paper

What this paper is about

Improving productivity and quality in software development is one of the major concerns of the software engineering discipline, as software systems grow to millions, and soon billions, of lines of code.Productivity and defect density levels that are considered very good today will be inadequate to keep up with this future growth.As a result, software development professionals and organizations are striving to improve existing processes and to develop new ones.One example of demonstrated benefits from these efforts is the success of the Personal Software Process (PSP) and the Team Software Process (TSP) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University.This paper discusses the structure of the TSP and PSP processes, industry experiences with their application, and their relationship to other process improvement frameworks, including the current version of the SEI's Capability Maturity Model (now known as CMMI).With this background, it reflects on the introduction of the PSP and TSP into software engineering curricula, and reports experiences at the Milwaukee School of Engineering, one of the first four ABET-accredited software engineering programs.

Why it matters

OpenAlex reports 3 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Improving productivity and quality in software development is one of the major concerns of the software engineering discipline, as software systems grow to millions, and soon billions, of lines of code.Productivity and defect density levels that are considered very good today will be inadequate to keep up with this future growth.As a result, software development professionals and organizations are striving to improve existing processes and to develop new ones.One example of demonstrated benefits from these efforts is the success of the Personal Software Process (PSP) and the Team Software Process (TSP) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University.This paper discusses the structure of the TSP and PSP processes, industry experiences with their application, and their relationship to other process improvement frameworks, including the current version of the SEI's Capability Maturity Model (now known as CMMI).With this background, it reflects on the introduction of the PSP and TSP into software engineering curricula, and reports experiences at the Milwaukee School of Engineering, one of the first four ABET-accredited software engineering programs.

Key concepts: Software Engineering Process Group, Personal software process, Software development, Software engineering, Capability Maturity Model Integration, Social software engineering, Team software process, Accreditation

Related papers

Back to paper searchBrowse research topicsOriginal source
Software Process: Applying Industrial Strength Methods In Engineering Education — Research Paper | ScholarLens