Software Release Methodology [Paperback]

Michael E. Bays (Author)

Book Description

ISBN-10: 0136365647 | ISBN-13: 978-0136365648 | Publication Date: July 3, 1999 | Edition: 1

63656-3 Improve software quality, lower costs, and get to market faster! Don't risk your software product's success through haphazard integration and release management! Software Release Methodology shows you "best practices" for every stage of a successful product release: source code control, product build, testing and defect tracking, code integration, software change management, and release engineering. No matter how large (or small) your project or software development organization, you'll find carefully designed, practical solutions that enhance quality, reduce costs, and get you to market faster. Coverage includes: *Why product builds are so difficult, and how to solve the problem. *Simple defect tracking techniques that make sure problems actually get fixed. *Managing releases on hard media, soft media, and "net" media. *Preventing problems on media masters. *Release numbering and naming: setting customer expectations and avoiding confusion. *Change control for managing your software development process from start to finish. *Organizational solutions that work in establishing release management and services.Bays presents expert techniques that have never been published before-and shows how to design a coherent integration and release process that's dramatically more effective than what you're doing now. If you're responsible for a successful software release, Software Methodology may be the most important book you'll buy this year.

Editorial Reviews

From the Inside Flap

Preface

Software release methodology is a field that unifies a number of previously abstract endeavors that occur during software product development. By unifying these abstract endeavors, we provide a more efficient, well-understood path from development to product release. The field focuses on the release activity as the driving force behind all development endeavors.

Why focus on release? It is my observation that for the majority of software product development efforts, time to market is everything. This is where a company's ability to execute on software releases becomes critical. Successfully balancing a new product's performance and feature set against its release date is an important capability in our industry.

Furthermore, additional goals such as quality, reliability, and performance take second place when compared with time to market. Although this seems to contradict the market pundits' demands for unimaginable strides in quality and functionality, it is an unfortunate reality to those faced with the development of successful products in today's industry. Companies rarely have the luxury to get to market on time and successfully implement all these secondary goals in their first release. If a company focuses on these secondary goals as its first priority, it risks not getting to market in time. If it doesn't, the result is that even though the company has a high-quality, technically innovative, reliable product, a more timely competitor has released an adequate solution first, and the market has become accustomed to the earlier product. The effort required to unseat an established competitor and capture an already dominated market is far greater than that needed to release the first acceptable solution and then maintain that initial success.

It is indeed rare to capture a market with only the initial release of a product. Release is an iterative, long-term game that must be played in an optimal, organized manner. In support of this time-to-market imperative, software release methodology endeavors to provide a reasonable framework for the development of that first and defining release that captures the market, as well as the future releases that secure a product's long term success.

In this book, software release methodology is defined in a commonly applicable format. Because of time-to-market pressure, development teams no longer have the time to continually reinvent the elements of software release. How to organize source control systems? How to track defects? How to know when to release? The answers to these simple questions can take years for a product team to determine, as the answers can be different for each product, and even for each individual product release. The elements that make up software release methodology are as follows:

Source code control

Builds

Defect tracking

System integration

Release classifications and numbering

Release distribution

Release services

Release management

These elements are defined so that their roles, responsibilities, and relationships to the release objectives are well understood. These definitions provide a template that can be customized and localized to suit the specific needs of an individual development effort. Most importantly, the development effort will not need to reinvent them from scratch with every new project that is undertaken.

It is my hope that the introduction and definition of this field will aid in efforts to improve and optimize the software development process as a whole.

From the Back Cover

63656-3

Improve software quality, lower costs, and get to market faster!

Don't risk your software product's success through haphazard integration and release management! Software Release Methodology shows you "best practices" for every stage of a successful product release: source code control, product build, testing and defect tracking, code integration, software change management, and release engineering. No matter how large (or small) your project or software development organization, you'll find carefully designed, practical solutions that enhance quality, reduce costs, and get you to market faster. Coverage includes:

• Why product builds are so difficult, and how to solve the problem.
• Simple defect tracking techniques that make sure problems actually get fixed.
• Managing releases on hard media, soft media, and "net" media.
• Preventing problems on media masters.
• Release numbering and naming: setting customer expectations and avoiding confusion.
• Change control for managing your software development process from start to finish.
• Organizational solutions that work in establishing release management and services.

Bays presents expert techniques that have never been published before-and shows how to design a coherent integration and release process that's dramatically more effective than what you're doing now. If you're responsible for a successful software release, Software Methodology may be the most important book you'll buy this year.

See all Editorial Reviews

Product Details

• Paperback: 256 pages
• Publisher: Prentice Hall; 1 edition (July 3, 1999)
• Language: English
• ISBN-10: 0136365647
• ISBN-13: 978-0136365648
• Product Dimensions: 9.1 x 7 x 0.6 inches
• Shipping Weight: 11.2 ounces (View shipping rates and policies)
• Average Customer Review: 3.3 out of 5 stars  See all reviews (16 customer reviews)
• Amazon Best Sellers Rank: #1,027,588 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

92 of 97 people found the following review helpful:

4.0 out of 5 stars Sound strategies for software configuration & release mgmt, August 1, 1999

By 

Brad Appleton (Arlington Heights, IL USA) - See all my reviews

This review is from: Software Release Methodology (Paperback)

Except for a few overinflated claims of originality, this is a fine book chock full of sound, proven strategies for configuration and release management of software. The author gives detailed coverage of strategies and guidelines for: source-code control; software builds; defect tracking; system integration; release classification and numbering; release distribution and services; and release management.

In each case the author explains both the "what" and the "why" behind the strategies, giving practical advice for their deployment in the real world, and practical experience from having already done so.

The only things that bothered me about the book were that (1) the author claims to be introducing a new field "software release methodology"; (2) the back of the book claims most of strategies in the book have never been published before; and (3) there is no bibliography or references section of any kind.

As someone who has been a software configuration management professional for the past twelve years, it is my understanding that release classification, numbering, distribution, and management have all long been considered part of the release engineering process. The other areas of source-control, builds, integration, and defect-tracking & change-control have long been considered part of software configuration management (SCM).

I dont understand why both CM and SCM fail to appear anywhere in the book (especially the index), since the first 7 chapters are precisely the stuff of SCM. I do know that release engineering is often considered part of SCM as well, but I agree with the author that it has been underemphasized for too long. It's good the author remedies this, but failing to even mention SCM, and claiming he's introducing a brand new field stretches reality a tad too far.

Similarly, claiming all or even most of these techniques have never been published before is also too grandiose a statement. I have seen most of them published before, in various books and journals and conference proceedings. The author has done a *great* service by collecting them together in one volume and making them more accessible to the practitioner in the trenches, but he's not the first to publish them (and he doesnt have to be in order for the book to be of value).

I can understand the author making a case that he's creating a "new field" by combining SCM and Release Engineering in a certain way (though I still think its a stretch); I can even understand claiming to be the first to publish these strategies in a single accessible volume (but not the first to publish them ever); What I cant understand is why there is not one single citation or bibliographic reference anywhere in the entire book.

To me, the lack of any bibliographic references seems inexcuseable, and combined with the aforementioned mistatements wreaks a bit too much of hubris/arrogance for my taste. By failing to provide published (as well as online) references, the author gives the reader no way to verify the book's claims of original work, nor to seek out further background material, nor demonstrate that the author performed the requisite due dilligence to comb the literature before making such claims.

It was unnecessary to claim originality for this work to be of value. A modicum of modesty should have been called for here. These three failings which amount to only a few pages of text leave a very sour taste on what is otherwise a very fine, substantive and insightful contribution in the other 250 or so pages of the book.

If not for those ever so brief yet overinflated claims, I would have given the book five stars instead of four. It really is a *must* *read* for anyone who is less than expert in the fields of software configuration management and release engineering. Just keep in mind that the material is not quite as inventive or innovative as those few pages would lead you to believe the rest of the book to be. Fortunately, this in no way detracts from the usefulness of the proven practices described therein.

26 of 28 people found the following review helpful:

5.0 out of 5 stars Great overview of these collective fields, August 5, 1999

By A Customer

This review is from: Software Release Methodology (Paperback)

As the author has observed these fields binding together so have I. I have searched on numerous occasions for texts that provide a unified perspective on these fields. Now I finally have it. The book does a great job of stepping through the mine-fields of SCM, defect tracking, and project management which have collectively been nothing but a disaster in my experience in about 6 software companies. While the book does not go into a low level of detail on the SCM models, as I would like I believe that it does a good overall job of the fields. Hope we can see more from this author in the future.

23 of 25 people found the following review helpful:

4.0 out of 5 stars The Proven path to Software Release, October 17, 2001

By 

Binoo Mathen (Bangalore, India) - See all my reviews

This review is from: Software Release Methodology (Paperback)

SCM and Software Release Management encompass a broad spectrum of activities and practices that ultimately determine the quality of the product and the control of the product release. Software configuration management (SCM) and Release Management may sound the same; `Software Release Management' by Michael E Bays lucidly provides an insight into what are the nuances.
Software configuration management is a key process area, which holds a significant importance in determining the control and success of the delivery process. Right from source code control, build management, defect tracking, change management, to multi-platform product releases, determines to a great extend the release process management methodologies that gives a structured approach to software development, that ensures that the efforts of the development team doesn't go wasted in providing the right versions and a more complete solution to the end-users.
The significance of software release management comes more to light in large projects involving large team, multi-site and multi-platform development. Full life-cycle projects which usually reflects wide gaps and variations between what is initially defined and what is finally delivered, demanding stringent and documented processes which control the requirement changes, defect fixes and change control mechanisms to the minutest possible detail. Michael E Bays captures in the most simplistic coverage, how this can be executed by proper release mgt methodologies. This calls for an efficient defect tracking and configuration mgt systems, to determine whether 'what we believe, is what we achieved'.