Software Engineering Economics is an invaluable guide to determining software costs, applying the fundamental concepts of microeconomics to software engineering, and utilizing economic analysis in software engineering decision making.

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.

This is the most authoritative archive of Barry Boehm's contributions to software engineering. Featuring 42 reprinted articles, along with an introduction and chapter summaries to provide context, it serves as a "how-to" reference manual for software engineering best practices. It provides convenient access to Boehm's landmark work on product development and management processes. The book concludes with an insightful look to the future by Dr. Boehm.

Software Engineering Economics is a relatively new discipline that deals with all segments of the software life cycle. The discipline has received much visibility in recent years because of the size and cost considerations of many software development and maintenance efforts. This book places additional emphasis on the Federal Government`s Information Resource Management initiative and deals with related issues such as Business Re-engineering, Functional Economic Analysis, Organizational Process Modelling and the Economics of Reuse.

The IT community has always struggled with questions concerning the value of an organization’s investment in software and hardware. It is the goal of value-based software engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule – such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extends the merely technical ISO software engineering definition with elements not only from economics, but also from cognitive science, finance, management science, behavioral sciences, and decision sciences, giving rise to a truly multi-disciplinary framework. Biffl and his co-editors invited leading researchers and structured their contributions into three parts, following an introduction into the area by Boehm himself. They first detail the foundations of VBSE, followed by a presentation of state-of-the-art methods and techniques. The third part demonstrates the benefits of VBSE through concrete examples and case studies. This book deviates from the more anecdotal style of many management-oriented software engineering books and so appeals particularly to all readers who are interested in solid foundations for high-level aspects of software engineering decision making, i.e., to product or project managers driven by economics and to software engineering researchers and students.

This volume presents a selection of the presentations from the first annual conference on Analytical Methods in Software Engineering Economics held at The MITRE Corporation in McLean, Virginia. The papers are representative of the issues that are of interest to researchers in the economics of information systems and software engineering economics. The 1990s are presenting software economists with a particularly difficult set of challenges. Because of budget considerations, the number of large new software development efforts is declining. The primary focus has shifted to issues relating to upgrading and migrating existing systems. In this environment, productivity enhancing methodologies and tools are of primary interest. The MITRE Software Engineering Analysis Conference was designed to address some of th,~ new and difficult challenges that face our profession. The primary objective of the conference was to address new theoretical and applications directions in Software Engineering Economics, a relatively new discipline that deals with the management and control of all segments of the software life-cycle. The discipline has received much visibility in the last twenty-five years because of the size and cost considerations of many software development and maintenance efforts, particularly in the Federal Government. We thank everyone who helped make this conference a success, especially those who graciously allowed us to include their work in this volume.

The Economics of Information Systems and Software focuses on the economic aspects of information systems and software, including advertising, evaluation of information systems, and software maintenance. The book first elaborates on value and values, software business, and scientific information as an economic category. Discussions focus on information products and information services, special economic properties of information, culture and convergence, hardware and software products, materiality and consumption, technological progress, and software flexibility. The text then takes a look at advertising to finance software, perspectives on East-West relations in economics and information, and evaluation of information systems. Topics include research on information systems, knowledge on Eastern European information services, GDR information institutes, local databases, GDR databases, CMEA directions, and theoretical propositions. The manuscript reviews software reuse, software methodology in the harsh light of economics, quantitative aspects of software maintenance management, and calibrating a software cost-estimation model. Concerns cover the need for calibration, measuring maintainability, prognosis of maintenance effort, object-oriented programming, metaprogramming, and software quality and reuse. The text is a dependable reference for computer science experts and researchers wanting to explore further the economics of information systems and software.

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).

A small program is presented to motivate the concerns for programmer productivity and program quality that are the central issues of this set of essays. The example is one which demonstrates the performance aspect of programming. In order to achieve program quality, where a program is understood and known to be correct, we need a primary program description. This primary program description not only describes the program but is also used to generate the program. The method of applying primary program descriptions to produce programs is called metaprogramming and is described in Chapter 3. In the later chapters, we show how the method can be analyzed from an economic point of view to address the issues of productivity as well. 1 Introduction In thinking about programming over the last decade, I have concluded that very little is known about the process of programming or the engineering of software [1]. The consequence of having very little established truth to use as a basis for thinking about programming is that almost every conclusion must be reasoned out from first principles. Also, you cannot rely solely on textbooks but must use experimentation and direct observation to gain some experience with which to proceed.

A groundbreaking book in this field, Software Engineering Foundations: A Software Science Perspective integrates the latest research, methodologies, and their applications into a unified theoretical framework. Based on the author's 30 years of experience, it examines a wide range of underlying theories from philosophy, cognitive informatics, denota