Every software project that has ever careened off the rails, blown its budget, or shipped a defective product to an embarrassed client had one thing in common: insufficient review. The uncomfortable truth about software development is that defects found late cost exponentially more to fix than defects found early — and most defects are found late because the teams involved either skipped the review process entirely, or conducted it badly.
Software Reviews & Audits: A How To Guide for Project Staff is the book that fixes that problem. Written by David Tuffley and grounded in the authoritative framework of IEEE Standard 1028, it is a comprehensive, practical, and immediately actionable guide to the full suite of review and audit activities that any serious software project demands. This is not a book of vague principles. It is a handbook — the kind you keep on your desk and consult before you chair a review meeting, not the kind you put on a shelf and reference in a footnote.
The book covers five distinct review types, each serving a different purpose at a different point in the project lifecycle. Management reviews assess whether a project is tracking to plan — covering schedule, resources, budget, and risk at the phase level. Technical reviews bring a formal team to bear on specific documents or software modules, verifying that content is correct, standards are met, and defects are identified and logged before they become embedded problems. Walkthroughs offer a more collaborative, improvement-focused approach, encouraging teams to explore alternatives and catch issues while development is still fluid. Audits provide the independent, objective evidence of compliance that clients, regulators, and quality managers require. And inspections — the most rigorous mechanism in the toolkit — apply systematic formal analysis to completed work, identifying defects with the precision that informal review simply cannot match.
What distinguishes this guide is its granularity. For each review type, Tuffley walks the reader through initiation, staffing, notification, input requirements, conduct, agenda structure, exit decisions, and follow-up actions. Nothing is assumed; nothing is glossed over. You will know exactly who needs to be in the room, how much notice they require, what material must be circulated beforehand, and what the three possible exit decisions mean and how to apply them. The roles — review leader, recorder, reviewer, author — are defined with a clarity that eliminates the ambiguity that so often causes reviews to drift into unproductive territory.
The book also addresses the practical texture of review management: how to maintain a review status register, when to conduct partial rather than complete reviews, what constitutes a major defect versus a minor one, and how to write a review summary report that actually drives action rather than gathering dust.
Particularly valuable is the book's treatment of the audit process — the most externally facing of all the review types. Tuffley provides a complete audit plan template covering background, objectives, scope, definitions, project processes, module identification, reporting requirements, distribution, follow-up, objective audit criteria, and budget. It is a framework that an audit leader could pick up and use immediately.
Appendices covering issue types, classification schemes, and severity ratings round out a reference that leaves nothing to chance.
If you manage software projects, develop software, work in quality assurance, or carry any responsibility for the integrity of a software deliverable, this book belongs in your professional library. It will not merely improve your review process — it will give you one worth having.
"synopsis" may belong to another edition of this title.
David Tuffley PhD is lecturer and researcher at Griffith University in Australia. David is a Software Engineer, though his interests range across Comparative Religion, Philosophy, Psychology, Anthropology, Literature, History, Design and Architecture. David has been an academic since 1999. For 15 years before academia David was a consultant for public and private sector IT clients in Australia and the United Kingdom. He combines theory and practice in a focussed and disciplined way that has proved effective for solving problems for clients.
"About this title" may belong to another edition of this title.
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947768
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: New. Seller Inventory # 20947768-n
Seller: California Books, Miami, FL, U.S.A.
Condition: New. Print on Demand. Seller Inventory # I-9781461130468
Seller: PBShop.store US, Wood Dale, IL, U.S.A.
PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461130468
Seller: PBShop.store UK, Fairford, GLOS, United Kingdom
PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461130468
Quantity: Over 20 available
Seller: Ria Christie Collections, Uxbridge, United Kingdom
Condition: New. In. Seller Inventory # ria9781461130468_new
Quantity: Over 20 available
Seller: THE SAINT BOOKSTORE, Southport, United Kingdom
Paperback / softback. Condition: New. This item is printed on demand. New copy - Usually dispatched within 5-9 working days. Seller Inventory # C9781461130468
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: New. Seller Inventory # 20947768-n
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947768
Quantity: Over 20 available
Seller: CitiRetail, Stevenage, United Kingdom
Paperback. Condition: new. Paperback. I N T R O D U C T I O NHow to Perform Reviews & Audits is a plain-english, simplified version of IEEE Std 1028-1988 - Standard for Software Reviews and Audits.This how to guide encompasses the range of review and audit activities undertaken during a project.Reviews and audits comprise the following five modules: Management review. The formal evaluation of a project level plan or project status relative to that plan by a designated review team.Technical review. The evaluation of specified software modules and documents aimed at ensuring that the software modules and documents comply with the applicable standards while conforming to the specifications. The tech-nical review may provide recommendations after the exami-nation of alternatives.Walkthrough. An evaluation process that can result in recommendations for improvement or identification of alternatives to the current software modules or documents being developed.Audit. Provide objective evidence of compliance of products and processes with standards, guidelines, specifications and procedures. Includes audits of the quality management system.Inspection. Rigorous formal evaluations designed to detect and identify defects in the reviewed material. Normally conducted after the event and initiated by persons outside of the project team. S C O P EHow to Perform Reviews & Audits applies to all project documents, software conduct specific reviews or audits - that need is defined by the project and quality plans. Also applies to the audit of the quality management system.O B J E C T I V E SHow to Perform Reviews & Audits provides definitions and uniform requirements to enable project staff to perform the necessary reviews and audits of products and processes.Contribution to IS Quality. An essential element in the development of project documentation is the verification and validation that their contents are true and accurate. It is recognised in the literature of software quality that the authors of documents and code inherently do not wish to find errors in their own work. They will often consciously or unconsciously overlook errors and inaccuracies. It is therefore not advisable to leave the review of project documentation to those who produce it. It is important for such checking to conducted in a consistent and systematic manner. If this is done, project documentation will serve the development process in the way in which they are intended.This how to guide is an valuable aid for project and quality managers to address the important process of performing reviews and audits. It is is an easy to use checklist, as defined by IEEE Std 1028, and template to achieve this end This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Seller Inventory # 9781461130468
Quantity: 1 available