a
network
connectivity device consisting of a copper cable that
physically connects two network devices or computers.
Note that cables are typically twisted pair or
coaxial.
(1) a user-oriented
performancequality
requirement specifying the minimum number of objects
(e.g., simultaneous users, simultaneous transactions, and
customers in a database) that an application or component
shall be able to support.
(2) a quantitative quality factor measuring the minimum
number of objects that an application or component is
actually able to support.
Contrast withlatency,
response time, and
throughput.
a formal statement by a
development organization that a work product meets its
requirements and that it is therefore suitable for its
intended use. Certification is based on a validation
technique such as inspection or testing.
A special kind of
use case that is
intended to specify a potential future behavior that will be
mandatory if a probable or important change occurs to the
requirements.
Contrast withmisuse case.
a measurement of the adequacy of test cases in terms of
the extent to which software elements (e.g., statements,
decisions, branches, paths, etc.) are executed during
testing.
a minor technical milestone at which point the current
version of one or more software work products are delivered
by the software development team to the integration team for
integration into the growing and evolving application.
Contrast withdocument
drop.
the manual task of creating a software component by
transforming a software design into source code written in a
programming language.
Synonym forprogramming.
written conventions specifying rules and guidelines for
the proper use of an individual programming language’s
constructs, commenting, naming, and formatting, etc. The
purpose of coding standards are to prevent programming
errors, control complexity, and promote the understandability
of the source code.
Synonym forprogramming
standards.
an interaction diagram in the form of a graph of nodes
and arcs that documents the potential interactions that can
occur between related classes of objects.
Contrast withsequence
diagram.
the integration testing of multiple
commercial-off-the-shelf (COTS) software components to
determine if they are not interoperable (i.e., if they
contain any interface defects).
a computer program that translates programs expressed in
a high-level programming language into machine code
instructions that computers must have to execute the
program.
the degree to which the structure and behavior of an
organization, application, or component is difficult to
understand and verify due to its large size, the large number
of relationships between its components, and the large amount
of interactions required by its collaborating components to
provide its capabilities.
an architecturally significant part of an
application or
framework with
well-defined inbound and outbound
interfaces and
associated
protocols that
encapsulate a cohesive documented set of
responsibilities.
Components are reusable, and are intended to be adaptable,
but not modified by their users. Components are typically
intended to be used in conjunction with other compatible
components from a well-architected component
framework.
See alsodata component,
hardware
component, and
software
component.
the essential hardware, software, personnel, and
documentation components of a system, their responsibilities,
their relationships, and their interfaces.
Contrast withconcurrency
architecture.
See alsoarchitecture.
a cohesive collection of collaborating components that
have been architected to work together. The component
framework defines the components, how they are related, the
choice of technology (e.g., CORBA, DCOM, and RMI) used to
connect them, and their specific interfaces.
a programmable hardware component that is controlled by
internally stored programs and that can perform substantial
computations (including arithmetic and logic operations)
without human intervention. A computer typically consists of
one or more processing units, memory units, and associated
peripheral input and output devices.
the processes and threads of an application, their
responsibilities, their relationships, and how distribution
units and classes of objects are allocated to them.
Contrast withcomponent architecture.
See alsoarchitecture.
a test coverage criteria that requires the test cases to
execute all possible outcomes taken by each condition in a
decision at least once and also each interface to the item
under test is invoked at least once.
Also known as decision coverage.
Contrast withbranch coverage,
path coverage, and
statement
coverage.
the test case identification technique that selects test
values so that each condition in a decision takes on all
possible outcomes at least once, and each interface to the
item under test is invoked at least once.
Contrast withbranch testing,
path testing, and
statement
testing.
(1) a user-oriented
quality
requirement specifying the degree to which an application
or component shall be able to be configured into multiple
variants.
the
configuration managementtask of
managing changes to
baselinedconfiguration items.
Note that configuration control includes the
evaluation, coordination, approval or disapproval, and
implementation of changes to configuration items after formal
establishment of their configuration identification.
the
configuration managementtask of
identifying, designating, and documenting components (with
associated documentation) as configuration items and
identifying baselines of configuration items.
a component with associated documentation that is
designated for configuration control and treated as a single
blackbox entity by the configuration management
activity.
the quality requirements specifying the required degree
of uniformity, standardization, and freedom from
contradiction within and between work products.
a mandatory architecture, design, ore implementation
decision that is treated as a requirement in that it
restricts the architecture, design, and/or
implementation.
guidelines for instantiating the process framework (e.g.,
by selecting relevant process components) and thereby
constructing an endeavor-specific process.
those
data
components (e.g., text, numerical data, static or animated
graphics, audio files, and video movie files) of an
application that are
published (and therefore visible) to its
users.
Example: the content of a store-front website may
include pictures and text describing the products sold.
Note that content typically has the following
relatively sequential state model (life cycle), the states of
which correspond to completion of the content management
tasks:
the
content management task
during which potential
content is edited for grammer,
spelling, and conformance to associated content standards
(e.g., digital branding).
the
content management task
during which raw potential
content is entered into a
content management
system.
For example: the content can be entered into a
content management system, images may be scanned, text may be
entered into templates, and text, images, audio files, and
movie clips may be converted into the proper format and
size.
the system testing of an integrated application that
attempts to cause failures involving actual or simulated
concurrency (e.g., starvation, deadlock, livelock, race
conditions, and priority inversion).
the activity consisting of the cohesive collection of all
tasks that are primarily performed to manage the
content of one or more related
applications.
See also:
the
content management task
during which
content is personalized to meet the
specific desires and needs of each individual user or group
of related users.
a semantic net that documents the context of a blackbox
business
enterprise,
application,
component, or
framework in terms of
the relevant
externals that interact
(either directly or indirectly) with it, and the relevant
relationships between them.
the management work product that models a mutually
binding agreement that formally specifies the obligations of
the development and customer organizations.
describing a delivery cycle in which the relationship
between phases and builds is based on assertions (e.g.,
preconditions and postconditions).
Contrast withtime-boxed.
(1) a developer-oriented
quality
requirement specifying the part of maintainability that
measures the ease with which defects shall be able to be
corrected in a delivered work product.
(2) a quality factor measuring the ease with which
defects can be corrected in a delivered work product, usually
measured in terms of mean-time-to-fix.
See also
maintainability.
(1) a user-oriented
quality
requirement specifying the degree to which a work product
(e.g., component, application, document) shall be free from
defects, typically specified in terms of the degree to which
it:
Fulfills its specified requirements.
Meets its associated user needs and
expectations, whether specified or not.
(2) a quality factor measuring the degree to which a work
product is actually free from defects, typically measured in
terms of:
Number of latent defects, possibly
categorized by impact.
Accuracy of its data. For example, must
time be measured to the nearest minute or second?
Precision of its data. For example, is
money stored in a manner that enables micropayments?
Timeliness of its behavior. For example,
how soon after an input occurs must the corresponding
output change?
an evaluation of how important a capability (e.g.,
use case path) is
to the client or user estimated in terms of the impact that
an associated defect or failure will have on the development
or operation of an application.
n. the requirements work product produced during
business (re)engineering that documents the results of the
analysis of the customer organization’s current
business.
vb. the business engineering task that analyzes the
customer organization’s current business.
Contrast withmarket
analysis and
user
analysis.
the number of independent basis paths through a software
component, calculated as the number of decision statements
plus 1.
Note that the cyclometric complexity is used to
calculate the number of test cases when using basis path
testing.
