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 80.
... 141 6.5.7 Storing Measurements: The History Database........................145 6.5.8 The People Impact..................................................................148 6.5.9 The Dark Side of Measurement........................
... impacts. For example, the Standish Group's Chaos Report annually surveys commercial and government information technology (IT) projects. They found that only 35% of the projects finished on time and within budget, a staggering 19% were ...
... impact of technology on products and processes; • Establish far-reaching yet achievable objectives for project cost, schedule,. Fig. 2.2. Measurements depend on stakeholder needs. Their goals of what to control or improve drive the ...
... impact of these decisions. This E4–measurement process can also be portrayed as a closed control loop. We insist that it be closed by means of the last (execution) step, that is, execute decisions based on the information collected ...
... impact do you have inside the enterprise? Who benefits most from the projects, and who creates the most difficulties for the projects? Why is that? What could you do to help this person, group, or customer? Fig. 2.5 shows this goal ...
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 |