Praise for Software Test Engineering with IBM Rational Functional Tester The Indispensable Resource for Automated Testing Automated software testing has become a critical exercise, especially for developers utilizing iterative and agile methods. However, to achieve the full benefits of automated testing, teams need a deep understanding of both its principles and their testing tools. If you’re among the thousands of developers using IBM Rational Functional Tester (RFT), this book brings together all the insight, examples, and real-world solutions you need to succeed. Eight leading IBM testing experts thoroughly introduce this state-of-the-art product, covering issues ranging from building test environments through executing the most complex and powerful tests. Drawing on decades of experience with IBM Rational testing products, they address both technical and nontechnical challenges and present everything from best practices to reusable code. Coverage Includes Integrating IBM RFT into your development processes Building highly efficient test environments, test harnesses, and test scripts Using RFT Visual Editor to extend testing automation to novice users Mastering basic scripting techniques, from data capture to script synchronization Managing script data using RFT Datapools Efficiently debugging scripts using EclipseTM or Visual Studio® Managing execution flow: playback settings, logic, error handling, and more Handling domains that are not supported by RFT Using advanced techniques, such as mouse delays and custom verification pointsTesting specialized software, including mainframe, SAP, Siebel, and Adobe® Flex® applications Extending RFT with external libraries Developing RFT support for third-party JavaTM or .NET controls Using RFT in both Linux® and Windows® environments Configuring internationalized testing within the RFT framework

The authoritative guide to DAD, IBM's disciplined approach to applying agile practices in enterprise scale projects. Integrate enterprise discipline with powerful, widely-used agile practices into a proven solution for the entire software lifecycle. Scale agile strategies for complex development challenges, without compromising agile's advantages.

Break the Old, Waterfall Habits that Hinder Agile Success: Drive Rapid Value and Continuous Improvement When agile teams don't get immediate results, it's tempting for them to fall back into old habits that make success even less likely. In Being Agile, Leslie Ekas and Scott Will present eleven powerful techniques for rapidly gaining substantial value from agile, making agile methods stick, and launching a "virtuous circle" of continuous improvement. Drawing on their experience helping more than 100 teams transition to agile, the authors review its key principles, identify corresponding practices, and offer breakthrough approaches for implementing them. Using their techniques, you can break typical waterfall patterns and go beyond merely "doing agile" to actually thinking and being agile. Ekas and Will help you clear away silos, improve stakeholder interaction, eliminate waste and waterfall-style inefficiencies, and lead the agile transition far more successfully. Each of their eleven principles can stand on its own: when you combine them, they become even more valuable. Coverage includes Building "whole teams" that cut across silos and work together throughout a product's lifecycle Engaging product stakeholders earlier and far more effectively Overcoming inefficient "waterations" and "big batch" waterfall thinking Getting past the curse of multi-tasking Eliminating dangerous technical and project debt Repeatedly deploying "release-ready" software in real user environments Delivering what customers really need, not what you think they need Fixing the root causes of problems so they don't recur Learning from experience: mastering continuous improvement Assessing whether you're just "doing agile" or actually "being agile" Being Agile will be indispensable for all software professionals now adopting agi≤ for coaches, managers, engineers, and team members who want to get more value from it and for students discovering it for the first time.

Testing IT provides a complete, off-the-shelf software testing process framework for any testing practitioner who is looking to research, implement, roll out, adopt, and maintain a software testing process. It covers all aspects of testing for software developed or modified in-house, modified or extended legacy systems, and software developed by a third party. Software professionals can customize the framework to match the testing requirements of any organization, and six real-world testing case studies are provided to show how other organizations have done this. Packed with a series of real-world case studies, the book also provides a comprehensive set of downloadable testing document templates, proformas, and checklists to support the process of customizing. This new edition demonstrates the role and use of agile testing best practices and includes a specific agile case study.

