|
|
|
|
| LEADER |
00000cam a2200000Ii 4500 |
| 001 |
OR_ocn968130168 |
| 003 |
OCoLC |
| 005 |
20231017213018.0 |
| 006 |
m o d |
| 007 |
cr unu|||||||| |
| 008 |
170110s2016 caua o 001 0 eng d |
| 040 |
|
|
|a UMI
|b eng
|e rda
|e pn
|c UMI
|d OCLCF
|d OCLCQ
|d YDX
|d VT2
|d UOK
|d CEF
|d KSU
|d DEBBG
|d WYU
|d C6I
|d UAB
|d UKAHL
|d OCLCO
|d OCLCQ
|
| 020 |
|
|
|z 9781491951774
|
| 020 |
|
|
|a 9781491951781
|
| 020 |
|
|
|a 1491951788
|
| 020 |
|
|
|a 149195177X
|
| 020 |
|
|
|a 9781491951774
|
| 029 |
1 |
|
|a GBVCP
|b 897166817
|
| 035 |
|
|
|a (OCoLC)968130168
|
| 037 |
|
|
|a CL0500000814
|b Safari Books Online
|
| 050 |
|
4 |
|a HD66
|
| 082 |
0 |
4 |
|a 658.4/022
|2 23
|
| 049 |
|
|
|a UAMI
|
| 100 |
1 |
|
|a Visser, Joost,
|e author.
|
| 245 |
1 |
0 |
|a Building software teams :
|b ten best practices for effective software development /
|c Joost Visser.
|
| 264 |
|
1 |
|a Sebastopol, CA :
|b O'Reilly Media,
|c 2016.
|
| 300 |
|
|
|a 1 online resource (1 volume) :
|b illustrations
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 588 |
|
|
|a Description based on online resource; title from title page (viewed January 9, 2017).
|
| 500 |
|
|
|a Includes index.
|
| 505 |
0 |
|
|a Copyright; Table of Contents; About the Authors; Preface; The Topic of This Book; Why You Should Read This Book; Who Should Read This Book; What You Need to Know to Read This Book; What This Book Is Not; About the Software Improvement Group (SIG); Related Books; Conventions Used in This Book; O'Reilly Safari; How to Contact Us; Acknowledgments; Chapter 1. Introduction; 1.1 Software Development as an Observable Process; 1.2 Software Quality According to the ISO 25010 Standard; Software Product Quality in ISO 25010; 1.3 The Contribution of Each Developer Matters.
|
| 505 |
8 |
|
|a 1.4 Measuring and Benchmarking Development Process Maturity1.5 The Goal-Question-Metric Approach; 1.6 An Overview of the Development Best Practices in This Book; Chapter 2. Derive Metrics from Your Measurement€Goals; 2.1 Motivation; 2.2 How to Apply the Best Practice; Goal; Question; Metric; 2.3 Make Assumptions about Your Metrics Explicit; Find Explanations Instead of Judgments When Metrics Deviate from Expectations; Using Norms with the GQM Approach; 2.4 Common Objections to GQM; Objection: Yes, Good Metric, but We Cannot Measure This; Chapter 3. Make Definition of Done Explicit.
|
| 505 |
8 |
|
|a 3.1 MotivationWith a DoD You Can Track Progress and Prove Success; A DoD Focuses on Software Quality; 3.2 How to Apply the Best Practice; 3.3 Common Objections to Using Definition of Done; Objection: DoD Is Too Much Overhead; Objection: DoD Makes the Team Feel Less Responsible; Objection: With DoD There Is No Room for Technical Maintenance; Objection: Changing the DoD May Mean Extra Work; Chapter 4. Control Code Versions and Development€Branches; 4.1 Motivation; Tracking Changes; Version Control Allows Independent Modification; Version Control Allows Automatic Merging of Versions.
|
| 505 |
8 |
|
|a 4.2 How to Apply the Best PracticeCommit Specifically and Regularly; Integrate Your Code Regularly; 4.3 Controlling Versions in Practice; 4.4 Common Objections to Version Control Metrics; Objection: We Use Different Version Control Systems; Objection: Measuring the Recommendations Is Unfeasible (for Example, Whether Commits Are Specific); 4.5 Metrics Overview; Chapter 5. Control Development, Test, Acceptance, and Production Environments; 5.1 Motivation; Controlled DTAP Clarifies Responsibilities Between Development Phases; Controlled DTAP Allows for Good Predictions.
|
| 505 |
8 |
|
|a Controlled DTAP Reveals Development Bottlenecks and Explains Problems More EasilyControlled DTAP Reduces Dependence on Key Personnel; 5.2 How to Apply the Best Practice; 5.3 Measuring the DTAP Street in Practice; 5.4 Common Objections to DTAP Control Metrics; Objection: A Controlled DTAP Street Is Slow; Objection: There Is No Need to Distinguish Test and Acceptance Environments; 5.5 Metrics Overview; Chapter 6. Automate Tests; 6.1 Motivation; Automated Testing Finds Root Causes of Bugs Earlier with Little Effort; Automated Testing Reduces the Number of Bugs; 6.2 How to Apply the Best Practice.
|
| 590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
| 650 |
|
0 |
|a Teams in the workplace.
|
| 650 |
|
0 |
|a Computer software
|x Development.
|
| 650 |
|
6 |
|a Équipes de travail.
|
| 650 |
|
7 |
|a Computer software
|x Development.
|2 fast
|0 (OCoLC)fst00872537
|
| 650 |
|
7 |
|a Teams in the workplace.
|2 fast
|0 (OCoLC)fst01144679
|
| 776 |
0 |
8 |
|i Print version:
|a Visser, Joost.
|t Building software teams : ten best practices for effective software development.
|d Sebastopol, California : O'Reilly Media, 2016, c2017
|z 9781491951774
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781491951781/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
| 938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH32258086
|
| 938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH32217808
|
| 938 |
|
|
|a YBP Library Services
|b YANK
|n 13305521
|
| 994 |
|
|
|a 92
|b IZTAP
|
