1. {application program}.

	2. {function application}.

The process of analysis, design, coding and testing software.

<process> The approach that engineering (and some other)
	disciplines use to specify how to create or do something.  A
	successful design must satisfies a (perhaps informal)
	{functional specification} (do what it was designed to do);
	conforms to the limitations of the target medium (it is
	possible to implement); meets implicit or explicit
	requirements on performance and resource usage (it is
	efficient enough).

	A design may also have to satisfy restrictions on the design
	process itself, such as its length or cost, or the tools
	available for doing the design.

	In the {software life-cycle}, design follows {requirements
	analysis} and is followed by implementation.

	["Object-Oriented Analysis and Design with Applications", 2nd
	ed., Grady Booch].

	(1996-12-08)

1. <application> Any specific type of {file} produced or
	edited by a specific {application}; usually capable of being
	printed.  E.g. "Word document", "Photoshop document", etc.

	2. <hypertext> A term used on some systems (e.g. {Intermedia})
	for a {hypertext} {node}.  It is sometimes used for a
	collection of nodes on related topics, possibly stored or
	distributed as one.

	3. <programming> To write {documentation} on a certain piece
	of code.

	(2003-10-25)

<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)

<programming> (Or "computer program", "program", "code") The
	instructions executed by a computer, as opposed to the
	physical device on which they run (the "{hardware}").

	The term was coined by the eminent statistician, {John Tukey}.

	Programs stored on {non-volatile storage} built from
	{integrated circuits} (e.g. {ROM} or {PROM}) are usually
	called {firmware}.

	Software can be split into two main types - {system software}
	and application software or {application programs}.  System
	software is any software required to support the production or
	execution of application programs but which is not specific to
	any particular application.  Examples of system software would
	include the {operating system}, {compilers}, editors and
	sorting programs.

	Examples of application programs would include an accounts
	package or a {CAD} program.  Other broad classes of
	application software include {real-time} software, {business
	software}, scientific and engineering software, {embedded
	software}, personal computer software and {artificial
	intelligence} software.

	Software includes both {source code} written by humans and
	executable {machine code} produced by {assemblers} or
	{compilers}.  It does not usually include the data processed
	by programs unless this is in a format such as {multimedia}
	which depends on the use of computers for its presentation.
	This distinction becomes unclear in cases such as {spread
	sheets} which can contain both instructions (formulae and
	{macros}) and data.  There are also various intermediate
	compiled or {semi-compiled}, forms of software such as
	{library} files and {byte-code}.

	Some claim that {documentation} (both paper and electronic) is
	also software.  Others go further and define software to be
	programs plus documentation though this does not correspond
	with common usage.

	The noun "program" describes a single, complete and
	more-or-less self-contained list of instructions, often stored
	in a single {file}, whereas "code" and "software" are
	uncountable nouns describing some number of instructions which
	may constitute one or more programs or part thereof.  Most
	programs, however, rely heavily on various kinds of {operating
	system} software for their execution.  The nounds "code" and
	"software" both refer to the same thing but "code" tends to
	suggest an interest in the implementation details whereas
	"software" is more of a user's term.

	(2002-07-21)

<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)

1. Working correctly.

	2. Pertaining to {functional programming}.

	3. {higher-order function}.

Specific computer hardware, as in the phrase
	"platform-independent".  It may also refer to a specific
	combination of hardware and {operating system} and/or
	{compiler}, as in "this program has been ported to several
	platforms".  It is also used to refer to support software for
	a particular activity, as in "This program provides a platform
	for research into routing protocols".

	(1994-12-07)

See {tuple}.

<programming> The first stage of software development which
	defines what the potential users want the system to do.  In
	modern methods these requirements should be testable, and will
	usually be traceable in later development stages.  A common
	feature of nearly all software is that the requirements change
	during its lifetime.

	See {software life-cycle}.

	(1995-11-11)

1. <storage> To move the head of a {disk drive} radially,
	i.e., to move from one {track} to another.

	2. <storage> To wind the {tape} to a given location.

	3. <programming> To move the pointer that marks the next {byte}
	to be read from or written to a {file}.

	(1997-07-15)

<artificial intelligence, information science> The objects,
	concepts and relationships that are assumed to exist in some
	area of interest.  A collection of {knowledge}, represented
	using some {knowledge representation} language is known as a
	{knowledge base} and a program for extending and/or querying a
	knowledge base is a {knowledge-based system}.

	Knowledge differs from {data} or {information} in that new
	knowledge may be created from existing knowledge using logical
	{inference}.  If information is data plus meaning then
	knowledge is information plus processing.

	A common form of knowledge, e.g. in a {Prolog} program, is a
	collection of {facts} and {rules} about some subject.

	For example, a {knowledge base} about a family might contain
	the facts that John is David's son and Tom is John's son and
	the rule that the son of someone's son is their grandson.
	From this knowledge it could infer the new fact that Tom is
	David's grandson.

	See also {Knowledge Level}.

	(1994-10-19)

1. <database> One or more large structured sets of persistent
	data, usually associated with software to update and {query}
	the data.  A simple database might be a single file containing
	many {records}, each of which contains the same set of
	{fields} where each field is a certain fixed width.

	A database is one component of a {database management system}.

	See also {ANSI/SPARC Architecture}, {atomic}, {blob}, {data
	definition language}, {deductive database}, {distributed
	database}, {fourth generation language}, {functional
	database}, {object-oriented database}, {relational database}.

	{Carol E. Brown's tutorial
	(http://accounting.rutgers.edu/raw/aies/www.bus.orst.edu/faculty/brownc/lectures/db_tutor/db_tutor.htm)}.

	2. <hypertext> A collection of {nodes} managed and stored in
	one place and all accessible via the same {server}.  {Links}
	outside this are "external", and those inside are "internal".

	On the {World-Wide Web} this is called a {website}.

	3. All the facts and rules comprising a {logic programming}
	program.

	(2005-11-17)

<operating system> All activities involved in completing any
	project on a computer from start to finish.  A job may involve
	several {processes} and several {programs}.

	This term originates from a time when a user would manually
	submit a job as a deck of {punched cards} which would
	typically include {source code} interspersed with {job control
	language} instructions to guide phases of the job such as
	{compilation}, {linking}, {execution} and printing.

	(2005-03-16)

<messaging> One of {Usenet}'s huge collection of topic groups
	or {fora}.  {Usenet} groups can be "unmoderated" (anyone can
	post) or "moderated" (submissions are automatically directed
	to a {moderator}, who edits or filters and then posts the
	results).  Some newsgroups have parallel {mailing lists} for
	{Internet} people with no netnews access, with postings to the
	group automatically propagated to the list and vice versa.
	Some moderated groups (especially those which are actually
	gatewayed {Internet} {mailing lists}) are distributed as
	"{digests}", with groups of postings periodically collected
	into a single large posting with an index.

	Among the best-known are comp.lang.c (the {C}-language forum),
	comp.arch (on computer architectures), comp.Unix.wizards (for
	{Unix wizards}), rec.arts.sf-lovers (for science-fiction
	fans), and talk.politics.misc (miscellaneous political
	discussions and {flamage}).

	Barry Shein <bzs@world.std.com> is alleged to have said,
	"Remember the good old days when you could read all the group
	names in one day?"  This gives a good idea of the growth and
	size of {Usenet}.

	See also {netiquette}.

	[{Jargon File}]

	(1994-12-13)

<job> (Or "computer programmer", "developer") Someone who
	writes or debugs {computer programs}, for a living or for fun.
	"Analyst/developer" is a common equivalent job title, implying
	the added role of {system analysis}.  The term may be
	qualified according to the type of software - "{application}
	programmer", "{system programmer}", etc.

	(2000-01-24)

<programming> The modification of a software product, after
	delivery, to correct faults, to improve performance or other
	attributes, or to adapt the product to a changed environment.

	Maintenance is an important part of the {software life-cycle}.
	It is expensive in manpower and resources, and one of the aims
	of {software engineering} is to reduce its cost.

	(1996-12-27)

The totality of features and characteristics of a product or
	service that bear on its ability to satisfy stated or implied
	needs.  Not to be mistaken for "degree of excellence" or
	"fitness for use" which meet only part of the definition.

	[{ISO8402}].

	(1995-11-10)

<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)

1. <networking> {e-mail address}.

	2. <networking> {Internet address}.

	3. <networking> {MAC address}.

	4. <storage, programming> An unsigned integer used to select
	one fundamental element of storage, usually known as a {word}
	from a computer's {main memory} or other storage device.  The
	{CPU} outputs addresses on its {address bus} which may be
	connected to an {address decoder}, {cache controller}, {memory
	management unit}, and other devices.

	While from a hardware point of view an address is indeed an
	integer most {strongly typed} programming languages disallow
	mixing integers and addresses, and indeed addresses of
	different data types.  This is a fine example for {syntactic
	salt}: the compiler could work without it but makes writing
	bad programs more difficult.

	(1997-07-01)

1. The art of debugging a blank sheet of paper (or, in these
	days of on-line editing, the art of debugging an empty file).

	2. A pastime similar to banging one's head against a wall, but
	with fewer opportunities for reward.

	3. The most fun you can have with your clothes on (although
	clothes are not mandatory).

	[{Jargon File}]

	(2003-02-12)

<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)

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)

