Uploaded July 2026 | Updated September 2026, 18 hours ago
This is the first podcast in a new series introducing the concept of Software Configuration Management (CM), explaining that it is a systematic method for ensuring the consistency of a system's attributes throughout its lifecycle by identifying and tracking every component, version, and dependency.
We emphasize that CM tools are crucial for reliable reproduction, auditing, and rollback of a system by maintaining a "single source of truth."
We look at the practical starting point of a new software development project, stressing the critical importance of creating a detailed customer requirement document, which acts as the product's blueprint for development and testing.
Finally, we suggest that the first necessary CM tool is a system, such as a Requirements or Issue Management platform, to manage and track these requirements and subsequent change requests as the project potentially evolves across multiple developmental phases.
This podcast is based on youtu.be/udGnxwMA4-Y and is based on a background of over 20 years experience in Configuration Management.
AI was used to assist in the creation of this video.
Source files and an Index to all our YouTube videos are accessible from here
gsfsoftware.co.uk/PBTutorials/Projects.htm
I don't work for, nor am I paid by, or sponsored by, the owners of PowerBASIC or any other company mentioned in this podcast, I'm just a fan of their products.
For more information on PowerBASIC visit
pbusers.org
OR
pump.richheimer.de/index.php
Music by ghosthack.de
This is the first podcast in a new series introducing the concept of Software Configuration Management (CM), explaining that it is a systematic method for ensuring the consistency of a system's attributes throughout its lifecycle by identifying and tracking every component, version, and dependency.
We emphasize that CM tools are crucial for reliable reproduction, auditing, and rollback of a system by maintaining a "single source of truth."
We look at the practical starting point of a new software development project, stressing the critical importance of creating a detailed customer requirement document, which acts as the product's blueprint for development and testing.
Finally, we suggest that the first necessary CM tool is a system, such as a Requirements or Issue Management platform, to manage and track these requirements and subsequent change requests as the project potentially evolves across multiple developmental phases.
This podcast is based on youtu.be/udGnxwMA4-Y and is based on a background of over 20 years experience in Configuration Management.
AI was used to assist in the creation of this video.
Source files and an Index to all our YouTube videos are accessible from here
gsfsoftware.co.uk/PBTutorials/Projects.htm
I don't work for, nor am I paid by, or sponsored by, the owners of PowerBASIC or any other company mentioned in this podcast, I'm just a fan of their products.
For more information on PowerBASIC visit
pbusers.org
OR
pump.richheimer.de/index.php
Music by ghosthack.de
