Managing Software Deliverables: A Software Development Management Methodology

The smallest logical entity specified in the design of a software system; must be of sufficient detail to allow the code to be developed and tested independently of other units. See module.

In testing, the process of ensuring that the software unit executes as intended; usually performed by the developer.

A new release of a software system to include a new version of one or more system components.

The capability of the software product to be understood, learned, used; is of value to the user, when used under specified conditions.

An individual or organization who operates or interacts directly with the system; one who uses the services of a system. The user may or may not be the customer. See customer.

Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the user to determine whether or not to accept the system. See Acceptance Test.

The software, input/output (I/O) devices, screens, procedures, and dialogue between the users of the system (people) and the system (or system component) itself. See interface.

A formal document that contains all essential information for the user to make full use of the new or upgraded system.

A formal survey used to gather the data needed to analyze current user satisfaction with the performance capabilities of an existing system or application; administered annually, or as needed.