|
|
|
|
A script which will be run after a file operation occurs. The script is attached via a definition in the Actions file.
Characteristics of an object. For Razor, these characteristics define how an object is presented on the display and how it is stored in the database. Examples of attributes types are ONE_OF_MANY, X_OF_MANY, TEXT_FIELD, STATE, CHECK_BOX TIME_STAMP and LABEL. See "Attribute types defined" on page 189.
A very popular and powerful text processing program which comes standard with most UNIX systems. It allows users to write programs specifically designed to parse ASCII files.
A script which will be run before a file operation occurs. The script is attached via a definition in the Actions file.
A "binary" file is typically considered to be one which contains something other than simple ASCII text. In the context of Razor, a binary file is treated specially, in that the versions program will use its own archival scheme instead of SCCS/RCS.
The bitmap program is supplied with most X installations, and is a perfectly fine package for generating the simple bitmap files which can be attached as glyphs to the issues, versions, and threads main displays.
To create a separate, uniquely tracked version of a file already under control. A branch is often created to make parallel changes to a file. These changes are later merged into the main line and the branch is terminated.
The operation of obtaining an editable copy of a file and locking it so that others may not edit the same version at the same time.
A temporary holding area employed during the association of issues to various check-in/check-out efforts in the versions program.
A UNIX program used for discovering and displaying the differences between similar ASCII files. Most systems will have an excellent set of man pages on this. (See also sdiff, on page 361.)
This is a common parlor trick employed by some GUI's. It allows you to physically drag icons across the screen from one place to another instead of typing in commands to make associations or rearrange file structures. For example, the Razor program allows you to use this technique to associate issues to editing activity.
This is a variable defined within a shell which may be used by various programs to control or alter their behavior.
An acronym for "Frequently Asked Questions". FAQ's are common and popular offerings provided by various Usenet news groups.
A set of meta-characters may be used to define the expansion of filenames. Simple examples such as `*' matching all characters and `?' matching any single character are commonly used. See UNIX in a Nutshell from O'Reilly for a full discussion of filename meta-characters.
A scheme which allows licenses to be used by any user on a network. As users obtain a license, the total number available to other users is decreased by one. When the user exits the program which uses the license, the license is returned to the available pool.
A small graphical image, used in the Razor programs to provide insight to the various files and issues under control. See bitmap.
A collection of related files, all containing unique names. Sometimes viewed as being similar to a directory.
Either locally defined or a locally chosen entry in the Razor password file. User group may be used to grant/limit access to the Razor database based on membership.
An account used to gain access via Razor remote clients before a password file is created by the Razor administrator.
A `hard rule' is a local convention that is being enforced by the Razor tool set, typically as the result of the judicious attachment of shell scripts to the various Razor activities. This differs from a `soft rule', which is a convention agreed upon by the members of a team, but which has no programmatic enforcement.
The place in the Razor database where historical information regarding all operations on an object have occurred. This file can be found in the History directory for the appropriate Razor group.
Hypertext Markup Language. It's what makes the web run. You may also want to consider IssueWeaver from Tower Concepts as a way of providing Web access to your issues database.
The place in the Razor database where current status of an object is maintained. This file can be found in the Info directory for the appropriate Razor group.
If you need to be looking this up in a glossary, you've been on mental vacation a bit too long. Did you have a nice time though? How was the weather?
A first rate program which may be used for problem reporting, bug tracking, issue definition, job jar, help desk, customer calls, etc.
Another fine product from Tower Concepts. Purchased separately, it provides a turnkey method for generating web page access in and out of your issues database.
An attribute type used in issues to represent a text only field. This attribute is often used to provide commentary or act as a visual delimiter on an issue form.
A widget set put together by a consortium of contributors to provide a consistent interface in the X-windowing environment.
The following is quoted from The Academic American Encyclopedia, on-line edition, Grolier Electronic Publishing, Danbury, CT., 1991, courtesy of Compuserve.
"Occam's razor is a logical principle attributed to William of Occam, although it was used by some scholastic philosophers prior to him. The principle states that a person should not increase, beyond what is necessary, the number of entities required to explain anything, or that the person should not make more assumptions than the minimum needed. This principle is often called the principle of parsimony. Since the Middle Ages it has played an important role in eliminating fictitious or unnecessary elements from explanations. In the development of logic, logicians such as Bertrand Russell removed traditional metaphysical concepts by applying Occam's razor."
An attribute type which defines a list of items to which exactly one must be selected. The ONE_OF_MANY object is displayed as a group of toggle buttons while the ONE_OF_MANY_STACK are represented as a pull-down menu.
Sun Microsystems' attempt at a standard widget set for the X-windows environment. They ended up abandoning it.
The user who owns the RAZOR_UNIVERSE directory in a Razor database. This user will also own all subdirectories under RAZOR_UNIVERSE when a new database is created. Care must be taken to insure that modifications made to the configuration of the database be performed by this user.
Although everyone has their own ideas on this one, we choose to be generic and refer to them as issues. What makes the most sense to you will stand as your definition.
Quality Assurance. QA people are charged with the reponsibility of ensuring a product is stable and meets customer requirements.
Rather than turn this into a sales pitch, Razor is a tool for developers of all ilks which provides the ability to track issues, control file versions and define product releases.
A collection of command line interfaces which allows users access to Razor system commands and also allows them to extend some of the GUI functionality to a command line task.
The last one in line who got stuck with installing and administering Razor. Actually, its not that bad. Razor is designed to grow in capability and control as your requirements demand.
"Revision Control System" -a freely distributable revision control tool; functionally and conceptually similar to SCCS.
A means of defining simple or complex text patterns using standard characters and special characters.
To make an older version of a file the latest version. Versions are not lost during this operation, rather a new instance of the reverted version is created as the latest file version.
Two files which setup the users environment. The rz_prep file is intended for C-shell users and should be sourced from the users .login or .cshrc file. The rz_prep.sh file is intended for Bourne or Korn shell users and should be dotted (.) in the user's .profile.
A UNIX utility which provides a side by side analysis of how two files differ. This is the work engine for the displays that Razor offers. (See also diff, on page 355.)
A powerful UNIX utility which is a stream-oriented editor allowing users to update and edit files easily.
A `soft rule', is a convention agreed upon by the members of a team, but which has no programmatic enforcement. This differs from a `hard rule' which is being enforced by the Razor tool set, typically as the result of the judicious attachment of shell scripts to the various Razor activities.
On UNIX systems, this the `root' account is provided special powers and security levels beyond that of mortals. Hence the term superuser.
A public domain scripting language which provides the ability to create GUI interfaces to script output.
An attribute type used in issues to allow for the input of time based information. The format of the input is configurable.
A version number is broken up into a number of parts (up to 4) as follows:
release.level[.branch.sequence]
The release number (sometimes referred to as major number) and level (sometimes referred to as minor number) will always appear. Each time an object is modified, the level will change automatically. The release number can also changed if the user chooses to have it changed. The branch and sequence numbers are used only for branch files. The branch number will indicate which in the sequence of branches from the release it occurred. The sequence number behaves in a similar fashion to the level number.
(c. 1285-1350) A philosopher from the middle ages who penned Occam's Razor. (see also Occam's Razor)
|
|
|
|
|
(Part 1 of 1 for this section) (Generated 09/13/99 at 18:27:09) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |