Information Technology Reference
In-Depth Information
❑❑❑❑❑❑❑❑❑
This chapter outlined the key risk areas that CI will help to mitigate,
such as database integration, testing, inspection, deployment, feed-
back, and documentation. Table 3-1 provides an overview of the mate-
rial covered in this chapter. You will find that by mitigating these risks
using CI practices, you will improve software quality.
TABLE 3-1
Summary of Risks and Mitigations
Risk
Mitigation
Lack of deployable
software
Use a CI system to build deployable software at any
time. Create a repeatable build process that uses all
software assets from the version control repository.
Late discovery of
defects
Run builds that include developer tests with every
change, so you can discover defects earlier in the
software lifecycle.
Lack of project
visibility
Know the health of your software at all times by run-
ning builds regularly. When effectively applying the
practice of CI, the project status is no longer in
question.
Low-quality software Run tests and inspections at every change so you
can discover potential defects that may be intro-
duced into the code base by learning the complexity,
duplication, design, code coverage, and other
factors.
How many risks do you have on your project that CI can help mitigate?
These questions should help you determine the risks on your project.
■
When do you find the most defects on your project, in the beginning
or in later parts of the lifecycle?
■
How do you determine the quality on your software projects? Are
you able to measure it?
■
Which processes on your projects are manual? Have you deter-
mined which processes you can or should automate?
