<language, programming> (J2EE) {Sun}'s {Java} platform for
	{multi-tier} {server}-oriented {enterprise} {applications}.

	The basis of J2EE is {Enterprise JavaBeans} (EJB).

	See also the Standard edition {J2SE} and the Micro edition
	{J2ME}.

	{Home (http://java.sun.com/j2ee/)}.

	(2000-04-20)

1. <storage> {Main memory} or {RAM}.  This term dates from the
	days of {ferrite core memory}; now archaic most places outside
	{IBM}, but also still used in the {Unix} community and by
	old-time {hackers} or those who would sound like them.

	Some derived idioms are quite current; "in core", for example,
	means "in memory" ({paged in}, as opposed to "on disk", {paged
	out}), and both {core dump} and the "core image" or "core
	file" produced by one are terms in favour.  Some varieties of
	Commonwealth hackish prefer {store}.

	[{Jargon File}]

	(1995-03-03)

	2. <processor> An {integrated circuit} design, usually for a
	{microprocessor}, which includes only the {CPU} and which is
	intended to form part of a complete circuit design which
	incorporates other circuits on the same chip such as {cache},
	{memory management unit}, I/O ports and timers.

	The {ARM6}, {ARM7} and {ARM8} are examples.

	3. <language> A varient on {kernel} as used to describe
	features built into a language as opposed to those provided by
	{libraries}.

	(1995-03-03)

1. See {multithreading}.

	2. See {threaded code}.

	3. {topic thread}.

	[{Jargon File}]

<World-Wide Web> (By analogy with "{applet}") A {Java} program
	that runs as part of a {network} service, typically an {HTTP
	server} and responds to requests from {clients}.

	The most common use for a servlet is to extend a {web server}
	by generating {web content} dynamically.  For example, a
	{client} may need {information} from a {database}; a servlet
	can be written that receives the request, gets and processes
	the data as needed by the {client} and then returns the result
	to the {client}.

	{Applets} are also written in {Java} but run inside the {JVM}
	of a {HTML} {browser} on the {client}.  Servlets and applets
	allow the server and client to be extended in a modular way by
	dynamically loading code which communicates with the main
	program via a standard programming interface.

	Servlets are more flexible than {CGI scripts} and, being
	written in {Java}, more portable.

	The spelling "servelet" is occasionally seen but {JavaSoft}
	spell it "servlet".  There is no such thing as a "serverlet".

	{(http://java.sun.com/products/servlet/)}.

	(2002-10-06)

<programming, World-Wide Web> (JSP) A freely available
	specification for extending the {Java Servlet} {API} to
	generate dynamic {web pages} on a {web server}.  The JSP
	specification was written by industry leaders as part of the
	Java development program.

	JSP assists developers in creating {HTML} or {XML} pages that
	combine static (fixed) page templates with dynamic content.
	Separating the {user interface} from content generation allows
	page designers to change the page layout without having to
	rewrite program code.  JSP was designed to be simpler than
	pure servlets or {CGI} {scripting}.

	JSP uses XML-like tags and scripts written in Java to generate
	the page content.  HTML or XML formatting {tags} are passed
	back to the client.  Application logic can live on the server,
	e.g. in {JavaBeans}.

	JSP is a {cross-platform} alternative to {Microsoft's} {Active
	Server Pages}, which only runs in {IIS} on {Windows NT}.

	Applications written to the JSP specification can be run on
	compliant web servers, and web servers such as {Apache},
	{Netscape Enterprise Server}, and Microsoft {IIS} that have
	had Java support added.  JSP should soon be available on
	{Unix}, {AS/400}, and {mainframe} platforms.

	{JavaServer Pages (http://java.sun.com/products/jsp/)}.

	{Infoworld Article
	(http://www.infoworld.com/cgi-bin/displayStory.pl?99063.ecjsp.htm)}.

	(1999-11-28)

<specification, business, programming> (EJB) A {server}-side
	{component architecture} for writing reusable {business logic}
	and {portable} {enterprise} applications.  EJB is the basis of
	{Sun}'s {Java 2 Platform, Enterprise Edition} (J2EE).

	Enterprise JavaBean components are written entirely in {Java}
	and run on any EJB compliant server.  They are {operating
	system}, {platform}, and {middleware} independent, preventing
	vendor {lock-in}.

	EJB servers provide system-level services (the "plumbing")
	such as {transactions}, security, {threading}, and
	{persistence}.

	The EJB architecture is inherently transactional,
	{distributed}, {multi-tier}, {scalable}, secure, and {wire
	protocol} neutral - any {protocol} can be used: {IIOP},
	{JRMP}, {HTTP}, {DCOM} etc.  EJB 1.1 requires {RMI} for
	communication with components.  EJB 2.0 is expected to require
	support for RMI/IIOP.

	EJB applications can serve assorted clients: {browsers}, Java,
	{ActiveX}, {CORBA} etc.  EJB can be used to wrap {legacy
	systems}.

	EJB 1.1 was released in December 1999.  EJB 2.0 is in
	development.

	Sun claims broad industry adoption.  30 vendors are shipping
	server products implementing EJB.  Supporting vendors include
	{IBM}, {Fujitsu}, {Sybase}, {Borland}, {Oracle}, and
	{Symantec}.

	An alternative is Microsoft's MTS ({Microsoft Transaction
	Server}).

	{Home (http://java.sun.com/products/ejb/)}.

	{FAQ (http://java.sun.com/products/ejb/faq.html)}.

	(2000-04-20)

<language, database, standard> /S Q L/ An industry-standard
	language for creating, updating and, querying {relational
	database management systems}.

	SQL was developed by {IBM} in the 1970s for use in {System R}.
	It is the {de facto standard} as well as being an {ISO} and
	{ANSI} {standard}.  It is often embedded in general purpose
	programming languages.

	The first SQL standard, in 1986, provided basic language
	constructs for defining and manipulating {tables} of data; a
	revision in 1989 added language extensions for {referential
	integrity} and generalised {integrity} {constraints}.  Another
	revision in 1992 provided facilities for {schema} manipulation
	and {data administration}, as well as substantial enhancements
	for data definition and data manipulation.

	Development is currently underway to enhance SQL into a
	computationally complete language for the definition and
	management of {persistent}, complex objects.  This includes:
	generalisation and specialisation hierarchies, {multiple
	inheritance}, user defined {data types}, {triggers} and
	{assertions}, support for {knowledge based systems},
	{recursive query expressions}, and additional data
	administration tools.  It also includes the specification of
	{abstract data types} (ADTs), object identifiers, {methods},
	{inheritance}, {polymorphism}, {encapsulation}, and all of the
	other facilities normally associated with object data
	management.

	The emerging {SQL3} standard is expected to be complete in
	1998.

	According to Allen G. Taylor, SQL does _not_ stand for
	"Structured Query Language".  That, like "SEQUEL" (and its
	pronunciation /see'kw*l/), was just another unofficial name
	for a precursor of SQL.  However, the IBM SQL Reference manual
	for DB2 and Craig Mullins's "DB2 Developer's Guide" say SQL
	_does_ stand for "Structured Query Language".

	{SQL Standards (http://www.jcc.com/sql_stnd.html)}.

	{An SQL parser
	(ftp://ftp.ora.com/published/oreilly/nutshell/lexyacc/)} is
	described in "Lex & Yacc", by Levine, Mason & Brown published
	by O'Reilly.

	{The 1995 SQL Reunion: People, Projects, and Politics
	(http://www.mcjones.org/System_R/SQL_Reunion_95/)}.

	["A Guide to the SQL Standard", C.J. Date, A-W 1987].

	["SQL for Dummies", Allen G. Taylor, IDG Books Worldwide].

	(2005-11-17)

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)

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