A
Abstraction
A representation of an entity that contains less information than the entity.
Acceptance
Final approval and receipt of a product or service by the customer.
Acceptance Criteria
The list of requirements that must be satisfied prior to the customer accepting delivery of the product.
Acceptance Management
The process used throughout the project to obtain approval for products or services.
.
Acceptance Test
Formal user testing performed prior to accepting the system (sometimes called client acceptance test or user acceptance test).
Access
To gain entry into, or to instruct or communicate with, the logical, arithmetical, or memory function resources of a computer, computer system, or computer network.
Accessibility
Access to information for people with disabilities comparable to that accorded people without disabilities.
Accountability
The property that enables activities on a system to be traced to an individual.
Accuracy
A quantitative measure of the magnitude of error, preferably expressed as a function of the relative error, a high value of this measure corresponding to a small error.
Acquisition
Generic term for hardware, software, or services acquired from an outside vendor or contractor.
Acquisition Process
The process of acquiring personnel, goods, or services for new or existing work within the general definitions of contracts requiring an offer and acceptance, consideration, lawful subject matter, and competent parties. (Refer to Procurement Plan.)
Acronym
A cryptic name for a project, or a program, based on the first letters of the name or words.
Action Plan
A plan that describes what needs to be done and when it needs to be completed. Project plans are action plans.
Active Project
A project that is in progress (Initiation, Planning and Design, Execution and Build, or Implementation workflow phase).
Activity
An element of work performed in a project. An activity has precise starting and ending dates, incorporates a set of tasks to be completed, consumes resources, and produces tangible results. Activities are often subdivided into tasks and multiple activities may compose a phase. (PMI)
Activity Definition
Identification of the specific activities that must be performed in order to produce project deliverables. (PMI)
Activity Description
Short phrase or label used in a network diagram to describe the scope of work for the activity. (PMI)
Activity Duration Estimate
Estimation of the amount of work that will be needed to complete an activity.
Actual Cost of Work Performed (ACWP)
Total costs incurred (direct and indirect) in accomplishing work during a given time period.
Actual Finish Date
A point in time when work actually ended for the task or activity.
Actual Start Date
The point in time that work actually began on the task or activity.
Adaptive Maintenance
Software maintenance performed to make a computer program usable in a changed environment. (IEEE)
Adaptive System
Describes software that has flexibility as the primary design point.
Administrative Closure
Generating, gathering, and disseminating information to formalize project completion (refer to Project Closeout Report).
Agency
Used to define a general state organizational level consisting of the Agency, Department, or Commission interchangeably.
Agreement
A project agreement is a document, or set of documents, that defines the scope, duration, cost, and deliverables for a project. A project agreement may take the form of a statement of work (SOW), project concept document (Charter), or a business contract (T&C).
Algebraic Language
A programming language that permits the construction of statements resembling algebraic expressions, such as X = Y + 5; e.g., FORTRAN. (IEEE)
Algorithm
A general term used to refer to a mathematical formula or processing routine that, based on parameters, performs a set calculation. A precise set of ordered instructions for carrying out some computation.
Algorithmic Language
A programming language designed for expressing algorithms; e.g., ALGOL. (IEEE)
Allocation
The process of distributing requirements, resources, or other entities among the components of a system. (IEEE)
Alpha Testing
A testing period in which pre-release versions of software products are given to a select group of users before the product is officially deployed.
Alphanumeric
A combination of alphabetic letters, numbers, and special characters (e.g., mailing address).
Alternative Analysis
Breaking down a complex scope situation for the purpose of generating and evaluating different solutions and approaches.
Alternatives
Identification of other approaches or solutions and the impact of tradeoffs to attain the objectives.
Analysis
The study and examination of something complex and the separation into its more simple components.
Anomaly
Anything observed that deviates from expectations. (IEEE Standard 1012)
Application
Generic term for a program, or system, that handles a specific business function.
Application Domain
Refers to the nature of the application.
Application Software
A complete, self-contained program that can perform work for a user. This is in contrast to system software such as an operating system, server processes, and libraries that exist in support of application software.
Application Software
Software designed to fulfill specific needs of a user. (IEEE)
Application System
A set of computer programs, data files, and related procedures that perform a set of related functions.
Approval Cycle
Process of gaining funding and management approval prior to project initiation.
Approve
To accept as satisfactory.
Approximation
A judgment on the order of magnitude of a systems project. The judgment is based on personal experience and knowledge of the general area. Approximations have a must lower level of accuracy than estimates based on work plans but have a higher degree of accuracy than sizings which are "ballpark" estimates.
Architecture
Imposes order and makes interconnections possible. Generally defined as an intermediate step between initial requirements and business functional specifications during which the entire complex of hardware, software, and design considerations are viewed as a whole. Refers to a blueprint for evolving a technical infrastructure.
Architecture Design Review
See Preliminary Design Review.
Argument
An independent variable.
Assessment
A general term for the formal management review of a process. Refers to the process of collecting evidence of performance against plan.
Assumption
Factors that are considered to be true, real, or certain. (PMI)
Assurance
Those activities that demonstrate the conformance of a product or process to specified criteria.
Assurance Plan
A document containing the technical and planning aspects of the assurance activities for a software development or acquisition project. Sometimes called the Software Quality Assurance Plan (SQAP).
Attribute
A named property of an entity.
Audit
A formal and detailed examination of the progress, costs, operations, results, or some other aspect of a project or system performed by an independent party.
Authentication
A process used to verify the integrity of transmitted data.
Authorization
The power granted to approve transactions, procedures, or systems. Defined as the organization authority.
Automation
The conversion of manual processes to automatic operation.
Availability
The time that an operational product must be available for use.
Return to top
B
Backbone
A high-speed computer network designed to interconnect lower-speed networks or clusters of dispersed user devices.
Backup
A "copy" of the current environment (e.g., databases, files) used to preserve the information that will be needed to resume operations.
Backward Pass
The calculation of late finish dates and late start dates for the uncompleted portions of a project. (Determined by working backwards through the network logic from the project's end date.)
Balanced Scorecard
Performance measurement system that allows both financial and non-financial objectives to be assessed for the purpose of making strategic business decisions.
Bar Chart
A management tool, synonymous with Gantt chart, used to plan and control the time and schedule elements of a project. The chart lists the major activities of the project, scheduled start and ending times, and current status (progress). The primary advantage of the bar chart is that the plan (schedule) and progress of the project can be portrayed graphically. Activities and other project elements are listed down the left side of the chart, dates are shown across the top, and activity durations are shown as date-placed horizontal bars.
Baseline
The original plan (for a project, work package, or activity), plus or minus approved changes. A work product that has been formally reviewed and agreed upon and that can be changed only through formal change control procedures. Baselines are usually deliverables and provide the basis for future work. (PMI)
Baseline Plan
The initial approved plan to which deviations will be compared as the project proceeds. A work product that has been formally approved and that can be changed only through formal change control procedures.
Batch
A term describing a method of operating computers. This method takes groups of transactions, executes them, and returns the results, all without human intervention.
Benchmark
A standard figure of merit which measurements or comparisons may be made.
Benefit to Cost Ratio
Determination of the dollars returned for every dollar invested.
Best Practice
Superior method or innovative practice that contributes to improved process performance, improved product quality, or improved business effectiveness.
Beta Testing
A process similar to alpha testing except that it occurs after alpha testing and prior to product release.
Big-bang Approach
A type of hardware / software integration where all of the project elements are combined all at once into one overall system, rather than in stages.
Black Box Testing
Testing that verifies that a given input produces the expected output without knowledge of the code.
Block Diagram
A diagram of a system represented by suitably annotated geometrical figures. (IEEE)
Block-structured Language
A programming language in which sequences of statements (blocks) are defined with begin and end delimiters and variables are not recognized outside the block (e.g., ADA, ALGOL, PL/1). (IEEE)
Boot
To initialize a computer system by clearing memory and reloading the operating system. (IEEE)
Bottom-up
Pertaining to an activity that starts with the lowest level component of a hierarchy proceeding to progressively higher levels. (IEEE)
Brainstorming
Technique used to generate creative ideas through the spontaneous interaction of a group.
Breakdown
Identification of the smallest activities, or tasks, in a job according to a defined procedure.
Bridge
Devices that connect two separate networks. Once bridging is accomplished, the bridge makes interconnected networks look like a single network.
Browser
A program on a computer that fetches and displays documents from the Internet.
Budget
A planned sequence of expenditures over time with costs assigned to specific tasks and activities.
Budget at Completion (BAC)
The estimated total cost of the project at completion.
Budgeted Cost of Work Performed (BCWP)
The sum of the approved cost estimates for activities completed during a given period of time.
Budgeted Cost of Work Scheduled (BCWS)
The sum of the approved cost estimates for activities scheduled to be performed during a given period of time.
Bug
An error in a program or fault in a piece of equipment.
Burn Rate
The number representing the average cost of the project by hour, day, week, phase, or month.
Business Case
Financial analysis of the cost versus benefit of a proposed project.
Business Impact Analysis
Identifies project constraints, alternatives, and related assumptions as they apply to the project.
Business Recovery Plan
A collection of procedures and information that is developed, compiled, and maintained in readiness for use in the event of an emergency or disaster.
Business Rules
A set of practices associated with certain business processes that are required by regulation, law, accounting controls, or common practice.
Return to top
C
Calendar
The time schedule used in developing a project plan. This calendar identifies project work days and can be altered to define the work week.
Calendar Unit
The smallest unit of time used in scheduling a project.
Capability Maturity Model (CMM)
A set of recommended practices in a number of key process areas that have been shown to enhance the capabilities of the software development organization. The CMM was developed for the federal government by the Software Engineering Institute (SEI) of Carnegie Mellon University (CMU).
Champion
The senior executive who takes on personal responsibility for the successful completion of a project.
Change
Modification to original specifications or alterations to achieve expected outcomes.
Change Control
A part of configuration management that reviews, approves, or tracks progress of alterations of a configuration item deliverable.
Change Control Board (CCB)
A formally constituted group of stakeholders responsible for approving or rejecting changes to the project baselines.
Change Management
The formal process of recording, analyzing, estimating, tracking and reporting of changes to the project baseline business functional requirements.
Change Management Plan
The formal, documented plan for managing change within the project.
Chart of Accounts
Any numbering system used to monitor project costs by category (e.g., labor, material, overhead) based on an approved set of accounts.
Charter
A document issued by senior management that formally authorizes the existence of a project. A project charter provides the project manager with authority to apply organizational resources to project activities. (PMI)
Checkpoint
A point in the development process at which project state, status, and results are checked, recorded, and measured.
Client/Server System
Primarily a relationship between processes running on separate machines. A client initiates the dialog by sending requests to the server asking for information or action.
Closeout Phase (Workflow)
The phase a project enters when all implementation activities are complete and the product finished. This is the last stage of the project workflow process prior to operations and maintenance.
Code Review
A formal meeting at which software code is presented and reviewed for approval by interested parties. (IEEE)
Coding
The transforming of logic and data from design specifications into a programming language. (IEEE)
Commercial Off-the-Shelf (COTS)
Hardware and software that can be purchased and put in service without additional development costs or a type of non-developmental software that is supplied by commercial sources.
Communications Management
The processes required to ensure the timely generation, collection, dissemination, storage, disposition, and disposal of project information.
Communications Management Plan
The formal document that defines communication management plans for the project.
Compatibility
The ability to run programs on multiple systems without alteration.
Components
Parts of a program or computer system.
Computer Aided Software Engineering (CASE)
Systems that attempt to automate some or all of the tasks involved in managing, designing, developing, and maintaining software systems.
Confidence Level
A level of confidence, stated as a percentage, for a budget or schedule estimate. The higher the confidence level, the lower the risk.
Configuration
The arrangement of a computer system as defined by the number, nature, and interconnections of constituent parts. (IEEE)
Configuration Management
Methodical storage and recording of all software components and deliverables during development. The process of identifying and defining the baseline items in a system, controlling the release and change of these items, and recording and reporting the status of baseline items and change requests.
Configuration Management System
The process, procedures, and tools used by the development organization to accomplish the configuration management requirement.
Configuration Management Plan
Documents what software configuration management activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. (IEEE)
Connectivity
Refers to the ability to send and receive information between locations, devices, and business services.
Constraint
Boundaries, restrictions, limitations, or obstructions to the successful completion of a project.
Contingencies
Specific provisions for unforeseen elements of cost and schedule within a project (refer to Padding).
Continuity Plan
An alternative for action if the project does not proceed according to plan or if the expected results are not achieved. The development of a management plan that identifies alternative strategies to be used to ensure project success if specified risk events occur. (Sometimes called a Business Continuity Plan)
Contract
A mutually binding agreement that obligates the seller to provide a specified product or service and obligates the buyer to pay for it. Contracts may be either: fixed price (lump sum contracts), cost reimbursable contract, or unit price contract. (PMI)
Contract Administration
Monitoring and control of performance, reviewing progress, making payments, recommending modifications, and approving contractor / supplier actions to ensure compliance with contractual terms during contract execution.
Control
A process for assuring that reality, or actual performance, meets expectations or planned performance.
Control Charts
Graphic displays of the results, over time and against established control limits, of a process.
Conversion
To change one system or data to another system.
Cooperative Processing
Computing that requires two or more distinct processors to complete a single transaction.
Corrective Action
Changes made to bring expected future performance of the project in line with the plan. (PMI)
Corrective Maintenance
Maintenance performed to correct faults in hardware or software. (IEEE)
Correctness
The degree to which a system is free from faults. (IEEE)
Cost / Benefit Analysis
A formal study in which the development, execution, and maintenance costs for a project are matched against the anticipated value of the product.
Cost Estimating
Developing an approximation (estimate) of the cost of the resources needed to complete the project. (PMI)
Cost Performance Index (CPI)
The ratio of budgeted costs to actual costs (BCWP/ ACWP) used to predict potential cost overrun - original cost estimate / CPI = projected cost at completion.
Cost Variance (CV)
Difference between the estimated cost of an activity and the actual cost of an activity.
Coverage Testing
Testing to ensure that all lines of code are exercised.
Crashing
Taking action to decrease the total project duration after analyzing a number of alternatives to determine how to get maximum duration compression for the cost.
Critical Activity
A task, activity, or event that, if delayed, will delay another important event - probably the completion of the project or a major milestone in the project. Any activity on the critical path.
Critical Design Review
Phase transition review for exit of the high-level design phase and entry into the detail design phase.
Critical Path
Derived from the PERT method, this term implies the set of activities that must be completed in sequence and on time if the entire project is to be completed on time. A missed task on the critical path will cause a product delivery delay. This is the longest time for the project from beginning to end.
Critical Path Method (CPM)
A scheduling technique using the precedence diagrams to determine the length of a project based on the end-to-end tasks that are critical to the completion of a project. One of the two most common forms of networking systems. CPM uses a one-time estimate for creating a project schedule.
Critical Success Factors
Objectives, goals, and conditions required for a project to demonstrate success.
Current Finish Date
The current estimate of the point in time when a task or activity will be completed.
Current Start Date
The current estimate of the point in time when a task or activity will begin.
Customer
The individual or organization that specifies the product specifications (requirements) and formally accepts the project deliverables or the person or organization receiving the product or service.
Return to top
D
Data
Describes the numbers, text, graphics, images, and voice stored in a form that can be used by a computer.
Database
A collection of data elements structured into one or larger sets of data.
Data Collection
The gathering and recording of facts, changes, and forecasts for reporting and future planning.
Data Dictionary
A centralized repository of information about data (e.g., meaning, origin, usage, format, relationship to other data elements). A file that defines the organization of a database.
Data Flow Diagram
A picture diagramming how data flows through a system.
Data Standards
Agreed upon terms for defining and sharing data.
Data Warehouse
A process by which operational data is transformed, stored, managed, and delivered for decision support systems.
Debugging
The process of correcting syntactic and logical errors detected during coding.
Decision Trees
Branching chart depicting the actions that occur from various combinations of decisions or conditions.
Decomposition
The process of breaking down activities and the work package to a manageable level.
Defect
A flaw in a system that causes the system to fail to perform as required.
Deliverable
Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. Often used more narrowly in reference to an external deliverable, this is a deliverable that is subject to approval by the project sponsor or customer. (PMI)
Dependency Diagram
Another name for a network or precedence diagram that shows the dependencies among tasks.
Design
The tasks associated with specifying and sketching the features and functions of a new application prior to coding.
Design Specification
A document that prescribes the form, parts, and details of the product.
Development Process
The process for managing the development of the defined product. Usually involves the implementation of a defined System Development Life Cycle (SDLC).
Development Project
The sum of all tasks and activities necessary to build a software product. Development projects provide new functionality or enhanced functionality to a new or existing application system.
Development System
The hardware and software tools and supporting equipment (e.g., operating systems, compilers, browsers) that will be used in software development.
Deviation
A departure from a specified requirement. (IEEE)
Disaster Recovery
Refers to the continuum of preventative planning through restoring technology assets in the event of a catastrophe.
Display
A pictorial, verbal, written, tabulated, or graphical means of transmitting findings, results, and conclusions.
Document
A medium and the information recorded on it. (IEEE)
Document of Understanding
A formal agreement between two parties. A contract that is sometimes referred to as a Statement of Work (SOW).
Documentation
The printed and displayed materials that explain an application to a user. Any written or pictorial information annotating, describing, defining, specifying, reporting, or certifying activities, requirements, procedures, results, or products.
Downward Compatible
Pertaining to hardware or software that is compatible with earlier versions of itself.
Duration
The period of time over which a task takes place. Duration establishes the schedule for a project and is usually expressed as hours, workdays, or workweeks.
Duration Compression
Shortening the project schedule without reducing the project scope.
Return to top
E
Early Finish Date
In the critical path method, the earliest possible point in time on which the uncompleted portions of an activity or project can be finished.
Early Start Date
In the critical path method, the earliest possible point in time in which the uncompleted portions of an activity, or project, can start.
Earned Value (EV)
A method for measuring project performance by comparing the amount of work that was planned with what was actually accomplished to determine if cost and schedule performance are as planned.
Effectiveness
A measure of the quality of attainment in meeting objectives.
Efficiency
A measure of the volume of output received for the input used.
Effort
The amount of work or labor (in hours or workdays) required to complete a task.
Elapsed Time
The time passed before the measuring takes place. It can be measured using labor hour or calendar day.
Encryption
The coding of data to prevent unauthorized access.
Environment
The set of tools and physical surroundings in which software is developed.
Error
A fault or discrepancy between what is computed and what is true.
Estimate
A predicted total of expenditures required to complete a task, activity, or project. An approximate judgement of the effort, cost, or time scale to perform a specified piece of work.
Estimate at Complete (EAC)
The expected total cost of a task or activity when the defined scope of work has been completed. EAC = Actual-to-date + Estimate-to-complete.
Estimate to Complete (ETC)
The expected additional cost of an activity when the defined scope of work has been completed.
Evolutionary Development Model
A system development life cycle approach whose stages consist of expanding increments of an operational software product. (Sometime called evolutionary prototyping.)
Execution and Build (Workflow)
Project workflow phase after Planning and Design but prior to Implementation. Includes activities from detail design to system test.
Exit Criteria
The set of conditions that must be met prior to completing a project phase or application.
Extendible
Describes an architecture that allows new technology to be added as business conditions change.
External Dependency
Any deliverable product or service from other organizations that may be critical to the project.
External Interface
The point where the software system interacts with other software systems, products, or people.
Return to top
F
Failure
A failure is a malfunction of a user's installation. It may result from a bug, incorrect installation, a communication line hit, a hardware failure, and so forth.
Failure Rate
The ratio of the number of failures of a given category to a given unit of measure. (IEEE)
Fast Tracking
Compressing the project schedule by overlapping activities that would normally be done in sequence (e.g., design and construction). (PMI)
Fault
An incorrect step, process, or data definition. (IEEE)
Feasibility
The degree to which the requirements, design, or plans for a system can be implemented under existing constraints. (IEEE)
Feature
A distinguishing characteristic of a software item. (IEEE)
Feedback
Information from some process that is sent back.
File
A named set of records.
Financial Close Out
Accounting analysis of how funds were spent in achieving a project.
Finish Date
The point in time associated with task or activity completion.
Firewall
A combination of hardware and software that separates a local area network (LAN) into two or more parts for security reasons.
Firmware
Hardware that contains a computer program or data that cannot be changed in the user environment.
Flexibility
The ease with which a system can be modified for use in other environments. (IEEE)
Float
The amount of time for a task to be freely scheduled without affecting other tasks in the project. (PMI)
Flowchart
A graphical representation of a process.
Forecasting
The management process of attempting to predict future events.
Formal Inspections
In-process technical reviews of a product of the software development life cycle conducted for the purpose of finding and eliminating defects.
Formal Testing
Testing conducted in accordance with documented test plans and procedures. (IEEE)
Framework
A device used to define the basic structure of materials according to an overall concept of planning and managing.
Function
An activity that spans the entire duration of a software project (e.g., status reporting, quality assurance, verification and validation).
Function Point
A measurement of the functionality of the software product in standard units independent of the coding language.
Function Testing
A part of systems testing that confirms that the application meets the user business requirements.
Functional Decomposition
Modular decomposition in which a system is broken down into components that correspond to system functions and sub-functions. (IEEE)
Functional Design
The process of defining the working relationship among the components of the system. (IEEE)
Functional Requirement
A requirement that specifies a function that a system must be able to perform. (IEEE)
Functional Specification
The formal description of a software system that becomes the blueprint for implementation.
Return to top
G
Gantt Chart
A method of displaying overlapped and partially concurrent activities by using horizontal lines to reflect the time required by each activity. The chart, named for Henry Lawrence Gantt, consists of a table of project task information and a bar chart that graphically displays the project schedule to be used in planning and tracking. (See bar chart.)
Gap Analysis
A format used to clarify the relationship between two factors. A detailed analysis of the reasons that actuals differ from plan.
Gate
Review at the end of a life cycle phase.
Gateway
Hardware or software that translates between two dissimilar protocols.
Goal
A strategic objective designed to provide a target for achievement through the attainment of enabling objectives.
Graph
A diagram that represents the variation of a variable in comparison to other variables.
Granular
Describes the art of writing small modules of code and / or objects.
Graphical User Interface (GUI)
A manner of presentation that makes use of windows, icons, menus, pointers, and scroll bars.
Guideline
Used to define a collection of steps that are recommendations to be followed to meet a stated policy.
Return to top
H
Hardcode
An informal term that describes a programming technique where data or procedures are specifically written into the program instructions.
Hardware
Physical equipment used to process, store, or transmit computer program data.
Hardware Specification
The functions, materials, dimensions, and workmanship that hardware item must satisfy.
Hierarchy
A structure in which components are ranked into levels of subordination. (IEEE)
Hosting
A service in which an application service provider houses an application and support the hardware and software needed to operate an information technology application.
Human Factors
The characteristics, limitations, physical requirements, and psychological needs of people that must be considered in the design and development of a system.
Hyper Text Markup Language (HTML)
The language used to convert text documents into online help and Web pages.
Return to top
I
Implementation Phase (Workflow)
Preparing the product for use by the customer. The workflow phase after Execution and Build prior to Closeout.
Incremental Development
Software development technique in which requirements definition, design, implementation, and testing occur in an overlapping, iterative manner resulting in incremental completion of the project. (IEEE)
Independent Review
A formal examination of a project conducted by an organization other than the development organization.
Independent Verification and Validation (IV&V)
A process whereby the products of the software development life cycle phases are independently reviewed, verified, and validated for completeness and accuracy.
Indicator
A measure or combination of measures that provides insight into a program issue or concept.
Information
The meaningful interpretation of data.
Information Distribution
Making needed information available to project stakeholders on a timely basis.
Infrastructure
Commonly supported tools, techniques, and environments shared by multiple applications and needed by all applications in order to operate properly. Examples of infrastructure include computer operating systems (e.g., MVS, Windows), networks, TCP/IP, security.
Initiation (Workflow)
Organization commitment to a project or phase of a project (Project Initiation workflow phase is the initial phase of the workflow process).
Input
Data from an external source.
Inspection
A semiformal to formal evaluation technique in which a software product is examined by a person or group other than the originator to detect faults errors, and violations of development standards. Sometimes called a walkthrough.
Integration
Describes the work, or device, required to connect two different systems that were not originally designed to work together.
Integration Test
Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them.
Integrity
The state of being free from unacceptable risk of error or omission.
Interface
A connection between two devices or systems.
Internal Interface
The point where the software system under development interacts with other components of the system under development.
Internet
Collection of government, military, university, research, and corporate networks that are connected and can communicate with each other.
Interoperability
The ability to have applications and computers utilizing different technologies work together on a network.
Intranet
An Internet network behind a firewall.
Investment Cost
The total of project cost (Initiation through Closeout phases) plus five (5) years of Operations and Maintenance costs.
Invitation for Bid (IFB)
Equivalent to a request for proposal (RFP) in a narrow view. (PMI)
Issue
A problem to be solved or a decision that has not been made. A list of problems, including a description of the issue, proposed corrective action plan, point of contact, and projected action date.
Issue Management
A process for providing a mechanism to document, research, and resolve issues that arise during a project.
Iterative Development
The repetition of a set of development phases in short successive combinations.
Return to top
J
Joint Application Development (JAD)
The combined effort of client, program, and development staff to define and elicit requirements for a system (JAR) or design a system (JAD). A methodology introduced by IBM to facilitate end-user and developer participation in the application development process.
Joint Application Requirements (JAR)
The joint effort of client, program, and development staff to define and elicit requirements for a system.
Return to top
K
Kernel
The portion of the operating system that is kept in memory at all times. (IEEE)
Key
A record identifier used for information retrieval.
Return to top
L
Lag
The amount of time after one task is started or finished before the next task may be started or finished.
Language
A means of communication, with syntax and semantics, consisting of a set of representations, conventions, and associated rules. (IEEE)
Late Finish Date
In the critical path method, the latest possible point in time that an activity may be completed without delaying a specified milestone.
Late Start Date
In the critical path method, the latest possible point in time that an activity may begin without delaying a specified milestone.
Lead
The amount of time that precedes the start of work on another task.
Leadership
The way in which the project manager influences the project team to behave in a manner that will facilitate goal achievement.
Legacy System
In-place systems using older technologies.
Lessons Learned
Information (positive or negative) resulting from feedback on project performance that may benefit future projects.
Life Cycle
Period of time that starts when a software product is conceived (concept formation) and ends when the software is no longer available for use (retirement).
Life Cycle Costing
The concept of including acquisition, operating, and disposal costs when evaluating various alternatives.
Limited Production
A production system that is rolled out to a predetermined subset of users and proven to perform as expected.
Listing
An orderly display or printout of data items. (IEEE)
Local Area Network (LAN)
A communications system confined to a limited area, typically a building, occasionally a group, and linking computers together via cable.
Lockout
A computer resource allocation technique in which shared resources are protected by permitting access by only one device at a time. (IEEE)
Logical Relationship
A dependency between two project activities.
Return to top
M
Maintainability
The ease with which maintenance support and changes can be performed on a computer system.
Maintenance
Refers to the ongoing activity that keeps software functioning in a technical and business environment (production). Maintenance may be corrective maintenance (defect repair), adaptive maintenance (preventing a defect before it occurs in a changed environment), or perfective maintenance (modifications to support business functional requirements).
Master Schedule
An executive summary that identifies the major components of a project against which dates for achievement are estimated, particularly those achievement dates designated as milestones.
Measure
1) To estimate or appraise by a criterion. 2) The result of counting or otherwise quantifying an attribute of a process or product. Measures are numerical values assigned to software attributes according to defined criteria. Often the terms measure and metric are used synonymously.
Measurement
The act or process of measuring. This process can be based on estimation or direct measurement.
Method
A way of doing something.
Methodology
A set of formal protocols followed when performing a task.
Metric
Quantitative measures of extent or degree to which software possesses and exhibits a certain characteristic, quality, property, or attribute.
Middleware
Software that hides the complexity of the networked computing environment from the users and application programmers. This layer of software provides a common interface and translation between an application and an operating system or other system services.
Milestone
A significant point or event in the project. (PMI)
Milestone Schedule
A summary-level schedule that identifies the major schedule milestones. (PMI)
Mistake
A human action that produces an incorrect result. (IEEE)
Mitigation
Taking steps to lessen risk by lowering the probability of occurrence or the impact of occurrence.
Model
A way of looking at reality, usually for the purpose of abstracting and simplifying it to make it understandable in a particular context.
Modular Programming
Programming that has as its fundamental assumption that a large piece of software should be separated into its constituent parts or modules thereby making for easier and faster development and maintainability. Modules were traditionally called subroutines or functions and now are often called objects.
Modularization
The splitting up of a software system into a number of manageable phases.
Monitoring
The capture, analysis, and reporting of actual performance compared to planned performance.
Return to top
N
Network
Describes the physical hardware and software connections between computers allowing information to be shared and electronic communications to take place.
Network Analysis
The process of identifying early and late start and finish dates for the uncompleted portions of project activities.
Network Diagram
The logical representation of tasks that defines the sequence of work in a project.
Node
One of the defining points of a network.
Nonconformance
A deviation from specified standards, procedures, plans, requirements, or design.
Non-Developmental Software (NDS)
Deliverable software that is not developed under contract but is provided by the vendor, contractor, or third-party supplier.
Return to top
O
Object
An entity that contains or receives data.
Objective
A concise statement of what the project is to achieve. The objectives are subordinate to higher level goals.
Operating System
System software that controls data storage, input and output to and from the keyboard, and the execution of applications written for it. It performs base services: prioritizing work, scheduling, memory management, etc.
Operations and Maintenance Cost
Cost to operate, support, and maintain a system after development. Operations and maintenance cost should be calculated on a five (5) year time line.
Operations and Maintenance Phase
The period of time in the software life cycle during which the software product is employed in its operational environment. (IEEE)
Opportunity Cost
The potential net benefit, or value, of an information technology investment that is lost by selecting an alternative investment.
Order of Magnitude
An approximate estimate made without detailed information. This type of estimate is used during the formative stages of a project (Initiation workflow phase).
Organization Breakdown Structure (OBS)
A depiction of the project organization arranged as it relates work packages to organizational units.
Output
Pertaining to data transmitted to an external destination. (IEEE)
Outsource
The practice of contracting out a project, service, or information technology operation.
Return to top
P
Package Acquisition
The purchase, or lease, of software from an outside source.
Package System
A "store bought" pre-defined application solution meeting a specific business need.
Padding
A standard project management tactic used to add extra time or money to estimates to cover for the uncertainty and risk of predicting future project activities.
Parallel Testing
The task of executing both the "new" and the "old" systems and comparing results.
Parametric Estimating
An estimating technique that uses a statistical relationship between historical data and other variables (e.g., lines of code, function points).
Pareto Diagram
A histogram, ordered by frequency of occurrence, which shows how many results were generated by each individual cause.
Path
A sequence of lines and nodes in a project network.
Path Testing
Testing to ensure that all logic paths within the code are exercised (Branch Testing).
Payback
A measure of time that indicates how much time will be required to recover (payback) an original investment.
Peer Review
A technical review in which a project artifact is inspected by a small group of experts.
Percent Complete
An estimate, expressed as a percentage (%), of the amount of work that has been completed.
Perfective Maintenance
Software maintenance performed to improve the performance, maintainability, or other attributes of a computer program. (IEEE)
Performance
The calculation of achievement used to measure and manage project deliverables.
Performance Evaluation
The technical assessment of a system or process to determine how effectively operating objectives have been achieved.
Performance Requirement
A requirement that imposes conditions on a functional requirement (e.g., speed, accuracy, storage usage). (IEEE)
Performance Testing
Verification of batch and on-line response time through volume and stress testing to determine throughput, response time, and availability.
Phase
The divisions of a software development life cycle into discrete stages (e.g., requirements, design, code, test, etc.). The period of time during the life cycle of a project in which a related set of software engineering activities is performed.
Phase Transition Review
Review at the end of a life cycle phase.
Pilot
An approach designed to evaluate a preliminary version of a system in a simulated production environment.
Pilot Testing
The testing process, equivalent to beta testing, that organizations use to test applications in a pre-production environment.
Plan
An intended future course of action.
Planned Finish Date
A point in time when work is scheduled to end for the task or activity.
Planned Start Date
The point in time that work is scheduled to begin on the task or activity.
Planned Value
The sum of the approved cost estimates for activities scheduled to be performed during a given period.
Planning and Design Phase (Workflow)
The phase a project enters after Initiation and prior to Execution and Build.
Platform
The hardware and support software with which a program is intended to operate.
Policy
High-level, overall statements that provide direction to state organizations where uniformity of action is essential.
Portfolio Management
The centralized management of one or more portfolios, which includes identifying, prioritizing, authorizing, managing, and controlling projects, programs, and other related work, to achieve specific strategic business objectives. (PMI)
Precedence
When one task must be completed before another task can be started, the first task is said to have precedence over the other.
Preliminary Design Review
Phase transition review for the preliminary high-level (architectural) design life cycle phase. Also known as Architectural Design Review.
Problem
In risk management, a problem is a risk that has materialized. Deviation from the normal or expected results.
Problem Resolution
The finding of a solution to technical, scheduling, or resource availability problems.
Procedure
A prescribed method, or technique, for performing work.
Process
The step-by-step sequence of activities (systematic approach) that must be carried out to complete a project.
Process Model
A model of a software project that depicts the relationship of the project functions, activities, and tasks to the major milestones, baselines, reviews, work products, project deliverables, and formal approvals that span the project. The State of North Carolina uses the IEEE process model.
Procurement Plan
The formal, documented, and approved plan to procure needed resources (hardware, software, or networks) and staff needed to complete the project.
Product
The end result of a process.
Product Baseline
The end result of a process.
Product Integration
Assembling individual hardware and software components into a functional whole.
Production Library
A software library containing software approved for current operational use. (IEEE)
Program -
A group of related projects managed in a coordinated manner.
Program Evaluation and Review Technique (PERT) -
The PERT method uses the concepts of milestones, activities, and slack time to calculate the critical path. The chart, which resembles a flow chart, depicts a box to represent each project task and a line connecting two boxes to represent the relationship between tasks.
Programming
The art of writing, in a computer understandable language, a set of instructions that produces software.
Project
A temporary endeavor (begin and end dates) undertaken (resources and plan) to create a unique product or service (business functional requirement). The combined resources (people, machines, materials), processes, and activities that are dedicated to building and delivering a product, or service to a customer.
Project Budget
The amount and distribution of money approved and allocated to a project.
Project Cost
Cost of project development cost from Project Initiation through Project Closeout phases.
Project File
A central repository of material pertaining to a project. (Project Notebook) (IEEE)
Project Duration
The time it takes to complete the entire project.
Project Lifecycle
A collection of generally sequential project phases whose name and number are determined by the control needs of the organization involved in the project.
Project Management
The combination of systems, techniques, and people required to successfully complete a project on time and within budget. (PMI)
Project Manager
The senior person responsible for the entire project.
Project Objectives
A description of the specific functionality that the project intends to accomplish.
Project Plan
A formal, approved document that describes the technical and management approach to be followed for a project and is used to guide both project execution and project control.
Project Sponsor
The department "customer" who will authorize project initiation, and who will receive, accept, and use the software product or service.
Proof of Concept
Software written to gather requirements, prove or test a technology, language, environment, or approach. A proof of concept should not be implemented as a production system.
Protocol
A set of rules and specifications that describes how a piece of software will behave and how other pieces of software must behave in order to work with the first piece of software.
Prototype
A small working version of a proposed system used to gather requirements, validate requirements, "show" what the system will look like, or demonstrate proof-of-concept.
Pseudo Code
A combination of programming language and natural language used for computer program design.
Return to top
Q
Quality (Product)
Conformance to business functional requirements with defect-free products. Quality reflects both the completeness of software or system features and functions, and error-free operation.
Quality (Process)
Verification and validation to established policies, standards, procedures and guidelines for software development.
Quality Assurance
Within the State of North Carolina, the process tracking and oversight function for monitoring project performance, adherence to commitments, and budget requirements.
Quality Assurance Plan
Defines the activities performed to provide assurance that the software-related items delivered to the customer conform to the established and contracted technical requirements. The Software Quality Assurance Plan also describes how the project will be audited to ensure that the policies, standards, practices, procedures, and processes applicable to the project are followed.
Quality Engineering
The process of incorporating reliability, maintainability, and other quality factors into software products.
Quality Management
A collection of policies, plans, procedures, specifications, and requirements.
Quality Metric
A quantitative measure of the degree to which an item possesses a given quality attribute.
Return to top
R
Rapid Application Development (RAD)
Methodology that emphasizes application development as an iterative prototype-to-production process.
Record
A set of data treated as a unit.
Recovery Procedures
Processes and procedures used to restore critical applications that provide support for vital business processes.
Re-engineering
Examination and alteration of an application system to reconstitute it in a new form (renovation). The practice of adapting existing systems to perform new or enhanced functions usually significantly different than the existing system.
Regression Test
Selective re-testing to detect errors or faults introduced during modification of a system.
Relational Database
A collection of data that is organized into tables so that relationships between and among data can be established.
Release
Specific version of a piece of software.
Release Management
The process used to manage the release of software into different environments (test, pre-production, production).
Reliability
Refers to the extent in which consistent outcomes are achieved. The degree of dependability usually expressed as the average / mean time to failure.
Resource Leveling
The process of shifting resources to even out the workload of team members.
Request for Proposal (RFP)
Formal statement by a department that they are soliciting enterprises to bid on a contract for a program, system or service.
Requirements
The statement of needs by a user that triggers the development of a program, system, or project. May be called business functional requirements or requirement specifications.
Requirements Allocation
The process of distributing requirements of a system to subordinate software and hardware elements.
Requirement Review
Phase transition review for the requirements life cycle phase.
Research and Development Project
A definition of a project type essentially exploring options for developing new systems or work products.
Reserve
A provision in the project plan to mitigate cost or schedule risk.
Resource
Something that is available for use.
Resource Leveling
Any form of network analysis in which scheduling decisions are driven by resource management concerns.
Resource Planning
Determination of the resources (people, equipment, material) needed and in what quantities.
Responsibility Matrix
Chart of project roles and responsibilities.
Retirement
Permanent removal of a system or program. (IEEE)
Reuse
Hardware or software developed for one application that can be used, in whole or in part, to satisfy the requirements of another system.
Review
A process or meeting during which a work product is discussed by interested parties. (IEEE)
Rework
Action taken to bring a nonconforming item into compliance with requirements. (PMI)
Risk
The probability that a project will experience undesirable events, which may create cost overruns, schedule delays, or project cancellation. The identification, mitigation, tracking, and management of those elements creating the risk situation.
Risk Analysis
An evaluation of the feasibility or probability that the outcome of a project will be the desired outcome.
Risk Assessment
Review, examination, and judgment of whether or not the identified risks are acceptable.
Risk Management
The process of assessing potential risks and reducing those risks within budget, schedule, and other constraints.
Risk Management Plan
A formal documented and approved document that identifies risk, assesses the impact of the risk, and provides the project response to the risk.
Risk Mitigation
Reduction in the impact of risk on the project scope, schedule, cost, or quality.
Robustness
The degree to which a component can function correctly in a stressful environment. (IEEE)
Rollout Plan
A formal, documented, and approved plan to rollout the system or product.
Root Cause
The primary cause for a problem or action.
Return to top
S
Scalable
A term describing an architecture or software that can handle expansion in the use as the need arises without adversely impacting systems management and operations.
Schedule
The planned dates for performing activities and the planned dates for meeting milestones.
Schedule Milestone
A significant event in the project schedule, such as an event restraining future work or marking the completion of a major deliverable. A schedule milestone has zero duration. Sometimes called a milestone activity. (PMI)
Schedule Variance
Difference between the scheduled completion of an activity and the actual completion of that activity.
Scope
The sum of the products and services to be provided by the project.
Scope Change
Any change to the project scope. Scope changes almost always require adjustment to the project cost and schedule. ("Scope Creep" - negative control of change.)
Scope Creep
The gradual addition of new requirements to the original product specifications.
Scope Statement
A document capturing the sum of products and services to be provided by the project.
Security
The degree to which a software product is safe from unauthorized use.
Sequential
Pertaining to the occurrence of two or more events where one must finish before the second can begin (e.g., serial process).
Server
A computer on a network that makes applications, print services, data, and communications available.
Simulation
A model that behaves like the proposed system.
Sizing
The process of estimating time at a relatively low level of confidence.
Slack
see float.
Slippage
The tendency of a project to exceed original estimates of cost and time.
Software
Computer programs, systems, and the associated documentation that describes them.
Software Development Life Cycle (SDLC)
The period of time that begins with the decision to develop a software product and ends when the software is delivered.
Software Development Process
The process by which user needs are translated into a software product.
Software Metric
A standard of measurement. It is a number assigned to a quantifiable concept that relates to a software product or to the process that created it.
Software Product Life Cycle
The set of all events and endeavors that occur within the birth-to-death cycle of a software product.
Software Project Management Plan
The controlling document for managing a software project. The SPMP defines the technical and managerial project functions, activities, and tasks necessary to satisfy the requirements of a software project.
Software Requirements Specifications
General term for the wide variety of paper-based descriptions of a program or system. Usually a document that contains the complete set of business functional requirements.
Specification
A detailed formulation, in document form, providing a definitive description of a system for the purpose of developing that system.
Spiral Model
Software development process where constituent activities are performed iteratively until all software requirements are met. (IEEE)
Staffing Plan
The formal, documented, and approved plan that identifies and allocates resources needed to complete the project.
Stakeholder
A person, or people, who will be affected either positively or negatively by project completion.
Standalone
Describes a computer workstation where the computer is not connected to any other computer on a network.
Standard
An approved, documented, and available set of criteria used to determine the adequacy of an action or object.
Statement of Work (SOW)
A narrative description of products or services to be supplied under contract.
Status Report
A management report, sometimes called an activity report, that provides the status of project activities over a period of time.
Strategic Plan
The long-range plan, outlining organizational goals and direction over a period of time, where the horizon is usually three to five years.
Strategy
A framework guiding choices that determine the nature and direction needed to attain an objective.
Stress Test
Testing that ensures that the system performs as expected under a high volume of transactions, high number of users. Sometimes called load testing.
Subcontract
Delegating tasks or sub-projects to contractors or other organizations.
System
A linked collection of programs, or components that performs a generic business or technical function.
System Design
The process of defining the hardware and software architecture for a system to satisfy specified requirements.
System Design Review
A review conducted to evaluate the manner in which requirements for a system have been allocated to configuration items. (IEEE)
System Integration
The activities involved in assembling hardware / software components into a deliverable product.
System Requirements Review
A review conducted to evaluate the completeness and adequacy of the defined requirements. (IEEE)
System Test
The final stage of testing on a completed project (prior to client acceptance test) when all hardware and software components are put together and tested as a whole.
Return to top
T
Tactical Plan
Specific improvements, or changes, that will be carried out in a fairly short time span (usually twelve (12) months).
Task
A discreet, identifiable, meaningful, and cohesive component (unit) of work on a project (usually 40 to 80 hours of effort). This is the smallest measurable unit of work producing a deliverable and is the lowest level of work on a project.
Task Description
A description that defines all the work required to complete a project task or activity including input, output, expected results, and quality specifications.
Team
A group of individuals working towards a common goal.
Techniques
Technical and managerial procedures that aid in the evaluation and improvement of the software development process. (IEEE)
Test
An activity in which a component is executed under specified conditions with the results observed and recorded. (IEEE)
Test Plan
A formal, documented, and approved plan that describes the scope, approach, resources, and schedule of intended test activities.
Test Phase
The period of time in the software life cycle during which the software product is evaluated and integrated to determine if requirements have been met. (IEEE)
Testing
The process of exercising, or evaluating, software by manual or automated means to demonstrate that the software satisfies specified requirements or to identify differences between expected and actual results. The set of defect removal tasks that include execution of all, or part, of an application on a computer.
Test Specifications
A document that prescribes the process and procedures to be used to verify that a product meets the business functional requirements.
Time Scale
Planned versus actual time needed to complete a task, activity, phase, or project.
Topology
The map or plan of a network.
Total Cost of Ownership (TCO)
The present value of all costs associated with an information technology investment that is incurred over the expected life of the investment.
Traceability
Manual or automated processes and procedures that map all software components from business function requirements through test cases.
Training Plan
The formal, documented, and approved plan that identifies the schedule and users to be trained on use of the program or system.
Transaction
The input / output to a system resulting from a business event.
Transition Plan
A document that specifies how a product is to transition from development to production support.
Trigger
Symptom or warning sign that generates action (e.g., risk management). (PMI)
Return to top
U
Unit Test
The testing carried out personally by individual programmers on their own code.
Usability
The quality of an application system that enables it to be easily understood and conveniently employed by the user.
User Manual
A document that represents the information necessary to employ the system. (IEEE)
User Testing
Testing process in which the user community, rather than the developer, performs the tests.
Utility Program
A system program designed to perform a common task.
Return to top
V
Validation
The process of evaluating software to assure that the "right product has been built"; that is, to assure that it meets functional and performance requirements (completeness).
Value Analysis
An activity devoted to optimizing cost performance. The systematic use of techniques that identify the required functions, establish values for the functions, and provide the functions at the lowest overall cost without loss of performance.
Variance
Actual deviation from plan.
Verification
The process that assures that the software has been "built right", that is, each intermediate product meets specific requirements (correctness).
Verification and Validation
The process of determining whether the requirements for a system are complete and correct. (IEEE)
Vision
The vision, or aim, expresses the purpose and rationale for achieving a defined objective. The vision is generally expressed in generic or abstract terms.
Return to top
W
Walkthrough
A software inspection process, conducted by peers, to evaluate the software element.
Waterfall Model
A software development life cycle approach developed by Winston W. Royce that partitions a project into manageable phases (requirements, design, implementation, and test).
White Box Testing
Testing that verifies that specific lines of code work as specified.
Wide Area Network (WAN)
A network where the computers are separated by significant distances and telecommunications links are implemented.
Work Breakdown Structure (WBS)
A task oriented family tree of phases, activities, and tasks that organizes, defines, and graphically displays the total work to be accomplished. A formal analysis of the activities, tasks, and sub-tasks that must be accomplished to build a software project. A product or activity oriented hierarchy tree depicting the elements of work that need to be accomplished in order to deliver a product. A deliverables-oriented grouping of project elements that organizes the total scope of the project.
Work Package
A specification for the work to be accomplished in completing an activity or task. A deliverable at the lowest level of the work breakdown structure.
Work Product
Any tangible item that results from a project function, activity, or task.
Workstation
Any machine with all of its installed storage, processing, and communications that can be either standalone or networked.
World Wide Web (WWW)
HTML-based Internet system, developed at the European Center for Nuclear Research (CERN) in Geneva that links documents located on geographically dispersed servers.
Return to top
X
Return to top
Y
Return to top
Z
* Definitions were extracted from Assessment and Control of Software Risks by Capers Jones (1994); Managing Software Development Projects (Second edition) by Neal Whitten (1995); IEEE Standards Collection: Software Engineering (1997 Edition); A Guide to the Project Management Body of Knowledge by the Project Management Institute Standards Committee (1996 / 2004); Best Practices in IT Architecture Planning and Implementation by Larry DeBoever; Essential Client/Server Survival Guide by Robert Orfali; Software Assurance Standard NASA-STD-2201-93, and The Complete Idiot's Guide to Project Management by Sunny and Kim Baker. |