1. <messaging> (From Hormel's Spiced Ham, via the Monty Python
	"Spam" song) To post irrelevant or inappropriate messages to
	one or more {Usenet} {newsgroups}, {mailing lists}, or other
	messaging system in deliberate or accidental violation of
	{netiquette}.

	It is possible to spam a newsgroup with one well- (or ill-)
	planned message, e.g. asking "What do you think of abortion?"
	on soc.women.  This can be done by {cross-post}ing, e.g. any
	message which is crossposted to alt.rush-limbaugh and
	alt.politics.homosexuality will almost inevitably spam both
	groups.  (Compare {troll} and {flame bait}).

	Posting a message to a significant proportion of all
	newsgroups is a sure way to spam Usenet and become an object
	of almost universal hatred.  Canter and Siegel spammed the net
	with their Green card post.

	If you see an article which you think is a deliberate spam, DO
	NOT post a {follow-up} - doing so will only contribute to the
	general annoyance.  Send a polite message to the poster by
	private e-mail and CC it to "postmaster" at the same address.
	Bear in mind that the posting's origin might have been forged
	or the apparent sender's account might have been used by
	someone else without his permission.

	The word was coined as the winning entry in a 1937 competition
	to choose a name for Hormel Foods Corporation's "spiced meat"
	(now officially known as "SPAM luncheon meat").  Correspondant
	Bob White claims the modern use of the term predates Monty
	Python by at least ten years.  He cites an editor for the
	Dallas Times Herald describing Public Relations as "throwing a
	can of spam into an electric fan just to see if any of it
	would stick to the unwary passersby."

	{Usenet} newsgroup: {news:news.admin.net-abuse}.

	See also {netiquette}.

	2. (A narrowing of sense 1, above) To indiscriminately send
	large amounts of unsolicited {e-mail} meant to promote a
	product or service.  Spam in this sense is sort of like the
	electronic equivalent of junk mail sent to "Occupant".

	In the 1990s, with the rise in commercial awareness of the
	net, there are actually scumbags who offer spamming as a
	"service" to companies wishing to advertise on the net.  They
	do this by mailing to collections of {e-mail} addresses,
	Usenet news, or mailing lists.  Such practises have caused
	outrage and aggressive reaction by many net users against the
	individuals concerned.

	3. (Apparently a generalisation of sense 2, above) To abuse
	any network service or tool by for promotional purposes.

	"AltaVista is an {index}, not a promotional tool.  Attempts to
	fill it with promotional material lower the value of the index
	for everyone.  [...] We will disallow {URL} submissions from
	those who spam the index.  In extreme cases, we will exclude
	all their pages from the index." -- {Altavista}.

	4. <jargon, programming> To crash a program by overrunning a
	fixed-size {buffer} with excessively large input data.

	See also {buffer overflow}, {overrun screw}, {smash the stack}.

	5. <chat, games> (A narrowing of sense 1, above) To flood any
	{chat} forum or {Internet game} with purposefully annoying
	text or macros.  Compare {Scrolling}.

	(2003-09-21)

<chat> On a real-time network (whether at the level of
	{TCP/IP}, or at the level of, say, {IRC}), to send a huge
	amount of data to another user (or a group of users, in a
	channel) in an attempt to annoy him, lock his terminal, or to
	overflow his network buffer and thus lose his network
	connection.

	The basic principles of flooding are that you should have
	better network {bandwidth} than the person you're trying to
	flood, and that what you do to flood them (e.g., generate ping
	requests) should be *less* resource-expensive for your machine
	to produce than for the victim's machine to deal with.  There
	is also the corrolary that you should avoid being caught.

	Failure to follow these principles regularly produces
	hilarious results, e.g., an IRC user flooding himself off the
	network while his intended victim is unharmed, the attacker's
	flood attempt being detected, and him being banned from the
	network in semi-perpetuity.

	See also {pingflood}, {clonebot} and {botwar}.

	[{Jargon File}]

	(1997-04-07)

1. <application, algorithm> To arrange a collection of items
	in some specified order.  The items - {records} in a file or
	data structures in memory - consist of one or more {fields} or
	members.  One of these fields is designated as the "sort key"
	which means the records will be ordered according to the value
	of that field.  Sometimes a sequence of key fields is
	specified such that if all earlier keys are equal then the
	later keys will be compared.  Within each field some ordering
	is imposed, e.g. ascending or descending numerical, {lexical
	ordering}, or date.

	Sorting is the subject of a great deal of study since it is a
	common operation which can consume a lot of computer time.
	There are many well-known sorting {algorithms} with different
	time and space behaviour and programming {complexity}.

	Examples are {quicksort}, {insertion sort}, {bubble sort},
	{heap sort}, and {tree sort}.  These employ many different
	data structures to store sorted data, such as {arrays},
	{linked lists}, and {binary trees}.

	2. <tool> The {Unix} utility program for sorting lines of
	files.

	{Unix manual page}: sort(1).

	(1997-02-12)

<security> ("brand spoofing", "carding", after "fishing")
	/fishing/ Sending {e-mail} that claims to be from some
	well-known organisation, e.g. a bank, to trick the recipient
	into revealing information for use in {identity theft}.  The
	user is told to visit a {web site} where they are asked to
	enter information such as passwords, credit card details,
	social security or bank account numbers.  The web site usually
	looks like it belongs to the organisation in question and may
	silently redirect the user to the real web site after
	collecting their data.

	For example, a scam started in 2003 claimed that the user's
	eBay account would be suspended unless he updated his credit
	card information on a given web site.

	(2006-01-19)