Negotiating a Common Understanding. Ways to the Get Started. Exploring the Possibilities. Clarifying Expectations. Greatly Improving the Odds of Success.

Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts. Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks. Part 1 introduces the core, essential skills of a master explorer. You'll learn to craft charters to guide your exploration, to observe what's really happening (hint: it's harder than it sounds), to identify interesting variations, and to determine what expected behavior should be when exercising software in unexpected ways. Part 2 builds on that foundation. You'll learn how to explore by varying interactions, sequences, data, timing, and configurations. Along the way you'll see how to incorporate analysis techniques like state modeling, data modeling, and defining context diagrams into your explorer's arsenal. Part 3 brings the techniques back into the context of a software project. You'll apply the skills and techniques in a variety of contexts and integrate exploration into the development cycle from the very beginning. You can apply the techniques in this book to any kind of software. Whether you work on embedded systems, Web applications, desktop applications, APIs, or something else, you'll find this book contains a wealth of concrete and practical advice about exploring your software to discover its capabilities, limitations, and risks.

Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles. About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose. About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban. This book is written for developers, testers, analysts, and business people working together to build great software. Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book. What's Inside Common process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies =============================================== Table of Contents Part 1 Getting started Part 2 Key process patterns Part 3 Case studies Key benefits Key process patterns Living documentation Initiating the changes Deriving scope from goals Specifying collaboratively Illustrating using examples Refining the specification Automating validation without changing specifications Validating frequently Evolving a documentation system uSwitch RainStor Iowa Student Loan Sabre Airline Solutions ePlan Services Songkick Concluding thoughts

Exploring Biblical Backgrounds provides students and teachers with a rich compendium of ancient primary sources that form essential readings for studying both the Old and New Testaments of the Bible. Containing a wide range of comparable texts from the ancient Near East, Second Temple Judaism, the Greco-Roman world, and early Christianity, this collection furnishes students with awareness and insight of the various contexts of the Bible and views into important parallels. Headnotes to the sections and to each individual reading enable students to understand how a reading connects to the biblical text, while the expansive Scripture index provides an easy tool for identifying the biblical texts referenced in the introductions. An indispensable companion for understanding how history and ancient ideas resonate in Scripture, Exploring Biblical Backgrounds guides students through the world out of which Scripture grew and prepares readers to hear the voice with which the Bible speaks.

Research Data Management (RDM) has become a professional topic of great importance internationally following changes in scholarship and government policies about the sharing of research data. Exploring Research Data Management provides an accessible introduction and guide to RDM with engaging tasks for the reader to follow and develop their knowledge. Starting by exploring the world of research and the importance and complexity of data in the research process, the book considers how a multi-professional support service can be created then examines the decisions that need to be made in designing different types of research data service from local policy creation, training, through to creating a data repository. Coverage includes: A discussion of the drivers and barriers to RDM Institutional policy and making the case for Research Data Services Practical data management Data literacy and training researchers Ethics and research data services Case studies and practical advice from working in a Research Data Service. This book will be useful reading for librarians and other support professionals who are interested in learning more about RDM and developing Research Data Services in their own institution. It will also be of value to students on librarianship, archives, and information management courses studying topics such as RDM, digital curation, data literacies and open science.

This is the digital version of the printed book (Copyright © 2005). If you develop software without understanding the requirements, you're wasting your time. On the other hand, if a project spends too much time trying to understand the requirements, it will end up late and/or over-budget. And products that are created by such projects can be just as unsuccessful as those that fail to meet the basic requirements. Instead, every company must make a reasonable trade-off between what's required and what time and resources are available. Finding the right balance for your project may depend on many factors, including the corporate culture, the time-to-market pressure, and the criticality of the application. That is why requirements management—gathering requirements, identifying the "right" ones to satisfy, and documenting them—is essential. Just Enough Requirements Management shows you how to discover, prune, and document requirements when you are subjected to tight schedule constraints. You'll apply just enough process to minimize risks while still achieving desired outcomes. You'll determine how many requirements are just enough to satisfy your customers while still meeting your goals for schedule, budget, and resources. If your project has insufficient resources to satisfy all the requirements of your customers, you must read Just Enough Requirements Management.