Configuration Management Principles and Practice

Configuration Management

Principles and Practice

Agile Software Series Page

7/31/02

3:08 PM

Page 1

The Agile Software Development Series

Alistair Cockburn and Jim Highsmith, Series Editors

For more information check out

Agile software development centers on four values identified in the Agile Alliance��s Manifesto:

? Individuals and interactions over processes and tools

? Working software over comprehensive documentation

? Customer collaboration over contract negotiation

? Responding to change over following a plan

The development of Agile software requires innovation and responsiveness, based on generating and

sharing knowledge within a development team and with the customer. Agile software developers

draw on the strengths of customers, users, and developers, finding just enough process to balance

quality and agility.

The books in The Agile Software Development Series focus on sharing the experiences of such

Agile developers. Individual books address individual techniques (such as Use Cases), group techniques (such as collaborative decision making), and proven solutions to different problems from a

variety of organizational cultures. The result is a core of Agile best practices that will enrich your

experience and improve your work.

Titles in the Series:

Alistair Cockburn, Surviving Object-Oriented Projects, ISBN 0-201-49834-0

Alistair Cockburn, Writing Effective Use Cases, ISBN 0-201-70225-8

Lars Mathiassen, Jan Pries-Heje, and Ojelanki Ngwenyama, Improving Software Organizations:

From Principles to Practice, ISBN 0-201-75820-2

Alistair Cockburn, Agile Software Development, ISBN 0-201-69969-9

Jim Highsmith, Agile Software Development Ecosystems, ISBN 0-201-76043-6

Steve Adolph, Paul Bramble, Alistair Cockburn, and Andy Pols, Patterns for Effective Use Cases,

ISBN 0-201-72184-8

Configuration Management

Principles and Practice

Anne Mette Jonassen Hass

Boston ? San Francisco ? New York ? Toronto ? Montreal

London ? Munich ? Paris ? Madrid

Capetown ? Sydney ? Tokyo ? Singapore ? Mexico City

Many of the designations used by manufacturers and sellers to distinguish their products are claimed

as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a

trademark claim, the designations have been printed with initial capital letters or in all capitals.

The author and publisher have taken care in the preparation of this book, but make no expressed or

implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the

information or programs contained herein.

The publisher offers discounts on this book when ordered in quantity for bulk purchases and special

sales. For more information, please contact:

U.S. Corporate and Government Sales

(800) 382-3419

corpsales@

For sales outside of the U.S., please contact:

International Sales

(317) 581-3793

international@

Visit Addison-Wesley on the Web:

Library of Congress Cataloging-in-Publication Data

Hass, Anne Mette Jonassen.

Configuration management principles and practice / Anne Mette Jonassen Hass.

p. cm.

Includes bibliographical references and index.

ISBN 0-321-11766-2 (alk. paper)

1. Software configuration management. I. Title.

QA76.76.C69 H37 2003

005.1��dc21

2002034458

Copyright ? 2003 by Pearson Education, Inc.

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,

or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording,

or otherwise, without the prior consent of the publisher. Printed in the United States of America.

Published simultaneously in Canada.

For information on obtaining permission for use of material from this work, please submit a

written request to:

Pearson Education, Inc.

Rights and Contracts Department

75 Arlington Street, Suite 300

Boston, MA 02116

Fax: (617) 848-7047

ISBN 0-321-11766-2

Text printed on recycled paper

1 2 3 4 5 6 7 8 9 10��MA��0706050403

First printing, January 2003

Contents

List of Figures

xxv

List of Tables

xxix

Foreword by Kim Caputo

xxxi

Foreword by Alistair Cockburn

xxxiii

Preface

xxxv

Introduction

xli

Part I

What Is Configuration Management? . . . . . . . . . . . . . . 1

Chapter 1 Definition of Configuration

Management Used in This Book . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1

1.2

Configuration Management Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Configuration Management Is Cyclic��or Is It?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Quality Assurance Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Audit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Process Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Unique Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

v

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download