home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Standards
/
CD2.mdf
/
ccitt
/
1992
/
z
/
z341_a1.asc
< prev
next >
Wrap
Text File
|
1991-12-31
|
9KB
|
267 lines
ANNEX A
(to Recommendation Z.341)
Classification of terms
1. Introduction
This annex classifies the MMI terms according to the following
classification scheme.
The purpose of this classification is to partition MMI terms into
conceivable collections:
a) to users of the MMI Recommendations;
b) to those who can benefit from the knowledge of MMI terms, such as
programmers; and
c) to developers of the MMI Recommendations, for the identification of
new work items, the organization of future work and new
Recommendations.
The classes are intended to aid the identification and delimitation of the
scope of the terms and therefore enhance the readability of the Recommendations and
specifications. For example, an MMI designer who wants to document the terms to be
used at the MMI can use this classification to organize the MMI documentation. The
following defines MMI terms and describes their use.
This classification scheme is inspired by the conceptual scheme work [1]
within ISO. The application area and scope are, however, different.
2. Overview
The totality of MMI terms is divided into classes shown in
Figure A-1/Z.341. The classes can form a hierarchical structure. If a term is
applicable to more than one class, it may appear in the most general class.
The classes can very well be divided into subclasses.
3. Classes and their usage
The following text defines different classes, explains their usage and
gives examples of their contents. Terms are classified as application- independent
and application-dependent terms. These classes are classified into subclasses.
1) Application-independent terms
Terms which can be common for all MMI applications:
a) Primitives
Terms which cannot be further defined but are used to define
other terms.
Users: Everyone, in particular, language designers. End
users can read system documentation which applies
these terms.
Examples: Predicates, logical connectors, quantifiers,
terms, etc.
b) Metaterms
General terms which are not restricted to the classes listed
below.
This class includes common terms from mathematics and logic as
well as general terms such as time and space.
Users: Everyone, in particular, language designers. End
users can read system documentation which applies
these terms.
Examples: Arithmetics, algebra, etc.
Space, time, terminology, phenomenon, etc.
1) APPLICATION-INDEPENDENT TERMS
a) Primitives
b) Metaterms
c) System specification terms
d) MMI manipulation and presentation terms
d1) MMI manipulation terms
d2) MMI presentation terms
2) APPLICATION-DEPENDENT TERMS
e) MMI terms for operations and maintenance
e1) computer equipment and computer software
e2) telecommunication networks and services
f) MMI constructs for the use of
telecommunications networks and services
g) Other application-dependent terms
Figure A-1/Z.341
Classification scheme
c) System specification terms
Terms restricted to one system description language, often aimed
at one application area.
Users: Everyone, in particular, applications system
designers including MMI designers. End users can read system
documentation which applies these terms.
Example: Block channel, signal, etc., in basic SDL.
Flow line, non-terminal input symbol, etc., in the
MML metalanguage. Entity, relationship, domain, cardinality,
etc., in the Entity-relationship approach.
d) Application-independent MMI manipulation and presentation terms
Terms needed to manipulate all MMI terms and to present terms common
for all MMI applications.
d1) MMI manipulation terms
Terms which can be used to manipulate other terms.
Users: Everyone who applies a man-machine interface, both end
users and system developers.
Examples: Next page, delete window, etc.
Retrieve (from database to screen), insert (from screen to
database).
d2) MMI presentation terms
Terms which are needed to present other terms.
Presentation terms are intended to present other terms.
Users: Everyone who observes a man-machine interface, both end
users and system developers.
Examples: Window, window area, field, pixel, etc.
Common field, work window area, etc.
2) APPLICATION-DEPENDENT TERMS
Terms which are not common for all MMI applications.
e) MMI terms for operations and maintenance
e1) computer equipment and computer software
Terms used for the management of software and equipment through
their whole life cycle.
Users: Everyone who explicitly accesses, installs or supports
computer resources, or administers their availability
including access administration.
Examples: Machine, terminal, program, program statement
database, etc.
Logon, backup, suspend, etc.
e2) telecommunications networks and services
Terms for the Administrations' manipulation and presentation of
telecommunications networks and services.
Users: Everyone in the Administrations who administers
telecommunications networks or services.
Examples: Subscriber, multiplex group, traffic intensity,
installation plan, subscriber equipment, etc.
Subscriber identity, circuit identity, etc.
Insertion of routing data, etc.
f) MMI terms for the use of telecommunications networks and
services
Terms which are specific for the subscribers' manipulation and
presentation of telecommunications networks and services.
Users: Everyone who applies telecommunications networks or
services.
Examples: Dial up, send Teletex, electronic envelope, etc.
g) Other application-dependent terms
Any application-dependent term which is not listed above.
Users: Everyone who applies MMIs for manipulating or presenting
data concerned with the actual topics.
Examples: Employee number, salary information, etc.
REFERENCE
1. VAN GRIETHUYSEN (J.J.), ed. - Concepts and Terminology for the Conceptual
Schema and the Information Base, Report ISO/TC97/SC21-N197, ANSI, 1982.
4. Classification of terms
4. Application-independent terms
4.1) b) application metaterms
arithmetic