Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 276 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
276
Dung lượng
7,19 MB
Nội dung
[...]... is calculated 2.6 SUMMARY Each software project and organization is faced with the question of what to measure To answer this question, you must know your customers and their goals REFERENCES 13 and use that to drive the appropriate definition of ameasurement program Standards and approaches such as the decision maker model, GQM, and GQM2 provide ways to answer that question Regardless of the approach. .. softwaremeasurementandestimation They graciously have allowed us to use their benchmarking data and models, as have the David Consulting Group, Quantitative Software Management Corporation, David Longstreet and Don Reifer Thank you all Our gratitude also to Vic Basili for his review and blessing of our take on his GQM model To the folks at Simula Research Laboratories—we love your work on estimation thank... each level is made up of process areas (PAs) These PAs identify what activities must be addressed to meet the goals of that level of maturity Softwareestimationand metrics indeed play a part in an organization reaching increasing levels of maturity For example, Level 2 contains a PA called Project Planning To fulfill this PA, the organization must develop reasonable plans based on realistic estimates... areas of measurements in software: size (Chapter 4) and complexity (Chapter 5) 1.3 MOTIVATION 3 A key task in software engineering is the ability to estimate the effort and schedule effectively, so we also provide a foundation in estimation theory anda multitude of estimation techniques (Chapter 6) We then introduce three additional areas of measurement: defects, reliability, and availability (Chapters... measure progress and compare it to planned performance At Level 4, the PAs focus on establishing a quantitative view of both the software process and the software project/ product Level 4 is all about measurement, to drive and control the process and to produce project/product consistency and quality The goal is to use metrics to achieve a process that remains stable and predictable and to produce a. .. a product that meets the quality goals of the organization and customer At Level 5, the focus is on continuous measurable improvement This means that organization must set measurable goals for improvement that meet the needs of the business and track the organization’s performance over time Clearly, a well-defined approach to estimationandmeasurement is essential for any software organization to move... what these measures might be, we will first lay a foundation in measurementandestimation theory and then build on that based on the practical needs of those involved in software development 1.4 SUMMARY This textbook will provide you with practical techniques for the estimationand quantitative measurement of software projects It will provide a solid foundation in measurementandestimation methods,... situations We will provide our readers, both students and software industry colleagues, with practical techniques for the estimationand quantitative measurement of software projects Software engineering has long been in practice both an art anda science The challenge has been allowing for creativity while at the same time bringing strong engineering principles to bear The software industry has not always... assessing and improving processes (see Reference 3 for details on each approach) and define levels of capability and maturity For example, the staged 6 INTRODUCTION approach defines five levels of organizational maturity: 1 2 3 4 5 Initial Managed Defined Quantitatively managed Optimizing As organizations mature, they move up to higher levels of the framework Except for Level 1, which is basically ad hoc software. .. Boston, 2003 [4] D Pitts, “Why is softwaremeasurement hard?” [online] 1999 Available from http://www.stickyminds.com Accessed Jan 6, 2005 2 What to Measure What you measure is what you get —Kaplan and Norton [1] There are many characteristics of software andsoftware projects that can be measured, such as size, complexity, reliability, quality, adherence to process, and profitability Through the course of . class="bi x0 y0 w0 h0" alt="" Software Measurement and Estimation A Practical Approach Linda M. Laird M. Carol Brennan A John Wiley & Sons, Inc., Publication Software Measurement and Estimation Press. and software industry colleagues, with practical techniques for the estimation and quantitative measurement o f software projects. Software engineering has long been in practice both an art and. information about Wiley products, visit our web site at www.wiley.com. Library of Congress Cataloging-in-Publication Data: Laird, Linda M., 1952- Software measurement and estimation: a practical approach