Author: William H. Puryear
Publisher:
ISBN:
Category : Specification writing
Languages : en
Pages : 250

View

Book Description

Author: United States. Federal Highway Administration
Publisher:
ISBN:
Category : Bridge construction contracts
Languages : en
Pages : 372

View

Book Description

Author: United States. Department of Defense
Publisher:
ISBN:
Category : Specification writing
Languages : en
Pages : 186

View

Book Description

Author: Gojko Adzic
Publisher: Simon and Schuster
ISBN: 1638351368
Category : Computers
Languages : en
Pages : 346

View

Book Description
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

Author: Wisconsin. Department of Transportation
Publisher:
ISBN:
Category : Bridges
Languages : en
Pages : 44

View

Book Description

Author: American Association of State Highway and Transportation Officials. Task Force for Roadside Safety
Publisher:
ISBN:
Category : Roads
Languages : en
Pages : 560

View

Book Description

Author: William H. Puryear
Publisher:
ISBN:
Category : Specification writing
Languages : en
Pages : 0

View

Book Description

Author: Ken Skorseth
Publisher:
ISBN:
Category : Gravel roads
Languages : en
Pages : 112

View

Book Description
The purpose of this manual is to provide clear and helpful information for maintaining gravel roads. Very little technical help is available to small agencies that are responsible for managing these roads. Gravel road maintenance has traditionally been "more of an art than a science" and very few formal standards exist. This manual contains guidelines to help answer the questions that arise concerning gravel road maintenance such as: What is enough surface crown? What is too much? What causes corrugation? The information is as nontechnical as possible without sacrificing clear guidelines and instructions on how to do the job right.

Author: Mario Cardinal
Publisher: Addison-Wesley
ISBN: 0132776510
Category : Computers
Languages : en
Pages : 243

View

Book Description
Most books about specifications still assume that requirements can be known up front and won’t change much during your project. In today’s “real world,” however, you must specify and build software in the face of high and continuing uncertainty. Scrum and other agile methods have evolved to reflect this reality. Now, there’s a complete guide to specifying software in agile environments when prerequisites are unclear, requirements are difficult to grasp, and anything about your project could change. Long-time agile coach and enterprise architect Mario Cardinal shows how to create executable specifications and use them to test software behavior against requirements. Cardinal shows how to trawl requirements incrementally, step-by-step, using a vision-centric and emergent iterative practice that is designed for agility. Writing for analysts, architects, developers, and managers, Cardinal makes a strong case for the iterative discovery of requirements. Then, he moves from theory to practice, fully explaining the technical mechanisms and empirical techniques you need to gain full value from executable specifications. You’ll learn to connect specifications with software under construction, link requirements to architecture, and automate requirements verification within the Scrum framework. Above all, Cardinal will help you solve the paramount challenge of software development: not only to solve the problem right, but also to solve the right problem. You will learn how to • Establish more effective agile roles for analysts and architects • Integrate and simplify the best techniques from FIT, ATDD, and BDD • Identify “core certainties” on which your project team should rely to ensure requirements discovery • Manage uncertainty by discovering stakeholder desires through short feedback loops • Specify as you go while writing small chunks of requirements • Use storyboarding and paper prototyping to improve conversations with stakeholders • Express stakeholder desires that are requirements with user stories • Refine your user stories, and plan more effective Scrum sprints • Confirm user stories by scripting behaviors with scenarios • Transform scenarios into automated tests that easily confirm your software’s expected behavior as designs emerge and specifications evolve • Ensure higher-quality software by specifying nonfunctional requirements

Author: Harold J. Rosen
Publisher: Wiley-Interscience
ISBN:
Category : Architecture
Languages : en
Pages : 312

View

Book Description
This third edition of the standard construction specifications writing guide has been updated to include new information on linking specifications to computer databases and to other parts of the design process. Construction Specifications Writing shows how to organize documents, consolidate the Federal government systems, generate well-researched mastertexts, automate specifications, write more condensed text, use full-time specifications consultants, and use the new knowledge-based specifying systems.