وبلاگ بلیان

Software Testing: Testing Across the Entire Software Development Life Cycle

جلد کتاب Software Testing: Testing Across the Entire Software Development Life Cycle

معرفی کتاب «Software Testing: Testing Across the Entire Software Development Life Cycle» نوشتهٔ McLeod R.، منتشرشده توسط نشر Addison Wesley Professional Pearson Education [distributor در سال 2007. این کتاب در فرمت pdf، زبان انگلیسی ارائه شده است.

One of the first comprehensive guides to testing every phase of software development and revisionBusinesses lose billions of dollars every year due to poorly tested software, and the body of professional software testers is grossly underpopulated. Now, Software Testing delivers a thorough treatment of everything a technology professional needs to become a proficient software tester. The presentation sequence builds from simple to complex examples, giving novice readers a foundation for grasping the material. The use of real-world case studies further enhances understanding, while diagrams, tables, and sample printouts help the reader to visualize the processes being discussed.Divided into four parts, this book provides: * An overview of software testing * A review of software development life cycles * Structured testing strategies and approaches * A complete life cycle software testing projectIdeal for graduate-level students of computer science and management information systems, this resourceful book also includes a companion Web site with tools and additional examples.

Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask: "How exactly am I supposed to write use cases?" Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable.

In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a "nuts-and-bolts" tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises—with answers—to illuminate the most important points.

Highlights of the book include:

  • A thorough discussion of the key elements of use cases—actors, stakeholders, design scope, scenarios, and more
  • A use case style guide with action steps and suggested formats
  • An extensive list of time-saving use case writing tips
  • A helpful presentation of use case templates, with commentary on when and where they should be employed
  • A proven methodology for taking advantage of use cases

With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.

Booknews

A specialist in object technology presents software developers with a current guide to writing use cases as a means of capturing the behavioral requirements of software systems and business practices. Covers key elements of use cases, a style guide with suggested formats, a list of time-saving writing tips, a set of use case templates with commentary, and learning exercises with answers to clarify important points. Annotation c. Book News, Inc., Portland, OR (booknews.com)

Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask:'How exactly am I supposed to write use cases?'Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable. In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a'nuts-and-bolts'tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises--with answers--to illuminate the most important points. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.

"This is the single best book on software quality engineering and metrics that I've encountered."
—Capers Jones, from the Foreword

Metrics and Models in Software Quality Engineering, Second Edition, is the definitive book on this essential topic of software development. Comprehensive in scope with extensive industry examples, it shows how to measure software quality and use measurements to improve the software development process. Four major categories of quality metrics and models are addressed: quality management, software reliability and projection, complexity, and customer view. In addition, the book discusses the fundamentals of measurement theory, specific quality metrics and tools, and methods for applying metrics to the software development process.

New chapters bring coverage of critical topics, including:

  • In-process metrics for software testing
  • Metrics for object-oriented software development
  • Availability metrics
  • Methods for conducting in-process quality assessments and software project assessments
  • Dos and Don'ts of Software Process Improvement, by Patrick O'Toole
  • Using Function Point Metrics to Measure Software Process Improvement, by Capers Jones

In addition to the excellent balance of theory, techniques, and examples, this book is highly instructive and practical, covering one of the most important topics in software development—quality engineering.

Though many books discuss software quality, this is the first book to integrate metrics with models and quality improvement strategies, and action plans with project experiences. Covering essential issues and techniques, Kan provides all the information needed to measure and improve the quality of the entire software development process from high-level to low-level design, and all phases of reliability.

protect Your Company's Web Site From Hack Attacks With This Guide To Proven Security-testing Techniques

it's Only A Matter Of Time Before An Unscrupulous Would-be Intruder Decides To Attack Your Organization's Web Site. If They're Successful, You Could Lose Confidential Customer Information, Intellectual Property, Or E-commerce Revenue. Fortunately, This Unique Book Describes A Set Of Security Tests That You Can Perform To Ensure Your Web Site Is Hack-resistant. Web Testing Expert Steven Splaine Offers A Straightforward, Easy-to-follow Approach To Security Testing That Can Be Used To Check Your Web Site's Vulnerabilities. Through Examples And Dozens Of Testing Checklists, You'll Learn How To Develop And Document A Test Plan To Test The Security Of A Web Site And Conduct A Risk Analysis To Help Determine Which Tests Should Be Given The Highest Priority.

following A Straightforward, Accessible Approach, This Book Will Take You Step-by-step Through The Process Of Testing The Security Of Your Web Sites And Applications. Whether You're A Software Tester, System Administrator, Developer, Manager, Web Master, Or Security Engineer, You'll Find Valuable Information On How To Use Testing As A Security Measure. In This Informative Book, Steven Splaine Covers:

* Planning The Security Testing Effort: Strategies, Teams, And Tools

* How To Define The Scope Of The Project

* Testing Network Security And System Software Configurations

* Checking For Security Vulnerabilities In Web Applications

* Evaluating How Well-prepared An Organization Is Against Assailants Who Use Social Engineering, Dumpster Diving, Inside Accomplices, Or Physical Methods Of Attack

* The Unique Challenges Of Testing Defenses Designed To Confuse An Intruder

* Using A Risk Analysis To Focus The Testing Effort On The Areas That Present The Greatest Threats To The Organization

How to Break Software is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. The testing techniques in this book are as flexible as conventional testing is rigid. And flexibility is needed in software projects in which requirements can change, bugs can become features and schedule pressures often force plans to be reassessed. Software testing is not such an exact science that one can determine what to test in advance and then execute the plan and be done with it. Instead of a plan, intelligence, insight, experience and a "nose for where the bugs are hiding" should guide testers. This book helps testers develop this insight. The techniques presented in this book not only allow testers to go off-script, they encourage them to do so. Don't blindly follow a document that may be out of date and that was written before the product was even testable. Instead, use your head! Open your eyes! Think a little, test a little and then think a little more. This book does teach planning, but in an "on- the-fly while you are testing" way. It also encourages automation with many repetitive and complex tasks that require good tools (one such tool is shipped with this book on the companion CD). However, tools are never used as a replacement for intelligence. Testers do the thinking and use tools to collect data and help them explore applications more efficiently and effectively. Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use Cases , Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations. Cockburn begins by answering the most basic questions facing anyone interested in use cases: "What does a use case look like? When do I write one?" Next, he introduces each key element of use cases: actors, stakeholders, design scope, goal levels, scenarios, and more. Writing Effective Use Cases contains detailed guidelines, formats, and project standards for creating use cases -- as well as a detailed chapter on style, containing specific do's and don'ts. Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals. The book includes practice exercises with solutions, as well as a detailed appendix on how to use these techniques with UML. For all application developers, object technology practitioners, software system designers, architects, and analysts. It's only a matter of time before an unscrupulous would-be intruder decides to attack your organization's Web site. If they're successful, you could lose confidential customer information, intellectual property, or e-commerce revenue. Fortunately, this unique book describes a set of security tests that you can perform to ensure your Web site is hack-resistant. Web testing expert Steven Splaine offers a straightforward, easy-to-follow approach to security testing that can be used to check your Web site's vulnerabilities. Through examples and dozens of testing checklists, you'll learn how to develop and document a test plan to test the security of a Web site and conduct a risk analysis to help determine which tests should be given the highest priority. Following a straightforward, accessible approach, this book will take you step-by-step through the process of testing the security of your Web sites and applications. Whether you're a software tester, system administrator, developer, manager, Web master, or security engineer, you'll find valuable information on how to use testing as a security measure. Our society has become increasingly reliant on software in the past decade; businesses have learned that measuring the effectiveness of software projects can impact the bottom line; and quality is no longer an advantage in the software marketplace (it is a necessity). For these reasons, the demand for quality in software engineering has taken center stage in the twenty-first century. In this new edition, Stephen Kan presents a thoroughly updated overview and implementation guide for software engineers faced with the challenge of ensuring quality. The book balances theory, techniques, and real-life examples to provide practical guidelines in the practice of quality. Although there are equations and formulas presented, the book's focus remains on helping the reader understand and apply the metrics and models. With this book as a map, readers can navigate through the complex field of quality, and benefit their organization by improving their processes and products. The definitive book on this essential topic of software development. Comprehensive in scope with extensive industry examples, it shows how to measure software quality and use measurements to improve the software development process. Four major categories of quality metrics and models are addressed: quality management, software reliability and projection, complexity, and customer view. In addition, the books discusses the fundamentals of measurement theory, specific quality metrics and tools, and methods for applying metrics to the software development process. -- from the back cover "How to Break Software takes a very applied and non-rigid approachto showing how to test software for common bugs. It is a departure from conventional testing in which testers prepare a written test plan and then use it as a script when testing the software. This book will teach you how to plan tests "on-the-fly" by providing ou with the insight, experience, and a "nose for where bugs are hiding" that all great testers have developed"--Back cover Takes an applied approach to teaching how to test software for common bugs. Instead of relying on a rigid plan, it should be intelligence, insight, experience and a "nose for where the bugs are hiding" that guide testers. This book helps testers develop this insight. The techniques presented here allow testers to go off-script. Covers security basics and guides reader through the process of testing a Web site. Explains how to analyze results and design specialized follow-up tests that focus on potential security gaps. Teaches the process of discovery, scanning, analyzing, verifying results of specialized tests, and fixing vulnerabilities. This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts
دانلود کتاب Software Testing: Testing Across the Entire Software Development Life Cycle