Continuous Integration: Improving Software Quality and Reducing Risk -- Chapter 2, Introducing Continuous Integration

This chapter, "Introducing Continuous Integration," attempts to answer the questions that you may have when making the decision to implement the practices of CI on a project. It provides an overview of the advantages and disadvantages of CI, and covers how CI complements other software development practices.

CI is not a practice that can be handed off to a project's "build master" and forgotten about. It affects every person on the software development team, so the chapter discusses CI in terms of what all team members must practice to implement it.

Book description:
For any software developer who has spent days in "integration hell," cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key,

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Quality Book Excerpts Perfect Software, Ch. 8: What Makes a Good Test Seven Steps to Mastering Business Analysis, Ch. 1 Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code? The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams Inherent Quality Simplicity, Section V: The Evolution Managing the Test People, Chapter 6: Keeping Your Beast Effective Software quality management Budget-friendly Web app performance testing, monitoring tips New requirements definition tools focus on chronic flaws CareGroup solves application performance issues with APM tool How to develop a software testing tools integration strategy Software testing affected by pressure to release software Software quality needs to be a continuous process Quality standards don't always mean fewer defects Countermeasures to e-voting security flaws E-voting machines still vulnerable in 2008 A software quality crisis is brewing Software development fundamentals Agile development growing, but problems remain Hamish Reid, software engineer, Perforce Software Agile, IBM tools boost Merge Healthcare's software quality Extending application lifecycle management to the enterprise Quiz: Open source software development Help with development life cycle metrics How to develop secure applications Manage component dependencies for improved system quality Survey: Agile interest high, but waterfall still used by many Continuous integration reduces bugs, increases productivity

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build tool  (SearchSoftwareQuality.com) development environment  (SearchSoftwareQuality.com) heuristics  (SearchSoftwareQuality.com) histogram  (SearchSoftwareQuality.com) intentional programming  (WhatIs.com) JAD  (SearchSoftwareQuality.com) lean programming  (SearchSoftwareQuality.com) peer review  (SearchSoftwareQuality.com) source code analysis  (SearchSoftwareQuality.com) Standard Performance Evaluation Corporation  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques.

The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than 40 CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility.

This chapter is excerpted from the new book titled, Continuous Integration: Improving Software Quality and Reducing Risk, authored by Paul Duvall, Steve Matyas and Andrew Glover, scheduled to publish by Addison-Wesley Professional in late June, 2007. Copyright Pearson Education, Inc., ISBN 0321336380. For more information, please visit www.awprofessional.com.

>> Read "Introducing Continuous Integration" now.

>> Buy the book