"Just the understanding and insights you will pick up about how people encounter and cope with combinations of technical, social, political, and economic opportunities and challenges make the book a joy to read and worth much more than the price of it alone." --Barry Boehm, from the Foreword This practical handbook shows you how to build an effective business case when you need to justify--and persuade management to accept--software change or improvement. Based on real-world scenarios, the book covers the most common situations in which business case analyses are required and explains specific techniques that have proved successful in practice. Drawing on years of experience in winning the "battle of the budget," the author shows you how to use commonly accepted engineering economic arguments to make your numbers "sing" to management. The book provides examples of successful business cases; along the way, tables, tools, facts, figures, and metrics guide you through the entire analytic process. Writing in a concise and witty style, the author makes this valuable guidance accessible to every software engineer, manager, and IT professional. Highlights include: How and where business case analyses fit into the software and IT life cycle process Explanations of the most common tools for business case analysis, such as present-value, return-on-investment, break-even, and cost/benefit calculation Tying the business process to the software development life cycle Packaging the business case for management consumption Frameworks and guidelines for justifying IT productivity, quality, and delivery cycle improvement strategies Case studies for applying appropriate decision situations to software process improvement Strategic guidelines for various business case analyses With this book in hand, you will find the facts, examples, hard data, and case studies needed for preparing your own winning business cases in today's complex software environment.

This book contains the extended and revised versions of selected papers from the Third International Symposium on Business Modeling and Software Design (BMSD 2013), held in Noordwijkerhout, The Netherlands, during July 8-10, 2013. The symposium was organized and sponsored by the Interdisciplinary Institute for Collaboration and Research on Enterprise Systems and Technology (IICREST), in cooperation with the Dutch Research School for Information and Knowledge Systems (SIKS), the Center for Telematics and Information Technology (CTIT), Aristotle University of Thessaloniki (AUTH), and AMAKOTA Ltd. The theme of BMSD 2013 was "Enterprise Engineering and Software Generation." The 13 full and 20 short papers presented at BMSD 2013 were selected from 56 submissions. The eight papers published in this book were carefully reviewed and selected from the 13 full papers. The selection includes papers touching upon a large number of research topics, ranging from more conceptual ones, such as modeling landscapes, process modeling, declarative business rules, and normalized systems to more practical ones, such as business-case development and performance indicators, and from more business-related topics, such as value modeling and service systems, to topics related to information architectures.

Residents in Boston, Massachusetts are automatically reporting potholes and road hazards via their smartphones. Progressive Insurance tracks real-time customer driving patterns and uses that information to offer rates truly commensurate with individual safety. Google accurately predicts local flu outbreaks based upon thousands of user search queries. Amazon provides remarkably insightful, relevant, and timely product recommendations to its hundreds of millions of customers. Quantcast lets companies target precise audiences and key demographics throughout the Web. NASA runs contests via gamification site TopCoder, awarding prizes to those with the most innovative and cost-effective solutions to its problems. Explorys offers penetrating and previously unknown insights into healthcare behavior. How do these organizations and municipalities do it? Technology is certainly a big part, but in each case the answer lies deeper than that. Individuals at these organizations have realized that they don't have to be Nate Silver to reap massive benefits from today's new and emerging types of data. And each of these organizations has embraced Big Data, allowing them to make astute and otherwise impossible observations, actions, and predictions. It's time to start thinking big. In Too Big to Ignore, recognized technology expert and award-winning author Phil Simon explores an unassailably important trend: Big Data, the massive amounts, new types, and multifaceted sources of information streaming at us faster than ever. Never before have we seen data with the volume, velocity, and variety of today. Big Data is no temporary blip of fad. In fact, it is only going to intensify in the coming years, and its ramifications for the future of business are impossible to overstate. Too Big to Ignore explains why Big Data is a big deal. Simon provides commonsense, jargon-free advice for people and organizations looking to understand and leverage Big Data. Rife with case studies, examples, analysis, and quotes from real-world Big Data practitioners, the book is required reading for chief executives, company owners, industry leaders, and business professionals.

