Wideman Comparative Glossary of Common Project Management Terms v3.1 is copyright by R. Max Wideman, March 2002.

Please feel free to point to this document. For non-profit purposes you may copy this page, either whole or as whole definitions provided the above copyright notice is attached. For inclusion in for-profit works, please contact the author at

File: PMG_R02.htm generated 12/19/2002 9:25:53 AM
Generated by program: PMGlosGen v1.33 Program Author: Graham Wideman

Introduction | What's New in Version 6.1 | International Recognition
About the Author | Sources and References
Content Index |
Order Your V6.1 Copy Here!

Request for Quotation - to - Resource Availability

***  prev

Definition     Editor's Choice
Request for Quotation
A formal invitation to submit a price for goods and/or services as specified. [D01641]

Equivalent to a Request for Proposal but with more specific application areas. [D01642]

Similar to a request for proposal, except that the desired items to be procured are stock or catalog items, and only price and delivery time need be proposed. [D01643]

 SPM 304-9
Request for Quotations
A solicitation for quotes. Commonly used under simplified acquisition procedures. [D03560]

A description of a condition or capability to which a system must conform; either derived directly from user needs, or stated in a contract, standard, specification, or other formally imposed document. [D04875]

Requirement Attribute
Information associated with a particular requirement providing a link between the requirement and other project elements. For example, priorities, schedules, status, design elements, resources, costs, hazards. [D04876]

Requirement Specification
Description of desired results. [D01644]

Requirement Type
A categorization of requirements - for example, stakeholder need, feature, use case, supplementary requirement, test requirement, documentation requirement, hardware requirement, software requirement, and so on - based on common characteristics and attributes. See Concept: Types of Requirements. [D04764]

A negotiated set of measurable customer wants and needs. [D01646]

See Needs. [D01645]

Needs or necessities; something demanded or obligatory. For clarification purposes, a clarifier should always precede requirements; that is, user requirements, system requirements, operational requirements, contract requirements, test requirements, etc. [D04218]

A discipline in the software-engineering process, whose purpose is to define what the system should do. The most significant activities are to develop a vision, a use-case model, and software requirements specifications. [D04761]

Requirements Definition
Statement of the needs that a project has to satisfy. [D04498]

Requirements Flowdown
The process of deriving and allocating requirements to all levels of system decomposition. [D04219]

Requirements Management
The process of exercising some control over the project scope to avoid scope creep, based on stakeholder needs rather than nice-to-haves. [D03238]

The process of defining the user/customer requirements and building the system requirements before going on to develop the performance specifications in detail. Requirements should be comprehensive and clear, well structured, traceable and testable. They should give rise to clearly specified project deliverables and should be tested against the original set of requirements. Any changes to the initial requirements should be traceable i.e. documented and explainable. [D03762]

A systematic approach to eliciting, organizing and documenting the requirements of the system, and establishing and maintaining agreement between the customer and the project team on the changing requirements of the system. See Concept: Requirements Management. [D04762]

Requirements of Society
Requirements including laws, statutes, rules and regulations, codes, environmental considerations, health and safety factors, and conservation of energy and materials. [D01647]

Requirements Traceability
The management of the parent/child relationships of all system requirements. [D04220]

Requirements Traceability Matrix
A document that maps the parent-child relationships of requirements. [D04221]

Requirements Tracing
The linking of a requirement to other requirements and to other associated project elements. [D04763]

Requirements Workflow
A discipline in the software engineering process whose purpose is to define what the system should do. The most significant activity is to develop a use-case model. [D04792]

The process of changing the logic, duration, and/or dates of an existing schedule in response to external imposed conditions. [D01648]

A feature of most PM software that recalculates the start and finish dates of all uncompleted activities based upon progress as of a specified date. [D03606]

The collecting of information about a particular subject. Studious inquiry or examination, especially investigation or experimentation aimed at the discovery and interpretation of facts, or the revision of accepted theories or laws in the light of new facts. Careful and diligent search. [D03239]

Research and Development
Technical pursuit of a new technology or design to support a strategic goal. [D04222]

A provision in the project plan to mitigate cost and/or schedule risk. Often used with a modifier (e.g., management reserve, contingency reserve) to provide further detail on what types of risk are meant to be mitigated.
Editor's Note: Unfortunately, the specific meaning of the modified terms vary by project management application area and may be contradictory. [D01649]

Reserve For Scope Changes
A sum of money set aside for changes in the Owner's requirements and to be used only at the direction of the Owner. [D01650]

Residential Construction
The construction, alteration, or repair of single family houses or apartment buildings of no more than four stories in height, and typically includes incidental items such as site work, parking areas, utilities, streets and sidewalks. [D03561]

Residual Risks
Those risks which are not avoided, eliminated or transferred in the risk mitigation strategy. [D05088]

Residual Value
The proceeds, less removal and disposal costs, if any, realized upon disposition of a tangible capital asset. [D03562]

Residue File
A file in the same format as the resource availability file containing a specification of the resources remaining after a project is scheduled. [D01651]

The finding of a solution to, and disposal of, a problem or issue. Reduction of complex notions into simpler ones, e.g. the development of a work breakdown structure. A formal expression of opinion, will, or intent voted by an official body or assembled group. [D03240]

Any personnel, material or equipment required for the performance of an activity.
Note: - Time is not a resource. It is the measure of the duration for which a resource is needed or used. Also, money is better not thought of as a resource, except in financing. It is better seen as the basis of evaluation of the resources used by an activity or task. [D05089]

An item required to accomplish an activity. Resources can be people, equipment, facilities, funding or anything else needed to perform the work of a project. [D01652]

Any factors, except time, required or consumed to accomplish an activity. Any substantive requirement of an activity that can be quantified and defined, e.g. manpower, equipment, material, etc. [D01653]

Project input (time, money, labor, machinery, etc.) [D01654]

Anything that is assigned to an activity or needed to complete an activity. This may include equipment, people, buildings, etc. [D03607]

Any variable capable of definition that is required for the completion of an activity and may constrain the project. Resources can be people, equipment, facilities, funding or anything else needed to perform the work of a project.
Note 1: A resource may be non-storable so that its availability has to be renewed for each time period (even if it was not utilized in previous time periods).
Note 2: A resource may be storable so that it remains available unless depleted by usage. Such a resource may also be replenished by activities producing credited and storable resource. [D04499]

Resource Accumulation
Process of accumulating the requirements for each resource to give the total required to date at all times throughout the project. [D04502]

Resource Aggregation
Summation of the requirements for each resource, and for each time period.
Note: Where the earliest start time of an activity is used alone, it is often termed an "early start" aggregation. Similarly a "late start" aggregation uses the latest start times. [D04500]

Totaling the requirement for a specific resource. [D01655]

Resource Allocation
The assignment of resources to tasks in a project. [D01657]

Distribution of resources over time or project parts. [D01656]

An iterative process of computing the schedule considering the limited availability of resources so that both time and cost may be minimized.

Progress on certain types of project can be constrained more by limitations of resources (people, machines, materials and money) than by logical sequence dictated by technical considerations. Generally such projects are "horizontal" e.g. Highway construction, rather than "vertical" e.g. High rise construction, although the latter may be constrained by both considerations. The resource loading required can only be determined after a schedule of activities has been developed. The schedule may then be modified, possibly prolonged, either to reduce the total resources required to complete the project or to "level" out peak demands. This avoids congestion at some times and inefficient resource usage at others. [D03087]

The assignment of people, equipment, facilities, or materials to a project. Unless adequate resources are provided, project work cannot be completed on schedule, and resource allocation is a significant component of project scheduling. [D03727]

 PPS&C p341
Resource Allocation Process
The scheduling of activities in a network with the knowledge of certain resource constraints and requirements. This process adjusts activity level start and finish dates to conform to resource availability and use. [D01658]

Resource Analysis
A term for resource leveling and resource smoothing. [D01659]

Resource Assignment
The work on an activity related to a specific resource. [D01660]

Resource Availability
The extent to which resources are available to meet the project's needs. [D03241]

The level of availability of a resource, which may vary over time. [D01661]

Definitions for page R02: 51

***  prev
next  ***

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Top of Page