357

Index

Absolute scale, 299Acceptance test, 98, 222ACME (Assembling Configuration Management

Environments) Project, 57Action-oriented team role, 139Active Development Line, 344, 347Activity areas, 3, 4-7. See also Change control;

Identification; Status reporting; Stor-age

baseline, 27metadata shared by, 5quality assurance process, 6-7

AdCoMs Project, 57Administrative documents, 82Agile software development, 207-11, 343-48

change authorization in, 347change control in, 345-46identification in, 346integration and build management in, 347-

48safety issues in, 344-45status reporting in, 348storage in, 346

Aktuar Systemer AS, 275Ambition, level of

expenses and, 68scoping configuration management task

and, 59-63, 67Analyst (systems engineer), 159-60Appleton, Brad, 57Approval

of configuration item, 103-6person responsible for, 97

Approval phase, change request in, 121

Architectural design, 98Assembling Configuration Management Envi-

ronments (ACME) Project, 57Assessment, 61Assets, 82-83

person responsible for, 151-52Attributed Files System (AtFS), 17Audit, 7Authority, conflicts of, 246Authorization, 11, 89

of change, in agile, 347for coding, 190for documents, 182for metadata, 96-97for milestone deliveries, 177

Baan CRM, 214Backpasses, 221, 222Backtracking in frequent-build development,

213-14Backup of systems in production, 197Balance point, 302-3Baseline(s), 27

in CMMI, 38establishment of, 269-70in maturity models, 29

“Belongs to” designation, 91Berczuk, Stephen, 57Best practices, collecting internally, 268Board for Software Standardisation and Control

(BSSC), 48Boehm, Barry, 218BOOTSTRAP 3.2, xliv, 40. See also SPICEBS 6488, 46, 47

358 Index

Build(s)in agile software development, 347-48multisite, 243-44

Build-and-smoke test (frequent-build tech-nique), 211-16

Build handling tools, 307Business Benefits of Software Best Practice,

Case Studies, The, 272Bypassing processes, 184-85

Capability level 1, 267-76baseline establishment, 269-70documentation, 271implementation of configuration manage-

ment, 272-76integrity establishment, 271starting from scratch, 267-69tracking and controlling changes, 270

Capability level 2, 37-38. See also PlanningCapability level 3. See Process(es)Capability level 4, 295, 297. See also Improve-

ment of configuration management, continuous

Capability level 5, 295, 297. See also Improve-ment of configuration management, continuous

Capability Maturity Model (CMM) version 1.1, xliv, 29-32

activities performed, 31-32definition of configuration management, 31maturity levels, 30-31

Capability Maturity Model for Software (SW-CMM) version 2.0, draft C, 33

Capability Maturity Model Integration (CMMI) SE/SW/IPPD version 1.02, 32-39, 56

capability levels, 36-39, 265-66definition of configuration management, 35discipline/environment description in, 33generic practices, 37-38goals for configuration management, 35maturity levels, 36practice-to-goal relationships, 35-36process areas, 34-35

Careers in configuration management, 137-38CCB. See Configuration control board (CCB)

Central ownership, 254, 258Cerebral team role, 139Certification, 61Change authorization in agile, 347Change control, 5, 8, 19-23

activities, 20-21in agile project, 345-46in coding, 190for company infrastructure, 252-53in composite systems, 227configuration control board and, 143in configuration management, 203connection with other activities, 23consequence analysis, 22of cross-organizational objects, 254for documents, 183establishment of, 270example of, 23, 24of external reuse components, 256in frequent-build development, 214inputs, 20of integration, 192-93for internal components, 260-61in iterative development, 220measurement data from, 132metadata usage, 21in milestone delivery, 178-79outputs, 20in parallel development, 248-49planning for, 284as process, 292process descriptions, 23product size and, 234in project management, 201for quality system, 263roles, 22-23in sequential development, 224in subcontractor management, 205in testing, 194for variants, 231in Web development, 238

Change control board (CCB), 346Change control tools, 307Change Management Process, 274Change phase, event registration in, 115

Index 359

Change requests, 8, 21, 116-23, 256content of, 119-20degree of formalism and, 122-23event registration and, 116-19phases of, 120-21

Changes, emergency, 183-85Charts, 286

control, 303-4“Cheating,” 184-85Class hierarchy for configuration items, 77-78Classification phase, event registration in, 115Closed phase, event registration in, 115CMB6-1C-94, 46CMII, 32-39, 56CMII Conference, 56CMM. See Capability Maturity Model (CMM)

version 1.1Codeline Policy, 344, 345Codelines, 344-45Coding, 187, 189-90Communication in agile development, 211Company infrastructure, 251-53Comparison tools, 249Compilation, conditional, 230Completer/finisher, 140Components for reuse (company product as-

sets), 82-83external, 254-57internal, 257-61

Composite deliveries, 237Composite systems, 225-27Composition report for configuration item, 127,

129Conditions for approval, 105Conferences, configuration management, 56Configuration control board (CCB), 22, 111,

141-44, 260-61multiple, 143, 144responsibilities of, 141-42skills and knowledge required for, 142-43

Configuration item(s)approval of, 15assembled in deliveries, 83class hierarchy for, 77-78composition report for, 127, 129

configuration management complexity for, 173, 174

defined, 77document as, 179formalism for, 60-61granularity of, 210history report for, 127, 128life cycle of, 5-6metadata for, 89-102

for authorization, 96-97data elements, 89-91for distribution, 101-2metadatabase medium, 90-91for relations to other configuration items,

97-101for unique identification, 91-95

name of, 91-92ownership of, 97for project management, 200proxy, for documents, 183registering, 103-23

approval, 103-6change requests, 116-23event registration, 111-16release request, 106-10

status of, 93status report for, 127storage of, 177-78tracing of, 98-99usage of, 15-16variants of, 229version information on, 93

Configuration managementin broader perspective, xlv-xlvibetween companies, xlvin company perspective, xli-xlivcyclicality of, 5-6defined, 3

Conflicts of authority, 246Consequence analysis, 22“Consists of” information, 100-101Content management, Web, 236Continuous integration (frequent-build) tech-

nique, 211-16Continuous representations, 33, 36, 38

360 Index

Control charts, 303-4Controlled library, 13, 17, 64, 283-84

release requests and, 106, 108Conventions, 292

defined, 290Co-ordinator, 139Cost/benefit analysis, 59-63Creation phase, change request in, 120, 121Cross-organizational activities, 149Cross-organizational functions, 251-63

company infrastructure, 251-53cross-organizational objects, 82-83, 253-54external reuse component development,

254-57internal asset development (product-line)

approach, 257-61quality system, 261-63

Cross-organizational perspective, xlivCruise Control, 307Culture, company, xliCustomer

demand for configuration management, xlvextra sales to, 70role of, 169-70

Customer contact manager, 167Customer relations, 275

Daily build (frequent-build) technique, 211-16Database and Selectors Cel configuration

(DaSC) Project, 57Data elements, 89-91Datamat Ingegneria dei Sistemi, 272-73Data types, 298Date, version, 93Decision making in agile development, 210Decision phase, event registration in, 113, 114Defined process. See Process(es)Delivery(ies)

composite, 237under configuration management, 83-85defined, 27document as, 179-80integration, 191internal, 285metadata for, 177-78

milestone, 175-79for modules, 289for planned events, 85-88project management and, 200by subcontractor, 206of subsystems, 285during testing, 193variants of, 229, 230Web, 237of working software, 210-11

Delta storage, 14Delta technique, 306“Derived from” information, 100Design, 72

of composite system, 226detailed, 98development, 187-88variants and, 229

Designer, 160-61Development

coding, 189-90documentation activities, 187-88external reuse component, 254-57integration, 191-93internal reuse component, 257-61maintenance, 197-98multisite (geographically distributed), 239-

45operational use, 194-97parallel, 246-49testing, 193-94Web, 235

Development (dynamic) library, 13-14, 17-18Development models, 85, 207-24

agile software development, 207-11, 343-48frequent-build technique, 211-16generic, xliiiintegrated product development, 216-17iterative, 85, 208, 218-20, 235sequential (waterfall) development, 85-86,

221-24Development tools, 249-50Diagrams, 286Direct measurement, 298Distribution, 90

Index 361

metadata for, 101-2Document(s), 179-83

administrative, 82authorization for, 182change control for, 183conditions of approving draft, 105as configuration item or delivery, 179-80development, types of, 188identification of, 180-82naming convention for, 74in project management, 201states for, 94status reporting on, 183storage of, 183tracing for, 182user requirement, 125

Documentation, 187-88in agile development, 211during implementation, 275, 276minimum, 271outdated, 71

Document control, 50DoD Mil-Std-483A-1985, 46DoD Mil-Std-973, 46, 48Drivers, 193Dynamic (development) library, 13-14, 17-18

EIA 649, 46EIA CMB4 standards, 46EIA CMB6 standards, 46EIA CMB7 standards, 46Electronic Industries Alliance Interim Standard

(EIA/IS) 731, Systems Engineering Capability Model (SECM), 33

Electronic objects in configuration manage-ment perspective, 79

Emergency changes, 183-85Employees of tool supplier, 314-15Empowered teams, 208-9Engineering in CMMI, 34Environment in agile development, 209-10Environments and tools, person responsible for,

155-56Error reduction in software products, 276Errors, 69-70

ESA PSS-05-09, 47, 48-49ESPRIT Project No. 22167, 57Estimation from configuration management

data, 132European Meteorological Satellite Organisation

(EUMETSAT), 17European Software Institute, 272Evaluation group, for tool selection, 311-12Evaluation phase, event registration in, 113,

114Evaluator, 140Event A/S, 275Event frequencies from configuration manage-

ment data, 132-33Event registration, 20-21, 111-16

change requests and, 116-19for company infrastructure, 252context of, 112-13degree of formalism and, 115-16, 117-18event life cycle and, 111of internal component problem, 260-61maintenance and, 197of operation use, 195-96phases of, 113-15types of, 111

Event (wish for modification), 20Exception handling, 184Expenses, estimating, 68External reuse component development, 254-57External roles, 169-71

customer, 169-70subcontractor, 171

FAA-STD-021, 47“False friends,” 26File storage, 183Financial status of tool supplier, 315Financing for tools, 310Finisher/completer, 140Flash plug-in, 255Food and Drug Administration (FDA), 49Formalism, 59-62

for configuration item, 60-61degree of, 61-66

approvals and, 105-6, 107

362 Index

change requests and, 122-23event registration and, 115-16, 117-18release requests and, 109-10

starting configuration management and, 61tools and, 62

Frequent-build technique, 211-16Fulfillment matrix, 246Full, company-wide process support tools, 307,

308Fuller, Ted, 236-37

GAMP, 49-50Geographically distributed (multisite) develop-

ment, 239-45example of, 239-40, 242-45identification in, 241organizational considerations, 240status reporting in, 242storage in, 241-42

Gilb, Tom, 297Glossary, 349-50Goal-Question-Metrics (GQM) technique, 273Goals, 35, 269-71

baseline establishment, 269-70change control establishment, 270defining and tracking, 150documentation, 271integrity, 271tools and, 308

Gold plating, 100Granularity

of configuration items, 210of configuration management, 72

Hardware-related delivery, 84Hardware under configuration management, 80Harvest, 308“Has been distributed to” information, 101-2Help desk, 156-57History report for configuration item, 127, 128

Identification, 7-11in agile project, 346authorization, 11of builds, 213

of company infrastructure, 252in composite systems, 227for configuration item approval, 104connection with other activities, 11of cross-organizational objects, 253-54of documents, 180-82of document types, 188for event registration, 112examples of, 9-11of external reuse components, 255inputs, 8of integration subsystems, 191-92of internal components, 259in iterative development, 220metadata for, 7, 8, 91-95of milestone delivery, 175-77in multiplatform products, 228in multisite development, 241outputs, 8parallel development and, 248pitfalls of, 74planning for, 283as process, 291, 292process descriptions, 9product size and, 234of project management document types, 201quality system objects, 262roles, 11in sequential development, 224of source code, 189in subcontractor management, 205of subitems, 181-82of test items, 193of variants, 230-31in Web applications, 237

IEEE-Std-610.12-1990, 48Implementation of configuration management,

272-76Datamat Ingegneria dei Sistemi, 272-73Event A/S, 275Istiservice, S.p.a., 274-75S.I.A. S.p.A., 273-74Sysdeco A/S, 276

Implementation phase, change requests in, 120Implementer, 140

Index 363

Improvement of configuration management, continuous, 295-304

metrics, 297-304analyzing, 301-4in general, 298-99selecting and defining, 300-301terms used in, 298

Indirect measurement, 298Individual support tools, 306-7, 308Infrastructure

under configuration management, 83cross-organizational functions and, 251-53

Institute for Information Technology, 57Institute of Configuration Management, 56Integrated product and process development

(IPPD) environment, 33Integrated product development, 216-17Integrated Product Development Capability Ma-

turity Model (IPD-CMM) version 0.98, 33

Integration, 187, 191-93in agile project, 347-48of new tools, 313

Integration Builds, 344, 347Integrators, 162-63Integrity, establishing, 271Interface control, 282Internal asset development (product-line) ap-

proach, 257-61Internal deliveries, 285International standards, 45-53

BS 6488, 46, 47DoD Mil-Std-483A-1985, 46DoD Mil-Std-973, 46, 48ESA PSS-05-09, 47, 48-49GAMP, 49-50IEEE-Std-610.12-1990, 48ISO 9000-3, 51-52ISO 9001:1994, 50-51ISO 9001:2000, 52-53overview of, 45-47

International Workshop on Software Configura-tion Management, 56

Interval scale, 299

IPD-CMM (Integrated Product Development Capability Maturity Model) version 0.98, 33

IPPD (integrated product and process develop-ment) environment, 33

ISO 9000-3, 51-52ISO 9001:1994, 50-51ISO 9001:2000, 52-53ISO 15504. See SPICEIstiservice, S.p.a., 274-75Iterative development, 85, 208, 218-20, 235

JTC1 12207-95, 47

KBST V, 47

Large systems, 233Librarian, 26, 144-46

activities of, 145skills required of, 145tools and, 146

Library, 13-14, 17-18. See also Storagecontrolled, 13, 17, 64, 283-84

release requests and, 106, 108dynamic (development), 13-14, 17-18proxy item in, 178static, 14

Licensing, 276Life cycle

under configuration management, 81responsibility and, 111

Logs of tools use, 64

“Made with” information, 100Mainline, 344Maintenance, 197-98

emergency changes in, 183Managed process, 38-39Management

relations to environment, 280-82subcontractor, 282support of configuration management, 273,

274Månsson, Bjarne, 214, 242-43

364 Index

MARF (Meteorological Archiving and Retrieval Facility), 17

Martin, James, 218Maturity models, xliv, 29-44

baseline in, 29Capability Maturity Model (CMM) version

1.1, 29-32activities performed, 31-32definition of configuration management,

31maturity levels, 30-31

Capability Maturity Model Integration (CMMI) SE/SW/IPPD version 1.02, 32-39, 56

capability levels, 36-39, 265-66definition of configuration management,

35discipline/environment description in, 33generic practices, 37-38goals for configuration management, 35maturity levels, 36practice-to-goal relationships, 35-36process areas, 34-35

degree of formalism and, 61improving configuration management and,

265-66ISO 15504 (SPICE) and BOOTSTRAP 3.2, 40-

44best practices, 42, 44definition of configuration management,

40goals, 40maturity levels, 42-43maturity of configuration management,

43-44process model, 20, 41

processes and, 290“May be distributed to” information, 101Mean, 302-3Measurement(s), 297-98. See also Metrics

configuration management as supplier of, 132-33

methods of, 300plans for, 300

Median, 302-3

Merge tools, 249Metadata, 5, 89-102

for authorization, 96-97in change control, 21data elements, 89-91for delivery, 177-78for distribution, 101-2on external reuse components, 255for identification, 7, 8, 91-95measurement data from, 132metadatabase medium, 90-91registration of, 90-91for relations to other configuration items,

97-101for unique identification, 91-95

Meteorological Archiving and Retrieval Facility (MARF), 17

Methods, description of, 287Metrics, 297-304

analyzing, 301-4in general, 298-99selecting and defining, 300-301terms used in, 298

Microsoft, 213-14Microsoft Visual SourceSafe (VSS), 13, 243-44,

283, 307MIDAS project, 273Milestone deliveries, 85-88, 175-79

authorization for, 177change control in, 178-79developments in, 175, 176generic content lists for, 177identification of, 175-77status reporting on, 179, 202storage and, 177-78

Milestones, 285-86agile, 346

MOD DEF-STAN 05-57/2, 47Mode, 302-3Modules

deliveries for, 289reusable, 258testing of, 72tracing, 190

Monitor/evaluator, 140

Index 365

Multiplatform products, 227-28Multiple stakeholders, 245-46Multisite (geographically distributed) develop-

ment, 239-45example of, 239-40, 242-45identification in, 241organizational considerations, 240status reporting in, 242storage in, 241-42

Multivariants, 228-31

Name of configuration item, 91-92National Inter-bank Network of Italy, 273NATO NAT-PRC-2, 47NATO STANAG 4159, 47Networks under configuration management, 80NIST S.P.500-161, 47Nominal scale, 299“Notes from the Front Lines: How to Test Any-

thing and Everything on a Web Site” (Fuller), 236-37

Object(s)cross-organizational, 82-83, 253-54electronic, 79physical, 78in product perspective, 79-81in project perspective, 81-83scoping and, 73-74

Operation, person responsible for, 152-53Operational use, 194-97

backup in, 197configuration management considerations,

195event registration of, 195-96organizational considerations in, 196release for, 195status reporting on, 196

Optimized process, 295Ordinal scale, 299Organizational considerations

for company infrastructure, 251in multisite development, 240in operational use, 196for tool support, 308-11

Organizational roles, 149-58asset management, 151-52environment and tools management, 155-56management, 149-50operations management, 152-53process management, 153-55support/help desk management, 156-57

Organization of configuration management, 281

Overall responsibility, 97Ovum, 56, 305Ownership

central, 254, 258of configuration item, 97multisite development and, 241of tools, 310

Parallel development, 246-49Parameter control, 229People-oriented team role, 139People perspective on configuration manage-

ment, xliPersonal build (frequent-build) technique, 211-

16Personnel, 267-68Pharmaceutical companies, guidelines from, 49Phase indication, 112-13Phase information, 111, 285-86Physical objects in configuration management

perspective, 78PIE (Process Improvement Experiment), 274Planned events, deliveries for, 85-88Planning, 71, 277-87

activities chapter, 282-84in frequent-build development, 212general advice, 277-79introduction section, 279-80management and relations to the environ-

ment chapter, 280-82measurement, 300in parallel development, 247schedule chapter, 285-86table of contents, 279templates in, 279for tools, 310

366 Index

tools, techniques, and methods chapter, 286-87

Plant role, 139Principles of Software Engineering Manage-

ment (Gilb), 297Private System Builds, 344, 347-48Private Workspace, 344, 346, 347Procedures, 292, 293

defined, 290Process(es), 289-94

in agile development, 209change control as, 292changing, 317defined, 290deployment of, 296-97identification as, 291, 292improvement of, 133, 295-97maturity models and, 290optimized, 295process model for, 291, 293-94

software code example of, 319-31tracing example of, 333-42

quantitative, 295recipe analogy of, 290-91special requirements for, 293status reporting as, 292-93storage as, 292

Process descriptionsin change control, 23in identification, 9in status reporting, 25in storage, 16-17

Process Improvement Experiment (PIE), 274Process management, 261-63

in CMMI, 34person responsible for, 153-55

Process perspective, xliv“Produced with” statement, 100Producers, 96Production time, 191Product-line (internal asset development) ap-

proach, 257-61Product perspective, xli-xlii

objects in, 79-81Products, 225-38

composite systems, 225-27life cycle of, xliimultiplatform, 227-28multivariants, 228-31safety-critical, 232-33size of, 233-34Web applications, 235-38

Profitability calculation, 67-71expenses, 68savings, 68-71

Programmer, 161-62Project management in CMMI, 34Project manager, 164-65Project perspective, xlii-xliii

objects in, 81-83Project-related roles, 159-68

analyst (systems engineer), 159-60customer contact manager, 167designer, 160-61integrators, 162-63programmer, 161-62project manager, 164-65quality assurance manager, 165-66subcontractor contact manager, 167-68testers, 163-64

Project-relate support tools, 308Project support functions, 199-206

configuration management, 202-3project management, 199-202quality assurance, 203-4subcontractor management, 204-6

Public relationships, 84-85Purpose, defining, 279PVCS, 307

Qualifications for configuration management, 138

Quality approval, 103-4Quality assurance activities, 203-4

effectiveness of, 133Quality assurance manager, 165-66Quality system, 261-63

under configuration management, 83standards for, 50-51

Quantitative process, 295

Index 367

RAD Model, 218Ratio scale, 299Raw data, 298Refactoring changes, 347Reference lists section of plan, 280Registration. See also Event registration

of configuration item, 103-23approval, 103-6change requests, 116-23event registration, 111-16release request, 106-10

of external reuse components, 256of metadata, 90-91tracing, 99

Regression Tests, 345, 347Release Line, 344, 345Release note, 125-26Release request, 106-10Releases, agile software, 346Reports. See Status reportingRepository, 344, 346Representation

continuous, 33, 36, 38staged, 36

Reputation of tool supplier, 315-16Requirements

multiple stakeholders and, 245-46outdated, 69for tools, 311, 312-14for variants, 229

Requirements managementin agile development, 210in iterative development, 219-20

Requirement specification as delivery, 84Resource investigator, 140Responsibility(ies)

of configuration control board, 141-42description of, in plan, 280, 281life cycle and, 111overall, 97for quality system, 262

Reusecomponents for, 82-83

external, 254-57internal, 257-61

development for, 257Roles, 22-23, 135. See also Organizational roles;

Project-related rolesin configuration management, 141-48

configuration control board, 141-44librarian, 144-46person responsible for, 146-48

external, 169-71customer, 169-70subcontractor, 171

RTCA DO/178B-92, 47Running number, 92

S.I.A. S.p.A., 273-74Safety-critical products, 232-33Sales, extra, 70Savings, estimating, 68-71Scalability of tools, 313Scale definitions, 299Schedule, planning of, 285-86Scope of plan, 280Scoping, 59-74

cost/benefit analysis, 59-63examples of, 64-67excluded objects, 73-74pitfalls in, 71-73profitability calculation, 67-71

expenses, 68savings, 68-71

Self-organizing teams, 208-9Sequential development, 85-86, 221-24Services under configuration management, 80-

81Shaper, 140Signatures, 105SISSI project, 272Small systems, 233Smoke Tests, 344-45, 347Software

under configuration management, 79-80criticality of, 232process model for (example), 319-31

Software Configuration Management Patterns (Berczuk & Appleton), 57

368 Index

Software Configuration Management (SCM), 343-48. See also Agile software devel-opment

Software development guidelines, 48-49, 51-52Software development standards, xlvSoftware engineering discipline in CMMI, 33Software Engineering Information Repository

(SEIR), 56-57Software Engineering Institute (SEI), 29, 56-57,

216, 257Software products, error reduction in, 276Software requirements, 98Source code, 77

conditions of approving, 105under informal configuration management,

63producer of, 96states for, 94-95storage of, 190unique identification of, 189

Special conditions, 239-50multiple stakeholders, 245-46multisite (geographically distributed) devel-

opment, 239-45parallel development, 246-49tool support, 249-50

Specialist, 140Specifications, development, 187-88SPICE, 40-44

best practices, 42, 44definition of configuration management, 40goals, 40maturity levels, 42-43maturity of configuration management, 43-

44process model, 20, 41

Spiral Model, 218Staged representation, 36Stakeholders, multiple, 245-46Standards, 282. See also International stan-

dardsdegree of formalism and, 61software development, xlv

Starting configuration management, degree of formalism and, 61

Statesfor documents, 94for source code, 94-95

Static library, 14Statistics, 302Status code, 112-13Status of configuration item, 93Status reporting, 23-26, 125-33

in agile development, 211, 348for company infrastructure, 253in composite systems, 227composition list, 127, 129in configuration management, 132-33, 203connection with other activities, 26for cross-organizational objects, 254on documents, 183for external reuse components, 256-57history report, 127, 128inputs, 25for internal component, 261in iterative development, 220on milestone delivery, 179, 202in multisite development, 242on operational use, 196outputs, 25in parallel development, 249planning for, 284as process, 292-93process descriptions, 25product size and, 234in project management, 201-2for quality system, 263release note, 125-26roles, 26in sequential development, 224status list, 127by subcontractor, 206trace reports, 130-31on variants, 231for Web systems, 238

Stock control, 109Storage, 12-18. See also Library

in agile project, 346for company infrastructure, 252of composite systems, 227

Index 369

of configuration item, 177-78, 202connection with other activities, 17of cross-organizational objects, 254delta, 14of documents, 183example of, 17-18of external reuse components, 255-56frequent-build and, 212, 213of integration information, 192of internal components, 259-60in iterative development, 220location of, 94main processes, 15-16medium of, 94milestone delivery and, 177-78in multisite development, 241-42in parallel development, 248pitfalls of, 74planning for, 283-84as process, 292process descriptions, 16-17product size and, 234of quality system, 262roles, 16-17of source code, 190subcontractor management and, 205of test environments, 194of variants, 231of Web applications, 238

Stubs, 193Subcontractor

configuration management by, xlvmanagement of, 204-6, 282role of, 171

Subcontractor contact manager, 167-68Subdelivery, 171Subitems, unique identification of, 181-82Subsystem(s)

deliveries of, 285integration, 191

Supplier, tool, 314-16Support, xlii-xliii, 156-57

in agile development, 209-10in CMMI, 34-35under configuration management, 81, 82

for tools, 316Survey of Existing and In-Work Software Engi-

neering Standards and Specifications, 45

SW-CMM (Capability Maturity Model for Soft-ware) version 2.0, draft C, 33

Synchronization in multisite development, 241-42, 243

Sysdeco A/S, 276Systems engineer (analyst), 159-60Systems engineering discipline in CMMI, 33System test specifications, 98

Task description, 285Teams

empowered, 208-9putting together, 140self-organizing, 208-9

Teamworker, 140Techniques, description of, 287Template(s), 258, 259, 292, 293

defined, 290for planning, 279

Testers, 163-64Testing, 187, 193-94

module, 72Third Party Codeline, 344Tool(s), 305-17

build handling, 307buying vs. do-it-yourself, 309change control, 307classes of, 306-8comprehensive information about, 74under configuration management, 81customizing, 274, 316-17development, 249-50formalism and, 62full, company-wide process support (total-

process-oriented), 307, 308guidelines for using, 308incremental deployment of, 274individual support, 306-7, 308librarian and, 146logs of use in controlled library, 64organizational considerations, 308-11

370 Index

in parallel development, 249person responsible for, 155-56planning for, 286product size and, 234project-related support, 308requirements for, 311, 312-14requirements for supplier, 314-16selecting, 274, 311-12training for, 274version control, 306-7

Tools perspective on configuration manage-ment, xliv

Tool support, 249-50Total-process-oriented tools, 307, 308Trace reports, 130-31Tracing, 63

coding, 190of configuration item, 98-99for documents, 182importance of, 99-100of integration, 192process model for (example), 333-42in project management, 201requirements, 210test-related, 193-94of variants, 231

Tracing registration, 99Tracking changes, 270Tracy (tracing tool), 333-42Training, 274, 275TSC AS, 275

Unique identification. See Identification

Unit Tests, 345, 347Usability of tools, 314Usage matrix, 257User requirement document, 125

Validation, 203Variants, 228-31Variation, statistical, 303Verification, 204Version control, 27, 38Version control tools, 306-7Version date, 93Version information on configuration item, 93Versions, new, 197-98Visual SourceSafe (VSS), 13, 243-44, 283, 307V-model, 98, 222Vocabulary section of plan, 280

Waterfall (sequential) development model, 85-86, 221-24

Web applications, 235-38external components in, 255tools for, 314

Wish for modification (event), 20W-model, 222, 223Working practices, realistic view of, 273WorkManager, 308Workspace management, 307

XP, 347

Yellow Pages for configuration management, 55