What configuration management tools can be used for development with OPNET, and what type of files should be under revision control (pr.c/pr.m/nd.m...)?

What configuration management tools can be used for development with OPNET, and what type of files should be under revision control (pr.c/pr.m/nd.m...)?

Engineers at OPNET use configuration management tools in the model development processes.Most OPNET model files are binary (not pure ASCII) files, and therefore you should choose configuration management software that can handle revision control of such files. Tools like Rational's Clearcase and Microsoft's Visual SourceSafe are known to work with binary files. Please note that this should not be construed as an endorsement of any particular version control software product.You should place all OPNET model files under revision control except for the following files:*.pr.o (process model object file - result of compiling *.pr.c)*.ex.o (external source code object file - result of compiling *.ex.c)*.ps.o (pipeline stage object file - result of compiling *.ps.c)*.nt.so (network respository - resulting of linking *.o files)*.pr.c (process model source file - auto-generated from *.pr.m)*.pr.h (process model header file - auto-generated from *.pr.c)Files of particular interest to manage are*.m (Various model files like *.pr.m, *.nd.m, *.nt.m)*.prj (Project files - contain references to scenarios)*.seq (Simulation sequence files - referenced by projects)*.ex.c (External source code files referenced by other processes)*.ex.h (External source header files)*.ps.c (Pipeline stage source files)*.ps.h (Pipeline stage header files)

DES Kernel->Process Modeling/Coding