The widespread deployment of millions of current and emerging software applications has placed software economic studies among the most critical of any form of business analysis. Unfortunately, a lack of an integrated suite of metrics makes software economic analysis extremely difficult. The International Function Point Users Group (IFPUG), a nonprofit and member-governed organization, has become the recognized leader in promoting the effective management of application software development and maintenance activities. The IFPUG Guide to IT and Software Measurement brings together 52 leading software measurement experts from 13 different countries who share their insights and expertise. Covering measurement programs, function points in measurement, new technologies, and metrics analysis, this volume: Illustrates software measurement's role in new and emerging technologies Addresses the impact of agile development on software measurement Presents measurement as a powerful tool for auditing and accountability Includes metrics for the CIO Edited by IFPUG's Management and Reporting Committee, the text is useful for IT project managers, process improvement specialists, measurement professionals, and business professionals who need to interact with IT professionals and participate in IT decision-making. It includes coverage of cloud computing, agile development, quantitative project management, process improvement, measurement as a tool in accountability, project ROI measurement, metrics for the CIO, value stream mapping, and benchmarking.

This book combines the synergies between performance improvement systems to help ensure safe and reliable operations, streamline procedures and cross-system auditing, and supporting regulatory and corporate compliance requirements. Many metrics are common to more than one area, such that a well-designed and implemented integrated management system will reduce the load on the Process Safety, SHE, Security and Quality groups, and improve manufacturing efficiency and customer satisfaction. Systems to improve performance include: process safety; traditional safety, health and environment; and, product quality. Chapters include: Integrating Framework; Securing Support & Preparing for Implementation; Establishing Common Risk Management Systems – How to Integrate PSM into Other EH; Testing Implementation Approach; Developing and Agreeing on Metrics; Management Review; Tracking Integration Progress and Measuring Performance; Continuous Improvement; Communication of Results to Different Stakeholders; Case Studies; and Examples for Industry.

Provides general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. The handbook will increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. Covers general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. Describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. Charts and tables.

Content Description #Includes bibliographical references and indexes.

Going where no book on software measurement and metrics has previously gone, this critique thoroughly examines a number of bad measurement practices, hazardous metrics, and huge gaps and omissions in the software literature that neglect important topics in measurement. The book covers the major gaps and omissions that need to be filled if data about software development is to be useful for comparisons or estimating future projects. Among the more serious gaps are leaks in reporting about software development efforts that, if not corrected, can distort data and make benchmarks almost useless and possibly even harmful. One of the most common leaks is that of unpaid overtime. Software is a very labor-intensive occupation, and many practitioners work very long hours. However, few companies actually record unpaid overtime. This means that software effort is underreported by around 15%, which is too large a value to ignore. Other sources of leaks include the work of part-time specialists who come and go as needed. There are dozens of these specialists, and their combined effort can top 45% of total software effort on large projects. The book helps software project managers and developers uncover errors in measurements so they can develop meaningful benchmarks to estimate software development efforts. It examines variations in a number of areas that include: Programming languages Development methodology Software reuse Functional and nonfunctional requirements Industry type Team size and experience Filled with tables and charts, this book is a starting point for making measurements that reflect current software development practices and realities to arrive at meaningful benchmarks to guide successful software projects.