國立虎尾科技大學 |

Automated defect prevention = best practices in software management /

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Automated defect prevention/ Dorota Huizinga, Adam Kolawa.
Reminder of title:	best practices in software management /
Author:	Huizinga, Dorota.
other author:	Kolawa, Adam.
Published:	Hoboken, N.J. :Wiley-Interscience : : c2007.,
Description:	1 online resource (xxvi, 426 p.) :ill. :
Subject:	Software failures - Prevention -
Online resource:	http://ieeexplore.ieee.org/servlet/opac?bknumber=5201515
ISBN:	9780470165171

Automated defect prevention = best practices in software management /
Huizinga, Dorota.

Automated defect preventionbest practices in software management /[electronic resource] :Dorota Huizinga, Adam Kolawa. - Hoboken, N.J. :Wiley-Interscience :c2007. - 1 online resource (xxvi, 426 p.) :ill.

Includes bibliographical references and index.

Preface. -- Features and Organization. -- Practice Descriptions. -- Intended audience. -- Acknowledgements. -- Permissions. -- Disclaimer. -- 1. The Case for Automated Defect Prevention. -- 1.1 What is ADP? -- 1.2 What are the goals of ADP? -- 1.2.1 People: Stimulated and Satisfied. -- 1.2.2 Product: High Quality. -- 1.2.3 Organization: Increased Productivity and Operational Efficiency. -- 1.2.4 Process: Controlled, Improved, and Sustainable. -- 1.2.5 Project: Managed through Informed Decision Making. -- 1.3 How is ASDP implemented? -- 1.3.1 Principles. -- 1.3.2 Practices. -- 1.3.3 Policies. -- 1.3.4 Defect Prevention Mindset. -- 1.3.5 Automation. -- 1.4 From the waterfall to modern software development process models. -- 1.5 Acronyms. -- 1.6 Glossary. -- 1.7 References. -- 1.8 Exercises. -- 2. Principles of Automated Defect Prevention. -- 2.1 Introduction. -- 2.2 Defect Prevention: Definition and Benefits. -- 2.3 Historical Perspective: Defect Analysis and Prevention in Auto Industry What Happened to Deming? -- 2.4 Principles of Automated Defect Prevention. -- 2.4.1 Principle 1: Establishment of Infrastructure: "Build a strong foundation through integration of people and technology". -- 2.4.2 Principle 2: Application of General Best Practices: "Learn from others mistakes". -- 2.4.3 Principle 3: Customization of Best Practices: "Learn from your own mistakes". -- 2.4.4 Principle 4: Measurement and Tracking of Project Status: "Understand the past and present to make decisions about the future". -- 2.4.5 Principle 5: Automation: "Let the computer do it". -- 2.4.6 Principle 6: Incremental Implementation of ADP s Practices and Policies. -- 2.5 Automated Defect Prevention based Software Development Process Model. -- 2.6 Examples. -- 2.6.1 Focus on Root Cause Analysis of a Defect. -- 2.6.2 Focus on Infrastructure. -- 2.6.3 Focus on Customized Best Practice. -- 2.6.4 Focus on Measurements of Project Status. -- 2.7 Acronyms. -- 2.8 Glossary. -- 2.9 References. -- 2.10 Exercises. -- 3. Initial Planning and Infrastructure. -- 3.1 Introduction. -- 3.2 Initial Software Development Plan. -- 3.2.1 Product. -- 3.2.2 People. -- 3.2.3 Technology. -- 3.2.4 Process. -- 3.3 Best Practices for Creating People Infrastructure. -- 3.3.1 Defining Groups. -- 3.3.2 Determining a Location for Each Group s Infrastructure. -- 3.3.3 Defining People Roles. -- 3.3.4 Establishing Training Program. -- 3.3.5 Cultivating a Positive Group Culture. -- 3.4 Best Practices for Creating Technology Infrastructure. -- 3.4.1 Automated Reporting System. -- 3.4.2 Policy for Use of Automated Reporting System. -- 3.4.3 Minimum Technology Infrastructure. -- 3.4.4 Intermediate Technology Infrastructure. -- 3.4.5 Expanded Technology Infrastructure. -- 3.5 Integrating People and Technology. -- 3.6 Human Factors and Concerns. -- 3.7 Examples. -- 3.7.1 Focus on Developer Ideas. -- 3.7.2 Focus on Reports Generated by the Minimum Infrastructure. -- 3.8 Acronyms. -- 3.9 Glossary. -- 3.10 References. -- 3.

