Software Engineering Glossary

Software Engineering Glossary

"C" Glossary Content

Press the "Letter" button to view the glossary contents for that specific letter.

Other topics within the glossary:

call	A transfer of control from one software module to another, usually with the implication that control will be returned to the calling module. Contrast with: go to A computer instruction that transfers control from one software module to another as in (1) and, often, specifies the parameters to be passed to and from the module. To transfer control from one software module to another as in (1) and, often, to pass parameters to the other module. Syn: cue See also: call by name; call by reference; call by value; call list; calling sequence.
call by address	See: call by reference.
call by location	See: call by reference.
call by name	A method for passing parameters, in which the calling module provides to the called module a symbolic expression representing the parameter to be passed, and a service routine evaluates the expression and provides the resulting value to the called module. Note: Because the expression is evaluated each time its corresponding formal parameters used in the called module, the value of the parameter may change during the execution of the called module. Contrast with: call by reference; call by value.
call by reference	A method for passing parameters, in which the calling module provides to the called module the address of the parameter to be passed. Note: With this method, the called module has the ability to change the value of the parameter stored by the calling module. Syn: call by address; call by location. Contrast with: call by name; call by value.
call by value	A method of passing parameters, in which the calling module provides to the called module the actual value of the parameter to be passed. Note: With this method, the called module cannot change the value of the parameter as stored by the calling module. Contrast with: call by name; call by reference.
call graph	A diagram that identifies the modules in a system or computer program and shows which modules call one another. Note: the result is not necessarily the same as that shown in a structure chart. Syn: call tree; tier chart. Contrast with: structure chart. See also: control flow diagram; data flow diagram; data structure diagram; state diagram.
call list	The ordered list of arguments used in a call to a software module.
call trace	See: subroutine tree.
call trace	See: call graph.
calling sequence	A sequence of computer instructions and, possibly, data necessary to perform a call to another module.
Capability Maturity Model	A description of the stages through which software organizations evolve as they define, implement, measure, control, and improve their software processes. This model provides a guide for selecting process improvement strategies by facilitating the determination of current process capabilities and the identification of the issues most critical to software quality and process improvement.
CASE	Acronym for computer-aided software engineering.
case	A single-entry, single-exit multipleway branch that defines a control expression, specifies the processing to be performed for each value of the control expression, and returns control in all instances to the statement immediately following the overall. Syn: multiple exclusive selective construct. Contrast with: go to; jump; if-then-else. See also: multiple inclusive selective construct.
catastrophic failure	A failure of critical software.
causal analysis	The analysis of defects to determine their underlying root cause.
causal analysis meeting	A meeting, conducted after completing a specific task, to analyze defects uncovered during the performance of that task.
CCB	Acronym for configuration control board. Acronym for change control board.
CDR	Acronym for critical design review.
certification	A written guarantee that a system or computer program complies with it specified requirements and is acceptable for operational use. For example, a written authorization that a computer system is secure and is permitted to operate in a defined environment. 3. The formal demonstration that a system or component complies with its specified requirements and is acceptable for operational use. 4. The process of confirming that a system or component complies with its specified requirements and acceptable for operational use.
change control	See: configuration control.
change control board	See: configuration control board.
change dump	A selective dump of those storage locations whose contents have changed since some specified time or event. Syn: differential dump. See also: dynamic dump; memory dump; postmortem dump; selective dump; snapshot dump; static dump.
channel capacity	The maximum amount of information that can be transferred on a given channel per unit of time; usually measured in bits per second or in baud. See also: memory capacity; storage capacity.
chapin chart	See: box diagram.
character	A letter, digit, or other symbol that is used to represent information.
character type	A data type whose members can assume the values of specified characters and can be operated on by character operators, such as concatenation. Contrast with: enumeration types; integer type; logical type; real type.
characteristic	See: data characteristic; software characteristic.
check box	A small, square box in a dialog box that can be selected or cleared. When a check box is selected, an X appears in the box. A check box represents an option that you can turn on or off.
checkpoint	A point in a computer program at which program state, status, or results are checked or recorded.
chief programmer	The leader of a chief programmer team; a seniorlevel programmer whose responsibilities include producing key portions of the software assigned to the team, coordinating the activities of the team, reviewing the work of the other team members, and having an overall technical understanding of the software being developed. See also: backup programmer; chief programmer team.
chief programmer team	A software development group that consists of a chief programmer, a backup programmer, a secretary/librarian, and additional programmers and specialists as needed, and that employs support procedures designed to enhance group communication and to make optimum use of each member's skills. See also: backup programmer; chief programmer; egoless programming.
choose	To pick an item by using the keyboard or mouse to begin an action. You choose a command on a menu to perform a task, and you choose a program-item icon to start an application.
CI	Acronym for configuration item.
clear	To turn off an option by removing the X from a check box. You clear a check box either by clicking it, or by selecting it and then pressing the SPACEBAR.
clear	To set a variable, register, or other storage location to zero, blank, or other null value. See also: initialize; reset.
click	To press and release a mouse button quickly.
client application	A Windows-based application that can accept linked or embedded objects.
Clipboard	A temporary storage area in memory that is used to transfer information. You can cut or copy information onto the Clipboard and then paste it into another document or application.
ClipBook page	A piece of information you have pasted onto your Local ClipBook. The piece of information (called a page) is permanently saved. Information on a ClipBook page can be copied back onto the Clipboard and then pasted into a document. You can share a ClipBook page with other people so that they can link to the page or embed it in another document.
close	To remove a window or dialog box, or quit an application. You close a window by choosing the Close command from the Control menu. When you close an application window, you quit the application.
closed loop	A loop that has no exit and whose execution can be interrupted only by intervention from outside the computer program or procedure in which the loop is located. Contrast with: UNTIL; WHILE.
closed subroutine	A subroutine that is stored at one given location rather than being copied into a computer program at each place that it is called. Contrast with: open subroutine.
CM	Acronym for configuration management.
CMM	Acronym for capability maturity model.
code	In software engineering computer instruction and data definitions expressed in a programming language or in a form output by an assembler, compiler, or other translator. See also: source code; object code; machine code; microcode. To express a computer program in a programming language. A character or bit pattern that is assigned a particular meaning; for example, a status code.
code breakpoint	A breakpoint that is initiated upon execution of a given computer instruction. Syn: control breakpoint. Contrast with: data breakpoint. See also: dynamic breakpoint; epilog breakpoint; programmable breakpoint; prolog breakpoint; static breakpoint.
code generator	A routine, often part of a compiler, that transforms a computer program from some intermediate level of representation (often the output of a root compiler or parser) into a form that is closer to the language of the machine on which the program will execute. 2. A software tool that accepts as input the requirements or design for a computer program and produces source code that implements the requirements or design. Syn: source code generator. See also: application generator.
code inspection	See: inspection.
code of ethics standard	A standard that describes the characteristics of a set of moral principles dealing with accepted standards of conduct by, within, and among professionals.
code review	A meeting at which software code is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Contrast with: design review; formal qualification review; requirements review; test readiness review.
code trace	See: execution trace.
code walkthrough	See: walkthrough.
coding	In software engineering, the process of expressing a computer program in a programming language. The transforming of logic and data from design specification (design descriptions) into a programming language. See also: software development process.
cohesion	The manner and degree to which the tasks performed by a single program module are related to one another. Types include coincidental, communicational, functional, logical, procedural, sequential, and temporal. Syn: module strength. Contrast with: coupling.
coincidental cohesion	A type of cohesion in which the tasks performed by a software module have no functional relationship to one another. Contrast with: communicational cohesion; functional cohesion; logical cohesion; procedural cohesion; sequential cohesion; temporal cohesion.
collapse	To hide additional directory levels below a selected directory in the directory tree.
color scheme	A combination of complementary colors for screen elements.
command	An expression that can be input to a computer system to initiate an action or affect the execution of a computer program; for example, the "log on" command to initiate a computer session. A word or phrase, usually on a menu, that you choose to carry out an action. You choose a command from a menu or type a command at the MS-DOS prompt. You can also type a command in the Run dialog box in File Manager or Program Manager.
command button	A button in a dialog box that carries out or cancels the selected action. Two common command buttons are OK and Cancel. Choosing a command button that contains an ellipsis (for example, Browse... ) causes another dialog box to appear.
command language	A language used to express commands to a compute system. See also: command-driven.
command-driven	Pertaining to a system or mode of operation in which the user directs the system through commands. Contrast with: menu-driven.
comment	Information embedded within a computer program, job control statements, or set of data that provides clarification to human readers and that does not effect machine interpretation. A descriptive message that you can assign to a shared resource or a computer. The comment appears in the Connect dialog box when others select the computer or resource.
commitment	A pact that is freely assumed, visible, and expected to be kept by all parties.
commitment to perform	See: common features.
common	See: common storage.
common area	See: common storage.
common block	See: common storage.
common cause (of a defect)	A cause of a defect that is inherently part of a process or system. Common causes affect every outcome of the process and everyone working in the process. (See special cause for contrast.)
common coupling	See: common-environment coupling.
common data	See: global data.
common features	The subdivision categories of the CMM key process areas. The common features are attributes that indicate whether the implementation and institutionalization of a key process area is effective, repeatable, and lasting. The CMM common features are the following: commitment to perform - The actions the organization must take to ensure that the process is established and will endure. Commitment to Perform typically involves establishing organizational policies and senior management sponsorship. ability to perform - The preconditions that must exist in the project or organization to implement the software process competently. Ability to Perform typically involves resources, organizational structures, and training. activities performed - A description of the roles and procedures necessary to implement a key process area. Activities Performed typically involve establishing plans and procedures, performing the work, tracking it, and taking corrective actions as necessary. measurement and analysis - A description of the need to measure the process and analyze the measurements. Measurement and Analysis typically includes examples of the measurements that could be taken to determine the status and effectiveness of the Activities Performed. verifying implementation - The steps to ensure that the activities are performed in compliance with the process that has been established. Verification typically encompasses reviews and audits by management and software quality assurance.
common storage	A portion of main storage that can be accessed by two or more modules in a software system. Syn: common area; common block. See also: global data.
common-environment coupling	A type of coupling in which two software modules access a common data area. Syn: common coupling. Contrast with: content coupling; control coupling; data coupling; hybrid coupling; pathological coupling.
communicational cohesion	A type of cohesion in which the tasks performed by a software module use the same input data or contribute to producing the same output data. Contrast with: coincidental cohesion; functional cohesion; logical cohesion; procedural cohesion; sequential cohesion; temporal cohesion.
communications settings	Settings that specify how information is transferred from your computer to a serial device (usually a printer or modem).
compaction	In microprogramming, the process of converting a microprogram into a functionally equivalent microprogram that is faster or shorter than the original. See also: local compaction; global compaction.
comparator	A software tool that compares two computer programs, files, or sets of data to identify commonalities or differences. Typical objects of comparison are similar versions of source code, object code, database files, or test results.
compatibility	The ability of two or more systems or components to perform their required functions while sharing the same hardware or software environment. The ability of two or more systems or components to exchange information. See also: interoperability.
compile	To translate a computer program expressed in a high order language into its machine language equivalent. Contrast with: assemble, decompile; interpret.
compile-and-go	An operating technique in which there are no stops between the compiling, linking, loading, and execution of a computer program.
compiler	A computer program that translates programs expressed in a high order language into their machine language equivalents. Contrast with: assembler; interpreter. See also: cross-compiler; incremental compiler; root compiler.
compiler code	Computer instructions and data definitions expressed in a form that can be recognized and processed by a compiler. Contrast with: assembly code; interpretive code; machine code.
compiler compiler	See: compiler generator.
compiler generator	A translator or interpreter used to construct part or all of a compiler. Syn: compiler compiler; metacompiler.
complexity	The degree to which a system or component has a design or implementation that is difficult to understand and verify. Contrast with: simplicity. Pertaining to any of a set of structure-based metrics that measure the attribute in (1).
component	One of the parts that make up a system. A component may be hardware or software and may be subdivided into other components. Note: The terms "module," "components," and "unit" are often used interchangeably or defined to be subelements of one another in different way depending upon the context. The relationship of these terms is not yet standardized.
component standard	A standard that describes the characteristics of data or program components.
component testing	Testing of individual hardware or software components or groups of related components. Syn: module testing. See also: integration testing; interface testing; system testing; unit testing.
composite type	A data type each of whose members is composed of multiple data items. For example, a data type called PAIRS whose members are ordered pairs (x, y). Contrast with: atomic type.
compound device	A device that plays specific media files. For example, to use a compound device, such as a MIDI sequencer, you must specify a MIDI file.
computer instruction	A statement in a programming language, specifying an operation to be performed by a computer and the addresses or values of the associated operands; for example, Move A to B. See also: instruction format; instruction set. Loosely, any executable statements in a computer program.
computer language	A language designed to enable humans to communicate with computers. See also: design language; query language; programming language.
computer name	The name that identifies your computer to other people on the network.
computer performance evaluation	An engineering discipline that measures the performance of computer systems and investigates methods by which that performance can be improved. See also: system profile; throughput; utilization; workload method.
computer program	A combination of computer instructions and data definitions that enable computer hardware to perform computational or control functions. See also: software.
computer program abstract	A brief description of a computer program that provides sufficient information for potential users to determine the appropriateness of the program to their needs and resources.
computer resource allocation	The assignment of computer resources to current and waiting jobs; for example, the assignment of main memory, input/output devices, and auxiliary storage to jobs executing concurrently in a computer system. See also: dynamic resource allocation; storage allocation.
computer resources	The computer equipment, programs, documentation, services, facilities, supplies, and personnel available for a given purpose. See also: computer resource allocation.
computer software component (CSC)	A functionally or logically distinct part of a computer software configuration item (CSCI), typically an aggregate of two or more software units.
computer software configuration item (CSCI)	An aggregation of software that is designated for configuration management and treated as a single entity in the configuration management process. Contrast with: hardware configuration item. See also: configuration item.
computer software unit (CSU)	An element specified in the design of a Computer Software Component (CSC) that is separately testable.
computer system	A system containing one or more computers and associated software.
computer-aided software engineering (CASE)	The use of computers to aid in the software engineering process. May include the application of software tools to software design, requirements tracing, code production, testing, document generation, and other software engineering activities.
computing center	A facility designed to provide computer services to a variety of users through the operation of computers and auxiliary hardware and through services provided by the facility's staff.
concept phase	The period of time in the software development cycle during which the user needs are described and evaluated through documentation (for example, statement of needs, advance planning report, project initiation memo, feasibility studies, system definition, documentation, regulations, procedures, or policies relevant to the project). The initial phase of a software development project, in phase of a software development project, in which the user needs are described and evaluated through documentation (for example, statement of needs, advance planning report, project initiation memo, feasibility studies, system definition, documentation, regulations, procedures, or policies relevant to the project).
concurrent	Pertaining to the occurrence of two or more activities within the same interval of time, achieved either by interleaving the activities or by simultaneous execution. Syn: parallel (2). Contrast with: simultaneous..
condition code	See: status code.
conditional jump	A jump that takes place only when specified conditions are met. Contrast with: unconditional jump.
configuration	The arrangement of a computer system or component as defined by the number, nature, , and interconnections of its constituent parts. In configuration management, the functional and physical characteristics of hardware or software as set forth in technical documentation and achieved in a product. See also: configuration item; form, fit, and function; version.
configuration audit	See: functional configuration audit; physical configuration audit.
configuration control	An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification. Syn: change control. Contrast with: configuration identification; configuration status accounting. See also: configuration control board; deviation; engineering change; interface control; notice of revision; specification change notice; waiver.
configuration control board (CCB)	A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items, and for ensuring implementation of approved changes. Syn: change control board. See also: configuration control.
configuration diagram	See: block diagram
configuration identification	An element of configuration management, consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. Contrast with: configuration control; configuration status accounting. 3. The current approved or conditionally approved technical documentation for a configuration item as set forth in specifications, drawings and associated lists, and documents referenced therein. See also: allocated configuration identification; functional configuration identification; product configuration identification; baseline.
configuration index	A document used in configuration management, providing an accounting of the configuration items that make up a product. See also: configuration item development record; configuration status accounting.
configuration item (CI)	An aggregation of hardware, software, or both, that is designated for configuration management and treated as a single entity in the configuration management process. See also: hardware configuration item; computer software configuration item; configuration identification; critical item. See also: hardware configuration item; computer software configuration item; configuration identification; critical item.
configuration item development record	A document used in configuration management, describing the development status of a configuration item based on the results of configuration audits and design reviews. See also: configuration index; configuration status accounting.
configuration management	A discipline applying technical and administrative direction and surveillance to a) identify and document the functional and physical characteristics of a configuration item, b) control changes to those characteristics, c) record and report change processing and implementation status, and d) verify compliance with specified requirements. See also: baseline; configuration identification; configuration control; configuration status accounting; configuration audit.
configuration management library system	The tools and procedures to access the contents of the software baseline library.
configuration status accounting	An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information including a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of approved changes. Contrast with: configuration control; configuration identification. See also: configuration index; configuration item development record.
configuration unit	The lowest level entity of a configuration item or component that can be placed into, and retrieved from, a configuration management library system.
connect	To assign a drive letter, port, or computer name to a shared resource so that you can use it with Windows .
consecutive	Pertaining to the occurrence of two sequential events or items without the intervention of any other event or item; that is, one immediately after the other.
consistency	The degree of uniformity, standardization, and freedom from contradiction among the documents or parts of a system or component. See also: traceability.
constant	A quantity or data item whose value cannot change; for example, the data item FIVE, with an unchanging value of 5. Contrast with: variable. See also: figurative constant; literal.
constant-failure period	The period of time in the life cycle of a system or component during which hardware failures occur at an approximately uniform rate. Contrast with: early-failure period; wearout-failure period. See also: bathtub curve.
constructive cost model	An algorithmic cost model known as COCOMO.
content coupling	A type of coupling in which some or all of the contents of one software module are included in the contents of another module. Contrast with: common environment coupling; control coupling; data coupling; hybrid coupling; pathological coupling.
Contents button	Displays the active application's Help Contents, from which you can choose the Help topic you want. The Contents button is in the Help button bar, directly below the menu bar.
contiguous allocation	A storage allocation technique in which programs or data to be stored are allocated a block of storage of equal or greater size, so that logically contiguous programs and data are assigned physically contiguous storage locations. Contrast with: paging (1).
contingency factor	An adjustment (increase) of a size, cost, or schedule plan to account for likely underestimates of these parameters due to incomplete specification, inexperience in estimating the application domain, etc.
continuous iteration	A loop that has no exit.
contract terms and conditions	The stated legal, financial, and administrative aspects of a contract.
control breakpoint	See: code breakpoint.
control codes	Codes that specify Terminal commands or formatting instructions (such as linefeeds or carriage returns) in a text file. Control codes are usually preceded by a caret (^). You enter these codes when you are assigning Terminal commands or tasks to function keys.
control coupling	A type of coupling in which one software module communicates information to another module for the explicit purpose of influencing the latter module's execution. Contrast with: common-environment coupling, content coupling; data coupling; hybrid coupling. pathological coupling.
control data	Data that select an operating mode or submode in a program, direct the sequential flow, or otherwise directly influences the operation of software; for example, a loop control variable.
control flow	The sequence in which operations are performed during the execution of a computer program. Syn: flow of control. Contrast with: data flow.
control flow diagram	A diagram that depicts the set of all possible sequences in which operations may be performed during the execution of a system or program. Types include box diagram, flowchart, input-process-output chart, state diagram. Contrast with: data flow diagram. See also: call graph; structure chart.
control flow trace	See: execution trace.
control language	See: job control language
Control menu	A menu that contains commands you can use to manipulate a window. To open the Control menu, you choose the Control-menu box to the left of the title bar in a window, or you select an application icon. Every application that runs in a window and some MS-DOS-based applications have a Control menu. Document windows and some dialog boxes also have Control menus.
control program	See: supervisory program.
control statement	A program statement that selects among alternative sets of program statements or affects the order in which operations are performed. For example, if-then-else, case. Contrast with: assignment statements; declaration.
control store	In a microprogrammed computer, the computer memory in which microprograms reside. See also: microword; nanostore.
control variable	See: loop-control variable.
Control-menu box	The box to the left of the title bar. When you click this box, the Control menu opens.
conventional memory	Up to the first 640K of memory in your computer. MS-DOS uses this memory to run applications.
conventions	Requirements employed to prescribe a disciplined uniform approach to providing consistency in a software product, that is, uniform patterns or forms for arranging data. See also: practices; standards.
conversational	Pertaining to an interactive system or mode of operation in which interaction between a user and a system resembles a human dialogue. See also: interactive; on-line; real time.
conversational compiler	See: incremental compiler.
conversion	Modification of existing software to enable it to operate with similar functional capability in a different environment; for example, converting a program from FORTRAN to Ada, converting a program that runs on one computer to run on another computer.
copy	To read data from a source, leaving the source data unchanged, and to write the same data elsewhere in a physical form that may differ from that of the source. For example, to copy data from a magnetic disk onto a magnetic tape. Contrast with: move.
coroutine	A routine that begins execution at the point at which operation was last suspended, and that is not required to return control to the program or subprogram that called it. Contrast with: subroutine.
corrective maintenance	Maintenance performed specifically to correct faults in hardware and software. Contrast with: adaptive maintenance; perfective maintenance.
correctness	The degree to which a system or component is free from faults in its specification, design, and implementation. The degree to which software, documentation, or other items meet specified requirements. The degree to which software, documentation, or other items meet user needs and expectations, whether specified or not.
correctness proof	See: proof of correctness.
counter	A variable used to record the number of occurrences of a given event during the execution of a computer program; for example, a variable that records the number of times a loop is executed.
coupling	The manner and degree of interdependence between software modules. Types include common-environment coupling, content coupling, control coupling, data coupling, hybrid coupling, and pathological coupling. Contrast with: cohesion.
crash	The sudden and complete failure of a computer system or component. See also: hard failure.
critical computer resource	The parameters of the computing resources deemed to be a source of risk to the project because the potential need for those resources may exceed the amount that is available. Examples include target computer memory and host computer disk space.
critical design review (CDR)	A review conducted to verify that the detailed design of one or more configuration items satisfy specified requirements; to establish the compatibility among the configuration items and other items of equipment, facilities, software, and personnel; to assess risk areas for each configuration item; and, as applicable, to assess the results of producibility analyses, review preliminary hardware product specifications, evaluate preliminary test planning, and evaluate the adequacy of preliminary operation and support documents. See also: preliminary design review; system design review. A review as in (1) of any hardware or software component.
critical item	In configuration management, an item within a configuration item that, because of special engineering or logistic considerations, requires an approved specification to establish technical or inventory control at the component level.
critical path	A series of dependent tasks for a project that must be completed as planned to keep the entire project on schedule.
critical piece first	A system development approach in which the most critical aspects of a software system are implemented first. The critical piece may be defined in terms of services provided, degree of risk, difficulty, or other criterion. See also: bottom-up; top-down.
critical software	Software whose failures could have an impact on safety, or could cause large financial or social loss.
criticality	The degree of impact of that requirement, module, error, fault, failure, or other item has on the development or operation of a system. Syn: severity.
crossassembler	An assembler that executes on one computer but generates object code for a different computer.
crosscompiler	A compiler that executes on one computer but generates machine code for a different computer.
cross-reference generator	A software tool that accepts as input the source code of a computer program and produces as output a listing that identifies each of the program's variables, labels, and other identifiers and indicates which statements in the program define, set, or use each one. Syn: cross-referencer.
cross-reference list	A list that identifies each of the variables, labels, and other identifiers in a computer program and indicates which statements in the program define, set, or use each one.
cross-referencer	See: cross-reference generator.
CSC	Acronym for computer software component.
CSCI	Acronym for computer software configuration item.
cue	See: call (3).
current directory	The directory that you are currently working in or that is selected in the directory window.
curriculum standard	A standard that describes the characteristics of a course of study on a body of knowledge that is offered by an educational institution.
customer	The individual or organization that is responsible for accepting the product and authorizing payment to the developing organization.
cutout	An area of the drawing you select by using the Scissors or Pick tool.
cycle	A period of time during which a set of events is completed. See also: software development cycle; software life cycle. A set of operations that is repeated regularly in the same sequence, possibly with variations in each repetition; for example, a computer's read cycle. See also: pass.
cycle stealing	The process of suspending the operation of a central processing unit for one or more cycles to permit the occurrence of other operations, such as transferring data from main memory in response to an output request from an input/output controller.
cyclic search	A storage allocation technique in which each search for a suitable block of storage begins with the block following the one last allocated.