There are three main elements to the Razor tool suite.
- Issues: a problem tracking system; provides a mechanism for organizing, coordinating, and tracking various tasks or issues through a site-defined life cycle.
- Versions: a file version control system; used to archive and monitor the evolution of changes made to files over the duration of a project. It is conceptually similar to SCCS or RCS.
- Threads: a build management tool; through this tool, users are able to define and track large groups of files as a single unit.
Although often seen as an "engineer's" tool, Razor's scope is easily extended to aid anyone within an organization. Its highly configurable interface allows for easy integration into a wide variety of environments. Its pieces can be used together or independently to best suit your needs.
Product highlights include...
- Highly configurable graphical interface makes insertion into existing customer processes simple.
- Command line interface allows for imbedding Razor actions into shell scripts.
- Ability to easily import existing SCCS and RCS investments into Razor.
- Uses either SCCS or RCS archival engines.
- Emphasizes e-mail interaction. Introduction of new issues, check-in/check-out of files, and database queries can be accessed via e-mail, simplifying interaction with customers and offsite personnel.
- Extremely easy to use; users typically need only minutes of training.
- Built on a non-proprietary, easily parsed, ASCII database which greatly simplifies the generation of site-specific query scripts.
- Attachment of user-defined actions both before and after tool events to implement process-specific requirements.
- Network-based client/server applications.
