Chief Programmer Team
F. T. Baker
Abstract
F. T. Baker
Abstract
Abstract The Chief Programmer Team organization and methodology are aimed at improving software quality and manageability. It was conceived in the late 1960s as a response to increasing cost and schedule problems in the development of large software systems, primarily due to the inability of the software development methods of the time to cope with the greater levels of complexity such systems required. The chief programmer would be the team's leader, a highly skilled programmer personally resposible for all aspects of developing a substantial programming project. The backup programmer would be an assistant chief programmer.
OpenAlex reports 7 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Abstract The Chief Programmer Team organization and methodology are aimed at improving software quality and manageability. It was conceived in the late 1960s as a response to increasing cost and schedule problems in the development of large software systems, primarily due to the inability of the software development methods of the time to cope with the greater levels of complexity such systems required. The chief programmer would be the team's leader, a highly skilled programmer personally resposible for all aspects of developing a substantial programming project. The backup programmer would be an assistant chief programmer.
Key concepts: Programmer, Computer science, Backup, Schedule, Software engineering, Software development, Software, Operating system