A brief but complete outline of what belongs in a business case and why it belongs. It assumes no prior background in finance or business planning. The focus is on questions like these: How do I prove that one choice is the best business decision? How do I show that all important costs and benefits are included? How do I show that alternative action proposals are compared fairly? How do I establish value for benefits--even non financial benefits? How do I build a business case when I am in a government or non profit organization? How do I minimize risk and show management how to maximize business results?

Presenting business problems in a case format, this text asks students to make good business decisions based on statistical information. The authors ask the student to evaluate realistic business situations and apply statistical reasoning to solve problems.

Frequently not enough attention is given to producing a comprehensive business case or to producing an economic justification for an information systems investment. In fact many organizations are not clear as to what constitutes a sound business case and how to go about producing one. This Professional level book for the Computer Weekly Professional Series will show how to go about justification for I.T. spend. This book is designed for all those who are involved in the decision to invest in information systems. This book is especially relevant to senior business executives, senior financial managers and IT executives. Business consultants, computer and corporate advisors will also find the ideas and material addressed in this text of particular benefit as will anyone involved in corporate and strategic planning. In addition, senior students such as those working towards their MBAs will find this book of use. A business case is a statement or a series of statements that demonstrate the economic value of a particular intervention, a course of action or a specific investment. A business case is not simply a financial forecast of the hardware and software costs and the expected benefits. A business case for an information systems investment involves a comprehensive understanding of both the likely resources as well as the business drivers which will assist business managers improve their performance and thereby obtain a stream of benefits from the investment. In general there are approximately six steps in producing a business case for an information systems investment. 1. Determine the high-level business outcomes that will be clearly and comprehensively expressed as a set of opportunities the organization can take advantage of, or problems that need to be rectified. 2. Identify the corporate critical success factors that will be supported or enhanced by the operation of the completed information systems project or investment. 3. Create a list of specific and detailed outcomes or benefits, their appropriate metrics, measuring methods and responsibility points that are represented by the stakeholders. 4. Quantify the contribution made by the outcomes, which requires associating numbers or benefit values with outcomes where this is possible. 5. Highlight the risks associated with the project. Fundamental to this new approach to developing a business case for information systems investment is the fact that it incorporates much more than the financial numbers which are typically found in the standard approach to a feasibility study. This approach looks behind the financial numbers to the improvements in business performance which are facilitated by information systems and which are the real drivers of the benefits. Furthermore, this approach to developing a business case allows the organization to manage the process so that the required results are achieved.

Effective decisions are crucial to the success of any software project, but to make better decisions you need a better decision-making process. In Evaluating Project Decisions, leading project management experts introduce an innovative decision model that helps you tailor your decision-making process to systematically evaluate all of your decisions and avoid the bad choices that lead to project failure. Using a real-world, case study approach, the authors show how to evaluate software project problems and situations more effectively, thoughtfully assess your alternatives, and improve the decisions you make. Drawing on their own extensive research and experience, the authors bridge software engineering theory and practice, offering guidance that is both well-grounded and actionable. They present dozens of detailed examples from both successful and unsuccessful projects, illustrating what to do and what not to do. Evaluating Project Decisions will help you to analyze your options and ultimately make better decisions at every stage in your project, including: Requirements–Elicitation, description, verification, validation, negotiation, contracting, and management over the software life cycle Estimates–Conceptual solution design, decomposition, resource and overhead allocation, estimate construction, and change management Planning–Defining objectives, policies, and scope; planning tasks, milestones, schedules, budgets, staff and other resources; and managing projects against plans Product–Proper product definition, development process management, QA, configuration management, delivery, installation, training, and field service Process–Defining, selecting, understanding, teaching, and measuring processes; evaluating process performance; and process improvement or optimization In addition, you will see how to evaluate decisions related to risk, people, stakeholder expectations, and global development. Simply put, you’ll use what you learn here on every project, in any industry, whatever your goals, and for projects of any duration, size, or type.

This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts.