This document provides an overview of using Rational Requirements Composer to organize design-driven development. It discusses the importance of requirements and outlines how Rational Requirements Composer can be configured to store requirements, wireframes, cities, categories, and data sources for a project. Real-world examples are shown of how wireframes, requirements, and unique data can be represented in Rational Requirements Composer to facilitate traceability between different project elements.

1. Organizing Design-Driven
Development Using Rational
Requirements Composer
Kurt Solarte
Managing Consultant, IBM I N T E R A C T I V E
ksolarte@us.ibm.com
RDM-1625
The premiere software and product delivery event.
June 6–10 Orlando, Florida

2. 2
Agenda
Overview of Design-Driven Development
Importance of Requirements
Brief Summary of Interactive Web Project: CityForward.org
Overview of Rational Requirements Composer Configuration
Real-World Example of Requirements with Visio Wireframes
Real-World Example of Requirements with Rational Requirements Composer
Real-World Example of Unique Data Use for Rational Requirements Composer
Questions

3. Design-Driven Development (D3)
Design Driven Development (D3) is a simple, agile-based approach for building
innovative solutions. It adds another dimension to overall software development by
bringing design, usability and innovation to the center stage. It is based on the
following principles:
Designfullness and Dreamfulfillment are the new mantra for business success.
Design is an accident that kicks in at conception, maximizing the opportunities to make
accidents happen is the key for innovation.
No process can guarantee better design. Creating a right environment with right set of
people is the only way to bring innovation.
The most powerful designs are always the result of a continuous process of simplification
and refinement.
Customers and users often need help to understand, verbalize, visualize and organize
their requirements.
D3 was originally coined by Henry Jacob of Arrk Limited.
(designdrivendevelopment.org, Henry Jacob [2010))

4. The Cost of Poor Requirements Gathering
The major consequence of poor For every million dollars spent on
requirements gathering is rework software development, $150,000
to $200,000 is wasted due to
Studies have shown that rework
can consume 30% to 50% of poor requirements (NICT)
total system development costs Requirements errors cost U.S.
(Boehm and Papaccio)
companies $30 billion a year in
Requirements errors account for total (NICT)
70% to 85% of the rework cost
(Leffingwell) 60% to 70% of IT project failures
occur directly as a result of poor
requirements gathering, analysis,
and management (Meta Group)
It costs far more to correct a defect that’s
found late in the project life cycle than to
fix it shortly after its creation (Grady)

5. Requirements are central to the work of IT Architects
TOGAF* puts Requirements Management squarely at the centre of its
Architecture Development Method
An IT Architect must put
requirements at the centre of
project, or risk failure
“Putting at the Centre” means
constant effort to understand and
manage
Especially, maintain traceability;
Keep track of how requirements
relate to each other, and to all
these other entities in the
framework
*The Open Group Architecture Framework

6. City Forward is being built on the idea of nurturing insight. More than an
information repository, it will enable users to interact with, add to, and make new
connections among data and discrete pieces of knowledge.
As part of IBM’s efforts to help build a smarter planet, City Forward is a
web-based, multi-sensory hub of insight and information that can be used by
cities and their citizens to see themselves in new and powerful ways.
This dynamic resource will lead users of all types to discover
and explore areas of particular relevance to their goals and
situations.

7. D3 Based User Experience Document

8. User Experience Document Table of Contents

9. D3 Visio-Based Wireframe

10. Rational Requirements Composer Structure
Project Structure
Section for Tracking Data Project
Section for Tracking Requirements
Section for Design Elements

11. Rational Requirements Composer – Table of Contents

12. Building Wireframes in Rational Requirements Composer

13. Building Wireframes in Rational Requirements Composer

14. Adding Requirements in Rational Requirements Composer

15. Rational Requirements Composer - Requirement Example

16. Building Wireframes in Rational Requirements Composer

17. Rational Requirements Composer – Table of Contents

18. Rational Requirements Composer – Wireframe (Eclipse View)

19. Rational Requirements Composer – Wireframe (Web View)

20. Collaborative Application Lifecycle Management Solution
Tester
Analyst Developer
Rational Requirements Rational Quality Manager
Rational Team Concert
Composer
Test Execution Results link to
defects
Defects can link to
requirements
Defects link to Test Execution
results

21. Managing a Data Project with Rational Requirements Composer
The Challenge:
Tracking Data Sources and their approvals
Tracking Coverage of Cities
Tracking Coverage of Categories
Showing Traceability between Cities, Sources, and Categories
The Solution:
Create all elements as requirements
Use free text body and comments capabilities to
track Data Source approvals
Track Coverage and Traceability by linking Cities,
Sources, and Categories

22. Storing Cities as Requirements

23. Storing Data Model Components as Requirements

24. Storing Datasources as Requirements

25. Linking Cities, Categories, and Datasources

26. Tracking Approvals for Audit Purposes

27. 2
7

28. 2
8
Daily iPod touch giveaway
SPONSORED BY
Complete your session surveys online each day
at a conference kiosk or on your Innovate 2010 Portal!
Each day that you complete all of that day’s session
surveys, your name will be entered to win the daily
IPOD touch!
On Wednesday be sure to complete your full conference evaluation
to receive your free conference t-shirt!

29. 2
9
www.ibm.com/software/rational
© Copyright IBM Corporation 2010. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind,
express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have
the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM
software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities
referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future
product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services
are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product,
or service names may be trademarks or service marks of others.

30. Resources & Bibliography
This presentation used IBM material from:
The Conference Report from the Academy of Technology conference on Requirements Best Practices and Innovations
Emily Plachy’s Academy of Technology presentation on Solution Design. Emily is the CTO for Methods and Tools in GBS
The Requirements Baseline presentation that the Core team for the Academy Requirements Conference developed. Ron Reid was the primary author
Other Conference Presentations by Kathleen Barret (client), Bob Rafuse, William Holmes, Eric Lawton, George de Candio, Martin Gladwell
Leading Large Services Opportunities: Applied Techniques for Consultants, Project Managers, and Technical Leaders
Requirements and Business Value Insights from the Academy Requirements Conference by Leo Marland
Bibliography:
Understanding and Controlling Software Costs, Barry W. Boehm and Philip N. Papaccio (1988)
Calculating the Return on Investment from More Effective Requirements Management, Dean Leffingwell (1997)
National Institute of Standards & Technology, U.S. Department of Commerce, The Economic Impacts of Inadequate Infrastructure for Software Testing (2002)
Coordinating Change Management & Requirements for Business Adaptability and Improved Life Cycle, Meta Group (2007)
An Economic Release Decision Model: Insights into Software Project Management, Robert Grady (1999)
Requirements Engineering (second edition), Hull, Jackson, & Dick (2005)
Requirements Engineering: A Good Practice Guide, Ian Sommerville and Pete Sawyer (1997)
Software Requirements (second edition), Karl E. Wiegers (2003)
INCOSE Systems Engineering Handbook, Vers. 3.1 (2007)
When Bad Requirements Happen to Good People, TLE workshop, Howard Smallowitz & Claudia Schroedl (2008)
Requirements Standards, IBM presentation, David C. Casler (2008)
Accelerate Development by Getting Requirements Right, Karl E. Wiegers (2007)
Study: Bad requirements-gathering hurts IT projects, Chris Kanaracus (2008)
designdrivendevelopment.org, Henry Jacob (2010)