Every software project carries a quiet, persistent anxiety: the fear that something has been missed. A feature quietly broken. An edge case never tested. A handoff poorly documented. The consequences range from embarrassing to catastrophic — and yet, in project teams around the world, testing documentation remains the discipline most likely to be improvised, deferred, or quietly abandoned under deadline pressure.
Software Test Plans: A How-To Guide for Project Staff exists to close that gap.
Grounded in the rigorous framework of IEEE Standard 829 — the gold standard for software test documentation — this book does something rare in technical literature: it makes a complex, multi-layered standard genuinely accessible. David Tuffley distils the full apparatus of professional software testing into a practical, clearly structured guide that any project team member can follow, whether they are a seasoned test engineer or a developer writing their first formal test plan.
The book maps the complete documentation lifecycle of a software testing program. It begins with the Test Plan itself — the governing document that defines what will be tested, how it will be tested, by whom, and by when. From there, Tuffley walks readers through each document in the testing suite: the Test Design Specification, which translates strategy into specific test scenarios; the Test Case, which pins down inputs, expected outputs, and pass/fail criteria with precision; and the Test Procedure Specification, the step-by-step operational guide that sits in a tester's hands during execution.
The book then turns to the accountability trail — the documents that prove testing actually happened and record everything that went wrong. The Test Item Transmittal Report governs what enters the test environment. The Test Log captures events as they unfold. The Test Incident Report formalises the investigation of anomalies, triggering corrective action. And the Test Summary Report closes the loop: a management-facing synthesis of results, variances, and quality assessments that gives leadership the evidence they need to make confident release decisions.
Throughout, Tuffley is careful to anchor each document in the software development lifecycle — explaining not just what to write, but when to write it and why it matters at that precise moment in the project. The result is a guide that reads less like a standard and more like a conversation with a knowledgeable colleague who has seen what happens when documentation is done well and what happens when it isn't.
The definitions section alone is worth the price of admission. White box testing versus black box testing. Bottom-up versus top-down strategies. Integration testing versus system testing versus acceptance testing. These distinctions are explained with clarity and economy, giving readers the conceptual vocabulary to participate meaningfully in testing discussions at any level of the organisation.
What separates this book from dry compliance manuals is its orientation toward the practical human reality of software projects: the project manager who needs a baseline for performance measurement; the quality assurance manager who must demonstrate process compliance; the test team that needs step-by-step guidance without extraneous clutter; the customer who must formally accept the product and needs evidence that justifies that confidence.
Software testing is not the glamorous end of development. But it is the end where quality is either confirmed or compromised. This book gives every member of a project team the tools to get it right — systematically, repeatably, and with the documentation to prove it.
Die Inhaltsangabe kann sich auf eine andere Ausgabe dieses Titels beziehen.
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.
„Über diesen Titel“ kann sich auf eine andere Ausgabe dieses Titels beziehen.
Anbieter: GreatBookPrices, Columbia, MD, USA
Zustand: As New. Unread book in perfect condition. Bestandsnummer des Verkäufers 20947764
Anzahl: Mehr als 20 verfügbar
Anbieter: GreatBookPrices, Columbia, MD, USA
Zustand: New. Bestandsnummer des Verkäufers 20947764-n
Anzahl: Mehr als 20 verfügbar
Anbieter: California Books, Miami, FL, USA
Zustand: New. Print on Demand. Bestandsnummer des Verkäufers I-9781461127741
Anzahl: Mehr als 20 verfügbar
Anbieter: PBShop.store US, Wood Dale, IL, USA
PAP. Zustand: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Bestandsnummer des Verkäufers L0-9781461127741
Anzahl: Mehr als 20 verfügbar
Anbieter: PBShop.store UK, Fairford, GLOS, Vereinigtes Königreich
PAP. Zustand: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Bestandsnummer des Verkäufers L0-9781461127741
Anzahl: Mehr als 20 verfügbar
Anbieter: Ria Christie Collections, Uxbridge, Vereinigtes Königreich
Zustand: New. In. Bestandsnummer des Verkäufers ria9781461127741_new
Anzahl: Mehr als 20 verfügbar
Anbieter: THE SAINT BOOKSTORE, Southport, Vereinigtes Königreich
Paperback / softback. Zustand: New. This item is printed on demand. New copy - Usually dispatched within 5-9 working days. Bestandsnummer des Verkäufers C9781461127741
Anzahl: Mehr als 20 verfügbar
Anbieter: GreatBookPricesUK, Woodford Green, Vereinigtes Königreich
Zustand: New. Bestandsnummer des Verkäufers 20947764-n
Anzahl: Mehr als 20 verfügbar
Anbieter: GreatBookPricesUK, Woodford Green, Vereinigtes Königreich
Zustand: As New. Unread book in perfect condition. Bestandsnummer des Verkäufers 20947764
Anzahl: Mehr als 20 verfügbar
Anbieter: CitiRetail, Stevenage, Vereinigtes Königreich
Paperback. Zustand: new. Paperback. I N T R O D U C T I O NHow to Write Software Project Plans is a plain-english, simplified version of IEEE 1058 - Standard for Software Project Management Plans.The project plan documents the planning work necessary to conduct, track and report on the progress of a project. It contains a full description of how the work will be performed.The benefit of using this how to guide is the consistency of presentation, enabling management to assess the plans, for their merits or limitations, more readily. In particular this how to guide specifies the format and content for a project plan by defining the minimal set of elements that shall appear in all project plans (additional sections may be ap-pended as required).The project plan includes the: - scope and objectives of the project - deliverables the project will produce - process which shall be employed to produce those deliverables - time frame and milestones for the production of the deliverables - organisation and staffing which will be established - responsibilities of those involved - work steps to be undertaken - budget S C O P EHow to Write Software Project Plans applies to the medium to large scale software development projects.O B J E C T I V E SHow to Write Software Project Plans allows the project manager to: consider all relevant aspects of the project, ensuring they will be considered during the project planning stageproduce project plans with consistent content and formatclarify the objectives, deliverables and manner of execution of the projectContribution to IS Quality. The literature of software quality widely recognises that up to 70% of IT development projects fail (in terms of either not being completed, or completed but not used by the client due to it unsuitability). One of the major contributing factors to this alarming situation is that the project was not planned comprehensively enough.While it is not possible to foresee every misfortunes that might possibly befall a project, there are nonetheless a well-defined set of actions and attributes which if employed in the planning stage can result in all foreseeable matters being addressed. This how to guide is an easy to use checklist, as defined by IEEE 1058, and template to achieve this end. It embodies the principle of failing to plan is planning to fail.In the same way as a systematic and comprehensive Statement of User Requirements can capture a more complete set of requirements, a project plan as provided by this how to guide allows the project manager to make sure he/she has considered all relevant matters in the planning stage, allowing them to avoid, as far as possible, unpleasant surprizes later This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Bestandsnummer des Verkäufers 9781461127741
Anzahl: 1 verfügbar