This book is about software product lines (SPLs) designed and developed taking UML diagrams as the primary basis, modeled according to a rigorous approach composed of an UML profile and a systematic process for variability management activities, forming the Stereotype-based Management of Variability (SMarty) approach. The book consists of five parts. Part I provides essential concepts on SPL in terms of the first development methodologies. It also introduces variability concepts and discusses SPL architectures finishing with the SMarty approach. Part II is focused on the design, verification and validation of SMarty SPLs, and Part III concentrates on the SPL architecture evolution based on ISO/IEC metrics, the SystEM-PLA method, optimization with the MOA4PLA method, and feature interaction prevention. Next, Part IV presents SMarty as a basis for SPL development, such as, the M-SPLearning SPL for mobile learning applications, the PLeTs SPL for testing tools, the PlugSPL plugin environment for supporting the SPL life cycle, the SyMPLES approach for designing embedded systems with SysML, the SMartySPEM approach for software process lines (SPrL), and re-engineering of class diagrams into an SPL. Eventually, Part V promotes controlled experimentation in UML-based SPLs, presenting essential concepts on how to plan, conduct, and document experiments, as well as showing several experiments carried out with SMarty. This book aims at lecturers, graduate students and experienced practitioners. Lecturers might use the book for graduate level courses about SPL fundamentals and tools; students will learn about the SPL engineering process, variability management, and mass customization; and practitioners will see how to plan the transition from single-product development to an SPL-based process, how to document inherent variability in a given domain, or how to apply controlled experiments to SPLs.

"If you'd like a glimpse at how the next generation is going to program, this book is a good place to start." —Gregory V. Wilson, Dr. Dobbs Journal (October 2004) Build Your Own Automated Software Testing Tool Whatever its claims, commercially available testing software is not automatic. Configuring it to test your product is almost as time-consuming and error-prone as purely manual testing. There is an alternative that makes both engineering and economic sense: building your own, truly automatic tool. Inside, you'll learn a repeatable, step-by-step approach, suitable for virtually any development environment. Code-intensive examples support the book's instruction, which includes these key topics: Conducting active software testing without capture/replay Generating a script to test all members of one class without reverse-engineering Using XML to store previously designed testing cases Automatically generating testing data Combining Reflection and CodeDom to write test scripts focused on high-risk areas Generating test scripts from external data sources Using real and complete objects for integration testing Modifying your tool to test third-party software components Testing your testing tool Effective Software Test Automation goes well beyond the building of your own testing tool: it also provides expert guidance on deploying it in ways that let you reap the greatest benefits: earlier detection of coding errors, a smoother, swifter development process, and final software that is as bug-free as possible. Written for programmers, testers, designers, and managers, it will improve the way your team works and the quality of its products.

IBM® has long been recognized as a leading provider of hardware, software, and services that are of the highest quality, reliability, function, and integrity. IBM products and services are used around the world by people and organizations with mission-critical demands for high performance, high stress tolerance, high availability, and high security. As a testament to this long-standing attention at IBM, demonstration of this attention to security can be traced back to the Integrity Statement for IBM mainframe software, which was originally published in 1973: IBM's long-term commitment to System Integrity is unique in the industry, and forms the basis of MVS (now IBM z/OS) industry leadership in system security. IBM MVS (now IBM z/OS) is designed to help you protect your system, data, transactions, and applications from accidental or malicious modification. This is one of the many reasons IBM 360 (now IBM Z) remains the industry's premier data server for mission-critical workloads. This commitment continues to apply to IBM's mainframe systems and is reiterated at the Server RACF General User's Guide web page. The IT market transformed in 40-plus years, and so have product development and information security practices. The IBM commitment to continuously improving product security remains a constant differentiator for the company. In this IBM RedguideTM publication, we describe secure engineering practices for software products. We offer a description of an end-to-end approach to product development and delivery, with security considered. IBM is producing this IBM Redguide publication in the hope that interested parties (clients, other IT companies, academics, and others) can find these practices to be a useful example of the type of security practices that are increasingly a must-have for developing products and applications that run in the world's digital infrastructure. We also hope this publication can enrich our continued collaboration with others in the industry, standards bodies, government, and elsewhere, as we seek to learn and continuously refine our approach.

"By incorporating systematic controls throughout the development process, the methods in Client-Server Software Testing on the Desktop and the Web can help any organization save time and money while building in quality for distributed systems."--BOOK JACKET.