Software Measurement: Establish - Extract - Evaluate - ExecuteSpringer Science & Business Media, 2007. gada 25. jūl. - 561 lappuses Our world and our society are shaped and increasingly governed by software. Since software is so ubiquitous and embedded in nearly everything we are doing, we need to stay in control. We have to make sure that the systems and their software are running as we intend - or better. Software measurement is the discipline that assures that we stay in control. In this volume, Ebert and Dumke provide a comprehensive introduction to software measurement. They detail knowledge and experiences about software measurement in an easily understood, hands-on presentation. Brief references are embedded from world-renown experts such as Alain Abran, Luigi Buglione, Manfred Bundschuh, David N. Card, Ton Dekkers, Robert L. Glass, David A. Gustafson, Marek Leszak, Peter Liggesmeyer, Andreas Schmietendorf, Harry Sneed, Charles Symons, Ruediger Zarnekow and Horst Zuse. Many examples and case studies are provided from Global 100 companies such as Alcatel-Lucent, Atos Origin, Axa, Bosch, Deloitte, Deutsche Telekom, Shell, Siemens and Vector Consulting. This combination of methodologies and applications makes the book ideally suited for both professionals in the software industry and for scientists looking for benchmarks and experiences. Besides the many practical hints and checklists readers will also appreciate the large reference list, which includes links to metrics communities where project experiences are shared. Further information, continuously updated, can also be found on the Web site related to this book: http://metrics.cs.uni-magdeburg.de/. |
No grāmatas satura
1.5. rezultāts no 74.
... ................ 260 9.3.3 Identifying Error-Prone Components..................................... 262 9.3.4 Defect Predictions in Embedded Systems.............................. 268 9.4. Validation and Testing.............
... identifying and specifying objectives. They ensure we stay on course and eventually reach those objectives. They are used to estimate, predict, or forecast software characteristics in order to achieve and improve understanding leading ...
... identifying how the improvement should be done. Asking questions helps in clarifying how the objectives of step 1 will effectively (and efficiently) be reached. We should not leapfrog this intermediate step because it reveals whether we ...
... identified types or categories [Pand04]. The nominal scale and the typological scale are summarized to the linguistic scales. ordinal scale: ((A, ∙≥),(R, ≥), μ), where ∙≥ describes ranking properties interval scale: ((A × A ...
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Saturs
1 | |
17 | |
41 | |
4 Planning the Measurement Process | 73 |
5 Performing the Measurement Process | 91 |
6 Introducing a Measurement Program | 109 |
7 Estimation of Size Effort and Cost | 165 |
8 Project Management | 199 |
11 Improving Processes and Products | 329 |
12 Controlling for IT and Software | 435 |
13 Measurement Repositories | 471 |
14 Empirical Laws and Rules of Thumb | 487 |
15 Getting yet more Information | 498 |
Glossary | 511 |
Literature | 539 |
Index | 554 |
Citi izdevumi - Skatīt visu
Software Measurement: Establish - Extract - Evaluate - Execute Christof Ebert,Reiner Dumke Priekšskatījums nav pieejams - 2007 |
Software Measurement: Establish - Extract - Evaluate - Execute Christof Ebert,Reiner Dumke Priekšskatījums nav pieejams - 2010 |