Dare to be Excellent

Dare to be Excellent : Case Studies of Software Engineering Practices That Work

4 (1 rating by Goodreads)
By (author)  , By (author) 

Free delivery worldwide

Available. Dispatched from the UK in 3 business days
When will my order arrive?

Description

No matter what anyone says, you can build extraordinarily high-quality software - and this book shows you exactly how the world's best software development organizations are doing it. The best practices described in this book cover the entire software lifecycle. Each chapter describes a real-world problem, and how it was identified, addressed and fixed. Coverage includes project planning, metrics, inspections, software reliability; unit, system and acceptance testing; design and construction, release control, post-implementation reviews and more. This will be an invaluable resource for anyone involved in software development, including developers, testers and project managers.
show more

Product details

  • Paperback | 384 pages
  • 149.86 x 223.52 x 25.4mm | 566.99g
  • Prentice Hall
  • Upper Saddle River, United States
  • English
  • 0130811564
  • 9780130811561

Back cover copy

8115F-2

Best practices from the world's highest-quality software development organizations.



Contrary to popular wisdom, you can build extraordinarily high-quality software-and this book shows you exactly how the world's best development organizations do it. From Cisco to Intel, Texas Instruments to Tandem, Dare To Be Excellent gives you an exclusive tour of today's software quality best practices. Each chapter describes a real-world problem, and exactly how it was identified, addressed and fixed-in detail. Dare To Be Excellent covers virtually the entire software lifecycle, including:

Project planning, management and support Software requirements Software reliability and automated testing Release planning and metrics Software inspections Managing key client/vendor relationships Software Development Process Handbook

By now, software engineering practices don't need to be defined; they need to be applied. Dare To Be Excellent shows how real organizations have gotten past obstacles that trip up so many companies. Even better, it shows how to fit best practices to your situation, instead of the other way around. Whether you're a developer, manager, tester or executive, you'll find proven ideas you can actually use to build higher-quality software starting right now.
show more

Table of contents

1. REQUIREMENTS (Texas Instruments)


Company Profile. Basic Concepts of Requirements. Reasons To Implement. Elicitation And Analysis Of Di Business Requirements. Lessons Learned. Conclusions.



2. PROJECT PLANNING (Intel Corporation)


Company Profile. Intel Corporation's Landesk Products. Anti-Virus Products. Anti-Viral (AV)Technologies. Virus Protection Software. The Revival Plan. Cultural Issues. The Result-a New Generation of Award-Winning, Sustainable LDVP Products. Lessons Learned. Conclusions.



3. TECHNOLOGY PROJECT MANAGEMENT PROCESS


(PKS Information Services) Company Profile. Reasons to Implement. Company Philosophy. Technology Project Management Process. Culture Change. Implementation. Final Results. Lessons Learned. Conclusions. TPMP Sample.



4. PROJECT SUPPORT OFFICE (Royal Bank Financial Group)


Company Profile. Reasons To Implement. Culture Change. Project Office. Challenges. Customer Satisfaction. Conclusions.



5. INSPECTIONS AS AN AGENT OF CHANGE


(Primark Investment Management Services Limited) Company Profile. Reasons to Implement. Measures of Software Quality. What Do We Mean By Process? How Did We Get Started? Lessons Learned. Culture Change. Strategic Plans. Challenges. Conclusions.



6. SOFTWARE RELIABILITY ENGINEERING


(Digital Technology International) Company Profile. Basic Concepts and Goals of Software Reliability Engineering. Reasons To Implement. Solutions To the Problem. Culture Change. Project Plan/Time-Line. Implemention. Results. Lessons Learned. Conclusions.



7. RELEASE PLANNING (Cisco Systems)


Company Profile. Reasons To Implement. Release Process. Culture Change. Lessons Learned. Conclusions.



8. RELEASE METRICS (TANDEM Telecom Network Solutions)


Company Profile. Introduction. Reasons for Implementation. Obtaining Buy-In. Assessing Measurements. Description of the Rating. Calculating the Confidence Rating. Implementation. Release Management in Action. Results. Lessons Learned. Conclusions.



9. CREATION OF A SOFTWARE DEVELOPMENT PROCESS HANDBOOK


(Phoenix Technologies Limited) Company Profile. Why Phoenix Created a Process Handbook. Cultural Issues. Drafting the Software Development Handbook. Lessons Learned. Continuous Improvement. Conclusions.



10. MANAGING CLIENT/VENDOR RELATIONSHIPS


(International Business Systems) Company Profile. Reason To Implement. Description of Process. The Handoff. Approach. Cultural Change. Project Plan/Time-Line. Results. Lessons Learned. Conclusions. Acryonyms/Abbreviations. References.



Index.
show more

About Linda Hayes

Alka Jarvisis Head of the Software Quality Division at Cisco Systems, CA, and author of Inroads to Software Quality (Prentice Hall PTR, 1997). She is President of the Bay Area Quality Assurance Association and an Applied Total Quality Advisory Board Member for University of California-Berkeley Extension.

Linda Hayeshas over fifteen years' experience in software development, quality assurance, testing and all phases of delivery and services. She is founder and past CEO of two software companies, including AutoTester, Inc., an automated tool vendor. She is author of the Automated Testing Handbook and writes the monthly Quality Quest column for Datamation.
show more

Rating details

1 ratings
4 out of 5 stars
5 0% (0)
4 100% (1)
3 0% (0)
2 0% (0)
1 0% (0)
Book ratings by Goodreads
Goodreads is the world's largest site for readers with over 50 million reviews. We're featuring millions of their reader ratings on our book pages to help you find your new favourite book. Close X