Jeżeli nie znalazłeś poszukiwanej książki, skontaktuj się z nami wypełniając formularz kontaktowy.

Ta strona używa plików cookies, by ułatwić korzystanie z serwisu. Mogą Państwo określić warunki przechowywania lub dostępu do plików cookies w swojej przeglądarce zgodnie z polityką prywatności.

Wydawcy

Literatura do programów

Informacje szczegółowe o książce

Software Measurement and Estimation: A Practical Approach - ISBN 9780471676225

Software Measurement and Estimation: A Practical Approach

ISBN 9780471676225

Autor: Linda M. Laird, M. Carol Brennan

Wydawca: Wiley

Dostępność: 3-6 tygodni

Cena: 597,45 zł

Przed złożeniem zamówienia prosimy o kontakt mailowy celem potwierdzenia ceny.


ISBN13:      

9780471676225

ISBN10:      

0471676225

Autor:      

Linda M. Laird, M. Carol Brennan

Oprawa:      

Hardback

Rok Wydania:      

2006-07-07

Ilość stron:      

280

Wymiary:      

244x162

Tematy:      

TJ

An effective, quantitative approach for estimating and managing software projects
How many people do I need? When will the quality be good enough for commercial sale? Can this really be done in two weeks? Rather than relying on instinct, the authors of Software Measurement and Estimation offer a new, tested approach that includes the quantitative tools, data, and knowledge needed to make sound estimations.
The text begins with the foundations of measurement, identifies the appropriate metrics, and then focuses on techniques and tools for estimating the effort needed to reach a given level of quality and performance for a software project. All the factors that impact estimations are thoroughly examined, giving you the tools needed to regularly adjust and improve your estimations to complete a project on time, within budget, and at an expected level of quality.
This text includes several features that have proven to be successful in making the material accessible and easy to master:Simple, straightforward style and logical presentation and organization enables you to build a solid foundation of theory and techniques to tackle complex estimationsExamples, provided throughout the text, illustrate how to use theory to solve real–world problemsProjects, included in each chapter, enable you to apply your newfound knowledge and skillsTechniques for effective communication of quantitative data help you convey your findings and recommendations to peers and management
Software Measurement and Estimation: A Practical Approach allows practicing software engineers and managers to better estimate, manage, and effectively communicate the plans and progress of their software projects. With its classroom–tested features, this is an excellent textbook for advanced undergraduate–level and graduate students in computer science and software engineering.

Spis treści:
Acknowledgments.
1. Intro duction.
1.1 Objective.
1.2 Approach.
1.3 Motivation.
1.4 Summary.
References.
Chapter 1 Side Bar.
2. What to Measure.
2.1 Method 1: The Goal Question Metrics Approach.
2.2 Extension to GQM: Metrics Mechanism is Important.
2.3 Method 2: Decision Maker Model.
2.4 Method 3: Standards Driven Metrics.
2.5 What to Measure is a Function of Time.
2.6 Summary.
References.
Exercises.
Project.
3. Fundamentals of Measurement.
3.1 Initial Measurement Exercise.
3.2 The Challenge of Measurement.
3.3 Measurement Models.
3.3.1 Text Models.
3.3.2 Diagrammatic Models.
3.3.3 Algorithmic Models.
3.3.4 Model Examples:   Response Time.
3.3.5 The Pantometric Paradigm – How to Measure Anything.
3.4 Meta–Model for Metrics.
3.5 The Power of Measurement.
3.6 Measurement Theory.
3.6.1 Introduction to Measurement Theory.
3.6.2 Measurement Scales.
3.6.3 Measures of Central Tendency and Variability.
3.6.3.1 Measures of Central Tendency.
3.6.3.2 Measures of Variability.
3.6.4 Validity and Reliability of Measurement.
3.6.5 Measurement Error.
3.7 Accuracy versus Precision and the Limits of Software Measurement.
3.7.1 Summary.
3.7.2 Problems.
3.7.3 Project.
References.
4. Measuring the Size of Software.
4.1 Physical Measurements of Software.
4.1.1 Measuring Lines of Code.
4.1.1.1 Code Counting Checklists.
4.1.2 Language Productivity Factor.
4.1.3 Counting Reused and Refactored Code.
4.1.4 Counting Non–Procedural Code Length.
4.1.5 Measuring the Length of Specifications and Design.
4.2 Measuring Functionality.
4.2.1 Function Points.
4.2.1.1 Counting Function Points.
4.2.2 Function Point Counting Exercise.
4.2.3 Converting Function Points to Physical Size.
4.2.4 Converting Function Points to Effort.
4.2.5 Other Function Point Engineering Rules.
4.2.6 Function Point Pros and Cons.
4 .3 Feature Points.
4.4 Size Summary.
4.5 Size Exercises.
4.6 Theater Tickets Project.
References.
5. Measuring Complexity.
5.1 Structural Complexity.
5.1.1 Size as a Complexity Measure.
5.1.1.1 System Size and Complexity.
5.1.1.2 Module Size and Complexity.
5.1.2 Cyclomatic Complexity.
5.1.3 Halstead′s Metrics.
5.1.4 Information Flow Metrics.
5.1.5 System Complexity.
5.1.5.1 Maintainability Index.
5.1.5.2 The Agresti–Card System Complexity Metric.
5.1.6 Object–Oriented Design Metrics.
5.1.7 Structural Complexity Summary.
5.2 Conceptual Complexity.
5.3 Computational Complexity.
5.4 Complexity Metrics Summary.
5.5 Complexity Exercises.
5.6 Projects.
References.
6. Estimating Effort.
6.1 Effort Estimation – Where are we?.
6.2 Software Estimation Methodologies and Models.
6.2.1 Expert Estimation.
6.2.1.1 Work and Activity Decomposition.
6.2.1.2 System Decomposition.
6.2.1.3 The Delphi Methods.
6.2.2 Using Benchmark Size Data.
6.2.2.1 Lines of Code Benchmark Data.
6.2.2.2 Function Point Benchmark Data.
6.2.3 Estimation by Analogy.
6.2.3.1 Traditional Analogy Approach.
6.2.3.2 Analogy Summary.
6.2.4 Proxy Point Estimation Methods.
6.2.4.1 Meta–Model for Effort Estimation.
6.2.4.2 Function Points.
6.2.4.2.1 COSMIC Function Points.
6.2.4.3 Object Points.
6.2.4.4 Use Case Sizing Methodologies.
6.2.4.4.1 Use Case Points Methodology.
6.2.4.4.2 Example: Use Case Point Methodology Example:   Home Security System.
6.2.4.4.3   Use Case Point Methodology Effectiveness.
6.2.5 Custom Models.
6.2.6 Algorithmic Models.
6.2.6.1 Manual Models.
6.2.6.2 Estimating Project Duration.
6.2.6.3 Tool Based Models.
6.3 Combining Estimates.
6.4 Estimating Issues.
6.4.1 Targets vs. Estimates.
6.4.2 The Limitations of Estimation – Why?.
6.4.3 Estimate Uncertainties.6.5 Estimating Early and Often.
6.6 Estimation Summary.
6.7 Estimation Problems.
6.8 Estimation Project – Theater Tickets.
References.
7. In Praise of Defects:   Defects and Defect Metrics.
7.1 Why study and measure defects?.
7.2 Faults vs. failures.
7.3 Defect Dynamics and Behaviors.
7.3.1 Defect Arrival Rates.
7.3.2 Defects vs. Effort.
7.3.3 Defects vs. Staffing.
7.3.4 Defect Arrival Rates vs. Code Production Rate.
7.3.5 Defect Density vs. Module Complexity.
7.3.6 Defect Density vs. System Size.
7.4 Defect Projection Techniques and Models.
7.4.1 Dynamic Defect Models.
7.4.1.1 Rayleigh Models.
7.4.1.2 Exponential and S–Curves Arrival Distribution Models.
7.4.1.3 Empirical Data and Recommendations for Dynamic Models.
7.4.2 Static Defect Models.
7.4.2.1 Defect Insertion and Removal Model.
7.4.2.2 Defect Removal Efficiency – A Key Metric.
7.4.2.3 Static Defect Model Tools.
7.5 Additional Defect Benchmark Data.
7.5.1 Defect Data By Application Domain.
7.5.2 Cumulative Defect Removal Efficiency (DRE) Benchmark.
7.5.3 SEI Levels and Defect Relationships.
7.5.4 Latent Defects.
7.5.5 Other Defects   Benchmarks and a Few Recommendations+.
7.6 Cost Effectiveness of Defect Removal by Phase.
7.7 Defining and Using Simple Defect Metrics: An example.
7.8 Some Paradoxical Patterns for Customer Reported Defects.
7.9 Defect Summary.
7.10 Problems.
7.11 Projects.
7.12 Answers to the initial questions.
References.
8. Software Reliability Measurement and Prediction.
8.1 Why study and measure software reliability?.
8.2 What is reliability?.
8.3 Faults and failures.
8.4 Failure Severity Classes.
8.5 Failure Intensity.
8.6 The Cost of Reliability.
8.7 Software Reliability Theory.
8.7.1 Uniform and Random Distributions.
8.7.2 The probability of failure during a time interval.
8.7.3 F(t) –

Koszyk

Książek w koszyku: 0 szt.

Wartość zakupów: 0,00 zł

ebooks
covid

Kontakt

Gambit
Centrum Oprogramowania
i Szkoleń Sp. z o.o.

Al. Pokoju 29b/22-24

31-564 Kraków


Siedziba Księgarni

ul. Kordylewskiego 1

31-542 Kraków

+48 12 410 5991

+48 12 410 5987

+48 12 410 5989

Zobacz na mapie google

Wyślij e-mail

Subskrypcje

Administratorem danych osobowych jest firma Gambit COiS Sp. z o.o. Na podany adres będzie wysyłany wyłącznie biuletyn informacyjny.

Autoryzacja płatności

PayU

Informacje na temat autoryzacji płatności poprzez PayU.

PayU banki

© Copyright 2012: GAMBIT COiS Sp. z o.o. Wszelkie prawa zastrzeżone.

Projekt i wykonanie: Alchemia Studio Reklamy