- Watches
- Home and Garden
- UK Electronics
- UK Books
- Health and Personal Care
- UK Sporting Goods
- Clothing, Shoes and Accessories
- Electronics, Gadgets and Computers
- CDs and Music Downloads
- UK Software and Video Games
- UK Toys and Games
- UK Home and Garden
- UK Video Games
- UK Baby Clothes and Accessories
- Books On
- German Electronics
Books : Computers & Internet : Programming : Software Design, Testing & Engineering : Quality Control
-
For any software developer who has spent days in “integration hell,” cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques.
The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility.
The book covers
- How to make integration a “non-event” on your software development projects
- How to reduce the amount of repetitive processes you perform when building your software
- Practices and techniques for using CI effectively with your teams
- Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software
- Assessments of different CI servers and related tools on the market
The book’s companion Web site, www.integratebutton.com, provides updates and code examples.
-
The first book to cover Agile Modeling, a new modeling technique created specifically for XP projects eXtreme Programming (XP) has created a buzz in the software development community-much like Design Patterns did several years ago. Although XP presents a methodology for faster software development, many developers find that XP does not allow for modeling time, which is critical to ensure that a project meets its proposed requirements. They have also found that standard modeling techniques that use the Unified Modeling Language (UML) often do not work with this methodology. In this innovative book, Software Development columnist Scott Ambler presents Agile Modeling (AM)-a technique that he created for modeling XP projects using pieces of the UML and Rational's Unified Process (RUP). Ambler clearly explains AM, and shows readers how to incorporate AM, UML, and RUP into their development projects with the help of numerous case studies integrated throughout the book.
-
When software development teams move to agile methods, experienced project managers often struggle—doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not “command and control.”
The authors begin by explaining how agile works: how it differs from traditional “plan-driven” methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute’s classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile--covering the emotional challenges, personal values, and key leadership traits you’ll need to succeed.
Coverage includes
- Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences
- Understanding the role and value of agile techniques such as iteration/release planning and retrospectives
- Using agile techniques to systematically and continually reduce risk
- Implementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvement
- Learning to trust your teams and listen for their discoveries
- Procuring, purchasing, and contracting for software in agile, collaborative environments
- Avoiding the common mistakes software teams make in transitioning to agile
- Coordinating with project management offices and non-agile teams
- “Selling” agile within your teams and throughout your organization
For every project manager who wants to become more agile.
Part I An Agile Overview 7
Chapter 1 What is "Agile"? 9
Chapter 2 Mapping from the PMBOKR Guide to Agile 25
Chapter 3 The Agile Project Lifecycle in Detail 37
Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49
Chapter 4 Integration Management 51
Chapter 5 Scope Management 67
Chapter 6 Time Management 83
Chapter 7 Cost Management 111
Chapter 8 Quality Management 129
Chapter 9 Human Resources Management 143
Chapter 10 Communications Management 159
Chapter 11 Risk Management 177
Chapter 12 Procurement Management 197
Part III Crossing the Bridge to Agile 215
Chapter 13 How Will My Responsibilities Change? 217
Chapter 14 How Will I Work with Other Teams Who Aren't Agile? 233
Chapter 15 How Can a Project Management Office Support Agile? 249
Chapter 16 Selling the Benefits of Agile 265
Chapter 17 Common Mistakes 285
Appendix A Agile Methodologies 295
Appendix B Agile Artifacts 301
Glossary 321
Bibliography 327
Index 333
-
-
“The clarity of David’s argument and the strength of his conviction are truly inspiring. If you don’t believe the world of software affects the world in which you live, you owe it to yourself to read this book.”
–Lenny Zeltzer, SANS Institute faculty member and the New York Security Consulting Manager at Savvis, Inc.“Geekonomics stays with you long after you finish reading the book. You will reconsider every assumption you have had about software costs and benefits.”
–Slava Frid, Gemini Systems, CTO, Resilience Technology Solutions“Information Security is an issue that concerns governments, companies and, increasingly, citizens. Are the computer systems and software to which we entrust our sensitive and critical information, technologies that are out of control? David Rice has written an important and welcome book that goes to the heart of this issue, and points to solutions that society as a whole needs to debate and embrace.”
–Nick Bleech, IT Security Director, Rolls-Royce“If you are dependent upon software (and of course, all of us in the modern world are) this book is a fabulous discussion of how and why we should worry.”
–Becky BaceThe Real Cost of Insecure Software
• In 1996, software defects in a Boeing 757 caused a crash that killed 70 people…
• In 2003, a software vulnerability helped cause the largest U.S. power outage in decades…
• In 2004, known software weaknesses let a hacker invade T-Mobile, capturing everything from passwords to Paris Hilton’s photos…
• In 2005, 23,900 Toyota Priuses were recalled for software errors that could cause the cars to shut down at highway speeds…
• In 2006 dubbed “The Year of Cybercrime,” 7,000 software vulnerabilities were discovered that hackers could use to access private information…
• In 2007, operatives in two nations brazenly exploited software vulnerabilities to cripple the infrastructure and steal trade secrets from other sovereign nations…
Software has become crucial to the very survival of civilization. But badly written, insecure software is hurting people–and costing businesses and individuals billions of dollars every year. This must change. In Geekonomics, David Rice shows how we can change it.
Rice reveals why the software industry is rewarded for carelessness, and how we can revamp the industry’s incentives to get the reliability and security we desperately need and deserve. You’ll discover why the software industry still has shockingly little accountability–and what we must do to fix that.
Brilliantly written, utterly compelling, and thoroughly realistic, Geekonomics is a long-overdue call to arms. Whether you’re software user, decision maker, employee, or business owner this book will change your life…or even save it.
The Alarming Cost of Insecure, Badly Written Software...
and How to Finally Fix the Problem, Once and for All!
Six billion crash test dummies: why you’re at greater risk than you ever imagined.
You pay the price: why consumers are legally and financially responsible for the mistakes of software manufacturers.
Broken windows: how software promotes epidemic cyber crime and threatens national security.
Who runs the show?: Why software manufacturers fought against the U.S. Food and Drug Administration’s attempts to protect the U.S. blood supply.
Protecting national infrastructure: real incentives for transforming software manufacturing.
Surviving the information superhighway: practical, must-read advice in a world of insecure code.
Preface xiii
Acknowledgments xix
About the Author xx
Chapter 1: The Foundation of Civilization 1
Chapter 2: Six Billion Crash Test Dummies: Irrational Innovation and Perverse Incentives 19
Chapter 3: The Power of Weaknesses: Broken Windows and National Security 73
Chapter 4: Myopic Oversight: Blinded by Speed, Baffled by Churn 131
Chapter 5: Absolute Immunity: You Couldn’t Sue Us Even If You Wanted To 179
Chapter 6: Open Source Software: Free, But at What Cost? 243
Chapter 7: Moving Forward: Rational Incentives for a Different Future 273
Epilogue 321
Notes 325
Index 341
-
Though many books discuss software quality, this is the first book to integrate metrics with models and quality improvement strategies, and action plans with project experiences. Covering essential issues and techniques, Kan provides all the information needed to measure and improve the quality of the entire software development process from high-level to low-level design, and all phases of reliability.
-
Effectively forecast, manage, and control software across the entire project lifecycle
Accurately size, estimate, and administer software projects with real-world guidance from an industry expert. Fully updated to cover the latest tools and techniques, Applied Software Measurement, Third Edition details how to deploy a cost-effective and pragmatic analysis strategy. You will learn how to use function points and baselines, implement benchmarks and tracking systems, and perform efficiency tests. Full coverage of the latest regulations, metrics, and standards is included.
- Measure performance at the requirements, coding, testing, and installation phases
- Set function points for efficiency, cost, market share, and customer satisfaction
- Analyze quality and productivity using assessments, benchmarks, and baselines
- Design and manage project cost, defect, and quality tracking systems
- Use object-oriented, reusable component, Agile, CMM, and XP methods
- Assess defect removal efficiency using unit tests and multistage test suites
-
Imagine a group of prehistoric hunters armed with stone-tipped spears. Their primitive weapons made hunting large animals, such as mammoths, dangerous work. Over time, however, a new breed of hunters developed. They would stretch the skin of a previously killed mammoth on the wall and throw their spears, while observing which spear, thrown from which angle and distance, penetrated the skin the best. The data gathered helped them make better spears and develop better hunting strategies. Quality data is the key to any advancement, whether it is from the Stone Age to the Bronze Age. Or from the Information Age to whatever Age comes next. The success of corporations and government institutions largely depends on the efficiency with which they can collect, organize, and utilize data about products, customers, competitors, and employees. Fortunately, improving your data quality does not have to be such a mammoth task. DATA QUALITY ASSESSMENT is a must read for anyone who needs to understand, correct, or prevent data quality issues in their organization. Skipping theory and focusing purely on what is practical and what works, this text contains a proven approach to identifying, warehousing, and analyzing data errors. Master techniques in data profiling and gathering metadata, designing data quality rules, organizing rule and error catalogues, and constructing the dimensional data quality scorecard. David Wells, Director of Education of the Data Warehousing Institute, says "This is one of those books that marks a milestone in the evolution of a discipline. Arkady's insights and techniques fuel the transition of data quality management from art to science -- from crafting to engineering. From deep experience, with thoughtful structure, and with engaging style Arkady brings the discipline of data quality to practitioners."
-
This practical, hands-on guide captures, categorizes, and builds a process of best practices to avoid creating defects during the development process—rather than fixing them after extensive analysis. While there are various proprietary and competing standards for reducing software defects, these methods suffer from issues surrounding timeliness, effectiveness, or cost. What’s more, many other books focus on fixing errors after they’ve been introduced. This guide, however, presents practical methods for reducing defect introduction through prevention and immediate detection and by moving the detection of defects closer to their introduction. Written by experts with over a century of software development experience among them, this book is not an idealized academic book. Instead, it distills many hard-won lessons into a single, workable lifecycle process that will help deliver better quality software.
-
A reorganized and comprehensive major revision of a classic book, this edition provides a bridge between introductory digital communications and more advanced treatment of information theory. Completely updated to cover the latest developments, it presents state-of-the-art error control techniques. Coverage of the fundamentals of coding and the applications of codes to the design of real error control systems. Contains the most recent developments of coded modulation, trellises for codes, soft-decision decoding algorithms, turbo coding for reliable data transmission and other areas. There are two new chapters on Reed-Solomon codes & concatenated coding schemes. Also contains hundreds of new and revised examples; and more than 200 illustrations of code structures, encoding and decoding circuits and error performance of many important codes and error control coding systems. Appropriate for those with minimum mathematical background as a comprehensive reference for coding theory.
-
Get an inside look at how one of Microsoft's Engineering Excellence directors drives discussions about coding best practices. The popular column, I. M. Wright's "Hard Code," was written by Eric Brechner's alter-ego to help stimulate discussion among development engineers at Microsoft--a proven-effective idea. Deliberately provocative, ideas have been debated and pondered by thousands within Microsoft and have increasingly drawn attention from others in the industry. With this book, these essays are now available to any developer. They are thematically arranged, each helping to spark the imagination, stimulate discussion, and promote debate about software development tasks and processes. They encourage developers to reexamine coding, testing, and software-development project-management practices--and gain insight into their own processes to help drive excellence in large, distributed business groups.
-
The practical handbook of software project management by practitioners, for practitioners! Endorsed by the Software Quality Institute (SQI), teaching skills you can use right now to drive maximum business value in any project-large or small. Softcover.
-
Today, companies capture and store tremendous amounts of information about every aspect of their business: their customers, partners, vendors, markets, and more. But with the rise in the quantity of information has come a corresponding decrease in its quality--a problem businesses recognize and are working feverishly to solve.
Enterprise Knowledge Management: The Data Quality Approach presents an easily adaptable methodology for defining, measuring, and improving data quality. Author David Loshin begins by presenting an economic framework for understanding the value of data quality, then proceeds to outline data quality rules and domain-and mapping-based approaches to consolidating enterprise knowledge. Written for both a managerial and a technical audience, this book will be indispensable to the growing number of companies committed to wresting every possible advantage from their vast stores of business information.
Key Features
* Expert advice from a highly successful data quality consultant
* The only book on data quality offering the business acumen to appeal to managers and the technical expertise to appeal to IT professionals
* Details the high costs of bad data and the options available to companies that want to transform mere data into true enterprise knowledge
* Presents conceptual and practical information complementing companies' interest in data warehousing, data mining, and knowledge discovery
-
Provides 16 of the world's leading SQA experts sharing their practical experience with the full range of techniques available for managing software quality. DLC: Computer software Quality control.
-
Software engineers and system developers need to understand the issues and develop the skills required to prevent destructive accidents before they occur. This book examines what is currently known about building safe electromechanical systems and looks at past accidents to see what lessons can be applied to new computer-controlled systems.
-
In this first volume of the Quality Software Management series, Gerald M. Weinberg tackles the first requirement for developing quality software: learning to think correctly -- about problems, solutions, and quality itself.Guidelines on management are introduced to stimulate the kind of thinking needed.
-
Explains specifically how quality characteristics of software products and processes can be quantified, plotted, and analyzed so the performance of software development activities can be predicted, controlled, and guided to achieve both business and technical goals. DLC: Software measurement.
-
To produce high-quality software, we need high-quality, effective managers. Becoming such a manager is the subject of this third stand-alone volume in Gerald Weinberg's highly acclaimed series.To be effective, managers must act congruently. That is, managers must not only understand the concepts of good software engineering, but also practice them, which sounds easier than it is in practice. Standing in the way is a lot of emotional baggage that we all carry, the author asserts, and congruence is the way to cope with our emotional baggage.
Congruence has the sense of "fitting" -- in this case simultaneously fitting your own needs, the needs of the other people involved, and the contextual needs (in business, for example, the business needs). Examples, diagrams, and tools such as the Myers-Briggs indicator fortify the author's recommendations.
-
-
Change is inherently dangerous. Moreover, change becomes even more dangerous when we don't know what we're doing. Attempts to change software organizations commonly fail because of inadequate understanding of change dynamics -- the same reason the organizations got into crisis in the first place.Jerry Weinberg concludes his series of four stand-alone volumes with this pragmatic, comprehensive testament on the fundamentals of change management.
From systems thinking to project management to technology transfer to the interaction of culture and process, this volume analyzes change from a broad range of perspectives, spanning the spectrum of sources of organizational change. Such breadth of awareness is essential for successful management of system evolution.
-
How can one be assured that computer codes that solve differential equations are correct? Standard practice using benchmark testing no longer provides full coverage because today's production codes solve more complex equations using more powerful algorithms. By verifying the order-of-accuracy of the numerical algorithm implemented in the code, one can detect most any coding mistake that would prevent correct solutions from being computed. Verification of Computer Codes in Computational Science and Engineering sets forth a powerful alternative called OVMSP: Order-Verification via the Manufactured Solution Procedure. This procedure has two primary components: using the Method of Manufactured Exact Solutions to create analytic solutions to the fully-general differential equations solved by the code and using grid convergence studies to confirm the order-of-accuracy. The authors present a step-by-step procedural guide to OVMSP implementation and demonstrate its effectiveness.Properly implemented, OVMSP offers an exciting opportunity to identify virtually all coding 'bugs' that prevent correct solution of the governing partial differential equations. Verification of Computer Codes in Computational Science and Engineering shows you how this can be done. The treatment is clear, concise, and suitable both for developers of production quality simulation software and as a reference for computational science and engineering professionals.