Software Measurement: Establish - Extract - Evaluate - Execute

Pirmais vāks
Springer 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:

No grāmatas satura

Lietotāju komentāri - Rakstīt atsauksmi

Ierastajās vietās neesam atraduši nevienu atsauksmi.

Atlasītās lappuses


1 Introduction
2 Making Measurement a Success A Primer
3 Measurement Foundations
4 Planning the Measurement Process
5 Performing the Measurement Process
6 Introducing a Measurement Program
7 Estimation of Size Effort and Cost
8 Project Management
11 Improving Processes and Products
12 Controlling for IT and Software
13 Measurement Repositories
14 Empirical Laws and Rules of Thumb
15 Getting yet more Information

9 Quality Control and Assurance
10 Measuring Software Systems

Citi izdevumi - Skatīt visu

Bieži izmantoti vārdi un frāzes

Populāri fragmenti

394. lappuse - Break down barriers between departments. People in research, design, sales, and production must work as a team, to foresee problems of production and in use that may be encountered with the product or service.
531. lappuse - A condition or capability needed by a user to solve a problem or achieve an objective. (2) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed document.
73. lappuse - IN physical science a first essential step in the direction of learning any subject, is to find principles of numerical reckoning, and methods for practicably measuring, some quality connected with it. I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a...
63. lappuse - The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.
394. lappuse - They apply to a division within a company. 1 . Create constancy of purpose toward improvement of product and service, with the aim to become competitive and to stay in business, and to provide jobs. 2. Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on leadership for change.
512. lappuse - ISO 9001 standard. assignable cause: (see special causes). audit: systematic, independent and documented process for obtaining audit evidence and evaluating it objectively to determine the extent to which audit criteria are fulfilled.
394. lappuse - Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on leadership for change. 3. Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place. 4. End the practice of awarding business on the basis of price tag.
266. lappuse - Since there are some guiding principles for decision support available, we focus on utilizing expert-derived, however vague, knowledge that we included in a fuzzy expert system-type classification scheme. If software engineering expert knowledge is available we recommend fuzzy classification before using learning strategies that are only result-driven (eg classification trees or mere neural network approaches). However, we see the necessity of such approaches when only few guiding principles are...
131. lappuse - The principle is hence nicknamed '80:20 rule' because it assumes that the 20 % share is responsible for 80 % of the problems. It is amazing that this simple approach holds in most application domains. Software quality management methods, such as root cause analysis, typically start with identifying the small amount of problems (20 %) that provide the biggest trade-off when resolved. The difference...
519. lappuse - Failure The termination of the ability of an item to perform a required function.

Par autoru (2007)

Christof Ebert is managing director and partner at Vector Consulting Services, has authored several books in software engineering and serves on editorial boards of several scientific journals and as a frequent keynote speaker at conferences.

Reiner Dumke is professor of software engineering at the university of Magdeburg, Germany, and speaker of the German informatics society (GI) expert group on metrics.

Bibliogrāfiskā informācija