Razor(R) Copyright 1992 - 2002 Visible Systems Corporation www.visible.com Thank you for trying Razor! GUIDE TO DEMO DATABASE ---------------------- With the release of Razor 4.2, we offer a demonstration database. This README is provided as a general overview of that database. As always, the Razor manual is the best source of information regarding Razor, and this README is meant to supplement the manual. This DEMO database is intended to give you a brief look at some of the things you can do with Razor. ISSUES (Problem Tracking) ------------------------- This Demo is comprised of two (2) Issues groups: Code and Action_items. The Code group is intended to emulate a very basic Razor tutorial. There are a few things configured for the Code group that demonstrate some controls that you may implement at your site. Start with Issue I...-..1 by double-clicking on the Issue. Read the text in the text panes and follow the instructions. The intent here is to guide you through some of the features of Razor. The Action_items group is wide open, meaning that you have free reign to do whatever you like (practice!) in that group. This is what you see in the columns on the Main Issue form: State, Priority, Issue Number, Title The State and Priority are both Bitmap pictures (user defined) that reflect at a quick glance what state and priority that Issue is at. VERSIONS (Version Control) -------------------------- The Versions program is the backbone of the configuration management aspect of Razor. Versions provides a straightforward mechanism for controlling, monitoring, and archiving changes made to files in your development environment. In the Versions tool, you have two (2) file control groups: Code and Configuration. The Code group is configured to simulate an example software development process. The Configuration group is wide open, meaning that you can practice and do whatever you wish. All of the configuration files that we modified for this demo are placed in the Configuration group. THREADS (Build/Release Management) ---------------------------------- The Threads program is the final piece of the Razor trilogy. It provides a mechanism for defining which unique combinations of files and versions "belong together" for the sake of a release or product build. A thread is what forms the relationship among specific versions of files. In the Threads tool, you have the same two file control groups: Code and Configuration. In Threads, these groups are for build management. In the code group, the are two Threads: code_baseline and patch. These threads are designed to simulate a possible release scenario. The same idea applies to the Configuration group. FEEDBACK -------- We appreciate all customer feedback - both good and bad! We'd really like to hear from you in regards to your thoughts on the Demo. Visible Systems 315-363-8000 (V) 315-363-7488 (F) Support: razor_support@visible.com