Use an Approach Inspired by Domain-Driven Design to Build Documentation That Evolves to Maximize Value Throughout Your Development Lifecycle Software documentation can come to life, stay dynamic, and actually help you build better software. Writing for developers, coding architects, and other software professionals, Living Documentation shows how to create documentation that evolves throughout your entire design and development lifecycle. Through patterns, clarifying illustrations, and concrete examples, Cyrille Martraire demonstrates how to use well-crafted artifacts and automation to dramatically improve the value of documentation at minimal extra cost. Whatever your domain, language, or technologies, you don't have to choose between working software and comprehensive, high-quality documentation: you can have both. · Extract and augment available knowledge, and make it useful through living curation · Automate the creation of documentation and diagrams that evolve as knowledge changes · Use development tools to refactor documentation · Leverage documentation to improve software designs · Introduce living documentation to new and legacy environments
Use an Approach Inspired by Domain-Driven Design to Build Documentation That Evolves to Maximize Value Throughout Your Development Lifecycle Software documentation can come to life, stay dynamic, and actually help you build better software. Writing for developers, coding architects, and other software professionals, Living Documentation shows how to create documentation that evolves throughout your entire design and development lifecycle. Through patterns, clarifying illustrations, and concrete examples, Cyrille Martraire demonstrates how to use well-crafted artifacts and automation to dramatically improve the value of documentation at minimal extra cost. Whatever your domain, language, or technologies, you don’t have to choose between working software and comprehensive, high-quality documentation: you can have both. · Extract and augment available knowledge, and make it useful through living curation · Automate the creation of documentation and diagrams that evolve as knowledge changes · Use development tools to refactor documentation · Leverage documentation to improve software designs · Introduce living documentation to new and legacy environments
The Global Citizenship Commission was convened, under the leadership of former British Prime Minister Gordon Brown and the auspices of NYU’s Global Institute for Advanced Study, to re-examine the spirit and stirring words of The Universal Declaration of Human Rights. The result – this volume – offers a 21st-century commentary on the original document, furthering the work of human rights and illuminating the ideal of global citizenship. What does it mean for each of us to be members of a global community? Since 1948, the Declaration has stood as a beacon and a standard for a better world. Yet the work of making its ideals real is far from over. Hideous and systemic human rights abuses continue to be perpetrated at an alarming rate around the world. Too many people, particularly those in power, are hostile to human rights or indifferent to their claims. Meanwhile, our global interdependence deepens. Bringing together world leaders and thinkers in the fields of politics, ethics, and philosophy, the Commission set out to develop a common understanding of the meaning of global citizenship – one that arises from basic human rights and empowers every individual in the world. This landmark report affirms the Universal Declaration of Human Rights and seeks to renew the 1948 enterprise, and the very ideal of the human family, for our day and generation.
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
Deliver software that does what it’s supposed to do! Behavior-Driven Development guides your software projects to success with collaboration, communication techniques, and concrete requirements you can turn into automated tests. In BDD in Action, Second Edition you’ll learn how to: Implement and improve BDD practices Prioritize features from business goals Facilitate an example mapping session Write automated acceptance tests Scale up your automated acceptance tests Deliver accurate reporting and documentation Around half of all software projects fail to deliver on requirements. Behavior-Driven Development (BDD) helps make sure that yours isn’t one of them. Behavior-Driven Development in Action, Second Edition teaches you how to ensure that everyone involved in a software project—from developers to non-technical stakeholders—are in agreement on goals and objectives. It lays out the communication skills, collaborative practices, and useful automation tools that will let you seamlessly succeed with BDD. Now in its second edition, this revised bestseller has been extensively updated with new techniques for incorporating BDD into large-scale and enterprise development practices such as Agile and DevOps. Foreword by Daniel Terhorst-North. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the Technology Behavior-Driven Development is a collaborative software design technique that organizes examples of an application’s desired behavior into a concrete, testable specification. Because the BDD process gathers input from all areas of an organization, it maximizes the likelihood your software will satisfy both end users and business stakeholders. The established collaboration practices and automation strategies in this book will help you maximize the benefits of BDD for your dev team and your business clients. About the Book In BDD in Action, Second Edition, you’ll learn to seamlessly integrate BDD into your existing development process. This thoroughly revised new edition now shows how to integrate BDD with DevOps and large-scale Agile systems. Practical examples introduce cross-functional team communication skills, leading a successful requirements analysis, and how to set up automated acceptance criteria. What’s Inside How BDD positively affects teamwork, dynamics, and collaboration with stakeholders Help teams discover and analyze requirements, uncover assumptions, and reduce risks Make acceptance, integration, and unit testing more effective Automate reporting and living documentation to improve transparency About the Reader For all development teams. No experience with BDD required. Examples in Java, JavaScript, and TypeScript can be easily expressed in your chosen language. About the Author John Ferguson Smart is the creator of the Serenity BDD framework and founder of the Serenity Dojo training school. Jan Molak is the author of the Serenity/JS testing framework, Jenkins Build Monitor, and other CD and testing tools. Table of Contents PART 1 - FIRST STEPS 1 Building software that makes a difference 2 Introducing Behavior-Driven Development 3 BDD: The whirlwind tour PART 2 - WHAT DO I WANT? DEFINING REQUIREMENTS USING BDD 4 Speculate: From business goals to prioritized features 5 Describing and prioritizing features 6 Illustrating features with examples 7 From examples to executable specifications PART 3 - HOW DO I BUILD IT? CODING THE BDD WAY 8 From executable specifications to automated acceptance tests 9 Writing solid automated acceptance tests 10 Automating acceptance criteria for the UI layer 11 Test automation design patterns for the UI layer 12 Scalable test automation with the Screenplay Pattern 13 BDD and executable specifications for microservices and APIs 14 Executable specifications for existing systems with Serenity/JS 15 Portable test automation with Serenity/JS 16 Living documentation and release evidence
Master BDD to deliver higher-value software more quickly To develop high-value products quickly, software development teams need better ways to collaborate. Agile methods like Scrum and Kanban are helpful, but they’re not enough. Teams need better ways to work inside each sprint or work item. Behavior-driven development (BDD) adds just enough structure for product experts, testers, and developers to collaborate more effectively. Drawing on extensive experience helping teams adopt BDD, Richard Lawrence and Paul Rayner show how to explore changes in system behavior with examples through conversations, how to capture your examples in expressive language, and how to flow the results into effective automated testing with Cucumber. Where most BDD resources focus on test automation, this guide goes deep into how BDD changes team collaboration and what that collaboration looks like day to day. Concrete examples and practical advice will prepare you to succeed with BDD, whatever your context or role. · Learn how to collaborate better by using concrete examples of system behavior · Identify your project’s meaningful increment of value so you’re always working on something important · Begin experimenting with BDD slowly and at low risk · Move smoothly from informal examples to automated tests in Cucumber · Use BDD to deliver more frequently with greater visibility · Make Cucumber scenarios more expressive to ensure you’re building the right thing · Grow a Cucumber suite that acts as high-value living documentation · Sustainably work with complex scenario data · Get beyond the “mini-waterfalls” that often arise on Scrum teams
Supreme Court Justice Antonin Scalia once remarked that the theory of an evolving, "living" Constitution effectively "rendered the Constitution useless." He wanted a "dead Constitution," he joked, arguing it must be interpreted as the framers originally understood it. In The Living Constitution, leading constitutional scholar David Strauss forcefully argues against the claims of Scalia, Clarence Thomas, Robert Bork, and other "originalists," explaining in clear, jargon-free English how the Constitution can sensibly evolve, without falling into the anything-goes flexibility caricatured by opponents. The living Constitution is not an out-of-touch liberal theory, Strauss further shows, but a mainstream tradition of American jurisprudence--a common-law approach to the Constitution, rooted in the written document but also based on precedent. Each generation has contributed precedents that guide and confine judicial rulings, yet allow us to meet the demands of today, not force us to follow the commands of the long-dead Founders. Strauss explores how judicial decisions adapted the Constitution's text (and contradicted original intent) to produce some of our most profound accomplishments: the end of racial segregation, the expansion of women's rights, and the freedom of speech. By contrast, originalism suffers from fatal flaws: the impossibility of truly divining original intent, the difficulty of adapting eighteenth-century understandings to the modern world, and the pointlessness of chaining ourselves to decisions made centuries ago. David Strauss is one of our leading authorities on Constitutional law--one with practical knowledge as well, having served as Assistant Solicitor General of the United States and argued eighteen cases before the United States Supreme Court. Now he offers a profound new understanding of how the Constitution can remain vital to life in the twenty-first century.
