Professional Documents
Culture Documents
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Acceptance criteria The criteria that a system or component must satisfy in order to be
accepted by customer
Acceptance testing Formal testing conducted to determine whether the system satisfies its
acceptance criteria enabling the customer to determine its acceptance.
Back to top
Boundary value A data value that corresponds to a minimum or maximum input, internal
or output value specified for a system or component.
Branch testing Testing designed to execute each outcome of each decision point in a
computer program.
Back to top
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 actives.
Checklists Questionnaires that help to complete project activities and prepare
deliverables for each stage/phase.
Cohesion The manner and degree to which the tasks performed by a single
software module are related to one another. Types include coincidental,
communicational, functional, logical, procedural, sequential, and
temporal.
Coincidental cohesion A type of cohesion in which the tasks performed by a software module
have nonfunctional relationship to one another.
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.
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.
Back to top
Data Flow Diagram A diagram that depicts data sources, data sinks, data storage, and
(DFD) processes performed on data as nodes, and logical flow of data as links
between the nodes.
Data structure A physical or logical relationship among data elements, designed to
support specific data manipulation functions.
Back to top
Entity-Relationship A diagram that depicts a set of real-world entities and the logical
(ER) diagram relationships among them.
Entry point A point in a software module at which execution of the module can
begin.
Environment testing Verification that the system (combined partitions) works correctly for
each environment for which the system was developed.
Event A well defined point in an activity, usually the beginning or the end.
Back to top
Feasibility The degree to which the requirements, design, or plans for a system or
component can be implemented under existing constraints.
Flexibility The ease with which a system or component can be modified for use in
applications or environments other than those for which it was
specifically designed.
Flow chart A control flow diagram in which suitably annotated geometrical figures
are used to represent operations, data, or equipment, and arrows are
used to indicate the sequential flow from one to another.
Function A defined objective or characteristic action of a system or component.
Also the smallest programming item. (Also known as a Sub-routine).
Functional cohesion A type of cohesion in which the tasks performed by a software module,
contribute to the performance of a single function.
Back to top
Global variable Data that can be accessed by two or more non-nested modules of a
computer program without being explicitly passed as a parameter
between the modules.
Graphical User Graphics-based user interface that uses icons, pull-down menus, on-
Interface (GUI) line help, drop-down lists, check boxes, pop-up windows, color and a
mouse to make screen navigation easier and more intuitive for the user.
Back to top
High level design The process of analyzing design alternatives and defining the
architecture, components, interfaces, and timing and sizing estimated
for a system or component.(Also known as Preliminary design).
Hybrid coupling A type of coupling in which different subsets of the range of values, that
data items can assume, for different and unrelated purposes in different
software modules.
Back to top
Icon Small, pictorial representation of an object (file, disk drive, etc.) used in
graphical user interfaces. The user selects an object by pointing to its
icon and clicking the mouse button.
Implementation The process of translating a design into hardware components,
software components or both. (Also called Construction).
Integration testing Integration testing occurs after all unit test plans are run. It checks
whether unit tested programs have compatibility in terms of interfaces. It
may optionally test the functioning of the integrated entity
Integrity The degree to which a system or component prevents unauthorized
access to, or modification of, computer programs or data.
Back to top
Job Control Language A language used to identify a sequence of jobs, describe their
(JCL) requirements to an operating system, and control their execution.
Back to top
Local variable A variable that can be accessed by only one modular set of tested
modules in a computer program.
Logical cohesion A type of cohesion in which the tasks performed by a software module
perform logically similar functions; for example, processing of different
types of input data.
Back to top
Machine independent Pertaining to software that does not rely on features unique to a
particular type of computer and therefore executes on computers of
more than one type.
Maintainability The ease with which a software system or component can be modified
to correct faults, improve performance or other attributes, or adapt to a
changed environment.
Maintenance The process of modifying a software system or component after delivery
to correct faults, improve performance or other attributes, or adapt to a
changed environment.
Metric Quantitative measures of the degree to which a system, component, or
process, processes a given attribute.
Back to top
Object A self-contained module of data and its associated processing.
Back to top
Pass/fail criteria Decision rules used to determine whether a software item or a software
feature passes or fails a test.
Path testing Testing designed to execute all or selected paths through a computer
program.
Pathological coupling A type of coupling in which one software module affects or depends
upon the internal implementation of another.
Portability The ease with which a system or component can be transferred from
hardware or software environment to another.
Preliminary design The process of analyzing design alternatives and defining the
architecture, components, interfaces, and timing and sizing estimated
for a system or component.(Also known as High Level Design).
Preliminary Design A review conducted to evaluate the progress technical adequacy, and
Review (PDR) risk resolution of the selected design approach for one or more
configuration items; to determine each design's compatibility with the
requirements for the configuration item. to evaluate the degree of
definition and assess the technical risk associated with the selected
manufacturing methods and process. to establish the existence and
compatibility of the physical and functional interfaces among the
configuration items and other items of equipment, facilities software and
personnel; and as, applicable, to evaluate the preliminary operational
and support documents.
Preventive Maintenance performed for the purpose of preventing problems before
maintenance they occur.
Procedural cohesion A type of cohesion in which the tasks performed by a software module
all contribute to a given program procedure, such as an iteration or
decision process.
Process hierarchy The arrangement of the system into sub-systems or modules, with each
module broken down into programs or units, and each program further
broken down into sub-routines or functions.
Program A group of one or more sub-routines, performing a higher level job, and
which is independently coded and tested as one unit. (Also known as
Unit.)
Project plan A document that describes the technical and management approach to
be followed for a project. The plan typically describes the work to be
done, the process required, the methods to be used, the procedures to
be followed the schedules to be met, and the way that the project will be
organized. For example, a software development plan.
Prototyping A hardware and software development technique in which a preliminary
version of part or all of the hardware or software is developed to permit
user feedback determines feasibility, or investigate timing or other
issues in support of the development process.
Pseudo code A combination of programming language constructs and natural
language used to express a computer program design.
Back to top
Quality Assurance A planned and systematic pattern of all actions necessary to provide
(QA) adequate confidence that an item or product conforms to established
technical requirements.
Quality Control (QC) A set of activities designed to evaluate the quality of developed or
manufactured products.
Back to top
Response time The elapsed time between the end of an inquiry or command to an
interactive computer system and the beginning of the system's
response.
Retirement phase The period of time in the software life cycle during which support for a
software product is terminated.
Reusability The degree to which a software module or other work product can be
used in more than one computer program or software system.
Review An activity to verify that the outputs of a phase in the software life cycle
conform to their specifications.
Back to top
Sequential cohesion A type of cohesion in which the output of one task performed by a
software module serves as input to another task performed by the
module.
Sign-off Signature of approval.
Simulation A model that behaves or operates like a given system when provided a
set of controlled inputs.
Software Requirement A process or meeting during which the requirements for a software
Review (SRR) system are reviewed to evaluate their responsiveness to an
interpretation of the system requirements and to determine whether
they form a satisfactory basis for proceeding into preliminary design of
the configuration items.
Software A document that specifies the essential requirements(functions
Requirements performance, design constraints, and attributes) of the software and its
Specs.(SRS) external interfaces.
Source Code Computer instructions and data definitions expressed in a form suitable
for input to an assembler, compiler, or other translator.Note: A source
program is made up of source code.
Specification A document that specifies, in a complete , precise, verifiable manner,
the requirements, design, behavior, or other characteristics of a system
or component, and, often the procedures for determining whether these
provisions have been satisfied.
Stability Quality of not changing. Either in the short term, not breaking down, or
in the longer term, not subject to design and/or requirements changes .
Back to top
Techniques Technical and managerial procedures that aid in the evaluation and
improvement of the software development process.
Temporal cohesion A type of cohesion in which the tasks performed by a software module
are all required at a particular phase of program execution; for example,
a module containing all of a program's initialization tasks.
Template A pre-defined model / structure / format, devised to capture data in a
consistent manner, and / or to ensure standardization while generating
multiple documents of similar type.
Test An activity in which a system or component is executed under specified
conditions, the results are observed or recorded, and an evaluation is
made of some aspect of the system or component.
Test case A set of test inputs, execution condition, and expected results
developed to aide in testing activities.
Test coverage The degree to which a given test or set of tests addresses all specified
requirements for a given system or component.
Test criteria The criteria that a system or component must meet in order to pass a
given test.
Test documentation Documentation describing plans for, or results of, the testing of a
system of component. Types include test case specification, test
incident report, test log, test plan, test procedure, test report.
Test driver A software module used to invoke a module under test and, often,
provide test inputs, control and monitor execution, and report test
results.
Test item A software item which is an object of testing.
Test log A chronological record of all relevant details about the execution of a
test.
Test summary report A document summarizing testing activities and results. It also contains
an evaluation of the corresponding test items.
Back to top
Unit A group of one or more sub-routines, performing a higher level job, and
which is independently coded and tested as one unit. (Also known as
Program).
Unit testing Checks whether the program or unit functions according to its
specifications.
Usability The ease with which a user can learn to operate, prepare inputs for, and
interpret outputs of a system or component.
Back to top
Back to top
Waiver A written authorization to accept a configuration item or other
designated item, which during production or after having been
submitted for inspection, is found to depart from specified requirements,
but is nevertheless considered suitable for use as is or after rework by
an approved method.
Walk-through A static analysis technique in which a designer or programmer leads
members of the development team and other interested parties through
a segment of documentation or code, and the participants ask questions
and make comments about possible errors, and make comments about
possible errors, violation of development standards, and other
problems.
Waterfall model A model of the software development process in which the constituent
activities, typically a concept, phase requirements phase, design phase,
implementation phase, test phase, and installation and checkout phase,
are performed in that order, possible with overlap but with little or no
iteration.
Work-around A temporary solution to the problem.
Work Breakdown The WBS describes the hierarchy of tasks (grouped into 'work
Structure (WBS) packages') to be carried out in a project. The WBS corresponds to the
structure of the work to be performed, and reflects the way in which the
project costs will be summarized and reported.
Back to top