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 68.
... schedule,. Fig. 2.2. Measurements depend on stakeholder needs. Their goals of what to control or improve drive the selection and effective use of measurements Fig. 2.4. To achieve lasting impact of decisions the E4–measurement. 22 2 ...
... schedule, quality and cost; • Predict and forecast future performance; • Communicate progress and improvement needs. There is some additional literature around taking a business perspective on software. Most of it looks into examples ...
... schedule predictability or reducing cost. Naturally, they should be selected based on the market and business situation, the maturity and certainly the priorities in the projects. Fig. 2.5. Measurements are derived from goals. They help ...
... schedule and budget adherence, earned value, or quality level are typical performance indicators that serve as “traffic lights” on the status of the individual project. Only those (amber and red) projects that run out of agreed variance ...
... schedule information, milestones, effort spent, defects detected, and so on). It is self-contained and easy to learn. Key information is collected in a single repository with access control to protect the consolidated information ...
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 |