(1) a user-oriented security
quality
requirement specifying the extent to which an application
or component shall identify clients (e.g.,
users and client
applications) before allowing them to use it.
(2) a quality factor measuring the extent to which an
application or component actually identifies clients (e.g.,
users and client applications) before allowing them to use
it.
Contrast withauthentication and
authorization.
(1) a user-oriented
securityquality
requirement specifying the degree to which an
application or
component shall protect
itself from infection by unauthorized undesirable programs
(e.g., computer viruses, worms, and Trojan horses).
(2) a
quality
factor measuring the degree to which an application or
component actually prevents its infection by unauthorized
introduction of undesirable programs.
(3) a
security
mechanism for protecting an application or component from
infection by unauthorized introduction of undesirable
programs (e.g., virus detection, analysis, and removal).
the
activity consisting of
the cohesive collection of all
tasks that are primarily
performed to build or acquire the application’s individual
components based on the application’s architecture and
design.
a property of a development process whereby units of work
are repeated to produce additional new work products or
capabilities of work products. Development cycles are
typically incremental because applications are too large and
complex to be built all at once in a big bang fashion.
Contrast withiterative.
an architectural or design decision regarding a data
component (content) that is to be treated as a requirement
and therefore will constrain the architecture and
design.
the incremental construction of a new definition (e.g.,
class, type) in terms of existing definitions without
disturbing the original defintions and their clients.
Inheritance is most often used to implement “a kind of”
relationships and polymorphism.
the first phase, during which the application’s initial
vision, partial requirements, and partial architecture are
captured so that the application scope and cost can be
estimated.
Contrast withconstruction
phase,
delivery phase,
retirement
phase, and
usage phase.
a relatively formal verification and validation
technique whereby one
or more inspectors use an inspection checklist to identify
defects in one or more related work products.
Contrast withaudit,
review, and
walkthrough.
a checklist of questions specific to a single kind of
work product and that is used during an inspection to ensure
that the inspectors have considered all significant potential
defects.
(1) a developer-oriented
quality
requirement specifying the ease with which an application
or component shall be able to be successfully installed.
(2) a quality factor measuring the ease with which an
application or component can be successfully installed,
typically measured in terms of the average amount of
person-hours required for a trained operator or hardware
engineer to perform the installation.
the deployment work product that provides procedures for
installing and configuring the application in such production
environments as data centers and hosting services.
a process framework guideline for selecting process
components from an existing class library of such components
to meet the needs of a specific project.
a development environment in which the tools have been
integrated to collaborate with each other (e.g., the output
of one tool can be used as the input to another tool).
the
activity consisting of
the cohesive collection of all tasks that are primarily
performed to connect the application’s components into an
executing version of the application.
Note that software integration typically consists of
coupling together multiple interfacing software components
using inheritance, aggregation, and message passing.
Note that system integration typically consists of
connecting hardware components and deploying software
components to hardware components.
a
server
computer used to support enterprise application
integration (EAI), typically by acting as a go-between
between
application
servers and legacy applications and databases.
(1) a user-oriented
securityquality
requirement specifying the degree to which an
application or
component shall ensure
that its data and communications are not intentionally
corrupted via unauthorized creation, modification, or
deletion.
(2) a quality factor measuring the degree to which an
application or component actually prevents the intentional
unauthorized corruption of its data and communications.
any named boundary across which two or more separate
elements (e.g., classes, components, hardware devices,
subsystems, systems) interact (e.g., service requests with
potential exceptions raised, physical connections) with each
other.
any documentation of the public information about an
interface that the developer of an element that uses the
interface needs to know in order to ensure that the element
correctly and effectively uses the interface.
(1) a user-oriented
configurabilityquality
requirement specifying the degree to which an application
or component shall be configurable to function appropriately
in a global environment including support for national
differences in:
Native languages, language idioms, spelling, and
character sets.
Formats of contact information such as name, address,
and phone number.
Currencies including real-time currency
conversion.
Legal issues such as import/export laws, tariff and
sales tax calculations, customs documentation, trademarks,
and privacy laws.
Culture (e.g., use of inappropriate colors, symbols, or
product names).
(2) a quality factor measuring the degree to which an
application or component is actually configured to function
appropriately in a global environment.
Contrast withfunctional
variants and
personalization.
the
role that is played when a
person engineers an application or component to meet its
internationalization requirements and thereby work properly
in the associated countries.
a build that does not result in a version of the
application being delivered by the development organization
to the customer organization. Internal builds are used
internally by the development organization to help manage
iterative and incremental development.
Contrast withrelease.
(1) a user-oriented
quality
requirement specifying the degree to which an application
or component shall be able to be successfully integrate with
other specified applications or components (e.g., browsers,
legacy databases, legacy applications, external systems, and
required COTS components).
(2) a quality factor measuring the degree to which an
application or component actually was able to be successfully
integrated with other specified applications or components.
Note that:
Successful integration means that the applications or
components can successfully communicate to exchange data,
make requests, and raise exceptions.
Interoperability is often specified in terms of the
ease with which integration can be accomplished and is
often measured in terms of required effort.
a
security
requirement specifying the degree to which an application
must ensure attempted access or modification by unauthorized
individuals is detected and properly handled.
an
assertion that must be
true both before and after the execution of each operation
(e.g., application use case, class method).
See alsopostcondition and
precondition.
a property of a development process whereby work units
are repeated on existing work products to improve them (e.g.,
to fix defects and adapt it to changes in requirements).
Contrast withincremental.
