I am doing a feasibility study to see if SVN can be used for maintaining a DO-178B/C project. Most of the DO178 projects I have seen uses CVS or similar configuration management tool which maintain versions for each file separately (which is not same as SVN). Here are some of the derived objectives for configuration management which are required by my project:
- For each file, complete modification history shall be available.
- There should be a way to prove that each version of file has been proofread. This demands that there should be a way to list all the modifications done on particular file since some previous TAG.
- For each modification done, a grouping should be possible by which I can figure out which files were modified for a common requirement. Normally we use a hashtag for each modification done in modification history comments. If same hashtag occurs in multiple files, they belong to same group.
- Finally a configuration index report should be available which lists the summary for each file modification independently since some already existing TAG. Normally this summary involves the baseline version of file, and then for each modification done since, list of hashtags for each modification and then the final version.
Does anyone know how can I use SVN so that i am still able to provide these reports to the software auditors.
Any CM tool can be used as long as all the SCM Process Objectives in Table 7-1 are satisfied. I think SVN can be used but cannot achieve all objectives. We also need other tool like Jira to do change control and problem reporting.