The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Improved application development: Part 3, Incorporating changes in requirements

Martin C. Brown (questions@mcslp.com), Freelance writer and consultant, MCslp

Martin C. Brown is a former IT Director with experience in cross-platform integration. A keen developer, he has produced dynamic sites for blue-chip customers, including HP and Oracle, and is the Technical Director of foodware.net. Now a freelance writer and consultant, MC (as he is better known) works closely with Microsoft® as an subject matter expert, is the LAMP Technologies Editor for LinuxWorld magazine, is a core member of the AnswerSquad.com team, and has written books on topics as diverse as Microsoft Certification, iMacs, and open source programming. Despite his best attempts, he remains a regular and voracious programmer on many platforms and numerous environments. MC can be contacted through this Web site at http://www.mcslp.com.

Summary: The focus of this third tutorial in the "Improved application development" series is on change management. This tutorial shows how individual change requests are linked and traced back to the original requirements specification, how you manage that information from within your development environment, and how you generate a new specification.

View more content in this series

Tag this!

Date: 28 Jun 2005
Level: Intermediate
PDF: A4 and Letter (846 KB | 57 pages)Get Adobe® Reader®

Activity: 1852 views
Comments:

Before you start

About this tutorial

This third part of the Improved application development series presents some of the issues of change management in application development. In Part 1 of this series, you looked at the initial stages of application development, when you created the requirements that will ultimately drive the project. In Part 2, you looked in more detail at the process of building the components in your application.

So far in this series, you've built the sample Auction application based on the original requirements. But what happens after you use the application and demonstrate it to the customer -- and your plans haven't quite worked out the way you expected?

In this tutorial, you will learn how you can link individual change requests to the original requirements specification for tracing as well as how you can generate a new specification to ensure that developers are building software against the latest customer needs. Change requests include defects reported by testers, users, or the customer support help desk as well as enhancement requests from clients and other stakeholders. For instance, the client might request an enhancement to the sample Auction application because he or she really wants the seller to use multiple pictures to describe an item or perhaps because the client want buyers to have an auto-bid option to automatically keep re-bidding amounts up to a maximum. Enhancement requests tend to represent stakeholder wishes; defects, on the other hand, are bugs and faults in design or code and are specifically related to a given release of an application or one of its components.

IBM® Rational® ClearQuest® is an ideal tool for collecting all requests for changes (defects and enhancement requests); accepting or rejecting them; and organizing, assigning, and approving the changes as they are accepted, resolved, and implemented. Some change requests have an impact on the original requirements specification that is still the driving force behind the project. To manage the impact of change on requirements, Rational ClearQuest integrates with IBM Rational RequisitePro® to track the link between enhancement requests and requirements specifications.

In this tutorial, you'll learn about:

Collecting change requests
Integrating Rational ClearQuest and Rational RequisitePro
Managing Rational ClearQuest data with IBM Rational Application Developer
Building a new version of the requirements specification
Modifying the application

Prerequisites

The focus of this tutorial is on two products in the Rational Suite: Rational RequisitePro and Rational ClearQuest. The tutorial also covers integrating the IBM Software Development Platform (which incorporates the IBM Rational Software Modeler and Rational Application Developer components) into the process. Links to download trial copies of most of these products are below. For a trial copy of Rational ClearQuest, you must contact your local IBM office.

To complete the steps in this tutorial, you need:

RequisitePro Version 2003.06.13 or later.
Rational ClearQuest Version 2003.06.13 or later.
Rational ClearQuest Eclipse Client:
- If you have Rational ClearQuest Version 2003.06.13.x, you need Version 6.0.0x of the client.
- If you have Rational ClearQuest Version 2003.06.14.x, you must use the 6.14.x Version of the Rational ClearQuest Eclipse client. You can download this version of the client by selecting Help > Software Updates > Find and Install within the IBM Software Development Platform. Follow the instructions to install the client.
Rational Application Developer Version 6.0
Rational Software Modeler Version 6.0

You also need to install the Auction application sample from the IBM Software Development Platform Showcase samples. These samples include a pre-built version of the Auction application that you have been building in this series. By using the pre-built version, you can continue the tutorial with the remainder of the code already configured. To install the sample, perform the following steps:

Select Help > Samples Gallery. .
In the Samples Gallery window, expand the Showcase samples folder.
Expand the Auction Application folder.
Expand the Construction folder.
Click Web Application. .
Click Import the sample to import the code and source files into your current workspace.

Find the Enterprise JavaBean (EJB) components for the application in your EJB Projects folder as the project AuctionV60EJB.

Comments

Close [x]

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Close [x]

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/

SITE_ID=1

Zone=Rational, Java technology

ArticleID=93187

TutorialTitle=Improved application development: Part 3, Incorporating changes in requirements

publish-date=06282005

author1-email=questions@mcslp.com

author1-email-cc=