Skip to main content

Rational Business Driven Development for Compliance

An IBM Redbooks publication

Note: This is publication is now archived. For reference only.

thumbnail 

Published on 08 November 2006, updated 08 November 2006

  1. .PDF (3.7 MB)


Share this page:   

ISBN-10: 073849657X
ISBN-13: 9780738496573
IBM Form #: SG24-7244-00


Authors: Ueli Wahli, Majid Irani, Ana Negrello, Celio Palma, Jason Smith and Matt Magee

    menu icon

    Abstract

    This IBM Redbooks publication is intended to help you design your processes and solutions using Rational products to manage compliance. It shows how Rational solutions can be applied by an organization to realize a controlled, auditable software development environment to help alleviate specific challenges imposed by standards, policies, and regulations.

    This book provides a usage model and product configuration guidance to help a tools administrator implement and configure some or all of the Rational tools to address compliance challenges. This book is intended help you and your partners understand the design and deployment of IBM Rational’s Business Driven Development for Compliance solution.

    This book focuses on problems addresses by Rational products. The emphasis is on auditable change processes, in particular using ClearQuest and ClearCase. We provide additional coverage of requirements for compliance using RequisitePro, and compliance attestation using ClearQuest Test Manager, IT governance using Rational Portfolio Manager, Rational Method Composer, and the Rational Unified Process (RUP).

    This book presents a solution for compliance management that demonstrates support of all three dimensions of business driven development of software for compliance, say what you do, do what you say, and be able to prove it.

    Table of Contents

    Chapter 1. A discussion about compliance

    Chapter 2. Compliance guidelines

    Chapter 3. IBM Rational's key capabilities for compliance management

    Chapter 4. Roadmap to compliance management

    Appendix A. Unified Method Architecture

     

    Others who read this also read