Dare to be Excellent
Case Studies of Software Engineering Practices That Work
Published on 16. December 1998
Book
Paperback/Softback
384 pages
978-0-13-081156-1 (ISBN)
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.KEY TOPICS:The best practices described in this book cover the entire lifecycle. Each chapter describes a real-world problem, and how it was identified, addressed and fixed by one of the world's best software development organizations. Coverage includes project planning, metrics, inspections, software reliability; unit, system and acceptance testing; design and construction, release control, post-implementation reviews and more.MARKET:Anyone involved in software development, including developers, testers and project managers.
More details
Language
English
Place of publication
Upper Saddle River
United States
Publishing group
Pearson Education (US)
Target group
College/higher education
Dimensions
Height: 150 mm
Width: 225 mm
Thickness: 23 mm
Weight
481 gr
ISBN-13
978-0-13-081156-1 (9780130811561)
Copyright in bibliographic data and cover images is held by Nielsen Book Services Limited or by the publishers or by their respective licensors: all rights reserved.
Schweitzer Classification
Persons
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.
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.
Content
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.
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.