- Taschenbuch: 252 Seiten
- Verlag: Addison-Wesley Professional; Auflage: 01 (4. November 2002)
- Sprache: Englisch
- ISBN-10: 0201741172
- ISBN-13: 978-0201741179
- Größe und/oder Gewicht: 18,3 x 1,8 x 23,1 cm
- Durchschnittliche Kundenbewertung: 1 Kundenrezension
- Amazon Bestseller-Rang: Nr. 439.006 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Software Configuration Management Patterns: Effective Teamwork, Practical Integration: Effective Teamwork, Practical Integration (Software Patterns Series) (Englisch) Taschenbuch – 4. November 2002
Kunden, die diesen Artikel gekauft haben, kauften auch
Kunden, die diesen Artikel angesehen haben, haben auch angesehen
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Stereotypes portray software engineers as a reckless lot, and stereotypes paint software configuration management (SCM) devotees as inflexible. Based on these impressions, it is no wonder that projects can be riddled with tension! The truth probably lies somewhere in between these stereotypes, and this book shows how proven SCM practices can foster a healthy team-oriented culture that produces better software. The authors show that workflow, when properly managed, can avert delays, morale problems, and cost overruns. A patterns approach (proven solutions to recurring problems) is outlined so that SCM can be easily applied and successfully leveraged in small to medium sized organizations. The patterns are presented with an emphasis on practicality. The results speak for themselves: improved processes and a motivated workforce that synergize to produce better quality software.
Effective software configuration management (SCM) strategies promote a healthy, team-oriented culture that produces better software.Software Configuration Management Patterns alleviates software engineers' most common concerns about software configuration managementperceived rigidity and an overemphasis on process.
Through the use of patterns, the authors show that a properly managed workflow can avert delays, morale problems, and cost overruns. The patterns approach illustrates how SCM can be easily and successfully applied in small- to mid-size organizations. By learning how these patterns relate to each other, readers can avoid common mistakes that too often result in frustrated developers and reduced productivity.
Key coverage includes instruction on how to:
Software Configuration Management Patterns also includes a detailed list of SCM tools and thorough explanations of how they can be used to implement the patterns discussed in the book. These proven techniques will assist readers to improve their processes and motivate their workforce to collaborate in the production of higher quality software.
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
Will heißen: Um zu kapieren, was Versionsverwaltung an sich ist, braucht man das Buch nicht unbedingt - es ist sehr ehrenvoll, dass das aufgeschrieben wurde - aber die Patternform ist nicht zwingend notwendig um Grundlagen zu erklären. Und um zu verstehen, wie man heute in einem agilen Projekt einen Continuous Integration Server mit Build-Management und und uns aufbaut, reicht das Buch nicht mal annähernd aus. Hat auch zugegeben garnicht den Anspruch. Deckt wirklich nur die Aspekte ab, die in einem Subversion oder PVCS drin sind.
Wer sich für CI-Server interessiert, dem sei zum Beispiel Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation (Addison-Wesley Signature) empfohlen
Die hilfreichsten Kundenrezensionen auf Amazon.com
However, two things prevent me from giving this book a 5-star rating:
1) The authors focus almost exclusively on source code version control. There is much more to configuration management than version control
2) The book is rather dated. Perhaps a new edition is due with some updates and comments on, for example, distributed version control systems - a lot has certainly changed there and I would reckon the authors have positions about that
In short, a good introductory book. Check out Continuous Delivery and its bibliography for more in-depth coverage of the subject.
The format of the book is very consistent and thus very easy to read. Each pattern has its own chapter and clearly identifies the problem and the solution in a particular context. It doesn't waste any paper and is a quick read and has been a reference I continue to use on a regular basis. The authors have taken something that can quickly become complex and make it easy to understand.
The authors have a very natural writing style and effectively use sidebars to bring their real-world experiences to the pattern. This book is a must read for software developers. I wish I could give it six stars.
Given my background in CI, I was most drawn to the Mainline, Private Workspace, Repository, Private System Build, Integration Build, Regression Test, and Third Party Codeline patterns. But, there is something for all developers and teams here.
I rarely comment on the physical book but I need to mention the bad printing. Many pictures and graphs in the book are not printed correctly. Instead they appear as gray rectangles.
The book is divided into three parts: an introduction, the Software Configuration Management (SCM) patterns, and appendices with information on SCM systems.
The introduction does not provide useful information. The author spends time defining generic concepts (such as 'organization') without bringing any insights to configuration management. I assume that part was written to fill in the book. You can safely skip it.
The patterns are the meat of the book. Some of the patterns are useful and nicely presented. For example, the need for a mainline and how to branch before a release are the two that stand out. They are good advice. Unfortunately most patterns are not explained appropriately. For example, the author presents several patterns related to tests (unit tests, smoke tests, regression tests). However the patterns do not properly make the connection to configuration management. For example: what are the best practices to integrate tests with SCM? The answer is not in the book. Overall I felt let down by the patterns. If you have some experience working in a group using a SCM, you won't learn anything new.
The final part about the various SCM systems is again a filler with little usefulness. You will learn a lot more by reading the manual of the SCM you are using.
There are several topics I wish had been included:
- Topology: how best to distribute the SCM system.
- Buddy builds: what are the best practices related to buddy builds, i.e., building before making a check-in.
I was looking forward to reading this book. Now that I have, I feel very much let down. The useful information could be contained in less than 10 pages.