This lesson starts midstream in the test planning process,
when you add a new requirement to the test plan.
The test plan is the focal point for all of your testing
activities for a particular test cycle; it can contain multiple test
cases that describe the scenarios that you are going to test. Requirements
help you to ensure life cycle traceability because you can link the
test cases with requirements in the test plan. In this lesson, you
log in as the test architect and add a new requirement to the test
plan.
- Log in as the test architect (Userid: amy, Password: amy)
when prompted with the login dialog box. Amy's dashboard opens.
With a dashboard, you get an overview of project information
and have easy access to more complete information. Dashboards are
composed of viewlets, which are small views that display
different facets of the project. You use the Viewlet Chooser to customize
your dashboard by adding, configuring, and editing viewlets.
Note: You can rearrange the dashboard by dragging viewlets.
Drag the My Tasks viewlet to the upper, right
corner of the dashboard.
Tip: To add, configure,
and edit viewlets, open the Viewlet Chooser by clicking Add
Viewlet from the upper, right corner of the dashboard.

- Open the Classics Java™ Test
Plan, by pointing to the Planning icon (
), and clicking View
Test Plans.
- In the View Builder window, deselect My
test plans only, and click Run.
- From the list of test plans, click Classics
Java Test Plan in the name column. The test plan opens
in the test plan editor.
Note: You can select the Show
All Sections checkbox at the bottom of the Table of Contents
to make all sections visible.
Tip: Take a few minutes
to familiarize yourself with the sections of the test plan.
- Click Requirements in the test plan
Table of Contents.
- To create a new requirement, click the Add New
Requirement icon (
). Important: You can use the installed requirement sample to decrease
the time it takes you to complete this lesson. Click the
Add
Requirement(s) icon (

), and select
New
Customer Order Requirement (Sample). Skip steps 6 and
7.
- When the dialog opens, type the following information:
- In the Summary field, type New
Customer Order Requirement.
- Leave the default for the Severity field
as Normal.
- In Owned By field, assign the
requirement to the test manager, Mary. You
might need to search for Mary by clicking More,
and then typing mary in the search field.
- In the Tags field, type new,
order, classics, java.
- In the Description field, type Test
the functionality of the Classics Java ordering system.
- Click Save.
- The new requirement is created and automatically associated
to the Requirements section of the test plan.

- Save the test plan.
In the next lesson, you continue as the test architect and
begin the review process.