This book describes an approach to software management based on establishing an infrastructure that serves as the foundation for the project. This infrastructure defines people roles, necessary technology, and interactions between people and technology. T.

ISBN: 9780470165171

Standard No.: 10.1002/9780470165171doi

Source: 10.1002/9780470165171Wiley InterSciencehttp://www3.interscience.wiley.com

UkSubjects--Topical Terms:

827564
Software failures
--PreventionIndex Terms--Genre/Form:

554714
Electronic books.

LC Class. No.: QA76.76.F34 / H85 2007eb

Dewey Class. No.: 005

Automated defect prevention = best practices in software management /
LDR:04930cam 2200445Ia 4500 001 700539
003 OCoLC
005 20121225141831.0
006 m o d
007 cr cn|
008 130624s2007 njua ob 001 0 eng d
016 7 $z 013755940 $2 Uk
019 $a 181086546 $a 647763223 $a 761392231
020 $a 9780470165171
020 $a 0470165170
020 $a 9780470165164 (electronic bk.)
020 $a 0470165162 (electronic bk.)
020 $z 9780470042120 (cloth)
020 $z 0470042125 (cloth)
024 7 $a 10.1002/9780470165171 $2 doi
035 $a (OCoLC)181349072 $z (OCoLC)181086546 $z (OCoLC)647763223 $z (OCoLC)761392231
035 $a ocn181349072
037 $a 10.1002/9780470165171 $b Wiley InterScience $n http://www3.interscience.wiley.com
040 $a DG1 $b eng $c DG1 $d OCLCQ $d DG1 $d IDEBK $d OCLCQ $d N$T $d YDXCP $d E7B $d OCLCQ $d IEEEE $d OCLCQ $d REDDC $d OCLCQ $d MERUC $d OCLCQ
049 $a HISA
050 4 $a QA76.76.F34 $b H85 2007eb
072 7 $a REF $x 000000 $2 bisacsh
082 0 4 $a 005 $2 22
100 1 $a Huizinga, Dorota. $3 827563
245 1 0 $a Automated defect prevention $h [electronic resource] : $b best practices in software management / $c Dorota Huizinga, Adam Kolawa.
260 $a Hoboken, N.J. : $b Wiley-Interscience : $b IEEE Computer Society, $c c2007.
300 $a 1 online resource (xxvi, 426 p.) : $b ill.
504 $a Includes bibliographical references and index.
505 0 $a Preface. -- Features and Organization. -- Practice Descriptions. -- Intended audience. -- Acknowledgements. -- Permissions. -- Disclaimer. -- 1. The Case for Automated Defect Prevention. -- 1.1 What is ADP? -- 1.2 What are the goals of ADP? -- 1.2.1 People: Stimulated and Satisfied. -- 1.2.2 Product: High Quality. -- 1.2.3 Organization: Increased Productivity and Operational Efficiency. -- 1.2.4 Process: Controlled, Improved, and Sustainable. -- 1.2.5 Project: Managed through Informed Decision Making. -- 1.3 How is ASDP implemented? -- 1.3.1 Principles. -- 1.3.2 Practices. -- 1.3.3 Policies. -- 1.3.4 Defect Prevention Mindset. -- 1.3.5 Automation. -- 1.4 From the waterfall to modern software development process models. -- 1.5 Acronyms. -- 1.6 Glossary. -- 1.7 References. -- 1.8 Exercises. -- 2. Principles of Automated Defect Prevention. -- 2.1 Introduction. -- 2.2 Defect Prevention: Definition and Benefits. -- 2.3 Historical Perspective: Defect Analysis and Prevention in Auto Industry What Happened to Deming? -- 2.4 Principles of Automated Defect Prevention. -- 2.4.1 Principle 1: Establishment of Infrastructure: "Build a strong foundation through integration of people and technology". -- 2.4.2 Principle 2: Application of General Best Practices: "Learn from others mistakes". -- 2.4.3 Principle 3: Customization of Best Practices: "Learn from your own mistakes". -- 2.4.4 Principle 4: Measurement and Tracking of Project Status: "Understand the past and present to make decisions about the future". -- 2.4.5 Principle 5: Automation: "Let the computer do it". -- 2.4.6 Principle 6: Incremental Implementation of ADP s Practices and Policies. -- 2.5 Automated Defect Prevention based Software Development Process Model. -- 2.6 Examples. -- 2.6.1 Focus on Root Cause Analysis of a Defect. -- 2.6.2 Focus on Infrastructure. -- 2.6.3 Focus on Customized Best Practice. -- 2.6.4 Focus on Measurements of Project Status. -- 2.7 Acronyms. -- 2.8 Glossary. -- 2.9 References. -- 2.10 Exercises. -- 3. Initial Planning and Infrastructure. -- 3.1 Introduction. -- 3.2 Initial Software Development Plan. -- 3.2.1 Product. -- 3.2.2 People. -- 3.2.3 Technology. -- 3.2.4 Process. -- 3.3 Best Practices for Creating People Infrastructure. -- 3.3.1 Defining Groups. -- 3.3.2 Determining a Location for Each Group s Infrastructure. -- 3.3.3 Defining People Roles. -- 3.3.4 Establishing Training Program. -- 3.3.5 Cultivating a Positive Group Culture. -- 3.4 Best Practices for Creating Technology Infrastructure. -- 3.4.1 Automated Reporting System. -- 3.4.2 Policy for Use of Automated Reporting System. -- 3.4.3 Minimum Technology Infrastructure. -- 3.4.4 Intermediate Technology Infrastructure. -- 3.4.5 Expanded Technology Infrastructure. -- 3.5 Integrating People and Technology. -- 3.6 Human Factors and Concerns. -- 3.7 Examples. -- 3.7.1 Focus on Developer Ideas. -- 3.7.2 Focus on Reports Generated by the Minimum Infrastructure. -- 3.8 Acronyms. -- 3.9 Glossary. -- 3.10 References. -- 3.
520 $a This book describes an approach to software management based on establishing an infrastructure that serves as the foundation for the project. This infrastructure defines people roles, necessary technology, and interactions between people and technology. T.
588 $a Description based on print version record.
650 0 $a Software failures $x Prevention $x Data processing. $3 827564
650 0 $a Software maintenance $x Data processing. $3 827565
650 0 $a Debugging in computer science $x Automatic control. $3 827566
650 0 $a Computer programs $x Testing $x Data processing. $3 827567
650 0 $a Computer programs $x Correctness. $3 827568
650 7 $a REFERENCE $x General. $2 bisacsh $3 810841
650 0 7 $a Debugging. $2 swd $3 827569
650 0 7 $a Softwarewartung. $2 swd $3 827570
655 4 $a Electronic books. $2 local $3 554714
700 1 $a Kolawa, Adam. $3 791774
710 2 $a Wiley InterScience (Online service) $3 772722
856 4 0 $3 IEEE Xplore $u http://ieeexplore.ieee.org/servlet/opac?bknumber=5201515
938 $a Ingram Digital eBook Collection $b IDEB $n 103229
938 $a YBP Library Services $b YANK $n 2740728
938 $a ebrary $b EBRY $n ebr10296302
938 $a EBSCOhost $b EBSC $n 208836
994 $a 92 $b TWHIS