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, Incorporate changes into requirements

Martin C. Brown ( questions@mcslp.com), Author, Studio B

Martin C. Brown, a Studio B author, 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 SME, is the LAMP Technologies Editor for LinuxWorld magazine, a core member of the AnswerSquad.com team and has written a number of 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 at questions@mcslp.com, or 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. In this tutorial, you will learn how individual change requests are linked and traced back to the original requirements specification, and how to generate a new specification.

View more content in this series

Tag this!

Date: 07 Sep 2004
Level: Introductory
PDF: A4 and Letter (1550 KB | 50 pages)Get Adobe® Reader®

Activity: 2069 views
Comments:

Before you start

About this tutorial

In part 3 of this series, you'll see some of the issues of change management in application development. In Part 1, Translating requirements into an application model, you looked at the initial stages of application development when creating requirements that will ultimately drive the project. In Part 2, Integrating XDE Professional into WebSphere, you looked in more detail at the actual building of the components in your application.

In this tutorial, you will learn how individual change requests are linked and traced back to the original requirements specification, and how to generate a new specification to ensure development is building software against the latest customers needs. Change requests include defects reported by testers, end-users, or the customer support help desk, and enhancement requests from clients and other stakeholders. As an example of an enhancement request in the sample auction application, the client might decide that they really want the seller to use multiple pictures to describe their item, or perhaps they want buyers to have an auto-bid option to automatically keep re-bidding amounts up to a maximum. Unlike enhancement requests that tend to represent stakeholder wishes, defects 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 ideal to collect all requests for changes (defects and ERs) and then accept/reject, organize, assign and approve the changes as they are accepted, resolved and implemented. Some change requests will have an impact on the original requirements specification that is still the driving force behind the project. To manage that impact of change to requirements, Rational ClearQuest integrates with IBM Rational RequisitePro to track the link between enhancement requests and requirements specifications.

Key parts of the tutorial include:

Collecting change requests
Integrating Rational ClearQuest and Rational RequisitePro
Building a new version of the requirements specification
Modifying the application

Should I take this tutorial?

This tutorial series is primarily targeted for project managers, program managers, and developers. Others in the software development business might also find it useful. In each of the tutorials in this series, you will learn about different Rational tools and the part they play in the software development process. Different team members might be interested in some tutorials more than others, but it is worth the time to take the complete series from beginning to end to see how all the products work together to form a cohesive process.

This tutorial details how individual change requests are linked and traced back to the original requirements specification, and how you can then generate a new specification to ensure development is building software against the needs of your customers. You will see how IBM Rational ClearQuest is ideally suited to collect and handle all change requests, and manage the impact of changes to requirements with the integration of Rational ClearQuest and Rational RequisitePro.

Ideally, you should be familiar with the application development process, and be involved in at least one part of the process. Familiarization with Rational tools is helpful, but not required.

Prerequisites

To complete the steps in this tutorial, two products in the Rational Suite are required: Rational ClearQuest and Rational RequisitePro. Links to these products are below.

Rational RequisitePro is available as a trial download.

Note that you must have the same releases of the tools for the integration to work. You'll be using v2003.06.12 of all the various tools in this series.

You will also need a copy of Rational ClearQuest.

A demonstration of developing the Online Auction system can be downloaded from the IBM Web site using the following links:

You can also find demonstration artifacts supplied as the example with the WebSphere Studio Application Developer, a tool you'll actually be using later in the series. Check the Auction panel in the first section for more details about the auction system and where to obtain the artifacts.

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

ArticleID=134862

TutorialTitle=Improved application development: Part 3, Incorporate changes into requirements

publish-date=09072004

author1-email= questions@mcslp.com

author1-email-cc=