Software Assurance Common Body Of Knowledge. We used SWEBOK in our work but we also needed a similar body of knowledge for software assurance. For that reason in 2005 the US.
The first books enumerating steps to produce software appeared in the early 1960. A Curriculum Guide to the Common Body of Knowledge to Produce Sustain and Acquire Software CBK resulted in a guide of. Because that knowledge base is structured on the most commonly accepted model for secure software assurance practice the DHS Common Body of Knowledge this mapping provides precise guidance about where the newly developed instructional content fits within the commonly accepted understanding of the correct elements of practical software assurance work.
It provides a solid taxonomy of terms and practices that has been accepted by academia industry and government.
For that reason in 2005 DHS created a working group to define a Common Body of Knowledge CBK for Secure Software Assurance. The profession is charged with the responsibility for tactical process improvement initiatives that are strategically aligned to the goals of the organization. For that reason in 2005 DHS created a working group to define a Common Body of Knowledge CBK for Secure Software Assurance. Software Assurance Common Body of Knowledge Workshop.