Your source is maintained in an industrial strength database with full transactional integrity. There is NO NEED for DATABASE ADMINISTRATION. Most SCM tools use simple flat files in which to store your source and versioning information, this leads to very limited scalability situations and is complicated by security and other file system related problems. | |||
Your source can be in any format you want, be it text, binary, graphics or web pages to name but a few. | |||
Of course, since most source code is text there are some features specific to enhancing text file development processes - | |||
|
|||
Complete set of source code management utilities including: | |||
Check in |
|||
Common (Across branches) | |||
Uncommon (Main line) | |||
Check out | |||
Read-only | |||
Edit common(top version) | |||
Edit uncommon(branching) | |||
Recommon (branch merging) | |||
Merge (branch reconciliation without branch termination) |
|||
Complete set of release management tools including | |||
|
|||
Complete set of reports for both the developers and the managers. Some examples include | |||
Report on CRs currently assigned to a user |
|||
Report on CRs assigned to a release |
|||
Report of all CRs assigned to a user within specified date |
|||
List all CRs created by a user for a given date range |
|||
Report all assigned CRs by state, severity and/or date |
|||
Report all CRs currently outstanding at specified severity | |||
Report all files currently checked out for edit by a user | |||
Report all CRs currently outstanding |