Sorting out terminology is an important task for the architect, just because it seldom gets done on its own by other project members. The architect requires consistent terminology to articulate the architectural specification. In addition, the architect often creates new terminology in order to give the developers a handle on key concepts. The following is a preliminary TRRS glossary:
Experience Report-
A report by an independent organization (not the product vendor) about a set of products.
Feature (or Product Feature)-
A significant product capability that is selected from an enumerated list in the TRRS Categories. Examples: Security, Directory, Database Access.
Operating Environment-
An enabling hardware/software platform configuration upon which products can execute.
Organization-
A participant in the TRRS that may be a standards group, a product vendor, a testing organization (providing product-related services), or an IT user.
Product-
A unit of commercially available software (i.e., readily available).
Product Related Service-
A technical service that relates directly to product capabilities or utilization. Example: Training and testing.
Standard Profile-
A "technology" that is published as an open systems specification (publicly available specification adopted by a standards group). A standard profile may be a derivative from a publicly available specification.
Technology-
A reference to the specification of a "feature." Either the technology is a standard profile, or there is a default technology category: PROPRIETARY. Examples: For Security Feature: CORBA Security, GSS API, Secure TCP/IP Sockets. For Directory Feature: CORBA Naming, CORBA Trader, LDAP, X.500.
