 |
Accessibility verification is the process
of ensuring that a Web application is accessible
to people with disabilities. Accessibility verification
can help you prevent functionality problems
that could occur when people with disabilities
(approximately 19% of the US population) try
to access your application with adaptive devices
such as screen readers, refreshable Braille
displays, and alternative input devices. >
more |
| |
 |
An automated nightly build is a process for
building an application every night through
an automated build system (a system or tool
which will automatically execute the required
steps at the scheduled time, without any human
intervention). >
more |
| |
 |
An automated infrastructure is vital to the
continued implementation and success of Automated
Error Prevention. This infrastructure is designed
to integrate quality into the very fiber of
the development process. >
more |
| |
 |
A bug-tracking system, such as GNATS or Bugzilla,
has two main uses. The first and most important
use is to record and track all errors not detected
by your test suite. >
more |
| |
 |
Confidence factors help you estimate the progress
of your current project using a scale from 0%
to 100%. >
more |
| |
 |
Connectivity verification is the process of
verifying that Web services (and other systems
connected with SOAP) exchange information correctly.
In an internal enterprise system, this might
involve verifying the connectivity between databases,
Web servers, application servers, middleware,
ERP systems, CRM systems, and legacy systems.
>
more |
| |
 |
A code review is the process where the developers
and the architect meet and discuss code. The
purpose of code reviews is to exchange ideas
about how the code is written and to establish
a standard group interpretation of the code.
>
more |
| |
 |
Coding standards are language-specific programming
rules that greatly reduce the probability of
introducing errors into your applications, regardless
of which software development model (iterative,
waterfall, eXtreme programming, and so on) is
being used to create that application. >
more |
| |
 |
Group culture is a development team's way
of working together, including their shared
habits, traditions, and beliefs. A positive
group culture should promote code ownership,
group cooperation, peer learning, common working
hours, and mutual respect. >
more |
| |
 |
Data pollution identification exposes incorrect
and poorly-formed data that was added to a database.
Data pollution identification involves scanning
through the specified fields of a database and
checking whether the data conforms to your restrictions.
>
more |
| |
 |
Defensive programming is the practice of anticipating
where failures can occur and then creating an
infrastructure that tests for errors, notifies
you when anticipated failures occur, and performs
damage-control actions you have specified. >
more |
| |
 |
Deployment is the process of making an application
available in a location where it will be exercised
in production mode. >
more |
| |
 |
GRS is a support infrastructure that collects
and correlates all information needed to support
the implementation of an Automated Error Prevention
(AEP) infrastructure. GRS consists of several
functional parts. >
more |
| |
 |
Load testing is the process of exercising
a Web-based or client/server application with
multiple users and verifying whether it functions
correctly under tested traffic levels, patterns,
and combinations. >
more |
| |
 |
Monitoring is the process by which you identify
and prevent problems with deployed client/server
or Web-based systems to ensure their continued
functionality and performance. Monitoring involves
using a tool that periodically checks a Web
site's overall health and sends you alerts when
it detects problems. >
more |
| |
 |
Performance testing is the process of executing
tests to determine how actual application performance
compares to predicted application performance.
>
more |
| |
 |
Regression testing is the process of running
all existing test cases and verifying that all
test cases pass. The purpose of regression testing
is to detect unexpected faults?
|
