1. {application program}.

	2. {function application}.

1. <programming> An independent piece of {software} which
	forms part of one or more larger {programs}.  Different
	languages have different concepts of a module but there are
	several common ideas.

	Modules are usually compiled seperately (in compiled
	languages) and provide an {abstraction} or information hiding
	mechanism so that a module's implementation can be changed
	without requiring any change to other modules.  In this
	respect they are similar to {objects} in an {object-oriented
	language}, though a module may contain many {procedures}
	and/or {functions} which would correspond to many objects.

	A module often has its own {name space} for {identifiers} so
	the same identifier may be used to mean different things in
	different modules.

	[Difference from {package}?].

	2. <hardware> An independent assembly of electronic components
	with some distinct function, e.g. a RAM module consisting of
	several RAM chips mounted on a small circuit board.

	(1997-10-27)

<operating system> A list from which the user may select an
	operation to be performed.  This is often done with a {mouse}
	or other pointing device under a {graphical user interface}
	but may also be controlled from the keyboard.

	Menus are very convenient for beginners because they show what
	commands are available and make experimentating with a new
	program easy, often reducing the need for user documentation.
	Experienced users however, often prefer keyboard commands,
	especially for frequently user operations, because they are
	faster to use.  In situations such as text entry where the
	keyboard must be used anyway, having to move your hand to the
	mouse to invoke a menu operation is slow.

	There are many different ways of presenting menus but the most
	common are the {menu bar} (with {pull-down menus}) and the
	{context-sensitive menu}.

	The term "menu" tends to be reserved for a list of actions or
	global options, whereas a "{list box}" or other graphical
	{widget} might present any kind of choice.

	See also {menuitis}.

	(1994-12-02)

<jargon> {Marketroid} jargon for "{software}", "{hardware}",
	"{protocol}" or something else too technical to name.

	The most flagrant abuse of this word has to be "{Windows NT}"
	(New Technology) - {Microsoft}'s attempt to make the
	incorporation of some ancient concepts into their OS sound
	like real progress.  The irony, and even the meaning, of this
	seems to be utterly lost on Microsoft whose {Windows 2000}
	start-up screen proclaims "Based on NT Technology", (meaning
	yet another version of NT, including some {Windows 95}
	features at last).

	See also: {solution}.

	(2001-06-28)

<software> Instructions for a computer in some programming
	language, often {machine language}.  The word "code" is often
	used to distinguish instructions from {data} (e.g. "The code
	is marked 'read-only'") whereas "{software}" is used in
	contrast with "{hardware}" and may consist of more than just
	code.

	(2000-04-08)

<language, programming> (Or "source", or rarely "source
	language") The form in which a computer program is written by
	the programmer.  Source code is written in some formal
	programming language which can be compiled automatically into
	{object code} or {machine code} or executed by an
	{interpreter}.

	(1995-01-05)

1. <chat> {Unix}'s simple {talk} command and {protocol}.
	write has been largely superseded by {talk} and then {irc}.

	An enhancement, {RWP}, has been proposed.

	2. <tool> A simple {text editor} for {Windows}.

	(1998-04-28)

<language, text> (XML) An initiative from the {W3C} defining
	an "extremely simple" dialect of {SGML} suitable for use on
	the {World-Wide Web}.

	{(http://www.w3.org/XML/)}.

	[Relationship to the {XSL} forthcoming subset of {DSSSL}?]

	(1997-11-20)

<standard> Standards are necessary for {interworking},
	{portability}, and {reusability}.  They may be {de facto
	standards} for various communities, or officially recognised
	national or international standards.

	{Andrew Tanenbaum}, in his Computer Networks book, once said,
	"The nice thing about standards is that there are so many of
	them to choose from", a reference to the fact that competing
	standards become a source of confusion, division,
	obsolescence, and duplication of effort instead of an
	enhancement to the usefulness of products.

	Some bodies concerned in one way or another with computing
	standards are {IAB} ({RFC} and {STD}), {ISO}, {ANSI}, {DoD},
	{ECMA}, {IEEE}, {IETF}, {OSF}, {W3C}.

	(1999-07-06)

<cryptography, communications> (PKI) A system of {public key
	encryption} using {digital certificates} from {Certificate
	Authorities} and other registration authorities that verify
	and authenticate the validity of each party involved in an
	electronic transaction.

	PKIs are currently evolving and there is no single PKI nor
	even a single agreed-upon standard for setting up a PKI.
	However, nearly everyone agrees that reliable PKIs are
	necessary before {electronic commerce} can become widespread.

	{US DOD PKI (http://www-pki.itsi.disa.mil/)}.

	{US NIST PKI (http://csrc.ncsl.nist.gov/pki/)}.

	{IETF PKIX Working Group (http://www.imc.org/ietf-pkix/)}.

	(1999-11-30)

<programming> Combining software or hardware components or
	both into an overall system.

	(1996-05-22)

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

/de'moh/ 1. A demonstration of a product, often of an early
	version or prototype.  A demo is a far more effective way of
	inducing bugs to manifest themselves than any number of {test}
	runs, especially when important people are watching.

	2. {demo version}.

	3. A program written to demonstrate the programmer's coding
	ability and/or the power of the computer it runs on.  Such
	demos are nearly always written in {machine code} and
	traditionally feature scrolling text about the author, his
	friends, his code and anything else he fancies and animated
	graphics.

	[{Jargon File}]

	(1994-11-04)

Software that mediates between an {application program} and a
	{network}.  It manages the interaction between disparate
	applications across the heterogeneous computing {platforms}.
	The {Object Request Broker} (ORB), software that manages
	communication between {objects}, is an example of a middleware
	program.

1. Corporate power elites distinguished primarily by their
	distance from actual productive work and their chronic failure
	to manage (see also {suit}).  Spoken derisively, as in
	"*Management* decided that ...".

	2. Mythically, a vast bureaucracy responsible for all the
	world's minor irritations.  Hackers' satirical public notices
	are often signed "The Mgt"; this derives from the
	"Illuminatus!" novels.

	[{Jargon File}]

	(1995-02-28)

<computer> (PDP) Early (1960's?) {Digital Equipment
	Corporation} family of {minicomputers}.  The best known ranges
	were the {PDP-10} and {PDP-11}.  {PAL} was the {assembly
	language}.

	(1997-11-21)

<chat> The owner of a {bot}.

	(1997-04-07)