Antipatterns And Patterns In Software Configuration Management

Introduction to patterns and antipatterns. The nature of a patterns: a brief tutorial. The lost disciplines: a system engineering perspective. The father of all management antipatterns. software engineering antipatterns and patterns. Software configuration management pattern and antipatterns. Management and process patterns and antipatterns. Requirements and testing patterns and antipatterns. Conclusions and resources.

Everything you need to anticipate and avoid the major pitfalls of project management-and ensure success! AntiPatterns in Project Management From the authors of the bestselling series on AntiPatterns come twenty new proven and practical solutions for successfully managing your software development project. in their familiar and entertaining style, the authors explore every phase of software development and identify the complex interaction of people, technology, and process issues that can cause a software development project to fail. With their pull-no-punches approach to project management, you'll learn how to balance these issues and ensure software development success. This book arms you with: * 6 People AntiPatterns that provide proven solutions to the people problems that occur within software development projects * 6 Technology AntiPatterns that help you deal with poor architectures and designs, and unstable technologies * 6 Processes AntiPatterns that help you uncover and correct the bad processes that ultimately cause a project to fail * The Standards AntiPattern that covers how to avoid the pitfalls and gain the benefits of adopting software development standards * The Collision AntiPattern that helps you successfully identify and eliminate multiple AntiPatterns that plague software development projects across different life-cycle phases, involving the disciplines of project management, software configuration management, and software development

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.

WhiletheSCM-10experimentprovedverysuccessful, theSCMcommunity feltthatitshouldgoforaformalworkshoponceagain. Infact, thiswouldopen uptheopportunitytodocumentcurrentresearchandfertilizethedevelopment ofthisdiscipline. Asaconsequence, thefollow-upworkshopSCM-11washeld as a co-located event with ICSE at Portland, Oregon in May 2003. The Call forPapersreceivedalivelyresponsewith36submissions, outofwhich15were acceptedforpublication(12longand3shortpapers). Thesepapersappearinthe secondpartofthisvolume, orderedbytopic. Inadditiontopaperpresentations, theworkshopprovidedsu?cienttimeforinspiringdiscussions. Thechairsofbothworkshopswouldliketoacknowledgetheinvaluablec- tributionsofallauthorsandspeakers, theprogramcommittees, theorganizers oftheICSEconferences, andSpringer-Verlag.

SCM practices are recognised as core functional areas in assisting a project team to identify, control, audit, and report on all configuration items of a project. Consequently they are then better able to control changes to the working environment. Moreira presents a totally unique book, offering a “how-to” guide for SCM implementation for commercial and technology fields. A thoroughly practical approach; this guide includes examples and instruction of SCM tasks. This book has an easy to follow set of tasks that can be customized to assist a SCM professional in implementing SCM in a more efficient and expedient manner while also imparting SCM knowledge. Provides a customisable step-by-step process in implementing SCM Discusses typical SCM activities at project level and includes source control, change control, problem management, etc. An accompanying website contains templates, procedures and other materials to aid understanding and encourage the practical applications of the material discussed throughout www.wiley.com/go/moreira_software/ Anyone who has to implement SCM in his/her company at every level will need this book and find its practical approach useful

Despite its negative sounding name, the positive benefits of AntiPatterns are enormous. This book discusses what AntiPatterns are and then provides practical guidelines on how to detect AntiPatterns and the refactored solutions that correct them. The authors discuss over 40 different AntiPatterns in the areas of software development, architecture, and project management.

An effective systems development and design process is far easier to explain than it is to implement. A framework is needed that organizes the life cycle activities that form the process. This framework is Configuration Management (CM). Software Configuration Management discusses the framework from a standards viewpoint, using the original

Do you have a nagging feeling that your monitoring needs improvement, but you just aren’t sure where to start or how to do it? Are you plagued by constant, meaningless alerts? Does your monitoring system routinely miss real problems? This is the book for you. Mike Julian lays out a practical approach to designing and implementing effective monitoring—from your enterprise application down to the hardware in a datacenter, and everything between. Practical Monitoring provides you with straightforward strategies and tactics for designing and implementing a strong monitoring foundation for your company. This book takes a unique vendor-neutral approach to monitoring. Rather than discuss how to implement specific tools, Mike teaches the principles and underlying mechanics behind monitoring so you can implement the lessons in any tool. Practical Monitoring covers essential topics including: Monitoring antipatterns Principles of monitoring design How to build an effective on-call rotation Getting metrics and logs out of your application

Software development has been a troubling since it first started. There are seven chronic problems that have plagued it from the beginning: Incomplete and ambiguous user requirements that grow by >2% per month. Major cost and schedule overruns for large applications > 35% higher than planned. Low defect removal efficiency (DRE) Cancelled projects that are not completed: > 30% above 10,000 function points. Poor quality and low reliability after the software is delivered: > 5 bugs per FP. Breach of contract litigation against software outsource vendors. Expensive maintenance and enhancement costs after delivery. These are endemic problems for software executives, software engineers and software customers but they are not insurmountable. In Software Development Patterns and Antipatterns, software engineering and metrics pioneer Capers Jones presents technical solutions for all seven. The solutions involve moving from harmful patterns of software development to effective patterns of software development. The first section of the book examines common software development problems that have been observed in many companies and government agencies. The data on the problems comes from consulting studies, breach of contract lawsuits, and the literature on major software failures. This section considers the factors involved with cost overruns, schedule delays, canceled projects, poor quality, and expensive maintenance after deployment. The second section shows patterns that lead to software success. The data comes from actual companies. The section’s first chapter on Corporate Software Risk Reduction in a Fortune 500 company was based on a major telecom company whose CEO was troubled by repeated software failures. The other chapters in this section deal with methods of achieving excellence, as well as measures that can prove excellence to C-level executives, and with continuing excellence through the maintenance cycle as well as for software development.