the architecture of a software application or component
in terms of its packages, their responsibilities, their
relationships, and their interfaces.
Contrast withcomponent
architecture and
concurrency
architecture.
the characteristic of a
stage whereby multiple
producers (e.g.,
roles,
teams) are concurrently
performing
tasks (e.g., different
producers are simultaneously working on different
work
products).
an
role that a person plays
when officially representing a partner organization when
interacting with members of development organizations and
customer organizations.
(1) a user-oriented
quality
requirement specifying the speed with which an application
or component shall execute its functions.
(2) a quantitative quality factor measuring the speed
with which an application or component actually executes its
functions, typically measured in terms of:
Capacity. The minimum number of objects that an application or
component can support (e.g. the minimum number of users or
transactions that it must be able to support).
Latency. The maximum time that is permitted for an application
or component to execute specific tasks (i.e., system
operations) or use case paths end to end.
Response Time. The maximum time that is permitted for an application
or component to respond to specific requests.
Throughput. The number of executions of a given system operation
or use case path that an application or component must be
able execute in a unit of time.
a
test that attempts to cause
failures to meet performance requirements under normal
operating circumstances in order to identify inefficiencies
and bottlenecks.
the system testing of an application against its
performance requirements under
normal operating circumstances in order to
identify inefficiencies and bottlenecks.
a
hardware
component consisting of a small, mobile, hand-held device
used for both personal and business use that creates, stores,
and communicates personal (e.g., calendar and address book)
and financial (e.g., expense reports) information.
(1) a user-oriented
configurabilityquality
requirement specifying the degree to which an application
or component shall be able to be configured so that
individual users each have a unique user-specific experience
(e.g., an e-Commerce application knows a buyer’s
preferences from previous purchases and presents appropriate
advertisements).
(2) a quality factor measuring the degree to which an
application or component is actually configured so that
individual users each have a unique user-specific experience.
Contrast withfunctional
variants and
internationalization.
that aspect of system architecture concerning the system
components, their relationships, and how they collaborate to
provide the system’s capabilities.
Contrast withlogical
architecture.
a
security
mechanism for achieving security requirements that is
based on hardware components (e.g., door locks, camera,
passcard reader), the placement of hardware components (e.g.,
placing the firewall within a locked data center), or
personnel (a guard performing security rounds).
(1) a developer-oriented
quality
requirement specifying the ease with which an application
or component can be moved from one environment (e.g.,
hardware, operating system, and browser) to another,
typically measured in terms of the maximum amount of effort
permitted.
(2) a quantitative quality factor measuring the actual
effort required to move an application or component from one
environment to another.
Note that portability includes:
The actual porting of the software, integration, data
conversion, and documentation updates.
Portability from the development or test (host)
environment to the production (target) environment.
Portability from one production environment to
another.
an
assertion that must
hold following the successful execution of the associated
function (e.g., use case path, class method).
See alsoinvariant and
precondition.
(1) a user-oriented
correctnessquality
requirement specifying either the maximum permitted
variability or standard deviation of a quantitative data
(e.g., measurements) from its average value, regardless of
its accuracy.
(2) a quantitative quality factor measuring the
variability of a defect from its average value.
For example, a temperature sensor is precise to .1
degree Celsius, but not very accurate because it consistently
under measures the temperature by 3.5 degrees (i.e., the
standard deviation of the temperature measurements may be
sufficiently precise, but useless because the average
temperature measurement returned by the temperature sensor is
3.5 degrees less than the true temperature making the
temperature sensor not very accurate).
Contrast withallowable
latent defects,
accuracy, and
timeliness.
an
assertion that must
hold prior to the successful execution of the associated
function (e.g., use case path, class method).
See alsoinvariant and
postcondition.
a
server
computer that provides presentation and personalization
functionality.
Note that presentation servers often set between the
web servers and the application servers in the hardware
architecture.
(2) a quality factor measuring the degree to which an application or component actually its sensitive data and
communications from specified externals.
(3) a security
mechanism for keeping
sensitive data and communications private.
For exampleencryption and
decryption.
Note that
authorization can
make privacy specific to individual [classes of] users.
a
convention that that documents the steps for performing a single
task or for performing the collection of tasks making up a single
work flow.
Contrast withguideline and
work flow.
1) a cohesive collection of endeavor-specific process
components (e.g., work products, their producers, and the
work units performed by the producers as they collaborate to
produce the work products) that models the enactment of an endeavor.
Contrast withmethod or
methodology.
the
activity consisting of all
tasks that are primarily
involving the production, institution, maintenance, and use
of an appropriate
process
framework.
the process engineering
task during which the process framework is extended with
one or more additional process components so that complete
processes can be constructed.
a mid-sized
endeavor consisting of a
two or more related projects that are managed as a unit in
order to obtain benefits not available from managing them
individually.
Contrast withenterprise and
project.
the
activity consisting of the cohesive collection of all
tasks that are primarily performed to manage a single program
of related projects in order to fulfil the program’s mission
and to achieve its objectives.
the manual task of creating a software component by
transforming a software design into source code written in a
programming language.
Synonym forcoding.
written conventions specifying rules and guidelines for
the proper use of individual programming language 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.
Contrast withcoding
standards.
an atomic
endeavor undertaken to
produce and deliver one or more versions of a major work
product (often an application) or to perform a service (e.g,
to reengineer a business).
Contrast withenterprise and
program.
the
activity consisting of the cohesive collection of all
tasks that are primarily performed to manage a single project
in order to fulfil its mission and to achieve its
objectives.
