Software Assessments, Benchmarks, and Best Practices


Book Description

Teaching software professionals how to combine assessments (qualitative information) and benchmarking (quantitative information) this text aims to encourage better software analysis.




Best Practices in Software Measurement


Book Description

Practical approach to software measurement Contains hands-on industry experiences




Metrics and Models in Software Quality Engineering


Book Description

""This is the single best book on software quality engineering and metrics that I've encountered."" --Capers Jones, from the Foreword"Metrics and Models in Software Quality Engineering, Second Edition," is the definitive book on this essential topic of software development. Comprehensive in scope with extensive industry examples, it shows how to measure software quality and use measurements to improve the software development process. Four major categories of quality metrics and models are addressed: quality management, software reliability and projection, complexity, and customer view. In addition, the book discusses the fundamentals of measurement theory, specific quality metrics and tools, and methods for applying metrics to the software development process.New chapters bring coverage of critical topics, including: In-process metrics for software testingMetrics for object-oriented software developmentAvailability metricsMethods for conducting in-process quality assessments and software project assessmentsDos and Don'ts of Software Process Improvement, by Patrick O'TooleUsing Function Point Metrics to Measure Software Process Improvement, by Capers Jones In addition to the excellent balance of theory, techniques, and examples, this book is highly instructive and practical, covering one of the most important topics in software development--quality engineering. 0201729156B08282002




Project Requirements: A Guide to Best Practices


Book Description

Project Requirements: A Guide to Best Practices gives project managers tools they can assimilate and apply easily to improve project success rates, reduce development costs, reduce rework, and accelerate time to market. Based on experience and best practices, this valuable reference will help you: • Clarify real requirements before you initiate project work • Improve management of project requirements • Save time and effort • Manage to your schedule • Improve the quality of deliverables • Increase customer satisfaction and drive repeat business Project Requirements: A Guide to Best Practices provides project managers with a direct, practical strategy to overcome requirements challenges and manage requirements successfully.




The Economics of Software Quality


Book Description

Poor quality continues to bedevil large-scale development projects, but few software leaders and practitioners know how to measure quality, select quality best practices, or cost-justify their usage. In The Economics of Software Quality, leading software quality experts Capers Jones and Jitendra Subramanyam show how to systematically measure the economic impact of quality and how to use this information to deliver far more business value. Using empirical data from hundreds of software organizations, Jones and Subramanyam show how integrated inspection, static analysis, and testing can achieve defect removal rates exceeding 95 percent. They offer innovative guidance for predicting and measuring defects and quality; choosing defect prevention, pre-test defect removal, and testing methods; and optimizing post-release defect reporting and repair. This book will help you Prove that improved software quality translates into strongly positive ROI and greatly reduced TCO Drive better results from current investments in debugging and prevention Use quality techniques to stay on schedule and on budget Avoid "hazardous" metrics that lead to poor decisions Important note: The audio and video content included with this enhanced eBook can be viewed only using iBooks on an iPad, iPhone, or iPod touch.




New Trends in Software Methodologies, Tools and Techniques


Book Description

"Papers presented at the Eighth International Conference on New Trends in Software Methodologies, Tools and Techniques, (SoMeT 09) held in Prague, Czech Republic ... from September 23rd to 25th 2009."--P. v.




A Guide to Selecting Software Measures and Metrics


Book Description

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.




Software Maintenance Success Recipes


Book Description

Software Maintenance Success Recipes identifies actionable formulas for success based on in-depth analysis of more than 200 real-world maintenance projects. It details the set of factors that are usually present when effective software maintenance teams do their work and instructs on the methods required to achieve success. Donald J. Reifer-an award winner for his contributions to the field of software engineering-provides step-by-step guidance on how to structure the job to complete all of the work related to the task.




Encyclopedia of Software Engineering Three-Volume Set (Print)


Book Description

Software engineering requires specialized knowledge of a broad spectrum of topics, including the construction of software and the platforms, applications, and environments in which the software operates as well as an understanding of the people who build and use the software. Offering an authoritative perspective, the two volumes of the Encyclopedia of Software Engineering cover the entire multidisciplinary scope of this important field. More than 200 expert contributors and reviewers from industry and academia across 21 countries provide easy-to-read entries that cover software requirements, design, construction, testing, maintenance, configuration management, quality control, and software engineering management tools and methods. Editor Phillip A. Laplante uses the most universally recognized definition of the areas of relevance to software engineering, the Software Engineering Body of Knowledge (SWEBOK®), as a template for organizing the material. Also available in an electronic format, this encyclopedia supplies software engineering students, IT professionals, researchers, managers, and scholars with unrivaled coverage of the topics that encompass this ever-changing field. Also Available Online This Taylor & Francis encyclopedia is also available through online subscription, offering a variety of extra benefits for researchers, students, and librarians, including: Citation tracking and alerts Active reference linking Saved searches and marked lists HTML and PDF format options Contact Taylor and Francis for more information or to inquire about subscription options and print/online combination packages. US: (Tel) 1.888.318.2367; (E-mail) [email protected] International: (Tel) +44 (0) 20 7017 6062; (E-mail) [email protected]




Rethinking Productivity in Software Engineering


Book Description

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll LearnReview the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology.