H_shemisone@yahoo.com "Yaakov" writes:
Are people using formal Version Control systems for embedded applications? If you're using something other than a nightly backup to the network server, I'd like to know what it is. Might want to formalize something where I work
Having viewed some of the answers you have already received on this
topic I will chip in and mention a commercial package. This is
actually a combination of two packages, one for the version management
side of the task, the other for the change management side.
MKS Source Integrity - RCS based version management
MKS Track Integrity - Change management database/logger.
(see http://www.mks.com/)
Both of these products working together implement the flowchart of
process management that is featured on my website and automates the
four forms and one register aspect of that process.
Of course, you only need a commercial package like the MKS products
if you have a largish team of people working on the project. I am
sure that the freely available tools will do some of the work of
the above packages. In small teams it is even possible to do the
job manually. However, run version and change management you must.
As someone else has aleady indicated, the use of a version control
system is not just for embedded source code. Version control should
be an integral part of the development process and cover all aspects
of design and manufacture.
--
********************************************************************
Paul E. Bennett ....................<email://peb@amleth.demon.co.uk>
Forth based HIDECS Consultancy .....<http://www.amleth.demon.co.uk/>
Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE......
Tel: +44 (0)1235-811095 .... see http://www.feabhas.com for details.
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************