Software Requirement Patterns: Foreword by Karl E. Wiegers (Best Practices)
Book 9 of 23: Developer Best PracticesWithall, Stephen
Used - Soft cover
Condition: Used - Good
Ships from Germany to U.S.A.
Quantity: 1 available
Add to basketCondition: Used - Good
Quantity: 1 available
Add to basketBefriedigend/Good: Durchschnittlich erhaltenes Buch bzw. Schutzumschlag mit Gebrauchsspuren, aber vollständigen Seiten. / Describes the average WORN book or dust jacket that has all the pages present.
Seller Inventory # M00735623988-G
Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification.
A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it’s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need―determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs―giving developers the valuable advice they need for building effective software requirements
Stephen J. Withall has been developing and specifying software systems for more than 26 years in a variety of roles: programmer, analyst/programmer, team leader, systems analyst, business analyst, project manager, systems architect, and chief technical officer. He has worked in diverse environments in companies big and small, in 17 countries across four continents. He has used object-oriented design approaches and technology for more than 16 years, and actively maintains his hands-on software development skills.
"About this title" may belong to another edition of this title.
1. Scope
For all orders via our store on the AbeBooks Marketplace, the following terms and conditions apply. Unless otherwise agreed, the inclusion of any terms and conditions of your own used by you is contradicted.
2. contracting party, conclusion of contract, correction options
The purchase contract is concluded with momox SE.
The subject of the contract is the sale of goods.
If an article is posted by us on AbeBooks, the activation of the offer page on AbeBooks is the binding offer to conclu...
| Order quantity | 10 to 20 business days | 10 to 20 business days |
|---|---|---|
| First item | US$ 11.34 | US$ 22.68 |
Delivery times are set by sellers and vary by carrier and location. Orders passing through Customs may face delays and buyers are responsible for any associated duties or fees. Sellers may contact you regarding additional charges to cover any increased costs to ship your items.