
At a Glance
412 Pages
Revised
25.4 x 17.78 x 2.54
Hardcover
$207.75
or 4 interest-free payments of $51.94 with
 orÂShips in 10 to 15 business days
| Preface | p. xix |
| Acknowledgments | p. xxiii |
| Overview of software configuration management | p. 1 |
| Introduction | p. 1 |
| Common SCM myths | p. 3 |
| SCM is a difficult, monotonous, and time-consuming activity | p. 3 |
| SCM is the responsibility of management | p. 3 |
| SCM is just for developers | p. 4 |
| SCM is just for the SCM team | p. 4 |
| SCM is just for the maintenance and technical support team | p. 4 |
| SCM slows down the software development process | p. 5 |
| SCM is only needed to get certifications | p. 5 |
| SCM tools will take care of everything | p. 6 |
| One SCM tool will suit everyone | p. 6 |
| SCM is expensive | p. 6 |
| SCM is just for the source code | p. 7 |
| SCM is change management and defect tracking | p. 7 |
| Software development can succeed without SCM | p. 7 |
| A brief history of SCM | p. 8 |
| SCM: Concepts and definitions | p. 9 |
| Importance of SCM | p. 11 |
| Benefits of SCM | p. 12 |
| Summary | p. 12 |
| References | p. 13 |
| The software development process | p. 15 |
| Introduction | p. 15 |
| Software development life cycle | p. 16 |
| SDLC phases | p. 18 |
| Project start-up | p. 19 |
| Requirements analysis and requirements specification | p. 21 |
| Systems analysis | p. 22 |
| High-level design | p. 24 |
| Low-level or detailed design | p. 25 |
| Coding and unit testing | p. 26 |
| System testing | p. 27 |
| Acceptance testing | p. 28 |
| Implementation | p. 29 |
| Project windup | p. 29 |
| Project maintenance | p. 30 |
| Retirement | p. 30 |
| Summary | p. 32 |
| References | p. 32 |
| Selected bibliography | p. 33 |
| Pitfalls in the software development process | p. 35 |
| Introduction | p. 35 |
| Communications breakdown problem | p. 36 |
| Shared data problem | p. 38 |
| Multiple maintenance problem | p. 39 |
| Simultaneous update problem | p. 41 |
| Summary | p. 42 |
| References | p. 42 |
| Need and importance of SCM | p. 43 |
| Introduction | p. 43 |
| Need for SCM | p. 43 |
| The nature of software products, projects, and development teams | p. 43 |
| Increased complexity and demand | p. 44 |
| Changing nature of software and need for change management | p. 46 |
| Benefits of SCM | p. 46 |
| Improved organizational competitiveness | p. 47 |
| Better customer service and improved customer goodwill | p. 47 |
| Better return on investment | p. 48 |
| Improved management control over software development activities | p. 48 |
| Improved software development productivity | p. 48 |
| Easier handling of software complexity | p. 49 |
| Improved security | p. 49 |
| Higher software reuse | p. 50 |
| Lower maintenance costs | p. 50 |
| Better quality assurance | p. 51 |
| Reduction of defects and bugs | p. 51 |
| Faster problem identification and bug fixes | p. 52 |
| Process-dependent development rather than person-dependent development | p. 52 |
| Assurance that the correct system has been built | p. 53 |
| Summary | p. 53 |
| References | p. 54 |
| SCM: Basic concepts | p. 55 |
| Introduction | p. 55 |
| Overview of SCM | p. 56 |
| Baselines | p. 57 |
| Check-in and checkout | p. 60 |
| Versions and variants | p. 61 |
| Parallel development and branching | p. 62 |
| Naming of versions | p. 64 |
| Source and derived items | p. 64 |
| System building | p. 65 |
| Releases | p. 65 |
| Deltas | p. 67 |
| SCM database | p. 69 |
| SCM activities | p. 70 |
| Summary | p. 71 |
| References | p. 71 |
| Selected bibliography | p. 71 |
| The different phases of SCM implementation | p. 73 |
| Introduction | p. 73 |
| Objectives of SCM implementation | p. 74 |
| Speed | p. 75 |
| Scope | p. 75 |
| Resources | p. 75 |
| Risk | p. 75 |
| Complexity | p. 75 |
| Benefits | p. 76 |
| Different phases of SCM implementation | p. 76 |
| SCM system design | p. 80 |
| SCM plan preparation | p. 81 |
| SCM team organization | p. 82 |
| SCM infrastructure setup | p. 82 |
| SCM team training | p. 82 |
| Project team training | p. 83 |
| SCM system implementation | p. 83 |
| SCM system operation and maintenance | p. 84 |
| Records retention | p. 84 |
| SCM system retirement | p. 85 |
| SCM tool retirement | p. 85 |
| Why do many SCM implementations fail? | p. 85 |
| Lack of top management buy-in, commitment, and support | p. 86 |
| Improper planning and budgeting | p. 86 |
| Use of the wrong SCM tool | p. 86 |
| Lack of training | p. 87 |
| Work culture of the organization | p. 87 |
| Summary | p. 87 |
| Reference | p. 88 |
| Selected bibliography | p. 88 |
| Configuration identification | p. 89 |
| Introduction | p. 89 |
| Impact of configuration item selection | p. 93 |
| Effects of selecting too many configuration items | p. 93 |
| Effects of selecting too few configuration items | p. 94 |
| Baselines | p. 94 |
| Configuration item selection | p. 96 |
| Checklist for selection of configuration items | p. 96 |
| Designation: Naming of configuration items | p. 98 |
| Configuration item description | p. 99 |
| Acquisition of configuration items | p. 99 |
| Summary | p. 100 |
| References | p. 100 |
| Selected bibliography | p. 100 |
| Configuration control | p. 103 |
| Introduction | p. 103 |
| Change | p. 104 |
| Proposing changes to the customer | p. 105 |
| Deviations and waivers | p. 105 |
| Change and configuration control | p. 106 |
| Problems of uncontrolled change | p. 106 |
| Configuration control | p. 107 |
| Change initiation | p. 110 |
| Change classification | p. 110 |
| Change evaluation/analysis | p. 111 |
| Change disposition | p. 112 |
| Change implementation | p. 113 |
| Change verification | p. 114 |
| Baseline change control | p. 115 |
| File-based versus change-based change management | p. 115 |
| Escalation and notification | p. 117 |
| Emergency fixes | p. 117 |
| Problem reporting and tracking | p. 118 |
| Problem reports and change requests | p. 118 |
| Problem identification | p. 119 |
| Defect classification | p. 121 |
| Requirements analysis | p. 122 |
| Design phase | p. 122 |
| Coding and testing phase | p. 122 |
| Defect severity | p. 122 |
| Defect prevention | p. 123 |
| Causal analysis | p. 123 |
| Defect knowledge base and help desks | p. 124 |
| Change control board | p. 124 |
| CCB composition | p. 125 |
| Functions of the CCB | p. 126 |
| Functioning of the CCB | p. 128 |
| Summary | p. 129 |
| References | p. 129 |
| Selected bibliography | p. 130 |
| Status accounting | p. 131 |
| Introduction | p. 131 |
| Status accounting information gathering | p. 133 |
| Status accounting database | p. 133 |
| Importance of status accounting | p. 135 |
| Status accounting reports | p. 136 |
| Change log | p. 137 |
| Progress report | p. 137 |
| CI status report | p. 137 |
| Transaction log | p. 137 |
| Status accounting and automation | p. 138 |
| Change/problem tracking reports | p. 139 |
| Difference reporting | p. 139 |
| Ad hoc queries | p. 139 |
| Journals | p. 140 |
| Summary | p. 140 |
| References | p. 140 |
| Selected bibliography | p. 141 |
| Configuration verification and audits | p. 143 |
| Introduction | p. 143 |
| Software reviews | p. 146 |
| Configuration verification | p. 146 |
| When, what, and who of auditing | p. 147 |
| Functional configuration audit | p. 149 |
| Physical configuration audit | p. 150 |
| Auditing the SCM system | p. 150 |
| Role of the SCM team in configuration audits | p. 151 |
| Configuration audits and SCM tools | p. 151 |
| Summary | p. 152 |
| References | p. 152 |
| Selected bibliography | p. 152 |
| SCM: Advanced concepts | p. 155 |
| Introduction | p. 155 |
| Version control | p. 155 |
| System building | p. 156 |
| Release management | p. 157 |
| Interface control | p. 158 |
| Subcontractor control | p. 160 |
| Software library | p. 161 |
| Summary | p. 162 |
| References | p. 163 |
| Selected bibliography | p. 163 |
| SCM standards | p. 165 |
| Introduction | p. 165 |
| Military standards | p. 170 |
| DOD-STD-2167A | p. 170 |
| DOD-STD-2168 | p. 171 |
| MIL-STD-973 | p. 171 |
| MIL-HDBK-61A (SE) | p. 171 |
| MIL-STD-2549 | p. 172 |
| MIL-STD-480B | p. 172 |
| MIL-STD-481B | p. 173 |
| MIL-STD-482 | p. 173 |
| MIL-STD-483A | p. 174 |
| MIL-STD-490A | p. 174 |
| MIL-STD-1521B | p. 174 |
| International/commercial standards | p. 175 |
| EIA-649-1998 | p. 176 |
| IEEE Std-828-1998 | p. 176 |
| ANSI/IEEE Std-1042-1987 | p. 176 |
| ANSI/IEEE Std-730-2002 | p. 177 |
| ANSI/IEEE Std-1028-1988 | p. 177 |
| IEEE/EIA 12207.0-1996 | p. 177 |
| IEEE/EIA 12207.1-1997 | p. 178 |
| IEEE/EIA 12207.2-1997 | p. 178 |
| ISO 9001:1994 | p. 179 |
| ISO 9001: 2000 | p. 179 |
| ISO 9000-3: 1997 | p. 180 |
| ISO 10007: 2003 | p. 181 |
| Summary | p. 181 |
| Selected bibliography | p. 185 |
| Software process improvement models and SCM | p. 187 |
| Introduction | p. 187 |
| Capability Maturity Model | p. 188 |
| Capability Maturity Model Integration | p. 189 |
| ISO/IEC 15504 | p. 190 |
| BOOTSTRAP | p. 191 |
| Trillium Model | p. 192 |
| Summary | p. 193 |
| Selected bibliography | p. 195 |
| SCM plans | p. 197 |
| Introduction | p. 197 |
| SCM plan and the incremental approach | p. 198 |
| SCM plan and SCM tools | p. 199 |
| SCM plans and standards | p. 199 |
| ANSI/IEEE Std-828-1998 and ANSI/IEEE Std-1042-1987 | p. 200 |
| MIL-HDBK-61A(SE)-2001 | p. 200 |
| EIA-649-1998 | p. 202 |
| ISO 10007: 2003 | p. 203 |
| Audit of the SCM plan | p. 204 |
| How to write a good SCM plan | p. 205 |
| Contents of a typical SCM plan | p. 207 |
| Sample SCM plans | p. 213 |
| Summary | p. 213 |
| Reference | p. 214 |
| Selected bibliography | p. 214 |
| SCM organization | p. 215 |
| Introduction | p. 215 |
| SCM and the organization | p. 216 |
| SCM organization | p. 217 |
| Automation and SCM team size | p. 221 |
| Skill inventory database | p. 221 |
| CCB organization | p. 223 |
| Summary | p. 225 |
| Reference | p. 226 |
| Selected bibliography | p. 226 |
| SCM tools | p. 227 |
| Introduction | p. 227 |
| Evolution of SCM tools | p. 227 |
| Reasons for the increasing popularity of SCM tools | p. 228 |
| Advantages of SCM tools | p. 229 |
| Information integration | p. 230 |
| Flexibility | p. 230 |
| Better analysis and planning capabilities | p. 230 |
| Use of latest technology | p. 231 |
| Why do many SCM tool implementations fail? | p. 231 |
| SCM tools and SCM functions | p. 232 |
| Version management | p. 233 |
| Change management | p. 233 |
| Problem tracking | p. 235 |
| Promotion management | p. 236 |
| System building | p. 236 |
| Status accounting (querying and reporting) | p. 237 |
| Configuration audits | p. 237 |
| Access and security | p. 237 |
| Customization | p. 238 |
| Web enabling | p. 238 |
| SCM tool selection | p. 239 |
| Selection process | p. 240 |
| Selection committee | p. 241 |
| Working with vendors | p. 241 |
| Role of technology | p. 242 |
| Selection criteria | p. 243 |
| Tool implementation | p. 245 |
| SCM tools: Make or buy? | p. 248 |
| Summary | p. 251 |
| References | p. 251 |
| Selected bibliography | p. 251 |
| Documentation management and control and product data management | p. 255 |
| Introduction | p. 255 |
| Document life cycle | p. 256 |
| Document creation | p. 258 |
| Document storage | p. 258 |
| Publishing | p. 258 |
| Viewing | p. 259 |
| Modification/change, review, and approval | p. 259 |
| Records retention | p. 259 |
| Document disposal | p. 260 |
| Archiving | p. 260 |
| Documentation and SDLC phases | p. 260 |
| Documentation management and control | p. 260 |
| PDM and DMC | p. 264 |
| Overview of PDM | p. 265 |
| Data management | p. 267 |
| Process management | p. 267 |
| Benefits of PDM | p. 268 |
| Reduced time-to-market | p. 269 |
| Improved design productivity | p. 269 |
| Improved design and manufacturing accuracy | p. 269 |
| Better use of creative team skills | p. 269 |
| Data integrity safeguarded | p. 270 |
| Better control of projects | p. 270 |
| A major step toward total quality management | p. 270 |
| PDM and SCM integration | p. 270 |
| PDM resources | p. 271 |
| Summary | p. 272 |
| References | p. 272 |
| Selected bibliography | p. 273 |
| SCM implementation | p. 275 |
| Introduction | p. 275 |
| Managing the implementation | p. 275 |
| SCM implementation plan | p. 276 |
| Risk assessment | p. 277 |
| Implementation strategy | p. 278 |
| Budget | p. 279 |
| Cost | p. 280 |
| Cost-benefit analysis | p. 282 |
| Performance measurement | p. 282 |
| SCM implementation team | p. 283 |
| Composition of the implementation team | p. 285 |
| Organization of the implementation team | p. 286 |
| How the implementation team works | p. 292 |
| Problem resolution | p. 294 |
| SCM tool vendors and vendor management | p. 294 |
| Training | p. 296 |
| Employees and employee resistance | p. 298 |
| Pilot project | p. 299 |
| Company-wide implementation | p. 299 |
| SCM implementation: The hidden costs | p. 300 |
| Training | p. 300 |
| Integration and testing | p. 300 |
| Data conversion/migration | p. 301 |
| External consultants | p. 301 |
| Summary | p. 301 |
| Reference | p. 302 |
| Selected bibliography | p. 302 |
| SCM operation and maintenance | p. 303 |
| Introduction | p. 303 |
| Employee relocation and retraining | p. 304 |
| Organizational structure | p. 305 |
| Roles and skills | p. 305 |
| Knowledge management | p. 306 |
| SCM tools and technology | p. 306 |
| Review | p. 307 |
| Operation of the SCM system | p. 307 |
| Interdepartmental coordination | p. 308 |
| SWOT analysis | p. 309 |
| Documentation | p. 309 |
| Training | p. 310 |
| Audits and reviews | p. 310 |
| CCB formation | p. 310 |
| SCM database management | p. 311 |
| Software upgrades, enhancements, and modifications | p. 311 |
| Help desks | p. 312 |
| Change/problem requests from customers and in-field emergency fixes | p. 312 |
| Reusability improvement | p. 312 |
| Metrics | p. 313 |
| SCM maintenance phase | p. 314 |
| Summary | p. 315 |
| Selected bibliography | p. 315 |
| SCM in special circumstances | p. 317 |
| Introduction | p. 317 |
| SCM and project size | p. 317 |
| SCM in large projects | p. 318 |
| Performance of SCM tools | p. 319 |
| Implementation strategy | p. 319 |
| Distributed, concurrent, and parallel development | p. 320 |
| Change management | p. 321 |
| Status accounting | p. 321 |
| System building | p. 322 |
| Skill inventory database | p. 322 |
| Training | p. 322 |
| Help desks and other knowledge-sharing systems | p. 323 |
| SCM costs | p. 323 |
| Concurrent and parallel development | p. 323 |
| Web site management | p. 324 |
| SCM in integrated development environments | p. 324 |
| SCM in distributed environments | p. 325 |
| SCM and CASE tools | p. 325 |
| Summary | p. 326 |
| Reference | p. 327 |
| Selected bibliography | p. 327 |
| SCM Resources on the Internet | p. 329 |
| SCM Bibliography | p. 333 |
| SCM Glossary and Acronyms | p. 359 |
| Author Biography | p. 371 |
| Index | p. 373 |
| Table of Contents provided by Rittenhouse. All Rights Reserved. |
ISBN: 9781580538824
ISBN-10: 1580538827
Series: Artech House Computing Library
Published: 31st December 2004
Format: Hardcover
Language: English
Number of Pages: 412
Audience: General Adult
Publisher: ARTECH HOUSE INC
Country of Publication: US
Edition Number: 2
Edition Type: Revised
Dimensions (cm): 25.4 x 17.78 x 2.54
Weight (kg): 0.87
Shipping
| Standard Shipping | Express Shipping | |
|---|---|---|
| Metro postcodes: | $9.99 | $14.95 |
| Regional postcodes: | $9.99 | $14.95 |
| Rural postcodes: | $9.99 | $14.95 |
Orders over $89.00 qualify for free shipping.
How to return your order
At Booktopia, we offer hassle-free returns in accordance with our returns policy. If you wish to return an item, please get in touch with Booktopia Customer Care.
Additional postage charges may be applicable.
Defective items
If there is a problem with any of the items received for your order then the Booktopia Customer Care team is ready to assist you.
For more info please visit our Help Centre.
You Can Find This Book In

Architecture Patterns with Python
Enabling Test-Driven Development, Domain-Driven Design, and Event-Driven Microservices
Paperback
RRP $125.75
$100.60
OFF

Hands-On Machine Learning with Scikit-Learn, Keras, and Tensorflow
Concepts, Tools, and Techniques to Build Intelligent Systems
Paperback
RRP $135.99
$108.79
OFF
This product is categorised by
- Non-FictionComputing & I.T.Computer Science
- Non-FictionComputing & I.T.Computer Programming & Software DevelopmentProgramming & Scripting Languages
- Non-FictionComputing & I.T.Computer Programming & Software DevelopmentSoftware Engineering
- Non-FictionEngineering & TechnologyIndustrial Chemistry & Manufacturing Technologies






















