Information Technology Reference
In-Depth Information
development environment
—The environment in which software
is written. This can include the IDE, build scripts, tools, third-party
libraries, servers, and configuration files.
inspection
—Analysis of source code/bytecode for the internal
quality attributes. In the context of this topic, we refer to the auto-
mated aspects (static and runtime analysis) as
software inspection.
integration
—The act of combining separate source code artifacts
together to determine how they work as a whole.
integration build
—An integration build is the act of combining
software components (programs and files) into a software system.
This build includes multiple components on bigger projects or only
low-level compiled source files on smaller projects. In our every-
day life, we tend to use the terms
build
and
integration build
inter-
changeably, but for the purposes of this topic we make the
distinction that an
integration build
is performed by a separate
integration build machine.
private (system) build
—Running a build locally on your worksta-
tion before committing your changes to the version control reposi-
tory, to lessen the chances that your recent changes break the
integration build.
2
quality
—The Free On-Line Dictionary of Computing
3
defines
quality as “an essential and distinguishing attribute of some-
thing...” and “superior grade.” The term
quality
is often overused,
and some seem to think it is based on perception. In this topic, we
take the stance that quality is a measurable specification just like
any other. This means you can identify specific metrics of quality,
such as maintainability, extensibility, security, performance, and
readability.
release build
—Readies the software for release to users. It may
occur at the end of an iteration or some other milestone, and it
must include any acceptance tests and may include more exten-
sive performance and load tests.
2. Based on
Software Configuration Management Patterns
by Stephen Berczuk and
Brad Appleton.
