Managing Software Deliverables: A Software Development Management Methodology

To modify a process, standard, procedure, or work pattern formally to fit a specific use or business need.

The computer that is the destination for a host communication; see host. In programming, a language into which another language is to be translated.

In project management, the smallest unit of work subject to management accountability; a work assignment for one or more project members fulfilling a role, as defined in a Work Breakdown Structure.

Relating to agreements, conditions, and/or requirements affecting the functionality and operation of a system. Compare with nontechnical.

The process of exercising the product to identify differences between expected and actual results and performance. Typically testing is bottomup: unit test, integration test, system test, and acceptance test.

A specific set of test data and associated procedures developed for a particular test.

Files/data developed for the purpose of executing a test; becomes part of a test case. See test case.

A metric used to measure the characteristics of a requirement that enable it to be verified during a test.

The form attached to the Test Analysis Report as a final result of the test reviews for all testing levels above the Integration test. See Test Analysis Report.

Formal documentation of the software testing as defined in the Test Plan.

T&E occurs during all major phases of the Systems Development Life Cycle, beginning with system planning and continuing through the operations and maintenance phase; ensures standardized identification, refinement, and trace ability of the requirements as such requirements are allocated to the system components.

The formal document that identifies the tasks and activities so the entire system can be adequately tested to assure a successful implementation.

Formal documentation of problems encountered during testing; the form is attached to the Test Analysis Report. See Test Analysis Report.

A formal phase review to determine that the test procedures are complete and to ensure that the system is ready for formal testing.

Software application products that assist in the design, development, and coding of software. Also called CASE tools; see Computer-aided software engineering.

An approach that takes the highest level of a hierarchy and proceeds through progressively lower levels; compare with bottom-up.

In requirements management, the identification and documentation of the derivation path (upward) and allocation path (downward) of requirements in the hierarchy.

The formal process of depicting, simulating, or portraying the operational characteristics of a system or system component in order to make someone proficient in its use.

A formal document that outlines the objectives, needs, strategy, and curriculum to be addressed for training users of the new or enhanced system.