Engineering Requirements Management DOORS Next

Engineering Requirements Management

DOORS Next

IBM

Contents

Welcome............................................................................................................... 1

Overview...............................................................................................................1

Engineering Requirements Management DOORS

Next.............................................................................1

Comparison of DOORS and DOORS Next.................................................................................................... 4

Conguration management capabilities..................................................................................................... 6

Video tours................................................................................................................................................... 9

Engineering Requirements Management DOORS Next overview......................................................... 9

Getting started...................................................................................................... 9

Administering RM projects........................................................................................................................ 12

Creating and managing requirements.......................................................................................................13

Installing.............................................................................................................14

Installing the RM application.....................................................................................................................14

Upgrading........................................................................................................... 14

Upgrading the RM application................................................................................................................... 14

Integrating.......................................................................................................... 14

DOORS........................................................................................................................................................15

Conguring RM as a consumer.............................................................................................................16

Associating RM projects with DOORS modules...................................................................................17

Conguring the Requirements Management application as a provider and DOORS as a

consumer.........................................................................................................................................17

Rational ClearQuest

................................................................................................................................. 19

Rational Change.........................................................................................................................................20

Administering......................................................................................................21

Administering IBM Engineering Lifecycle Management servers..............................................................21

Administering requirements projects or components..............................................................................21

Permissions.......................................................................................................................................... 21

Creating projects.................................................................................................................................. 26

Managing project or component properties........................................................................................ 28

Copying artifacts between projects..................................................................................................... 62

Deleting artifacts from the repository................................................................................................. 65

Administering link validity....................................................................................................................66

Baselines.............................................................................................................................................. 66

Enabling Electronic signatures for a baseline..................................................................................... 67

Administering components..................................................................................................................68

Managing query workload....................................................................................................................79

Backing up and restoring the RM index les....................................................................................... 80

Analyzing and validating TRS feeds.....................................................................................................81

Initialize the publish services.............................................................................................................. 81

Extending product function....................................................................................................................... 82

Extending the RM application.............................................................................................................. 82

Extending by using OSLC services....................................................................................................... 83

Managing............................................................................................................ 87



Dashboards in the RM application.............................................................................................................87

Composing and managing requirements.................................................................................................. 87

Joining a requirements project............................................................................................................87

Dening requirements..........................................................................................................................90

Managing requirements..................................................................................................................... 188

Managing artifacts by using congurations.......................................................................................224

Reporting.......................................................................................................... 254

Reporting in the Requirements Management (RM) application.............................................................254

Creating document-style reports.......................................................................................................255

Running data warehouse reports...................................................................................................... 257

Reports in the RM application............................................................................................................257

RM reportable REST API.................................................................................................................... 258

Compare conguration report........................................................................................................... 258

Troubleshooting.................................................................................................260

Troubleshooting the RM application....................................................................................................... 260

Log le locations................................................................................................................................ 261

Enabling web client logging............................................................................................................... 261

Fixing a converter issue in the server in headless mode.................................................................. 262

Recovering missing artifacts from congurations.............................................................................263

Fixing le preview font issues in other languages.............................................................................263

Opening artifacts in multiple tabs or windows..................................................................................264

Opening artifacts in new tabs in the same window.......................................................................... 264

Redirecting HTTP requests................................................................................................................264

Pasting invalid XHTML text................................................................................................................ 265

Cutting, copying, and pasting text..................................................................................................... 265

Updating custom Word templates.....................................................................................................266

Creating a hyperlink to a local le......................................................................................................266

Moving artifacts from a folder............................................................................................................266

Creating a project template for a large project................................................................................. 267

Support information for the Requirements Management application..............................................267

Troubleshooting local congurations......................................................................................................268

Glossary ........................................................................................................... 268

A............................................................................................................................................................... 268

B............................................................................................................................................................... 271

C............................................................................................................................................................... 273

D............................................................................................................................................................... 277

E............................................................................................................................................................... 279

F................................................................................................................................................................280

G............................................................................................................................................................... 282

H............................................................................................................................................................... 282

I................................................................................................................................................................ 283

J................................................................................................................................................................285

K............................................................................................................................................................... 285

L................................................................................................................................................................285

M...............................................................................................................................................................287

O............................................................................................................................................................... 288

P............................................................................................................................................................... 289

Q............................................................................................................................................................... 291

R............................................................................................................................................................... 291

S............................................................................................................................................................... 294

T................................................................................................................................................................298

U............................................................................................................................................................... 300

V............................................................................................................................................................... 300

W.............................................................................................................................................................. 301



iii

X............................................................................................................................................................... 302

Z............................................................................................................................................................... 302

Notices..............................................................................................................303

Index................................................................................................................ 306

iv

Welcome

Overview

This section provides overview and getting started information.

Overview of DOORS Next

IBM Engineering Requirements Management DOORS Next (DOORS Next) is a requirements management

tool that helps you store, categorize, link, and share product requirements with stakeholders such as

reviewers, designers, testers, and developers.

DOORS Next is the Requirements Management (RM) application in the IBM Engineering Lifecycle

Management (ELM) solution, which integrates IBM products to provide a complete set of applications

for software or systems development. The RM application uses a web client and the Jazz platform to

dene, manage, and report on requirements.

The following diagram shows the development lifecycle that the solutions support. To see overviews of

the applications that are represented in the image, click the boxes. For example, click Validate and verify

to see an overview of IBM Engineering Test Management (ETM).

Welcome

1. Overview of Engineering Requirements Management DOORS Next

2. Overview of Engineering Rhapsody

Model Manager

3. Overview of Engineering Workflow Management

4. Overview of Engineering Test Management

5. Overview of Global Conguration Management

6. Overview of Reporting

7. Overview of Engineering Insights

Create a single view of requirements

Stakeholder, business, system, product, hardware, software, and other requirements represent business

needs from different perspectives with different levels of detail. Requirements have several formats, such

as diagrams, tables, forms, and text. Usually, several people are involved in creating, analyzing, reviewing,

approving, designing, and developing requirements.

 Engineering Requirements Management DOORS Next

DOORS Next can store multiple types of requirements in a common repository. Bringing all requirements

together in a single place, removing redundancy, and connecting related content is essential to effectively

managing requirements in large projects.

For an interactive workflow diagram of the requirements denition and management process, see Getting

started with requirements management.

Trace linkages between requirements

Requirements are often related in many ways. Business requirements drive product requirements,

which in turn drive hardware and software requirements. Product requirements cascade to component

requirements and granular requirements are linked to more comprehensive requirements. The result is a

web of relationships with many dependencies.

With DOORS Next, you can create relationships between requirement artifacts. You can then use grid or

tree views to see top-level or drilled-down views of those links.

For details, see Traceability.

Evaluate the impact of changes to requirement

As a product evolves, initial requirements can change or be removed during development. Because

requirements are linked, a change in one requirement can affect other requirements. The Links Explorer in

DOORS Next graphically displays the links between artifacts. When an artifact changes, the Links Explorer

automatically flags all links from that artifact as suspect. By tracing the suspect links, you can identify all

requirements that are affected by a change.

For details, see Linking to development, design, test, and requirements artifacts

Create review workflows

DOORS Next encourages collaboration through reviews. You can set up reviews of requirements and

identify reviewers. As a review owner, you can see the progress, comments, and status of all participants

in the review. You can broadcast emails, leave instructions, or even change the status of the review. As a

reviewer, you can leave comments and vote.

For details, see Requirement workflows.

Monitor project performance with metrics

By default, metrics are collected at regular intervals to provide the most recent view of data, as well

as trends over time, which can help you evaluate the ongoing health of your project. For example, the

“Requirements covered by test cases” metric monitors the extent to which requirements are covered by

test cases over time.

The data warehouse can also provide detailed traceability for requirements. For example, you can see

all work items that implement a set of requirements, along with properties such as status, priority, story

points, and due date.

For details, see Reporting in the RM application.

Baseline projects and track change history

DOORS Next tracks and records metadata to measure project efciency and churn, such as who modied

information, and which changes occurred when.

You can capture baselines of your project requirements for a snapshot of your project at a point in time.

You can compare projects against a previous baseline to determine what’s changed.

DOORS Next stores the history of changes to artifacts. You can access all revisions of an artifact to see

which modications occurred when. You can also use the historical record of an artifact to undo any

changes and restore the artifact to a previous state.

For details, see Baselines in RM projects.

Extend functionality with APIs

Overview

DOORS Next provides a client extension API that you can use to extend tool functionality by using

technologies such as HTML and JavaScript. You can create and host a catalog of extensions on a server so

that your team can share them.

For details, see Extending the RM application.

Conguration management

You can use conguration management in the RM application to create versions of requirement

artifacts and to link them to other team artifacts, such as test cases and designs. Use congurations

(streams and baselines) to manage reuse, traceability, and parallel development. Teams by using

conguration management enabled ELM applications can contribute requirements, design, test, and

source congurations to global congurations. Global congurations ensure artifact links resolve to the

correct versions, and also facilitate reuse across versions or variants of your software or product line. For

more information about congurations, see Getting started with conguration management.

Exchange requirements data with OSLC and ReqIF

The software architecture for the RM application is based on the Open Services for Lifecycle Collaboration

(OSLC) specication, which uses a common set of resources, formats, and REST architectural services to

enable data sharing between applications. You can use the OSLC integration protocol to link requirements

in IBM Engineering Requirements Management DOORS with artifacts in DOORS Next.

You can exchange requirements data between the two products by using ReqIF, which is an evolution of

the Requirements Interchange Format that is governed by the Object Management Group (OMG). With

ReqIF, teams in different organizations can use different requirements management tools to work on

shared specications to construct a consistent view of a solution. For details, see Importing and Exporting

ReqIF les.

Part of the Jazz community

The ELM products are developed transparently on the open and extensible Jazz platform. On Jazz.net,

you can download the products and their milestones, track development schedules, join discussion

forums, open enhancement requests, and interact with the product developers. To learn more about

the products, see the developer-written articles in the Jazz.net library or the topics about complex

deployment scenarios on the Deployment wiki.

Related information

Overview of the solution

Client access license management overview

Planning to deploy and install

Interactive installation guide

Getting started with requirements management

Security considerations for IBM Engineering Lifecycle Management

Tips for requirements management

Troubleshooting the RM application

PDF documentation of Doors Next

Comparison of DOORS and DOORS Next

IBM Engineering Requirements Management DOORS (DOORS) and IBM Engineering Requirements

Management DOORS Next (DOORS Next) are requirements management (RM) products with many

similar capabilities. However, the products offer different implementations and strategic opportunities

for requirements analysts and design, development, and test teams.

DOORS, which is in version 9, is a market-leading RM solution. It provides a wide range of RM capabilities

and a rich scripting language. DOORS also integrates with other products and has a large, active

community of users. This product works well for the largest programs and projects and also for smaller

teams.

 Engineering Requirements Management DOORS Next

DOORS Next is an RM collaboration platform with a web client. This product includes capabilities such as

visual requirements denition, work item and test integration, and planning. It runs as an application on

the Jazz

server and can be installed and integrated with other IBM Engineering Lifecycle Management

(ELM) products.

Both products provide traceability to manage requirements across the development lifecycle, support

requirements-driven development and testing, and link to design and modeling resources. In addition, the

products can be used together. For example, you can link requirements and related artifacts across the

two products. Modules and objects that are exported from DOORS can be imported into DOORS Next.

Capabilities and strengths

DOORS helps teams in complex, high-compliance, systems engineering programs. It provides mature

capabilities, such as structured requirements specication modules, roundtrip data import and export,

electronic signatures, baselines, and customizable requirements views with multi-level traceability.

For offline work or printing, views can be exported to document formats or spreadsheets. DOORS

also supports requirements change management which is driven by a process dened in a change

management tool. This product can be scaled to large development projects with tens of thousands of

objects or hundreds of concurrent users.

DOORS offers a user-programmable, extensible API called the DOORS eXtension Language (DXL). DXL

provides a way to customize these activities:

• Automating administration

• Creating multi-level traceability views

• Calculating metrics

• Implementing business logic

• Extending the user interface

• Integrating with other tools

Along with the RM capabilities of the DOORS client and built-in database, the optional IBM Engineering

Requirements Management DOORS - Web Access (DWA) component supports review and common

editing tasks in a web browser. DWA is ideal for distributed teams that do not require the full capabilities

of the DOORS client.

DOORS Next uses the capabilities of Jazz Team Server to support team collaboration through dashboards,

reviews, and comments. Users, projects, data types, artifact types, attributes, and tags have a common

administration. These common services and type systems help project teams consistently dene and

manage requirements.

In ELM, project areas, team members, and processes are managed across associated applications:

Requirements Management (RM), Quality Management (QM), and Change and Conguration Management

(CCM). Because a commercial database is used, system and project administrators can follow flexible and

standardized operational procedures.

The web client for DOORS Next provides tools to dene requirements in rich-text documents and visual

representations in business process diagrams, use case diagrams, storyboards, user interface sketches,

and screen flows. Requirement artifacts can be organized and reused in views, collections, and modules.

The web client supports traceability links to related requirements artifacts and across ELM applications to

development plans, work items, test plans, test cases, designs, and models.

For document generation, DOORS and DOORS Next use the capabilities of Engineering Document

Generation and IBM Engineering Lifecycle Optimization - Publishing to create customizable, dashboard-

based graphical reports.

For a high-level comparison of the client and server architecture in both tools, see the next diagram.

Overview

For more information about DOORS, see the DOORS documentation.

For information about using the ELM, see “Getting started with DOORS Next” on page 9.

For information about the development of DOORS Next as a Jazz.net project, see the DOORS Next page

and this blog post.

Conguration management in the RM application

Use conguration management in the Requirements Management (RM) application to manage

components, streams, baselines, and change sets, to compare congurations, and to complete other

conguration management tasks.

This high-level overview briefly describes the conguration management capabilities in the RM

application. For comprehensive and task-related information, see Getting started with conguration

management.

Before your team can use conguration management capabilities, an administrator must read the

considerations for enabling conguration management, and then obtain an activation key:

• For pilot environments, read the considerations and generate an activation key.

Note: Conguration management capabilities of RM and QM, and global conguration management is

an added service for IBM Engineering Lifecycle Management Base SaaS and IBM Engineering Lifecycle

Management Extended SaaS customer environments, and should only be enabled by the SaaS provider.

Software conguration management (SCM) in CCM is included in Cloud offerings at no additional cost.

• For production environments, discuss your plans with your IBM Client representative or contact

IBMSupport.

 Engineering Requirements Management DOORS Next

Use the conguration management capabilities in the RM application to set up unique working

environments for individuals or teams. For example, you can create components to represent collections

of artifacts, instead of working with all the artifacts from the project in one stream. You can create

streams and baselines of projects at specic points in time, review and approve changes to artifacts, and

make changes visible to other teams or individuals. You can also enable link validity in a conguration

management enabled project.

Streams and baselines are referred to as congurations. You can create and view baselines in a project

even if you do not have conguration management enabled. However, after you enable a project for

conguration management, the Current Conguration menu contains conguration-related options that

you can use to create and compare baselines and streams, and optionally create change sets, as seen in

this example:

Streams, baselines, and change sets in conguration management

A stream is a conguration in which you create and modify artifacts at a specic development level. For

example, you might create a stream when you start a new release or branch of a design, project, or

product.

A baseline is an immutable conguration that provides a snapshot of your project at a specic point in

time. Baselines are useful for capturing the state of a stream, and are typically used to record important

stream congurations so that they can be re-created. When you create a new stream, a baseline of the

previous stream is created automatically.

A change set is a grouping of changes that remains separate from the stream in which it was created until

you deliver the change set to the stream. After you deliver your change set to the originating stream, you

can then deliver the change set to other streams. Using change sets is an optional but convenient way to

track and deliver changes in your development environment.

The name of the stream, baseline, or change set that you select to work in is shown at the top of the

Current Conguration menu. For example, if you create and switch to a baseline called My Baseline, it

appears on the Current Conguration menu, as shown in this example:

To work in a different conguration, expand the Current Conguration menu, click Switch, click

Requirements Management Conguration and search for another conguration in which to work. You

can also switch to a global conguration from this menu.

When you rst create a project, an initial component and stream are automatically created that manage

the artifact versioning information for the project. You can create more components to organize artifacts

based on your project needs. To manage components and congurations, from the Administration menu,

select Manage Components and Congurations.

Overview

The streams in a component are shown on the Component window, on the Streams tab, based on their

relationship to each other:

Tip:

• To see the baselines that were created in a stream, click the stream and then click the Baselines tab. To

compare the contents of two streams, select the streams and click Compare .

• If your team uses global congurations, you can create a baseline of an RM stream from the

conguration tree view in the Global Conguration Management (GCM) application. See Creating

baselines of streams contributed by other ELM applications.

If you are working in a parallel development environment, you might have individual streams whose

contents are derived from a common stream. To make changes in your stream visible to other team

members, you deliver your changes to the common stream, which also known as the flow target. From the

common stream, team members can accept changes into their own streams to ensure that they have the

most recent versions of artifacts.

The hierarchy of the streams in the indicates the flow target for streams. For example, if you create a

Release 1.1 stream from a Release 1.0 stream, the streams are shown as follows:

In this example, the Release 1.0 stream is the flow target for the Release 1.1 stream, which was created

from Release 1.0. If you double-click the Release 1.1 stream and select to compare the stream with the

flow target, you can compare the contents of Release 1.0 with the contents of Release 1.1.

For more information about conguration management, see the video Conguration Management

Overview for CLM v6 releases.

Related concepts

“Baselines in requirements projects” on page 66

 Engineering Requirements Management DOORS Next

In a requirements project, a baseline captures the entire project at a moment in time. For example, you

might create a project baseline before you create an artifact review to ensure that the artifacts do not

change during the review. A baseline includes all artifacts, folder trees, and public tags.

“Managing artifacts by using congurations in the RM application” on page 224

You can manage changes to artifacts and work in a parallel, multi-stream environment by using

conguration management capabilities. These capabilities include creating baselines of projects at

specic points in time, reviewing and approving changes to artifacts, and making changes visible to other

teams or individuals.

Related information

Conguration management: concepts and capabilities

Components

Global conguration management

Managing changes to artifacts using change sets

Video tours

To learn more about IBM Engineering Requirements Management DOORS Next, see this Guided Tour for

DOORS Next:

If you are evaluating or getting started with the RM application, see the Requirements Management

Scenarios on Jazz.net. These scenarios guide you through installing and setting up projects, creating

modules and requirement artifacts, and creating reports.

Related information

Learning resources for the IBM Engineering Lifecycle Management (ELM)

Engineering Requirements Management DOORS Next overview

Watch this tour to get an overview of IBM Engineering Requirements Management DOORS Next (DOORS

Next).

You can download this video from theVideo link

You can watch the below video to get an overview of DOORS:

Getting started with DOORS Next

This topic presents an example of a typical process for project managers, product managers, and

requirements analysts who must assess a business problem and develop requirements for a proposed

solution. The process is represented here in outline form. Your process might vary depending on the state

of the subject system, your stakeholders, your team structure, and your tools.

For an introduction to IBM Engineering Requirements Management DOORS Next (DOORS Next), see

“Overview of DOORS Next” on page 1.

The following diagram shows a simplied workflow for the requirements denition and management

process, which includes traceability relationships between requirements and development and test

artifacts. The process is explained in more detail in a later section. Click a box in the diagram for more

information on a specic task.

Getting started with DOORS Next

1. Click this area to get information about creating vision documents

2. Click this area to get information about creating requirements

3. Click this area to get information about creating collections

4. Click this area to get information about linking to development and test artifacts

5. Click this area to get information about linking to development and test artifacts

6. Click this area to get information about creating requirements

7. Click this area to get information about modifying and managing requirements

8. Click this area to get information about modifying and managing requirements

9. Click this area to get information about working with plans

10. Click this area to get information about creating work items

11. Click this area to get information about creating a test plan

12. Click this area to get information about creating test cases

 Engineering Requirements Management DOORS Next

1: Setting up the project

The project manager or requirements analyst sets up a project by completing these tasks:

1. Create a requirements project. Use a project template to establish a starting point for artifact types,

attributes, link types, and folder structure.

2. Customize artifact types, attributes, link types, folder structure, artifact queries (lters), and

dashboards, as required.

3. Work with project managers and team leaders to plan team organizations and roles, security,

communications, and iteration and milestones schedules.

4. Coordinate with project managers and team leaders to plan for associating requirements with

development and test artifacts throughout the application lifecycle.

See “Creating requirements projects” on page 26, “Project dashboards” on page 88, “Managing project

or component properties in requirements projects” on page 28, Managing users, Administering ELM

project areas, IBM Engineering Lifecycle Management (ELM), and “Linking to development, design, test,

and requirement artifacts” on page 201.

2: Assessing the problem

The requirements analyst collects input about the business problem by completing these tasks:

1. Interview stakeholders and users of the system.

2. Gather documentation on the current system.

3. Import documents into a requirements project.

The documents that you produce in the preceding steps must address the following topics:

• Current process and problems

• Goals and objectives

• Stakeholder requirements

• Issues and risks

• Thoughts and ideas

See “Importing and exporting les” on page 152

3: Creating requirements

The requirements analyst creates requirements that are based on assessment documents and these

requirements denition activities. The analyst and other team members create traceability by linking

between artifacts.

1. Create a vision document to address stakeholder needs and business goals with high-level project

requirements. Use business process diagrams and high-level use case diagrams to describe proposed

solutions.

2. Create a collection or a module that contains high-level requirements. Review and approve the

requirements collection or module, as described in the next section.

3. Link high-level requirements collections and modules with development release plans and test plans.

4. Dene detailed requirements that support the high-level requirements. Create use case diagrams,

storyboards, user interface sketches, and other resources to support the requirement denition.

5. Review and approve the requirements.

6. Link requirements to individual development plan items and test cases.

See “Vision document” on page 122, “Creating collections” on page 175, “Linking to development,

design, test, and requirement artifacts” on page 201, and “Dening requirements” on page 90.

Getting started with DOORS Next

4: Reviewing requirements

The requirements analyst creates a collection of requirements or a module and invites other team

members to review them by completing these tasks:

1. Create a project baseline and create a review from the baseline.

2. Add artifacts and participants to the review.

3. Participants add comments as they approve or disapprove artifacts.

4. Revise requirements to incorporate review comments.

5. Participants review revised requirements and approve them.

6. Finalize the review.

See “Creating reviews” on page 185

and “Baselines in requirements projects” on page 66.

5: Managing requirements

Manage requirements by using traceability links, tags, attributes, ltering, and dashboards. Use these

capabilities to do these activities:

• Create relationships between requirements and other artifacts, including release plans, work items, test

plans, and test cases.

• Categorize requirements.

• Assign properties to requirements.

• Create and compare project baselines.

• Monitor relationships for status, suspect traceability using the Link Validity feature, and the impact of

changes among teams and throughout the application lifecycle.

See “Managing requirements” on page 188

, “Linking to development, design, test, and requirement

artifacts” on page 201, “Baselines in requirements projects” on page 66, and “Dening requirements”

on page 90.

6: Enabling Conguration Management (optional)

Enable conguration management capabilities. Use these capabilities to do these activities:

• Create streams and change sets in addition to baselines.

• Deliver change sets to streams.

• Deliver changes between streams.

• Compare congurations.

• Work in global congurations.

See Conguration Management in the RM application, https://www.ibm.com/docs/en/elms/elm/7.0.2?

topic=SSYMRC_7.0.2/com.ibm.jazz.vvc.doc/topics/c_cm_assess.html, Global conguration management

Getting started for requirements management project

administrators

If you are a requirements project administrator or requirements analyst lead, these guidelines can help

you get started.

Before you begin

• After the Requirements Management (RM) application is installed, run the Jazz Team Server Setup

wizard. That wizard completes several important functions, such as conguring the requirements

management server, and guides you through the creation of an administrative user.

• Your repository administrator must create users and assign licenses at the repository level.

 Engineering Requirements Management DOORS Next

• Read Getting started with project areas and lifecycle projects. You might also want to review

Understanding user access control.

Tip: If you are interested in using the optional conguration management capabilities in the RM

application, refer to Administering congurations.

Procedure

1. Create a requirements project. Select a project template to populate the project with predened

artifact types and a project structure. For more information, see “Creating requirements projects” on

page 26.

2. Add users to the project and assign them project roles. For more information, see Adding and

modifying users as members of project areas and team areas.

3. Optional: Assign permissions at the project level or at a team level. For more information, see

Permissions for requirements projects.

4. Optional: To meet specic project needs, customize the artifact types, attributes, data types, and

link types. For more information, see “Managing project or component properties in requirements

projects” on page 28 and “Creating link types for requirements projects” on page 36.

5. Organize the artifacts in the project by modifying the project folder.

What to do next

You can now begin to create and manage requirements

Getting started with creating and managing requirements

If you are a product manager or requirements analyst lead, follow these guidelines to get yourself and

your team started with creating and managing requirements.

Before you begin

Administrators must complete the administrative tasks that are associated with creating the Jazz

repository and a requirements management project area. Product managers and requirements analysts

must review the requirements management process to see an example of the workflow to get started.

Procedure

1. Use the Artifacts page and other project pages to create, view, and manage project artifacts.

2. Upload external documents

and import comma-separated values (CSV), Microsoft Word,

OpenDocument, and Rich Text Format documents to the project, as needed. The documents can

include preliminary information such as problem statements, stakeholder needs, and a project

management plan. You can extract requirement artifacts from documents as you import them or from

documents that are already in the project.

3. Create requirements. Create high-level requirements to describe the product features. Create detailed

requirements to elaborate the feature requirements. You can create requirements as individual

artifacts in rich-text documents or in the structured content of a module. You can also run reports.

4. Create supporting artifacts to help elaborate and give context for the requirements.

5. Use the Project Dashboard to track recent activities and other project properties. You can also use

saved views and lters to manage requirements on the Artifacts page and other project pages.

6. Create traceability by linking high-level requirements, detailed requirements, and supporting artifacts.

You can also trace requirements to other applications across the software development lifecycle to

complete these tasks:

• Implement requirements with development plans and work items

• Validate requirements with test plans and test cases

Getting started with DOORS Next

7. Create collections or modules to organize requirements into related groups to prepare for requirement

reviews and other management activities. You can use collections and modules to link requirements to

development plans and test plans.

8. Initiate requirements reviews. Create review for requirements collections or modules or individual

artifacts, and add team members to serve as reviewers and approvers.

Installing

This section describes how to install the Requirements Management (RM) application.

Installing the Requirements Management application

For information about installing Jazz Team Server and the Requirements Management (RM) application,

see the related help topics for the IBM Engineering Lifecycle Management (ELM).

About this task

For information about installing the RM application, see Installing Jazz Team Server and the ELM

applications.

Note: The capabilities that are provided by the RM application are licensed as IBM Engineering

Requirements Management DOORS Next (DOORS Next).

Related information

Upgrading

This section contains instructions to upgrade the Requirements Management (RM) application for the IBM

Engineering Lifecycle Management (ELM).

Upgrading the Requirements Management application

For information about upgrading Jazz Team Server and the Requirements Management (RM) application,

see the related help topics about upgrading the IBM Engineering Lifecycle Management (ELM). The

capabilities that are provided by the RM application are licensed as IBM Engineering Requirements

Management DOORS Next (DOORS Next).

Note: If you are using version-aware reporting, after upgrading the RM application, you must perform a

TRS 2.0 full rebase. For details, see the associated section of the interactive upgrade guide.

Related information

Upgrading ELM

Integrating the Requirements Management (RM)

application with other products

You can integrate the Requirements Management (RM) application with other products.

Note that for projects that have been enabled for conguration management, the integration product

must support linking to versioned artifacts.

 Engineering Requirements Management DOORS Next

Integrating the Requirements Management application and DOORS

You can integrate IBM Engineering Requirements Management DOORS (DOORS) with the Requirements

Management (RM) application in the IBM Engineering Lifecycle Management (ELM). You can link

requirement artifacts in the RM application to requirement objects in DOORS modules. After you create

links, you can display a summary of the linked object or go to the object. You can also add a widget to your

dashboard to monitor the status of linked objects.

Before you begin

• Make sure that you have the host name and IP address for the Jazz Team Server where the RM

application is registered.

• You must have an installation of DOORS and IBM Engineering Requirements Management DOORS - Web

Access (DWA) version 9.5 or later.

• You must know the URL for the DWA root services. That URL is in the following format: https://

host-name:8443/dwa/public/rootservices.

• You must have login credentials for DOORS as a database manager or as a custom user who has the

power to manage the database and open the database properties.

Note: The operating system of the DOORS server and the RM server must have the same date and time,

with a difference of 5 minutes or less.

About this task

Note: The capabilities that are provided by the RM application in ELM are licensed as IBM Engineering

Requirements Management DOORS Next (DOORS Next).

You can use this integration to add and remove traceability links between the RM application and DOORS.

You can include these traceability links in traceability reports in the RM tools. RM integrations with DOORS

and other external RM applications use the References link type. You can create links in either the RM

application in ELM or in DOORS. When you work in one application, you are prompted to log in to the

other application repository to gain access to existing links and gain permission to create new links. Links

are stored in the source application where they are created. The target application queries the source

application for any integration links and then displays those links. You can place your cursor over a link

to display a summary of the linked object or click the link to go to the object. After you log in, if the

integrated repository becomes unavailable, a message is displayed.

Permissions for creating links between the RM application and DOORS are controlled at the project level

in RM. Permissions are checked for the local project not the remote project or module.

If you try to remove a link that is stored in DOORS from the RM application in ELM, an error is displayed if

the module in DOORS is open. You can delete the link in DOORS or close the module and delete the link in

the RM application.

Complete the integration tasks as they are listed below.

Related concepts

“Importing migration package les” on page 166

You can import requirements from an IBM Engineering Requirements Management DOORS (DOORS)

migration package le into IBM Engineering Requirements Management DOORS Next (DOORS Next). The

migration package le must be in your le system.

Related tasks

“Linking to development, design, test, and requirement artifacts” on page 201

Integrating the Requirements Management (RM) application with other products

Conguring the Requirements Management application as a consumer and

DOORS as a provider

To enable linking between IBM Engineering Requirements Management DOORS (DOORS) and the

Requirements Management (RM) application, you must congure the RM application as a consumer and

DOORS as a provider.

Before you begin

You must be able to log on to the Jazz server as a user who has Jazz Administrator privileges.

Procedure

1. Log on to the Jazz server as a user who has Jazz Administrator privileges. For the RM application, go to

https://host-name:9443/rm/admin.

2. On the Server tab, select the Friends (Outbound) page.

3. At the Friends List, click Add.

4. In the Add Friend window, type a name for the IBM Engineering Requirements Management DOORS -

Web Access (DWA) server, such as DWA.

5. Enter the URL for the DWA root services in this format: https://host-name:8443/dwa/public/

rootservices.

6. Enter an OAuth secret.

The OAuth secret code phrase is associated with the new OAuth consumer key. This code phrase can

contain one or more words and special characters. It cannot exceed 50 characters, and it is never

shown in the user interface. This code phrase acts as a password to access the friend server.

7. Click Create Friend and then click Next.

A provisional key is created.

8. Copy the provisional key for later use and click Finish.

9. To verify that the consumer key was created in DOORS:

a) Log on to DOORS as a database manager or a custom user who has the power to manage the

database, and open the database properties.

b) In the DOORS client, do one of these steps:

• For DOORS version 9.5.1 and later, click File > OSLC > Local Keys.

• For earlier versions of DOORS 9.5, right-click the database node in the left panel and click

Properties. Click the Local Keys tab.

c) In the Local Keys window, click Add to add RM as an OAuth consumer.

d) For the consumer name, type a recognizable name for the consumer, such as RM.

e) For the consumer key, enter the provisional key that was created in the friend entry on the Jazz

Team Server.

f) Type and conrm the OAuth secret.

g) Click Register.

What to do next

You can now associate an RM project with a DOORS module

 Engineering Requirements Management DOORS Next

Associating an RM project with a DOORS module

To enable linking between IBM Engineering Requirements Management DOORS (DOORS) and the

Requirements Management (RM) application, you must associate an RM project area with a DOORS

module.

About this task

In the RM application, associations are made at the project level. In DOORS, associations are made to

modules, but not to projects or module views. To create links to objects in multiple modules in DOORS,

each module must be associated to the RM project. When you create a link from an RM artifact, all

modules in the repository might be displayed in the selection list, even though some modules might not

be associated. If you select an object in a module that is not associated with the RM project, the link is not

created.

Procedure

1. Open a project in the RM application.

2. From the Adminstration menu, click Manage This Project Area.

3. In the Associations section, click Add.

4. In the Add Association window, from the Application list, select DOORS Web Access.

5. From the Association list, select a Related Requirement association, which supports the References

link type.

6. In the Artifact Containers section, select a module in a DOORS project and click OK.

7. To verify the association:

a) Open a requirement in the RM application.

b) In the Links section of the sidebar, click Create Link icon.

c) In the Create Link window, select the References link type.

d) From the Artifact Container list, select Services for Project Requirements Document and click

Choose Existing.

e) Select a requirement that is in the DOORS project and click Open.

What to do next

You can now congure Requirements Management as a provider and DOORS as a consumer

Conguring the Requirements Management application as a provider and

DOORS as a consumer

To enable linking between IBM Engineering Requirements Management DOORS (DOORS) and the

Requirements Management (RM) application, you must congure RM as a provider and DOORS as a

consumer.

Before you begin

You must be able to log on to Jazz Team Server as a user with Administrator privileges.

Procedure

1. Log on to Jazz Team Server as an Administrator by navigating to https://host-name:9443/jts/

admin.

2. Click Manage Server.

3. On the Server tab, click Consumers (Inbound).

4. In the Register Consumer section, type a consumer name, such as DOORS, and a consumer secret.

5. Click Register.

Integrating the Requirements Management (RM) application with other products

A new entry is created in the Authorized Keys section. Copy the consumer key that was generated for

that entry.

6. To enable all users, members, and non-members to access and perform tasks in the project area that

you registered, complete these steps:

a) Log on to the RM server by navigating to https://host-name:9443/rm/admin.

b) Click Advanced Properties.

CAUTION: It is important to note that, if the

DisableLoginRequestForAssociatedProjects property is enabled by setting the

value to True, any links that exist in RM projects on another server, links to Quality

Management projects, and the links that exist in the associated DOORS projects are not

displayed in IBM Engineering Requirements Management DOORS Next (DOORS Next) links

sidebar.

c) On the Advanced Properties page, search for the property called

DisableLoginRequestForAssociatedProjects, click the associated Current Value entry

and change it to True. This property controls whether users must log in to projects that are

associated with the current RM project. If you enable this property, users who do not have access

to the associated projects are not prompted for credentials.

d) Click Save.

7. Log on to DOORS as a database manager or a user with permissions to manage the database and

open the database properties.

8. In the DOORS client, complete one of the following steps:

• For DOORS version 9.5.1 and later, click File > OSLC > Remote Services.

• For earlier versions of DOORS 9.5, right-click the database node in the left pane and click

Properties. Click the Remote Services tab.

9. In the Remote Services window, next to the Server list, click Add.

10. Create an entry for the RM application:

a) Enter a name, such as RM.

b) In the Location eld, enter the URI to the RM application root services.

For example, enter https://host-name:9443/rm/rootservices.

c) For DOORS 9.5 and 9.5.0.1, select OSLC version 2.0.

For later versions of DOORS, the highest OSLC version is detected from the provider automatically.

d) Enter the consumer key that you copied when you registered the new consumer in step “5” on

page 17.

e) Click Register.

11. In the Remote Services window, next to the Collaboration Links list, click Add.

12. In the Add Service Link Type window, from the Server list, select the RM application server. If you

are prompted, log on to the RM server.

13. From the Service Providers list, select an RM project.

14. From the Link Types list, select an association that supports the References link type and then click

Add.

What to do next

To verify the integration, open a module in DOORS and create a References link from the Link menu for an

object to a requirement in an RM project.

 Engineering Requirements Management DOORS Next

Integrating the Requirements Management application and

Rational ClearQuest

When IBM Rational ClearQuest is integrated with the Requirements Management (RM) application in

the IBM Engineering Lifecycle Management (ELM), you can associate requirements with defects, tasks,

requests for enhancements, and other record types. The capabilities that are provided by the RM

application in ELM are licensed as IBM Engineering Requirements Management DOORS Next (DOORS

Next).

Before you begin

• Install the RM application and congure Jazz Team Server.

• Install the compatible version of the Rational ClearQuest web server component. You can install the

Rational ClearQuest web server on the same computer as the RM application or on a remote computer.

For more information, see "Deploying and installing Rational ClearQuest" in the Installing section of the

Rational ClearQuest documentation

• Congure the integration in Rational ClearQuest. For instructions, see Rational ClearQuest

documentation. This conguration requires that you apply the OSLCLinks package to your Rational

ClearQuest schema. Optionally, you can apply the RequirementsChangeRequest package to the

schema.

• Obtain an Analyst Client Access License or a license with similar requirements management

capabilities.

• Create or access a requirements management project to integrate with a Rational ClearQuest schema

repository. You must have project administrator permissions in the requirements management project.

If a requirements management project does not exist, see Creating requirements projects.

• Use public host names rather than aliases or proxies for the Rational ClearQuest web server and Jazz

Team Server.

• Disable any software that blocks pop-up windows in your browser.

Procedure

1. Set up cross-server communication with Rational ClearQuest.

a) In a web browser, go to https://fully qualified hostname:9443/jts/admin.

b) On the Server Administration page, click the Server tab.

c) In the Communication section, click Friends (Outbound). The Friends page opens.

d) Click Add. The Add Friend window opens.

e) Type the name to use to identify the Rational ClearQuest web server.

f) For the root services URI, type the concatenation of the public URI and the Rational ClearQuest

discovery context information.

For example, https://cq-hostname/cqweb/oslc/repo/schema-repository/discovery,

where cq-hostname is the name of your Rational ClearQuest web server and schema-repository is

the name of your Rational ClearQuest schema repository.

g) For the OAuth secret, enter a code to associate with the new OAuth consumer key of the server.

Note: Do not enter the key itself; enter a shorter phrase to associate with the actual key.

h) In the Re-type Secret eld, retype the OAuth Secret code phrase.

i) Select Trusted to designate the Rational ClearQuest web server as a Trusted consumer. Trusted

consumers can share authorization with other trusted consumers and do not require user approval

to access data.

j) Click Create Friend. If the connection to the root services URI was successful, a message conrms

that the friend was added and that a provisional key was generated. Click Next.

Integrating the Requirements Management (RM) application with other products

k) Click the Grant access for the provisional key link.

l) Enter an administrator user ID. Click Continue and log in to the Rational ClearQuest web server.

m) Click Yes to approve the consumer key. Click Finish.

2. Complete the steps in "Conguring ClearQuest Web server for cross-server communication", which is

in the Integrating section of the Rational ClearQuest documentation. If you already completed those

steps, skip to the next step.

3. In the RM application, create a link between the Rational ClearQuest user database and the

requirements management project area.

a) In the RM application, from the Administration menu click Manage Project Areas.

b) Click the project area to congure.

c) Scroll to the Associations section, and then click Add.

The Add Association page opens.

d) From the Application list, select your Rational ClearQuest web server and log in to the server when

you are prompted.

e) From the Association list, select an association type to use for the integration.

For example, Uses - Implementation Requests or Uses - Requirements Change Requests.

f) In the Artifact Container section, click the Rational ClearQuest databases.

g) Click OK and then save the changes to the project area. If needed, add another association type.

What to do next

Team members in your project can now start creating links between requirement artifacts and Rational

ClearQuest records.

Related information

Rational ClearQuest documentation

Integrating the Requirements Management application with IBM

Rational Change

You can integrate IBM Rational Change with the Requirements Management (RM) application in the IBM

Engineering Lifecycle Management (ELM). You can link RM requirement artifacts with change requests in

Rational Change.

Note: The capabilities of the RM application in ELM are provided by IBM Engineering Requirements

Management DOORS Next (DOORS Next).

Conguring the integration

For information about conguring the integration, see these help topics in the Rational Change

documentation:

• Using the OSLC-CM REST API

• Integrating with OSLC consumers

• Integrating with an OSLC provider

The Rational Change documentation uses the integration with IBM Engineering Test Management

(ETM) as an example. Other OSLC integrations are congured in a similar way. If you need to supply

the root services URI for the RM application, the typical format is https://host-name:9443/rm/

rootservices.

Optionally, you can modify a Rational Change lifecycle so that the RM application can automatically create

links from change requests (CRs) back to their related RM requirements. In Rational Change, add these

string attributes to your lifecycle and show forms with the OSLC_LINK web type:

• tracksRequirement

 Engineering Requirements Management DOORS Next

• affectsRequirement

For more information, see a similar integration with ETM that is described in Integrating with OSLC

consumers in the Rational Change documentation.

Linking requirement artifacts and change requests

After the integration is congured, your team can create links between ELM RM artifacts and CRs in

Rational Change.

In Rational Change, change requests can be congured as various types, such as defect, task, or

enhancement. You can add links in Rational Change CR show forms in the relatedChangeRequests

attribute. Select the RM application from the Friends list and create a link to a requirement artifact. For

more information, see Integrating with an OSLC provider

In the RM application, use the Implemented By link type to link requirement artifacts to CRs in Rational

Change. You cannot link requirement modules or collections to CRs, but you can link artifacts in a module

or a collection. For information about similar lifecycle linking from the RM application, see “Linking to

development, design, test, and requirement artifacts” on page 201.

Administering

This section describes how to administer servers and project areas in the Requirements Management

(RM) application.

Administering IBM Engineering Lifecycle Management servers

After you install and start your IBM Engineering Lifecycle Management server and applications, you can

perform administrative tasks such as managing users and conguring or troubleshooting the server.

For more information, see Administering servers.

Administering requirements projects or components

Administrators can create, congure, and manage requirements projects or components.For information

about conguring a UNIX system for image generation, see the Jazz.net wiki.

Permissions for Requirements Management (RM) projects

Permissions to complete operations in the Requirements Management (RM) application are assigned to

individual roles on the Permissions page of the project area. You can assign permissions at the project

level, or for more granular control, at a team level. Then, use the project area process sharing feature

to standardize and reuse across projects. After you assign permissions, you can view or change the

permissions in the Team Ownership Overview window.

Note: To know more about setting permissions for projects in which conguration management is

enabled, see Setting permissions for congurations in lifecycle management products.

You can assign create, modify, and delete permissions that are based on artifact types, artifact attributes,

link types, and on locations such as a folder, artifact, or module. As shown in the following table, two

classes of permissions exist: project conguration and team conguration.

Administering

Table 1. Permission classes in the Requirements Management application

Permission class Description

Project conguration This class is for setting high-level project permissions. The permissions in this

class enable these operations:

• Setting project-level permissions

• Modifying types

• Creating templates

• Creating baselines

• Creating change sets

Team conguration This class is for setting permissions on a more granular level. You can use this

permission class to set location-based permissions. The permissions in this

class enable these operations:

Artifact operations

Create, delete, or modify artifacts by type.

Modify artifacts by attribute.

Folder operations

Create, delete, or modify folders.

Link operations

Create, delete, or modify links by type.

Team ownership operations

Modify team ownership.

Lock operations

Manually lock artifacts and override locks of other users.

View operations

Create, delete, or modify shared views.

Permissions on a project level

To set permissions on a project level, you dene role actions at the project level. For a description of the

project process roles for requirements management, see roles. For detailed instructions on how to set

permissions, see modifying permissions.

Permissions on a team level for location-based granular control

To set permissions on a team level for more granular control, you must rst create a team area. For a

detailed example, see “Workflow for setting location-based permissions” on page 23

When you create team areas, remember this information:

• Team areas are created as children of the project.

• Multiple team areas can be created in each project.

• Team areas are hierarchical. Users who are members of the parent project or team area are effectively

members of the child team areas. If users need to have permissions set in multiple team areas, you can

add them to a parent team area.

 Engineering Requirements Management DOORS Next

Tip: Because project-level permissions take precedence over team level permissions, in certain

situations you might want to forgo adding users at the project level and add them to team areas only.

• Team areas are optional. If you do not need to set permissions on a granular level, you can set security

at the project level.

Workflow for setting location-based permissions

General workflow to create location-based permissions by using a team area is as follows:

1. Create a team area.

2. Add users to the team area.

3. Assign process roles to the users in the team area.

4. Modify the process roles for the roles in that team area.

5. Assign team ownership based on location in the folder hierarchy or to specic artifacts or modules.

Permissions on a project level for process sharing

IBM Engineering Requirements Management DOORS Next (DOORS Next) supports process sharing

between projects. You can share the following between projects:

• User roles

• Workflow

• Permissions

To enable process sharing:

1. Select the project for sharing the project's permissions, user roles, and workflow.

2. On the Administration menu, click Manage This Project Area.

3. On the Overview page, in Process Sharing, select Allow other project areas to use the process

conguration from this project area.

See the tutorial on Creating a provider project area

. You can use the process conguration of the modied

project in new and updated projects. If you update existing projects, go to the Workflow page and the

Roles page and clear the overrides.

For permissions specic to individual types, you can import types from projects by using the

process conguration. To import project properties, on the Administration menu, click Import Project

Properties.

Example - Giving a group of users exclusive permission to create a specic artifact

type

Suppose that you have a Business Goals folder in your requirements project, and you want to give a

group of users exclusive permission to create Business Goal artifacts in that folder. To do so, complete the

following steps:

1. Remove the permission to create business goals for everyone in the Administrator role.

2. Enable that permission for a team area.

3. Assign team ownership of the team area to the folder.

Administering

The following procedure provides more details about this example. It also describes how to see an

overview of the team ownership of folders and artifacts in a project in the Team Ownership Overview

window.

1. Log in to the Administration page of Jazz Team Server.

2. In the Manage Application Artifacts section, click Manage Project Areas.

3. Click an active project area.

4. Click Permissions and then click Administrator role.

5. Under Permissions For Administrator, expand Save Artifact. To Create Business Goal artifact, click

the Revoke Permissions icon.

6. Click Save. The permission to create a business goal is removed from all Administrators. However,

that permission is enabled by default for the Author role.

7. Click Overview.

8. In the Team Area Hierarchy section, click the Create Team icon and create a team area named

Business Group.

9. Add members to the Business Group team area, and assign the Author process role to each member,

and click Save.

10. Assign team ownership of the Business Group team area to the Business Goals folder:

a. Open the RM application, and click the menu of the Business Goals folder.

b. Click Assign Team Ownership.

 Engineering Requirements Management DOORS Next

The Associate Project/Team Area window opens.

c. Select the Business Group team area, and then click OK.

Now only the members of the Business Group team area have permission to create Business Goal

artifacts in the Business Goal folder. You can assign team ownership to modules and to artifacts in a

similar manner.

Complete the following steps to see an overview of the team ownership of folders and artifacts in a

project:

1. From the Administration menu , click Manage Project Properties.

2. Click the Team Ownership Overview tab. The Team Ownership Overview window opens.

Administering

You can change the ownership in this window by clicking the Set Ownership icon .

If you enabled conguration management for your project, see Creating global conguration process

templates.

Related tasks

Creating templates for requirements projects or components

You can create a project or component template, and select the elements to include in it. When

conguration management is not enabled, you create templates for a project. When conguration

management is enabled, you create templates for a component. You can include or exclude artifacts,

artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags,

and shared saved lters. After you create templates, you cannot modify them.

Related information

Permissions

Administering global conguration project areas

Creating requirements projects

Jazz project administrators can create projects and modify project structure and team membership.

Before you begin

To create a project, you must log in to the repository as a user with JazzAdmins or JazzProjectAdmins

repository permissions. You must also be assigned the IBM Engineering Requirements Management

DOORS Next (DOORS Next) Analyst role and the associated client access license. If you want to

enable conguration management, an RM administrator must enter a valid license key. See Activating

conguration management.

Procedure

1. If you have not already done so, log in

to a requirements project repository.

2. On the Administration menu , click Manage Project Areas.

3. On the Active Project Areas page, click Create Project Area.

4. In the New Project window, enter a project name and optional description.

5. Optional: To apply the process conguration from another project area to the new one, enable the Use

the process conguration from another project area for this project area option, click Change, and

choose a project area in the list.

6. Click Save.

A new project is created and the Application Administration page opens.

 Engineering Requirements Management DOORS Next

7. Optional: To enable conguration management for the new project area, on the Application

Administration page, in the navigation pane, click Conguration Management and click Enable

Conguration Management.

8. Optional: To add content to a project area, you can use one of the following options depending upon

whether conguration management is enabled for the project area:

• Apply a project or component template

a. Click Explore Project.

b. Click either the Project name or Component name, Explore Dashboard, or Show Modules.

c. In the Project Setup or Component Setup window, click Apply a project template or Apply a

component template. The Apply Template dialog box appears.

d. Select a template and click Finish. For a list of available templates, see “Requirements project

templates” on page 48.

e. To access this option later, click the Administration menu, and select Apply Template.

However, the option disappears after types or requirements are created.

Note: You must have a template that is already dened in the application. For more information,

see “Creating templates for requirements projects or components” on page 46 and “Managing

templates for requirements projects or components” on page 47.

• Import project or component properties from an existing component

a. Click Explore Project.

b. Click either the Project name or Component name, Explore Dashboard, or Show Modules.

c. In the Project or Component Setup window, click Import Project properties or Import

Component properties from an existing project or component. Choose your source project or

component.

d. To access this option later, click the Administration menu and select Manage Project

Properties or Manage Component Properties and then select Import Project Properties or

Import Component Properties.

Note:

– You can access this option after requirements or types are created since it is able to merge

the type systems from the source and target project area or component.

– Use this option to copy the type system from an existing project area or component to your

current project area or component. For more information, see “Importing properties from

another Requirements Management (RM) project or component” on page 61.

• Manually dene artifact types

a. To manually dene artifact types, click Explore Project.

b. Click either the Project name or Component Name, Explore Dashboard, or Show Modules. In

the Project Setup or Component Setup window, select Manually dene artifact types.

c. To access this option later, click the Administration menu, select Manage Project Properties or

Manage Component Properties. You can access this option anytime. For more information, see

Managing project or component properties in requirements projects.

9. Click Finish.

Important: You cannot create project areas from the Administration menu on the All Projects page,

or from an existing project area. To create project areas, use Application Administration. You can

apply project templates using the Administration menu in existing project areas.

Note: You can also create content in a project area by using an import operation. To import content,

click Explore Project. Click the Project Name or Component Name, Explore Dashboard, or Show

Modules. If there are no types that are created, the system displays the Project Setup or Component

Setup wizard. You must create the new project area. The Project Setup or Component Setup wizard is

not available after creating the requirements or types.

Administering

Results

A new project is created. If conguration management is enabled, the new project contains a component

and there is an initial stream for the component.

What to do next

You can add team members

to the project and begin adding artifacts. You can also add folders and dene

artifact types and attributes. You can also use an import operation to create artifact types or attributes.

For more information, see Importing and exporting les. You can use only the ReqIF import if there are

no artifact types already created by using any one of the options that are listed in step 8. To return to the

Artifacts page, click the project name on your Project Dashboard page or on the Home drop-down menu.

If conguration management is enabled, you can now use the component to represent a collection of

versioned artifacts within the project area. For example, instead of working with all the artifacts from

the project in one stream (for example, that represents a physical piece that is called a Handheld Meter

Reader), you can use a component to represent a smaller collection of artifacts (for example, to represent

a smaller physical piece such as a Sensor in the handheld meter reader).

To start working in the initial stream of the component, click the project name. Your conguration context

is set to the initial stream of the component. To create and see links to artifacts in other applications

(QM, RM, DM, and CCM applications), a Global Conguration Management conguration lead must add

a conguration of the component and congurations from the other applications to the same global

conguration.

Related concepts

“Permissions for Requirements Management (RM) projects” on page 21

Related tasks

“Creating templates for requirements projects or components” on page 46

You can create a project or component template, and select the elements to include in it. When

conguration management is not enabled, you create templates for a project. When conguration

management is enabled, you create templates for a component. You can include or exclude artifacts,

artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags,

and shared saved lters. After you create templates, you cannot modify them.

“Creating artifacts” on page 91

In a requirements project, you can create rich-text and graphical artifacts.

Related reference

“Requirements project templates” on page 48

Related information

Components

Managing project or component properties in requirements projects

Each project template contains predened artifact types. You can also create customized artifact types,

artifact attributes, and artifact data types for a project or component. Those artifacts types can then

be used by team members to create project or component requirements or related artifacts, such as

customized collections.

Before you begin

You must be assigned to the administrator process role to do these tasks.

About this task

When customizing artifact types and their related elements, you might want to begin with the most basic

elements of the artifact, which are artifact data types. You can use those customized data types to create

custom artifact attributes. You can then add those customized attributes to custom artifact types.

 Engineering Requirements Management DOORS Next

To watch a video that shows how to create custom artifact types, click the Show Me link at the beginning

of the topic.

Related concepts

“Requirement artifacts” on page 92

“Link constraints in the RM application” on page 42

Link constraints are rules that an administrator can set up to specify which kinds of links are allowed in a

project or across projects. If no rules are created, all links are allowed. However, if you create rules, only

the links in the rules are allowed.

“Requirement workflows” on page 195

A Requirements workflow is a state transition model in which you dene the state that artifacts of a

specied type can be in and the actions that users can select to move these artifacts from one state to

another. You can nd topics that are in a specic state by creating a lter.

Related tasks

“Creating link types for requirements projects” on page 36

“Importing properties from another Requirements Management (RM) project or component” on page 61

You can import the properties from one Requirements Management (RM) project or component into

another project or component. When conguration management is not enabled, you import properties

from project to project. When conguration management is enabled, you import properties from

component to component. The properties that are imported by default include all the artifact types,

attribute data types, link types, and link constraints that are dened in the project or component.

Creating requirement artifact types

Artifact types classify requirements and related artifacts and provide a consistent set of attributes for

each type. You can use the artifact types that come with the sample project templates, or you can create

custom artifact types and assign predened and custom attributes to them.

Before you begin

You must have administrator permission to create and modify artifact types.

Procedure

1. From the Administration menu

, click Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

2. Click the Artifact Types tab, and then click New Type.

3. Enter a name and description.

4. Optional: To change the default icon for the artifact type, click Change.

If you select a different icon, all artifacts of this type are shown with that icon.

5. Select a default artifact format.

6. If you selected Module as the format, in the Preferred Module Content eld, select multiple artifact

types to use and specify how they are ordered.

When other team members add artifacts to modules, the preferred artifact types are shown by

default. You can change the order of the preferred artifact types or remove them. The order of

preferred artifact types is used in several menus:

• Create button

• Artifact row menu

• Type menu on the inline editor toolbar for modules

Tip: If you plan to use headings in the module, include a type that is identied as a heading type.

Administering

7. Optional: Select Preferred Link Types. If you select preferred link types, you limit the link types that

are available when you create a link.

8. Optional: To place a frequently used artifact type at the top of the list when you create an artifact

by using the Create button, select Make this artifact type a preferred artifact type check box.

Infrequently used artifact types are available under the Other option.

9. Optional: To enable the Lookup Term feature for text-based artifact types, select Use artifacts of this

type as glossary terms check box . You can use the Lookup Term feature to search for term artifacts

from within text-based artifacts.

10. Optional: If you want artifacts of this type to be shown as headings when you add them to a module,

select In modules, display artifacts of this type as headings by default check box.

11. Optional: If this artifact type is a supporting document that you frequently upload, select the Make

this artifact type a preferred upload option check box. When you upload an artifact, the supporting

document is the default artifact type.

12. Optional: To select a workflow for an artifact type, click Workflow and select a workflow from the list.

You can select the default workflow or also create a custom workflow.

Note: If you create an artifact and the artifact type is associated with a workflow, the newly created

artifact is populated with the initial workflow state.

13. Optional: In the URI eld, specify a unique URI to identify the artifact type across RM projects.

You must use a unique URI for each artifact type within a project. If another project has an equivalent

artifact type, you can use the URI of the equivalent artifact type to ensure consistency across

projects. In a project that is enabled for conguration management, you can use the same URI for

equivalent artifact types that are in different components.

For example, Project_A has an artifact type named "Functional Requirement". When you create

Project_B, you dene an attribute that is named "Requirement - Functional". Your organization

considers these attributes equivalent even though their names and enumeration values differ. Assign

the same URI to both artifact types to ensure consistent meaning across projects.

Note: URIs and Type names are also important for cross-team reporting on artifact types. If the

Type name or URI changes in reporting, the results depend on which content is accessed from

Lifecycle Query Engine (LQE). For more information, see Scenarios for maintaining Rational DOORS

Next Generation type systems for baselines and editable congurations.

14. To add an attribute to the artifact type, click Add Attribute.

15. Click Save.

Related concepts

“Requirement artifacts” on page 92

“Requirement workflows” on page 195

A Requirements workflow is a state transition model in which you dene the state that artifacts of a

specied type can be in and the actions that users can select to move these artifacts from one state to

another. You can nd topics that are in a specic state by creating a lter.

Related tasks

“Managing project or component properties in requirements projects” on page 28

Each project template contains predened artifact types. You can also create customized artifact types,

artifact attributes, and artifact data types for a project or component. Those artifacts types can then

be used by team members to create project or component requirements or related artifacts, such as

customized collections.

“Importing properties from another Requirements Management (RM) project or component” on page 61

You can import the properties from one Requirements Management (RM) project or component into

another project or component. When conguration management is not enabled, you import properties

from project to project. When conguration management is enabled, you import properties from

component to component. The properties that are imported by default include all the artifact types,

attribute data types, link types, and link constraints that are dened in the project or component.

“Creating a glossary and terms” on page 178

 Engineering Requirements Management DOORS Next

A glossary is a group of terms that you have dened to build consistent, common terminology for your

project.

Related information

Repository and role-based permissions

Creating attributes for requirement artifacts

When you create requirements in a project, you can create custom artifact attributes to use in custom

artifact types. Custom attributes are based on predened and custom artifact data types, which dene the

properties of the attribute, such as textual entries, integers, date, time, or team member names.

Before you begin

You must have administrator permissions to create and modify artifact attributes, and you must be in a

Requirements Management (RM) application project.

Procedure

1. From the Administration menu , click Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

2. Click the Artifact Attributes tab, and then click New Attribute.

3. Enter a name and description.

4. Select a data type.

You can also create a new data type. For more information, see “Creating requirement attribute data

types” on page 32.

5. If you want users to be able to select multiple values from the list of attribute values, select Multiple

values allowed.

6. Optional: Enter an initial value that is shown when you create a requirement artifact that contains an

attribute of this type.

7. Optional: In the URI eld, specify a unique URI to identify the artifact attribute across RM projects,

with the syntax http://hostname/domain/myLabel.

Restriction: When you specify a URI, ensure that it follows these conventions:

• Complies with the RFC 3986 specication (with support for Unicode characters in the path, query,

and fragment only, as specied by RFC 3987).

• Species an absolute URI.

Note: If you use Lifecycle Query Engine as your data source, specify a URI to ensure consistency for

reporting across projects.

In a project, use a unique URI for each artifact attribute. If another project has an equivalent attribute,

use the equivalent attribute's URI to enable a shared vocabulary for reporting. Also, dene URIs for

each of the enumerated values, and use the same URIs to denote equivalent values. In a project that is

enabled for conguration management, you can use the same URI for equivalent attributes that are in

different components.

If the Requirements Management (RM) projects dene a "Priority" property, use the same URI

for it in each project, such as http://my.org/ns/rm/Priority. If another project denes an

"Importance" property that is the same as "Priority", use the same URI for both properties.

8. Click Save.

Administering

Creating requirement attribute data types

You can create custom attribute data types that can be used in custom attributes. Attribute data types

dene the properties of the attribute values. They provide structure and consistency to custom attributes

by offering the administrator a limited set of data types that have a predened behavior and constraints.

Before you begin

You must have administrator permissions to create and modify attribute data types.

About this task

Custom attribute data types are available for use in all custom and non-custom attributes in the project.

New custom attribute data types must be based on one of three kinds:

• Simple

• Enumerated list of values

• Bounded range of values

Simple data types use one of the following base data types:

integer

An integer.

float

A number that can contain decimal digits.

boolean

A check box (marked or cleared).

date

A calendar entry.

time

A 24-hour time selection or an entry in this format: hours:minutes:seconds.

dateTime

Calendar and time entries.

string

Alphanumeric text.

duration

A time duration entry (integers) in hours, days, or weeks.

user

Search the repository team members and select one.

An enumerated list of values is a numbered list of values with textual labels. You can add and remove

numbered entries and arrange entries in any order.

Tip: If a data type uses an enumerated list of values, note the order of the values in the table. That

order is the same order that the values will be in when you assign the attribute value to any artifact;

for example, in the artifact sidebar. The number that is assigned in the value eld is the number that is

used when artifacts are sorted by that attribute. When you order artifacts by an attribute (ascending), the

enumerations with the lowest value will be rst.

For a bounded range of values, you must specify a minimum and maximum for a range of any of the

following base data types:

integer

An integer.

float

A number that can contain decimal digits.

date

A calendar entry.

 Engineering Requirements Management DOORS Next

dateTime

Calendar and time entries.

Procedure

To create a custom attribute data type:

1. Click the Administration menu , and then click Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

An administrative page opens that has tabs for artifact types, attributes, data types, link types, and

templates.

2. Click the Attribute Data Types tab.

3. Click New Data Type.

4. Enter a name and description for the data type.

5. Select a kind of value and a base data type, where applicable.

6. If you plan to work with an enumerated list or a bounded range of values, create entries as needed.

7. Optional: In the URI eld, specify a unique URI to identify the attribute data type across RM projects.

Within a project, you must use a unique URI for each attribute data type. If another project has

an equivalent data type, you should use the equivalent type's URI to ensure consistency across

projects and enable a shared vocabulary for reporting. In a project that is enabled for conguration

management, you can use the same URI for equivalent attribute data types that are in different

components.

For example, Project_A has an attribute named "Glossary_visibility", which has an enumerated list

of values: Enterprise, Organization, or Project, each corresponding to an integer. When you create

Project_B, you dene an attribute named "Denition_scope". Possible values are Corporation, Division,

and Team. Your organization considers these data types equivalent even though their names and

enumeration values differ. Assign the same URI to both data types to ensure consistent meaning

across projects and so that you can report on equivalent data types across projects.

8. Click Save.

Module options

A module is a structured document that is composed of multiple artifacts. These artifacts or content of

the modules are stored by default in a folder which is created in the same directory as the module. In

the Modules Options tab, an administrator can change this default to specify another folder to store the

multiple artifacts of a module. You can use drag-and-drop to move one or more folders and re-organize

them. If your project area has not been enabled for conguration management, an administrator can

schedule a refresh of the module view to ensure that the latest module content is loaded from the data

warehouse.

Before you begin

If you have conguration management enabled for your project, you must have JazzAdmin or

JazzProjectAdmin permission to create and modify modules.

If you have conguration management enabled for your project, you must have JazzAdmin or

JazzProjectAdmin or have the Create Component permission to create and modify module content

folder behavior.

Procedure

1. From the Administration menu

, click Manage Project Properties.

Administering

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

2. Click the Modules Options tab.

3. In the Module Content folder set the default location to where the artifacts of a module are stored.

Select any one of the options:

• Same folder as the module, to save the artifacts in the same folder as the module.

• Specied folder, to save the artifacts in a different folder. When a folder is selected as the common

content folder, it is displayed with a different icon in the folder hierarchy.

Note: If the Folder Structure option is selected for templates (see Creating templates for

requirements projects or components) and the Specied folder option is used, the module

template is saved in the Specied folder .

4. Click Save.

Note:

• The Module Content folder setting will only affect new modules. The location of the content folders

for existing modules will not be changed when the setting is changed.

• To include the Module Content folder setting when creating templates (see Creating templates

for requirements projects or components), make sure to include the project or component Folder

Structure in the template.

• When you Import Project or Component Properties, the Module Content folder setting does not

get imported.

Considerations when selecting Specied folder for module content:

• When a Specied folder is selected for module content, the content for all modules will

be saved under the common folder. In order to provide organization to the common folder,

when a module is created, its folder hierarchy will be duplicated under the common folder.

In this example, a common module content folder named Base Artifacts is used for module

content artifacts. A module Account Subsystem is created under User Requirements within the

Non-Functional Requirements folder. Within the common module content folder, the module’s folder

hierarchy is duplicated and the module’s content folder Account Subsystem artifacts is created.

Note:

 Engineering Requirements Management DOORS Next

– The Base Artifacts folder is not available on the Modules or Collections tab. You can access the

folder on the All tab.

– The folder hierarchy will only be duplicated when the module is created. If a module is moved to

another folder or if a folder containing modules is moved, the common folder hierarchy will not be

updated.

– When folders are duplicated under the common module folder, the folders are assigned the same

team area as the original folders.

• When a Specied folder is selected for module content, the folder cannot be deleted. If you want

to delete the folder, either select another folder as the common content folder or select the Same

folder as the module option.

• When a Specied folder is selected for module content, any user that has permission to create

modules will automatically have permission to create folders under the common content folder

when a module is created.

Refresh Module Views

Before you begin

To schedule module view refreshing, you must have the Manage View Schedule permission.

About this task

If your project area has not been enabled for conguration management, you can schedule to Refresh

Module Views. Module views are loaded as collections into the data warehouse during the ETL process.

A view can become outdated if someone updates its contents without editing the view itself. In Refresh

Module Views schedule when the system checks for updates each day.

Procedure

1. From the Administration menu

, click Manage Project Properties.

2. Click the Modules Options tab.

3. Use Add Module View to list the module views that need to be checked and ensure that they contain

the latest content. When you add a view to the list, it is shown only if it is unique to the module and is

shared.

See Filters and views in modules.

Related tasks

Creating modules

You can create modules and module content directly in a project or by importing a Microsoft Word

document, ReqIF le, or rich-text document.

Mapping Contexts

You can use the mapping contexts feature for exchanging requirements between IBM Engineering

Requirements Management DOORS Next (DOORS Next) and IBM Engineering Requirements Management

DOORS (DOORS).

About this task

You can use the mapping contexts feature to automatically map identical type elements from DOORS into

a single instance of each identical type. This feature helps in removing or reducing type duplication when

you import requirements in DOORS Next. You can create mapping contexts and use the contexts while

importing or exporting ReqIF les.

Administering

Procedure

1. From the Administration menu , click Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

2. Click the Mapping Contexts tab.

3. Click New Context.

4. Specify a name for the mapping contexts.

5. Optional: Provide additional information as description.

6. Click Save.

You can view the mapping contexts in the Mapping Contexts list. You can apply the mapping

context to an imported package. For more information, see “Importing artifacts from ReqIF les to

a requirements project or component” on page 168.

You can also use the mapping context to a subsequent export of the same package. For more

information, see “Exporting artifacts from a requirements project or component into ReqIF les” on

page 173.

Related tasks

“Importing and exporting ReqIF les” on page 167

Requirements Interchange Format (ReqIF) les are XML les that you can use to exchange requirements

and associated metadata between requirements tools or requirements repositories. For example, you

can exchange data between IBM Engineering Requirements Management DOORS (DOORS) and IBM

Engineering Requirements Management DOORS Next (DOORS Next). When the exchange is nished, a

report is generated that shows the data that was imported or exported. Using ReqIF to migrate multiple

components or a single component with multiple streams from one environment to another is not

supported. The supported method to migrate a repository to a new environment is Server Rename. If

you want to migrate a partial Requirements Management repository to another environment, you need

to consider engaging IBM Expert Labs, or an IBM Business Partner to explore options that comprise of

custom utilities in addition to ReqIF.

Creating link types for requirements projects

You can create link types to customize the linking relationships between artifacts. Links can show

relationship properties such as artifact origin, derivation, dependency, hierarchy, and associations

between requirements, development, and test artifacts.

Link relationships are directional, and labels typically differ at either end of the link; for example,

requirement A links to requirement B; and requirement B is linked from requirement A. The direction

of each link is also indicated by an icon. For more information, see “Link direction” on page 41

You can use custom link types and system-dened link types to link artifacts in the same project, across

different projects, or across different servers.

Before you begin

You must have administrator permissions to create and modify link types.

About this task

Depending on the project template that was used to create your project, the project might have an

extensive list of predened link types, such as the following types:

• Link - Link To/Link From

• Decomposition - Parent Of/Child Of

• ELM development - Implemented By/Implements

• ELM test - Validated By/Validates

 Engineering Requirements Management DOORS Next

Predened link types in templates can include both system-dened and custom link types. You can use

the predened link types as examples for creating custom link types.

Procedure

1. On the Administration menu , click Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

2. Click Link Types.

All link types in the project are listed. System-dened link types are designated in the Description

eld.

3. Click Add.

4. In the New Link Type window, enter a name, and optionally description. Create a name that describes

the relationship in a general way and includes the logic from both directions.

5. Enter a unique URI value, for example, https://hostname.com/domain/myLabel. This value is

needed for cross-project linking. For cross-project links, both the projects or components must dene

the same link types, with the same external RDF URIs. If you are using link constraints, you must

dene equivalent URI for the requirement types.

Restriction: When you specify a URI, ensure that it follows these conventions:

• Complies with the RFC 3986 specication (with support for Unicode characters in the path, query,

and fragment only, as specied by RFC 3987).

• Species an absolute URI.

6. To add directional labels, select the Provide directional labels for the relationship check box.

7. Enter labels in the Outgoing and Incoming elds.

8. Click Save.

Related concepts

Linking artifacts in different projects or components

A link represents a relationship between artifacts. Link relationships are directional and indicated by an

icon. Link types help you dene and customize the linking relationships between artifacts. Each link type

has an Outgoing and an Incoming role. You can create links between artifacts in different projects on

the same server or on different servers. If you enable conguration management, you can create links

between artifacts in different components.

Related tasks

“Importing properties from another Requirements Management (RM) project or component” on page 61

You can import the properties from one Requirements Management (RM) project or component into

another project or component. When conguration management is not enabled, you import properties

from project to project. When conguration management is enabled, you import properties from

component to component. The properties that are imported by default include all the artifact types,

attribute data types, link types, and link constraints that are dened in the project or component.

“Linking between artifacts in modules” on page 136

You can link artifacts that are in the same module or artifacts that are in different modules.

Link types in requirements projects

Requirements projects include several predened link types for traceability.

Administrators can view the link types for a project and create link types on the Link Types page, which

they can access by clicking the Administration menu and then clicking Manage Project Properties > Link

Types. If you have conguration management that is enabled for your project, on the Administration

menu, click Manage Component Properties.

Note: For traceability to work in cross-project links, link types in both the projects or components must

specify the same external RDF URIs. See Creating link types

to learn how to assign an URI to a link type.

Administering

The following table provides descriptions of most of the traceability link types in the Requirements

Management (RM) application.

Table 2. Requirements management link types

Incoming link type

Outgoing link

type Description

Constrained By Constrains Captures the relationship between requirement

artifacts when one artifact limits or holds back

the other artifact. For example, an artifact can be

constrained by a requirement that it must conform to.

Embedded In Embeds Tracks a containment relationship between RM

artifacts. These types of relationships occur when you

complete operations such as inserting an artifact and

inserting an image for a text artifact.

Extracted From Extracted Extraction captures when the content of a

requirement artifact was created from the contents

of another requirement artifact. This type of link

is created during extraction-based operations; for

example, when you create an artifact by saving an

existing artifact as a new artifact.

Illustrated By Illustrates Illustrates the relationships between graphical and

text artifacts.

Link From Link To Tracks a general relationship between requirement

artifacts.

Mitigates Mitigates Captures the relationship between requirements and

risks. A requirement mitigates one or more risks, and

a risk is mitigated by one or more requirements.

Parent Of Child Of Decomposition captures part-whole relationships

between requirement artifacts. Typically, these types

of links represent artifact hierarchies.

Satised By Satises Captures how the different levels of requirements

are elaborated. For example: an approved vision

statement in a vision document can be satised by

one or more stakeholder requirements.

Synonym Synonym Relates requirement term artifacts that are

synonymous.

This link type is bidirectional. The link is shown as

Synonym from either endpoint.

Term Referenced From References Term Artifact Term Reference captures glossary-based

relationships between requirement artifacts. This

type of link is created during term-based operations

for text artifacts, such as when you create a term.

Link types in RM also include links to other IBM Engineering Lifecycle Management (ELM) applications.

This link type is available only through an OSLC integration. For more information about OSLC link type

denitions, see The OSLC Requirements Management (RM) Vocabulary and RM Resource Denitions.

Incoming links are when the link is created in the RM application and Outgoing links are when the link is

created outside of the RM application.

 Engineering Requirements Management DOORS Next

Important: To make sure that all the link types that are described in the following table are available in a

project:

• Establish project association denitions. See Adding associations.

• Integrate RM with the other application.

In addition, Outgoing link types are shown only if the link is created by the other application. Such as an

Affects link is visible only if the link is created in the change management application.

Table 3. Requirements management link types across ELM applications

Incoming link type Outgoing link type

Description

Change and Conguration Management (CCM) application

Affected By Affects Captures the relationship between a

requirement artifact and a change management

work item that affects the implementation of

the requirement artifact. For example, a defect

in the Change and Conguration Management

(CCM) application can affect the implementation

of a requirement artifact.

Note: The Affected By link type is not available

for modules and collections.

Implemented By Implements Captures the relationship between a

requirement artifact and a change management

work item that describes the implementation

of the requirement artifact. For example, a

story in the CCM application can describe the

implementation of a requirement artifact. In the

CCM application, links of this type are shown as

Implements links.

Note: For modules and collections the

Implemented By link type is only available to

plan items in the CCM application.

Tracked By Tracks Captures the relationship between a

requirement artifact and a change management

item that tracks the implementation of the

requirement artifact. For example, a plan

item in the CCM application can track the

implementation of a requirement artifact. In the

CCM application, links of this type are shown as

Tracks links.

Note: The Tracked By link type is not available

for modules and collections.

Architecture Management (AM) application Note: As of version 7.0.0, DM is no longer part of the ELM

solution.

Derives Architecture

From Element

Derives Architecture

Element

Captures the relationship between a

requirement artifact and a model element. For

example, a UML use case in an architecture

management application can represent a

requirement artifact. The requirement artifact

derives from the UML use case.

Administering39

Table 3. Requirements management link types across ELM applications (continued)

Incoming link type Outgoing link type

Description

Rened By Architecture

Element

Renes Architecture

Element

Captures the relationship between a

requirement artifact and a design element.

Design resources can be linked to requirements

management artifacts by using the Rened By

Architecture Element link type. These link types

are visible in RM as the Renes Architecture

Element link type.

Satised By Architecture

Element

Satises Architecture

Element

Captures the relationship between a

requirement artifact and an architecture

management item that represents a model of

the requirement artifact.

Traced By Architecture

Element

Trace Architecture Element Traces the relationship between a requirement

artifact and an architecture management

item that traces the model element to the

requirement artifact.

Links in another RM instance or another RM project area

Referenced By References Tracks a relationship between requirement

artifacts. These types of relationships

occur when requirement artifacts reference

requirement artifacts in another RM instance or

another project area.

Quality Management (QM) application

Validated By Validates Captures the relationship between a

requirement artifact and a test artifact that

validates the implementation of the requirement

artifact. For example, a test plan in the Quality

Management (QM) application can validate the

implementation of a requirement artifact. In the

QM application, links of this type are displayed

as Validates links. Validated By links point from

the RM application to IBM Engineering Test

Management (ETM).

Related concepts

“Links between artifacts” on page 203

A link represents a relationship between artifacts. Links are mechanisms for referring to related

information. You create some links manually. Other links are created automatically when you complete

certain tasks. There are different properties for trace links, content links, links to base artifacts, and links

in modules.

Link constraints

Link constraints are rules that an administrator can set up to specify which kinds of links are allowed in a

project or across projects. If no rules are created, all links are allowed. However, if you create rules, only

the links in the rules are allowed.

Related tasks

“Creating link types for requirements projects” on page 36

Related reference

“Links across OSLC domains ” on page 85

 Engineering Requirements Management DOORS Next

The Requirements Management (RM) application in the IBM Engineering Lifecycle Management (ELM)

integrates with other application domains by using standard link types as implementations of the OSLC

specications.

Related information

Open Services for Lifecycle Collaboration

Linking between artifacts in the Eclipse client

Linking between artifacts in the web client

Linking to requirements and development artifacts in QM

Link direction

Link types help you dene and customize the linking relationships between artifacts. Each link type has an

Outgoing and an Incoming role.

You can set labels that explain the directional relationship of the link, for example Illustrates and

Illustrated By. To set labels for the Incoming and Outgoing roles for link types, see Creating link types

for requirements project.

When link types are displayed in the user interface, icons indicate the direction of the link type role.

Note: For OSLC link types, direction icons are only shown for IBM Engineering Workflow Management

(EWM), IBM Engineering Test Management (ETM), and References links.

You can also lter or group artifacts according to the direction of the link type role in the Links Sidebar.

From the ltering drop-down menu select Link Type and select Show all, Show Outgoing, or Show

Incoming to lter artifacts by the direction of its associated links. From the grouping drop-down menu,

select Group by Link Type to group artifacts that have Incoming and Outgoing links.

For more details on cross-project or cross-component links for artifacts, see Linking artifacts in different

projects or components.

Utilities to change links and repair incorrectly stored links

• Link swapper tool: Changes the direction of an existing custom link type into a new link type that you

specify.

• Link storage tool: Ensures that cross-component links are stored in the component with the outgoing

endpoint of the link.

You can download these utilities from DOORS Next wiki

Related concepts

“Links between artifacts” on page 203

A link represents a relationship between artifacts. Links are mechanisms for referring to related

information. You create some links manually. Other links are created automatically when you complete

certain tasks. There are different properties for trace links, content links, links to base artifacts, and links

in modules.

“Linking artifacts in different projects or components” on page 206

A link represents a relationship between artifacts. Link relationships are directional and indicated by an

icon. Link types help you dene and customize the linking relationships between artifacts. Each link type

has an Outgoing and an Incoming role. You can create links between artifacts in different projects on

the same server or on different servers. If you enable conguration management, you can create links

between artifacts in different components.

Administering

“Conguration management in the RM application” on page 6

Related tasks

“Linking between artifacts in modules” on page 136

You can link artifacts that are in the same module or artifacts that are in different modules.

“Reusing artifacts in modules” on page 146

Artifacts can be reused in multiple contexts in a project, including collections and modules. You can edit

artifact content in a module or by opening the artifact outside the module. Content changes are reflected

in all contexts. Links, tags, and comments are specic to the context in which they are created. If you

want links, tags, and comments to reflect in all contexts, edit the artifact outside the module as a base

artifact.

Link constraints in the RM application

Link constraints are rules that an administrator can set up to specify which kinds of links are allowed in a

project or across projects. If no rules are created, all links are allowed. However, if you create rules, only

the links in the rules are allowed.

Administrators can create link rules on the Link Constraints tab in the project properties. These rules

govern the creation of links in Requirements Management (RM) projects and across RM projects on the

same server.

Note:

• Link constraints cannot span applications.

• Link constraints are supported only for RM Link types such as Link To and RM user-dened link types.

Link types that are OSLC-based such as Referenced By or Validated By or that are used for linking to

other applications are not supported.

Link creation with link constraints

After you create link rules, the options for creating links from context menus and in the Create Link

window are affected by those rules.

In the following example, a single rule species that a Business Goal artifact has a Satises link to a Vision

artifact:

Because this is the only rule in the project, no other links are allowed. If you are creating a link from a

Vision artifact or Business Goal artifact, only the Satises and Satised By link types are available. No

other link types are available from any other artifacts.

For example, if you create a link from a Business Goal artifact, only the Satises link type appears as a

menu option:

 Engineering Requirements Management DOORS Next

In addition, in the Create Link window, you can select only those artifact types that are allowed based on

the initial artifact type and the selected link type, as shown in the following image:

In the Create Link window, you can also select certain components and artifact types based on dened

link constraints, including the artifact types that contain a cross-component artifact type.

Administering

Tip: Link rules constrain only new links that are created. Links that existed before you created or changed

the rules are not affected by the new rules. However, you can search for and manually modify links that

don't adhere to any new or changed constraints; for example, if the link type is no longer allowed, but the

artifact types do satisfy the constraints, then you can change the link type. However, if the artifact type is

not allowed, then you can only delete the link type.

Cross-project linking

To enable linking between artifacts in different projects, you must dene a rule that allows linking for the

particular link type in both projects, and the rules must match. When you create cross-project links, rather

than using ANY as the link end, you can select a specic artifact type in target project.

For example, for the "Link (Link To/Link From)" link type, if you want Business Goal artifacts in Project 1

to link to Feature artifacts in Project 2 (which also implies that Feature artifacts in Project 2 can link from

Business Goals in Project 1), you must dene the rules as follows:

Project 1:

Project 2:

These rules match because both directions of the link type are allowed in each project.

Note: If a project does not have any constraints, it is compatible with all rules. For example, suppose

Project 1 has a rule that a Feature artifact can link to any artifact type. If Project 2 does not have any

constraints that are dened, the Feature artifact in Project 1 can link to any artifact in Project 2. However,

if Project 2 has constraints that are dened, an explicit matching rule must exist in Project 2.

When you create link constraints, you can also select a cross-project or cross-component type as a link

end. The cross-project or cross-component name is displayed after the artifact type name. For example,

you can create a constraint such as Business Goal (Project A) Link To Vision (Project B), where Business

Goal is the source artifact type, (Project A) is the source cross project type, Link To is the link type, Vision

is the target artifact type, and (Project B) is the target cross project type.

Note: If you add a link constraint for a remote project, and that project is enabled for conguration

management, you must be working in a global conguration.

Cross-component linking

 Engineering Requirements Management DOORS Next

To enable linking between components, you must dene a rule that allows linking for the particular link

type in both components. When you create cross-component links, you can select a cross-component

type as a link end. The cross-component name is displayed after the type name in cross-component

types.

Note: If you want to enforce link constraints for remote components, you must be working in a global

conguration that supports cross-component linking.

Cross-project or cross-component linking is automatically enabled for system-dened link types.

However, if link constraints are set the cross-project and cross-component linking is governed by the

link constraint rules.

Cross-project linking and Cross-component linking for a custom link type

For cross-project or cross-component linking for a custom link type, you dene a URI for the link type.

For example, https://hostname.com/domain/myLabel. If you use link constraints, you must dene

equivalent URIs for the requirement types. If the URI of an artifact included in a link constraint is edited,

the link constraint is not updated with the new URI. Since the link constraint is not updated the custom

link type will no longer have the link constraint that is applied to. It is invalid since no type matches

previous RDF URI and therefore it will not be displayed under link constraints section.

Flexibility for link rules

You can make link rules more flexible by using ANY as the target artifact type. For example, if you create

a "Link" link type for a Business Process Diagram artifact, and you specify ANY as the target artifact type,

you can create links from a Business Process Diagram artifact to any artifact type in the current project.

In addition, you can specify ANY in a link rule to enable links to web resources or to artifacts in another

RM project.

Automatic generation of link constraints

As a project administrator, you can automatically generate link constraint rules based on the existing link

relationships by clicking Generate Rules. The link constraint rules that are required to satisfy existing

link relationships are identied and appended to the list. If your project includes cross-project links, the

cross-project rules are also automatically created for the specify project. To create the corresponding

rule, you must click Generate Rules in the linked project.

You cannot automatically generate link constraints for custom types. If you create two projects that each

have their own custom type, and create a link between them, when you click Generate Rules, the rules

are created by using the ANY keyword. For example, the rst project would contain a Project1CustomType

Link to ANY rule, and the second project would contain an ANY Link To Project2CustomType rule.

Preferred link types

Preferred link types that you specify for an artifact type are subject to the link rules that are in effect. For

example, if you have a preferred link type of Satises for an artifact type, but your link rules do not allow

this link type, the Satises link type is ignored.

Versioning constraints

Constraints are versioned and handled by the conguration management capabilities; they can vary

across congurations, be delivered in change sets, and can be compared and merged.

Related concepts

Linking artifacts in different projects or components

A link represents a relationship between artifacts. Link relationships are directional and indicated by an

icon. Link types help you dene and customize the linking relationships between artifacts. Each link type

has an Outgoing and an Incoming role. You can create links between artifacts in different projects on

Administering

the same server or on different servers. If you enable conguration management, you can create links

between artifacts in different components.

“Links between artifacts” on page 203

A link represents a relationship between artifacts. Links are mechanisms for referring to related

information. You create some links manually. Other links are created automatically when you complete

certain tasks. There are different properties for trace links, content links, links to base artifacts, and links

in modules.

Related tasks

“Creating link types for requirements projects” on page 36

“Managing project or component properties in requirements projects” on page 28

Each project template contains predened artifact types. You can also create customized artifact types,

artifact attributes, and artifact data types for a project or component. Those artifacts types can then

be used by team members to create project or component requirements or related artifacts, such as

customized collections.

Related reference

“Link types in requirements projects” on page 37

Creating templates for requirements projects or components

You can create a project or component template, and select the elements to include in it. When

conguration management is not enabled, you create templates for a project. When conguration

management is enabled, you create templates for a component. You can include or exclude artifacts,

artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags,

and shared saved lters. After you create templates, you cannot modify them.

Before you begin

To create requirements templates, you must have an Analyst client access license. You must also have at

least one of the following prerequisites:

• JazzAdmins repository permissions

• The Administrator role in the project

Important: Applying project templates from a version n of DOORS Next to a n-1 is not supported. For

example, you cannot apply a project template from 7.x version to 6.x version for creating project areas.

To view your repository permissions and client access license, open a project. From the User Prole

, click View My Prole and Licenses. To view your project role, from the Administration

menu , click Manage This Project Area.

About this task

To create templates, you open an existing project or component and create the template.

Procedure

To create a template, open an existing project or component and complete these steps:

1. Click the Administration menu

and click Manage Project Properties.

If conguration management is enabled for your project, on the Administration menu, click Manage

Component Properties.

2. On the project administration page, click the Templates tab.

3. From the list on the left, select Project Templates.

If conguration management is enabled for your project, on the Administration menu, click

Component Templates.

 Engineering Requirements Management DOORS Next

4. Click New Template.

5. In the Create Template window, specify the name, description, and the items to include in the

template, and then click OK.

Some items in the list have dependencies on other items; therefore, some items are selected by

default when you select others.

What to do next

The next time that you create a requirements project or component, you can select the new template

from the New Project wizard. To know more about how to edit, delete, download, or upload a template,

see Managing requirements project templates

Note: After you create a template, you cannot modify it. You also cannot modify any predened templates

that are provided with the application. To create a revised version of a template, create a project or

component from the template, modify and save the project or component, and then create a template

from it.

The default size limit for templates is approximately 10,000 artifacts, although this value varies by

product version. If you have several thousand artifacts, you can override the default size limit.

Related concepts

“Error occurs during project template creation for a large project” on page 267

If an error occurs when you try to create a project template, you can resolve the error by using one of the

following solutions:

Related tasks

“Managing artifact templates” on page 59

You can delete or edit artifact templates from the project administration Templates page. You can also

update the template with any changes in the artifact that the template is based on.

Related information

Creating components

Managing templates for requirements projects or components

You can delete, download, modify, and upload templates for requirements projects or components.

When conguration management is not enabled, you manage templates for projects. When conguration

management is enabled, you manage templates for components. You use the download and upload

capabilities to copy a template to another Jazz repository.

Before you begin

To delete, modify, or upload a template, you must have the following prerequisites:

• An Analyst client access license

• JazzAdmins repository permissions

To view your repository permissions and client access license, open a project. In the upper-right corner,

from the User Prole menu

, click View My Prole and Licenses. To view your project role, from

the Administration menu , click Manage This Project Area. To complete this task, you must be in

a project or component, or dashboard.

Important: You cannot use a template as a backup because the artifact history, comments, reviews, and

access controls are not preserved. Templates do not preserve the links that are outside of the artifacts.

About this task

The following procedure is for managing project templates. The process for managing component

templates is similar, but the names and labels are specic to components. In projects enabled for

congurations, you manage component templates.

Administering

Procedure

• To edit, delete, or download a project template by using the web client:

a) Open a project, click the Administration menu , and select Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

b) On the project administration page, click the Templates tab.

c) In the Templates list, click Project Templates.

d) Select a template in the list, click the Edit menu

to the right of the entry, and select one of the

following options:

– Click Edit to open the Manage Template window where you can change the template name and

description.

– Click Delete to remove the template from the repository.

– Click Download to save the template to your computer as a template archive le. Templates that

you download do not include comments, reviews, history, or access controls.

• To upload a template:

Important: Project templates from a different DOORS Next version are not supported.

a) Click Upload Template.

b) In the Upload Project Template window, browse to and select the template archive le to upload.

c) Click Upload. After the upload is complete, click Close.

The uploaded template is displayed in the template list.

Related tasks

“Creating templates for requirements projects or components” on page 46

You can create a project or component template, and select the elements to include in it. When

conguration management is not enabled, you create templates for a project. When conguration

management is enabled, you create templates for a component. You can include or exclude artifacts,

artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags,

and shared saved lters. After you create templates, you cannot modify them.

Related information

Modifying a Lifecycle Project Application template to access a requirements project template

Requirements project templates

You can use several different templates to create new requirements projects.

Important: Applying project templates from a version n of DOORS Next to a n-1 is not supported. For

example, you cannot apply a project template from 7.x version to 6.x version for creating project areas.

The following table provides a brief description of some of the sample project templates. However, for

a more comprehensive list of the artifact types, artifact attributes, attribute data types, link types, and

templates that comprise each sample, create a project by using a project template and then click Manage

Project Properties from the Administration menu.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

Note: SAFe 6.0 templates for IBM Engineering Lifecycle Management (ELM) are available on Jazz.net.

You can download the templates from SAFe 6.0 templates for IBM Engineering Lifecycle Management.

The available predened process templates are Full SAFe 6.0 and Essential SAFe 6.0. You can use

them to congure tooling environment for SAFe Portfolio, Large Solution, Portfolio, or Essential SAFe 6.0

conguration in ELM. For more information, see Say Hello to SAFe 6.0!.

 Engineering Requirements Management DOORS Next

Table 4. Project templates

Project Template Description

Agile Requirements Sample Provides a sample agile component that contains the user

stories and requirements for a ctitious company. The following

artifact types are included in this sample:

• Feature

• Non-Functional

• Part

• Personal Collection

• Release Collection

• Simple Flow Diagram

• Wireframe

• Supporting Resource

• Term

• User Story Elaboration

Agile Requirements Template Provides artifact types, attributes, data types, and a project

folder structure to support the agile process. It includes

an artifact type and a document template for user story

elaboration. The following artifact types are included in this

template:

• Feature

• Non-Functional

• Part

• Personal Collection

• Release Collection

• Simple Flow Diagram

• Sketch

• Supporting Resource

• Term

• User Story Elaboration

Administering49

Table 4. Project templates (continued)

Project Template Description

JKE Banking Sample Provides a sample application that includes a full project

structure with folders and sample artifacts to support a

ctitious banking program. If you are a rst-time user, use

this option to look at sample artifacts and to see how artifacts

can be linked. The following artifact types are included in this

template:

• Actor

• Business Goal

• Business Process Diagram

• Business Rule

• Collection

• Feature

• Goal

• Graphical Artifact

• Heading

• Non Functional

• Process Guidance

• Requirement

• Supporting Resource

• Term

• Use Case Diagram

• Use Case Requirement

• Use Case Specication

• User Story Elaboration

• Vision

 Engineering Requirements Management DOORS Next

Table 4. Project templates (continued)

Project Template Description

Medical Devices Template Provides a structure to support medical device developers

in meeting FDA Design Control requirements. The following

artifact types are included in this template:

• Document - Module

• FMEA - Object

• Glossary Term

• Heading

• Information

• Reference - Module

• Risk

• Risk - Module

• Stakeholder Denition

• Stakeholder Requirement

• Stakeholder Requirements - Module

• System Function

• System Requirement

• System Requirements - Module

• Trade Study Document

• Trade Study Assessment Criterion

• Vision Document - Module

• Vision Statement

Requirement Template for Testers

Provides a structure to support testers. Includes a folder called

Testers. The following artifact types are included in this

template:

• Requirement

• Test Plan Collection

SAFe 4.0 Portfolio Component

Template

Provides a structure to support a project with Scaled Agile

Framework environment (SAFe ) artifact types, link types,

templates, folder structure, and views. The following artifact

types are included in this template:

• [SAFe] Lightweight Business Case

• [SAFe] Strategic Theme

• [SAFe] Value Stream

• Free-Form Diagram

• Heading

• Information

• Program Increment Collection

• Role

• Supporting Doc

• Term

Administering51

Table 4. Project templates (continued)

Project Template Description

SAFe 4.5 Essential Component

Template

Provides a structure to support a project with Scaled Agile

Framework environment (SAFe ) artifact types, link types,

templates, folder structure, and views. The following artifact

types are included in this template:

• Program

• Vision

SAFe 4.5 Portfolio Component

Template

Provides a structure to support a project with Scaled Agile

Framework environment (SAFe ) artifact types, link types,

templates, folder structure, and views. The following artifact

types are included in this template:

• Strategic Theme

• Value Stream, Program

• Vision, Solution Intent

• Solution Context

• Lean Business Case

• Lifecycle Scenario

• Scenario Act

• Scenario Scene

SAFe 4.5 Large Solution Component

Template

Provides a structure to support a project with Scaled Agile

Framework environment (SAFe ) artifact types, link types,

templates, folder structure, and views. The following artifact

types are included in this template:

• Value Stream

• Program

• Vision

• Solution Intent

• Solution Context

• Lean Business Case

• Lifecycle Scenario

• Scenario Act

• Scenario Scene

52 Engineering Requirements Management DOORS Next

Table 4. Project templates (continued)

Project Template Description

SAFe 4.5 Full Component Template Provides a structure to support a project with Scaled Agile

Framework environment (SAFe ) artifact types, link types,

templates, folder structure, and views. The following artifact

types are included in this template:

• Strategic Theme

• Value Stream, Program

• Vision, Solution Intent

• Solution Context

• Lean Business Case

• Lifecycle Scenario

• Scenario Act

• Scenario Scene

System Requirements Sample Provides a sample application that includes a full project

structure with folders, modules, and sample artifacts to

support a ctitious program called Automated Meter Reader.

The following artifact types are included in this sample:

• Actor

• Diagrams and sketches

• Hardware Requirement

• Hardware Specication

• Hazard and Risk

• Hazard and Risk Register

• Heading

• Information

• Personal Collection

• Release Collection

• Requirements Specication

• Software Requirement

• Software Specication

• Stakeholder Requirement

• Stakeholder Specication

• System Requirement

• System Specication

• Term

• Use Case Module

• Vision Statement

• Vision Document

Administering

Table 4. Project templates (continued)

Project Template Description

System Requirements Template Provides a structure to support a systems engineering

component. The following artifact types are included in this

template:

• Actor

• Diagrams and sketches

• Hardware Requirement

• Hardware Specication

• Hazard and Risk

• Hazard and Risk Register

• Heading

• Information

• Personal Collection

• Release Collection

• Requirements Specication

• Software Requirement

• Software Specication

• Stakeholder Requirement

• Stakeholder Specication

• System Requirement

• System Specication

• Term

• Use Case Module

• Vision Statement

• Vision Document

 Engineering Requirements Management DOORS Next

Table 4. Project templates (continued)

Project Template Description

Traditional Requirements Sample Provides a sample enterprise component that contains the

enterprise requirements, terms, and other artifacts for a

ctitious company. The following artifact types are included in

this sample:

• Actor

• Business Goal

• Business Process Diagram

• Business Rule

• Collection

• Feature

• Heading

• Non Functional

• Persona

• Process Guidance

• Storyboard

• Supporting Resource

• Term

• Use Case Diagram

• Use Case Requirement

• Use Case Specication

• User Story Elaboration

• Vision

Traditional Requirements Template

Provides a structure to support traditional requirements

projects. Artifact types include features, software

requirements, stakeholder requests, sketches, parts, use case

diagrams, and terms. The following artifact types are included

in this template:

• Feature

• Heading

• Information

• Personal Collection

• Release Collection

• Requirement Specication

• Software Requirement

• Stakeholder Request

• Term

Administering55

Table 4. Project templates (continued)

Project Template Description

Use Case Requirements Sample Provides a sample use case component that contains the use

cases, diagrams, and requirements for a ctitious company.

The following artifact types are included in this sample:

• Actor

• Feature

• Heading

• Information

• Personal Collection

• Process Diagram

• Release Collection

• Requirement Specication

• Sketch

• Stakeholder Request

• Supplementary

• Term

• Use Case

• Use Case Diagram

Use Case Requirements Template Provides a structure to support use-case-driven requirements

projects. Artifact types include features, use cases, business

process diagrams, supplementary requirements, stakeholder

requests, sketches, parts, use case diagrams, and terms. The

following artifact types are included in this template:

• Actor

• Feature

• Heading

• Information

• Personal Collection

• Process Diagram

• Release Collection

• Requirement Specication

• Sketch

• Stakeholder Request

• Supplementary

• Term

• Use Case

• Use Case Diagram

Scaled Agile Framework (SAFe) project templates

The Scaled Agile Framework (SAFe) methodology is an industry standard framework for helping

organizations scale agile and lean practices to an enterprise level. The framework denes roles, activities,

artifacts, and workflows that provide best practices and guidance for enterprises to use lean and agile

principles across the organization, which spans both business and engineering roles. This helps to deliver

value across agile portfolios that includes solutions, programs, and teams.

 Engineering Requirements Management DOORS Next

Requirements management is a key aspect of the SAFe methodology that takes a systems view of

the features that are being delivered, capturing expected behavior, models, wireframes, and related

requirements to drive an iterative approach to feature delivery.

Note: SAFe 6.0 templates for IBM Engineering Lifecycle Management (ELM) are available on Jazz.net.

You can download the templates from SAFe 6.0 templates for IBM Engineering Lifecycle Management.

The available predened process templates are Full SAFe 6.0 and Essential SAFe 6.0. You can use

them to congure tooling environment for SAFe Portfolio, Large Solution, Portfolio, or Essential SAFe 6.0

conguration in ELM. For more information, see Say Hello to SAFe 6.0!.

Related information

Scaled Agile Framework (SAFe) 5.0 Essential process template

Scaled Agile Framework (SAFe) 5.0 Full process template

Scaled Agile Framework (SAFe) 5.0 Quality Management process templates

Scaled Agile Framework (SAFe) 5.0 Requirement Management process templates

Requirements management is a key aspect of the SAFe

methodology that takes a systems view of

the features that are being delivered, capturing expected behavior, models, wireframes, and related

requirements to drive an iterative approach to feature delivery.

This release provides two predened process templates that support Scaled Agile Framework (SAFe) to

help you capture expected behavior and related requirements across all the congurations:

• Full: Portfolio level and Large Solution level

• Essential: Program level and Team level

You can use each template to create a Requirement Management project area that includes the necessary

roles, artifact templates and categories, and dashboard for that conguration.

Requirement Management for Full SAFe 5.0

Use this SAFe template to establish a requirements management environment that contains the artifacts

that are required to support design, development and delivery of a Portfolio including multiple Large

Solutions, or Value Streams, orchestrating delivery of Features across Programs.

The SAFe artifacts that are included with this template are Portfolio Canvas, Value Stream Canvas, SWOT

Analysis, TOWS Options Matrix, Strategic Theme with Objectives and Key Results (OKR), Value Stream,

Program, Vision, Solution Intent, Solution Context, Lean Business Case, Lifecycle Scenario, Scenario Act,

and Scenario Scene. This environment might be associated with one or more Essential SAFe tooling

environments.

Requirement Management for Essential SAFe 5.0

Use this SAFe template to establish a requirements management environment that contains the artifacts

that are required to support design, development, and delivery of Program Features and Stories. The SAFe

artifacts that are included with this template are Program, Vision, and Solution Context. This environment

might be associated with a Portfolio, Large Solution, or Full SAFe tooling environment.

For more information, see IBM support for SAFe

Scaled Agile Framework (SAFe) 4.6 Requirements Management process templates

Requirements management is a key aspect of the SAFe

methodology that takes a systems view of

the features that are being delivered, capturing expected behavior, models, wireframes, and related

requirements to drive an iterative approach to feature delivery.

This release provides two predened process templates that support Scaled Agile Framework (SAFe) to

help you capture expected behavior and related requirements across all the congurations:

• Full: Portfolio level and Large Solution level

• Essential: Program level and Team level

Administering

You can use each template to create a Requirement Management project area that includes the necessary

roles, artifact templates and categories, and dashboard for that conguration.

Requirement Management for Full SAFe 4.6

Use this SAFe template to establish a requirements management environment that contains the artifacts

that are required to support design, development and delivery of a Portfolio including multiple Large

Solutions, or Value Streams, orchestrating delivery of Features across Programs. The SAFe artifacts that

are included in this template are Portfolio Canvas, Value Stream Canvas, Strategic Theme, Value Stream,

Program, Vision, Solution Intent, Solution Context, Lean Business Case, Lifecycle Scenario, Scenario Act,

and Scenario Scene. This environment might be associated with one or more Essential SAFe tooling

environments.

Requirement Management for Essential SAFe 4.6

Use this SAFe template to establish a requirements management environment that contains the artifacts

that are required to support design, development, and delivery of Program Features and Stories. The SAFe

artifacts that are included in this template are Program and Vision. This environment might be associated

with a Portfolio, Large Solution, or Full SAFe tooling environment.

For more information, see IBM support for SAFe

Creating artifact templates

You can create an artifact template from an existing artifact. Artifact templates offer an easy way to reuse

artifact content and related properties as a basis for new artifacts.

Before you begin

You must have project administrator permission to create an artifact template.

About this task

Artifact templates:

• Are tied to the artifact type and format of the artifact on which they are based.

• Include the artifact content, attributes, attribute values, and links.

• Do not include tags and comments.

• Can be used only to create new artifacts of the same type and format.

For information on creating templates from modules, see Creating module templates

Procedure

For a quick way to create a template from an open artifact, click the Create Artifact Template icon

in the toolbar, or perform the following steps.

To create an artifact template from the Administration page:

1. Open a project by using the web client and click the drop-down menu at the Administration icon

and select Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

An administrative page opens.

2. Click the Templates tab.

3. In the Templates list, click Artifact Templates.

4. Click New Template.

5. In the Create Template window, specify the name and optional description for the template.

 Engineering Requirements Management DOORS Next

6. In the Create template based on eld, click Browse to locate an artifact for the basis of the template.

7. In the Search for artifacts eld, enter a partial name for an artifact.

All artifacts that match the partial entry are displayed in the Select artifact list.

8. Select an artifact as the basis for the new template and click OK.

9. On the Create Template window, click Create. After the operation is complete, click Close.

What to do next

When you create a new artifact, you can base it on this artifact template. Lists of templates are organized

by artifact type and artifact format. When creating an artifact, you must select the artifact type to view all

templates associated with that type.

Note: You can view templates in the Template eld of the Create an artifact with attributes

dialog.

After you create an artifact from the template, the content of that artifact is independent of the template

and the original artifact that the template was based on. Any changes to the original artifact and its

template are not reflected in the new artifact.

Managing artifact templates

You can delete or edit artifact templates from the project administration Templates page. You can also

update the template with any changes in the artifact that the template is based on.

About this task

You must have project administrator permissions to delete or edit an artifact template.

Procedure

To delete or edit an artifact template using the web client:

1. Open a project, click the drop-down menu at the Administration icon

and select Manage

Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

A project administration page opens.

2. Click the Templates tab.

3. In the Templates list, click Artifact Templates.

4. Select a template in the list and click the drop-down menu at the Edit icon at the right end of the

entry and select Delete or Edit.

5. If you select Edit, the Manage Template window opens and you can do any of the following actions:

• Change the template name.

• Change the template description.

• Update the contents of the artifact template with any changes that have been made in the artifact

since it was used to create the template.

6. Click OK to complete the operation.

Creating module templates

You can create a module template from an existing module. Module templates offer an easy way to reuse

structure and content as a basis for new modules. When you create a module template, you have options

Administering

to create copies of the headings and other artifacts from the source module, or reuse and share the

source content in the new module.

Before you begin

You must have project administrator permissions to create templates.

About this task

In a module template, you can reuse the headings and other artifacts that are in the source module, or

you can copy (duplicate) them to create headings and other artifacts in the template.

When you create a module template, the content of the module is not saved in the template. If the

module that the template is based on is changed, the next artifact that is created based on that template

contains the changes.

When you create an artifact template, the content of the artifact is saved in the template. If the artifact

that the template is based on is changed, the next artifact that is created based on that template will not

contain the changes.

Procedure

1. Open a project in the web client, click the Admin menu (

), and click Manage Project

Properties.

2. Click the Templates tab.

3. In the Templates list, click Artifact Templates.

4. Click New Template.

The Create Template window opens.

5. Specify the name and optional description for the template.

6. Next to the Create template based on eld, click Browse to locate a module for the basis of the

template.

7. In the Search for artifacts eld, enter a partial name or ID for a module.

All artifacts that match the partial entry or ID are displayed in the Select artifact list.

8. Select a module as the basis for the new template and click OK.

9. In the Create Template window, in the Duplication policy eld, select one of the following options to

copy or reuse content in the new module:

• Duplicate all artifacts: Creates headings and other artifacts. These are copies of the headings

and artifacts that are in the source module.

• Duplicate no artifacts: Reuses all existing headings and other artifacts. The only new artifact is

the module that a user creates from the template.

• Duplicate all heading artifacts: Creates headings that are copies of the existing ones, and reuses

other existing artifacts.

• Re-use all heading artifacts: Reuses existing headings. Creates copies of all other artifacts.

• Duplicate all artifacts specied by a view, re-use all other artifacts: Creates headings and

other artifacts that are copies of existing ones if they match the criteria of lters in a saved view.

All other headings and artifacts are reused. If you use this option, a menu is displayed from which

you can select the view to use.

10. Click Create.

What to do next

For options to manage the template, from the Project Properties page, click Template. You can select

commands from the menu

to the right of any module template in Artifact Templates list.

 Engineering Requirements Management DOORS Next

• To edit the template, click Edit. In the Manage Template window, you can change the template name,

description, or duplication policy.

• To modify the content of the module that is the source for the template, click Edit Content. The source

module opens. Any changes that you make to reused content affects all instances of that content in the

project. Any changes to duplicated content is reflected in any modules that are created subsequently

from the template.

• To remove the template from the project, click Delete.

Related tasks

“Reusing artifacts in modules” on page 146

Artifacts can be reused in multiple contexts in a project, including collections and modules. You can edit

artifact content in a module or by opening the artifact outside the module. Content changes are reflected

in all contexts. Links, tags, and comments are specic to the context in which they are created. If you

want links, tags, and comments to reflect in all contexts, edit the artifact outside the module as a base

artifact.

Importing properties from another Requirements Management (RM) project

or component

You can import the properties from one Requirements Management (RM) project or component into

another project or component. When conguration management is not enabled, you import properties

from project to project. When conguration management is enabled, you import properties from

component to component. The properties that are imported by default include all the artifact types,

attribute data types, link types, and link constraints that are dened in the project or component.

Before you begin

To import properties, you must have both the administrator role and permissions:

• In the project area settings, you must be listed in the Administrators section.

• In the project area settings, you must be listed in the Members section and have the Administrator role

assigned.

About this task

To import properties, you open a project or component and then import the properties from another

project or component into the current one.

Note: Only the default properties such as artifact types, artifact attributes, attribute data types, link types,

and link constraints that are dened in the project or component are imported.

Note: If an artifact type is associated with the workflow, the association is not preserved in the current

component after the import.

Procedure

1. In RM, open the project into which you want to import project properties.

2. From the Administration menu

, click Manage Project Properties or Manage Component

Properties.

3. In the upper right of the screen, click Import.

4. In the Import Project Properties window, click Browse and select the project from which you want to

import the type system.

Important: If you import a type system into two different streams in a component, the type system

is duplicated when changes are delivered between these streams. The application does not recognize

that the type system is same and creates a duplicate type system. To avoid this problem, use a special

stream in each component for the type systems in that component. Then, merge any type system

Administering

changes from that special stream to all of the development streams in that component. For best

practices and additional information about the type systems, see the following articles:

• Maintaining the Rational DOORS Next Generation type system in a conguration-management-

enabled environment. Part 1: Manual procedures

• Maintaining the Rational DOORS Next Generation type system in a conguration-management-

enabled environment. Part 2: Automation

• Maintaining the Rational DOORS Next Generation type system in a conguration-management-

enabled environment. Part 3: Automation tool deep dive

5. Click OK and then click Next.

6. Review the property changes and click Finish.

Note: If both projects have properties with the same name, the properties are merged in the current

project.

Results

When the import process is complete, refresh the project to see the new properties.

Related tasks

“Copying artifacts between projects” on page 62

You can copy artifacts between projects in the Requirements Management (RM) application.

“Managing project or component properties in requirements projects” on page 28

Each project template contains predened artifact types. You can also create customized artifact types,

artifact attributes, and artifact data types for a project or component. Those artifacts types can then

be used by team members to create project or component requirements or related artifacts, such as

customized collections.

“Creating link types for requirements projects” on page 36

Copying artifacts between projects

You can copy artifacts between projects in the Requirements Management (RM) application.

Before you begin

Before you copy artifacts between projects, verify the following items:

• You are logged in as a user with JazzAdmins or JazzProjectAdmins repository permissions. You are

assigned the Administrator role.

• Both projects have the same setting for conguration management: either both are enabled or both are

disabled.

• If you use global congurations, ensure that you are using a global conguration that has contributions

from both projects.

• The target project contains the same artifact types, artifact attributes, and attribute data types as the

artifacts in the source project.

Important: To copy artifacts, the target project must contain the same artifact types as the source

artifacts that are being copied, including URIs or artifact names. Otherwise, no artifacts are copied.

If the target project does not contain the same artifact attributes or attribute data types, the source

artifacts are copied, but the attribute values are not.

Note: When copying and pasting modules or collections across components or projects, the shared and

private views of the module or collection are copied. If the target component or project contains views

that are shared across all modules or collections of the same type or shared across all modules or

collections. And have the same name as the reused views in the copied module or collection, the copied

views are not resolved. Instead, multiple views with the same name exist after the paste operation is

run and must be resolved manually.

In projects that are enabled for conguration management, conrm whether you want to copy artifacts

between components or clone them. To help you decide, see Cloning artifacts between components.

 Engineering Requirements Management DOORS Next

About this task

You can copy most artifacts between projects, including collections, modules, embedded artifacts, and

diagrams. However, the copy function does not support copying the following items:

• Graphical artifacts that require a browser plug-in, such as sketches, storyboards, screen flows, and

business and use case diagrams

• Tags

• Comments

Note: Copying and pasting of artifacts between streams in the same component is not allowed. A more

appropriate way to move data from one stream to another is to deliver the change set(s) that contain that

data. This ensures you get the same concept in both places and that the version history is correct. At that

point, if you want to copy the artifact somewhere else within the stream you may do so. Alternatively, you

can also copy or paste within your current stream and then deliver the change set.

Procedure

1. Verify that the target project contains the same artifact types, artifact attributes, and attribute data

types as the artifacts that you plan to copy. To view the project properties, complete these steps:

a) Open the target project, click the drop-down menu for the Administration icon and select

Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

b) Click the Artifact Types tab, the Artifact Attributes tab, and the Attribute Data Types tab.

Tip: If your target project does not contain the necessary project properties, you can import the

artifact type system from the source project. For information about importing the type system from

another project, see Importing project properties

Important: To copy artifacts between projects, the value in the URI eld for artifact types or the

artifact names in both the source and target projects must match. The URI value or name must also

match between source and target artifact attributes and between artifact data types.

The value in the URI elds must be in this format:

https://hostname/word1/word2

For example, if you work for a company that is called Big-Bank, and you want to copy artifacts of

type Actor from a source project, you might put the following value in the Actor artifact type URI

eld:

https://www.big-bank.com/types/actor

If you copy the type system from the source project to the target project, you ensure that the value

in the source URI eld gets propagated to the target URI eld in the target project.

2. In the target project, right-click the folder into which to copy the artifacts and click Copy from a

project.

3. In the wizard that opens, follow the prompts to select the project, and the artifacts or modules to copy.

When you select modules, all the views from those modules will be copied from the source to the

target.

Tip: You can also view the collections that need to be copied or cloned to the target project by clicking

the Add Collection button.

4. If the servers are hosted by the same domain server or different domain servers, you can also use the

Paste as Link option between components on different servers.

a) Copy the source artifact.

b) Select the target artifact and click Paste as Link.

Administering

c) In the Create Link window, select the link type.

d) Click OK and a Link has been created message will be displayed.

Related concepts

“Linking artifacts in different projects or components” on page 206

A link represents a relationship between artifacts. Link relationships are directional and indicated by an

icon. Link types help you dene and customize the linking relationships between artifacts. Each link type

has an Outgoing and an Incoming role. You can create links between artifacts in different projects on

the same server or on different servers. If you enable conguration management, you can create links

between artifacts in different components.

Related tasks

“Importing properties from another Requirements Management (RM) project or component” on page 61

You can import the properties from one Requirements Management (RM) project or component into

another project or component. When conguration management is not enabled, you import properties

from project to project. When conguration management is enabled, you import properties from

component to component. The properties that are imported by default include all the artifact types,

attribute data types, link types, and link constraints that are dened in the project or component.

“Creating link types for requirements projects” on page 36

“Creating attributes for requirement artifacts” on page 31

When you create requirements in a project, you can create custom artifact attributes to use in custom

artifact types. Custom attributes are based on predened and custom artifact data types, which dene the

properties of the attribute, such as textual entries, integers, date, time, or team member names.

Related reference

“Link types in requirements projects” on page 37

Related information

Cloning artifacts between components

 Engineering Requirements Management DOORS Next

Deleting artifacts from the repository

You can permanently delete artifacts from a Requirements Management (RM) application repository by

using the Delete from Repository feature. Use this procedure to delete sensitive data or to resolve a data

spill.

Before you begin

Warning: This feature is intended only as a mechanism to carefully and permanently delete

sensitive data from a repository and should not be used for reducing database size or deleting

general resources.

To enable this feature, you must meet the following conditions:

• Use version 6.0.2 or later (for 6.x versions).

• Use version 7.0.2 or later (for 7.x versions).

• Have the JazzAdmins permission.

• Set the data.purge.enabled advanced property to true.

• Set the dump.dir advanced property to an absolute le system path.

• Have access to the RM application server le system.

Important:

• In previous 6.x versions, data was stored by using the Jazz Foundation Service (JFS) APIs only and was

referred to as JFS data. The JFS data was deleted by using the delete feature. However, starting with the

7.0 version, most of the data is created and managed by using the 0.6 API storage mechanism and is

referred to as 0.6 data. The deletion process and behavior for 0.6 data is different as compared to JFS

data. When you use the delete feature, the 0.6 data is redacted or edited in-place while the JFS data is

deleted. For more information, see Difference between JFS data and 0.6 data.

• The Delete Resource Data wizard is no longer available in the application under the Delete from

Repository tab. You must use a repotools command to delete the data due to restrictions on the

API that manages and updates 0.6 data. DOORS Next server must not be online when you run this

command. For more information, see Running the purge repotools command.

About this task

Typically, when you delete an artifact from an RM project, the artifact is removed from the project and is

archived in the repository. However, if you have sensitive data that you want to permanently delete from

the repository, you can use the Delete from Repository feature to accomplish this task.

The Delete from Repository process for JFS data and 0.6 data includes three main steps.

1. Identify the artifacts for deletion. You can use the Export Data Dump option to export resources to the

le system where you can analyze them for sensitive data.

For 0.6 data, all the data for the

selected component or project is exported. For JFS data, you might choose to limit it to only a subset

of the storage areas most likely to contain sensitive data or export the content of all storage areas. You

can search through these exported les to identify which resources contain sensitive information. The

search result creates a list of URLs for the versions that require deletion.

Note: A project area is selected for export, by default.

2. Create a list of version URLs for the system to delete JFS data. For 0.6 data, append a set of

serialized-item-handles to redact the 0.6 data. This list must be stored in a plain text le and have only

one URL per line. For more information, see Running the purge repotools command.

3. After the system deletes or redacts the specied URLs and their history, you verify that all the sensitive

data was purged from the repository. To do this, you export the data to the le system again, repeat the

search for sensitive data, and then delete all the les that were exported.

Administering

For more information and instructions for deleting sensitive data, see Delete from Repository feature on

Jazz.net.

Note: Content on Jazz.net is governed by the Jazz.net Terms of Use and is provided as-is without

warranties of any kind.

Administering link validity in ELM applications

As a conguration lead or application administrator, you decide whether to show or hide link validity

and validity summary information for your project area. These tasks are common to the IBM Engineering

Lifecycle Management (ELM) applications that use link validity.

About this task

See Enabling link validity in AM, QM, and RM project areas to read about showing and hiding link validity

information in your project area.

Quality Management application: If your project area does not have conguration management

capabilities enabled, you cannot use this feature. Project areas not enabled for congurations use suspect

link traceability. For details, see Suspect traceability.

To learn more about link validity, see the related links.

To learn more about conguration management:

• https://www.ibm.com/docs/en/elms/elm/7.0.2?topic=SSYMRC_7.0.2/com.ibm.jazz.vvc.doc/topics/

c_cm_assess.htmlGetting started with conguration management: Learn about conguration

management and local congurations.

• Global Conguration Management: Learn how global congurations provide a view of all the artifacts

that are contained in a set of related local congurations. Global congurations are managed by the

Global Conguration Management (GCM) application.

• Introduction to conguration management with IBM Engineering Lifecycle Management (ELM): YouTube

playlist on the Software Education channel.

Related tasks

Granting access to link validity data for building Report Builder reports

Related information

YouTube video: Achieving consistency across linked data by using link validity (Software Education

channel)

Baselines in requirements projects

In a requirements project, a baseline captures the entire project at a moment in time. For example, you

might create a project baseline before you create an artifact review to ensure that the artifacts do not

change during the review. A baseline includes all artifacts, folder trees, and public tags.

To create baselines, you must have the appropriate permissions. By default, the Conguration

Administrator role has permission to create baselines, but the Administrator and Author roles do not.

Important: To work with streams and change sets in addition to baselines, you must enable conguration

management capabilities for the project. For more information, see Conguration Management.

You can create a baseline from the Current Conguration menu. When you are working in a baseline, the

name of the baseline appears at the top of the menu, as shown in this example.

Note: When you create a new baseline, it does not appear in the list of baselines until you refresh the

application.

 Engineering Requirements Management DOORS Next

After you create a project baseline,baseline you can perform the following tasks:

• View the content of the project as it existed when the baseline was created

• Search for and display other baselines

• Compare the contents of two baselines

Restriction: You cannot modify a project baseline or the version of an artifact that is part of a baseline.

However, you can modify the most recent version of that artifact.

To compare two baselines, you must rst switch to an initial baseline. After the name of the rst baseline

appears at the top of the Current Conguration menu, click Compare Congurations, click Baseline in

the Conguration Context window, and search for and select the second baseline. A wizard opens in

which you can compare the two baselines.

Related concepts

“Modules in the Requirements Management application” on page 129

A module is a structured document that is composed of multiple artifacts. You can create structure in a

module by modifying the order and hierarchy of its artifacts. The artifacts that are created for modules

are stored as module content in a folder. Base artifacts can be used to manage the module artifacts

independent of the module.

Related tasks

“Comparing collections” on page 177

You can use the Requirements Management application to compare two different collections.

Related information

Permissions

Enabling Electronic signatures for a baseline

For compliance purposes, your organization might require you to validate and sign a baseline. You can

congure a project to require electronic signatures on baselines. This helps for audit purposes.

About this task

An administrator can set project-level settings for electronic signatures. The administrator has permission

to:

• Display text that explains the signicance of signing.

• Determine if users must provide a comment when signing.

• Determine if users must select a reason for signing.

• Use the Add option, to enter a list of reasons for signing. An user can select an option from the displayed

list.

Procedure

1. On the Administration menu, click Manage Project Areas page.

2. On the Active Project Areas page, click your project.

3. Under Requirements, click Electronic Signature.

4. In the text box, provide an explanation for why the signature is required for the project.

5. If team members must add a comment when they electronically sign the baseline, select the Require

a comment check box.

6. If team members must provide a reason for signing the baseline, select the Require the user to select

a reason for signing check box.

7. Click Add Reason, and enter a new reason to add to the Value list. You can add as many reasons as the

project requires and then use the Move Up and Move Down controls to change the list order.

Related tasks

Signing a baseline electronically

Administering

If your project or organization requires validation of baselines you can add an electronic signature to

validate and sign it.

Administering components in the RM application

In projects that are enabled for conguration management, as a conguration lead, you complete the

tasks that are related to managing components for your project.

Before you begin

• An RM project administrator must enable conguration management

for the project.

• You must be assigned the Conguration Lead role or have permission to manage components. On the

Permissions page in the application administration section, see the Conguration Management group

for the permissions related to managing components. Assign permissions based on the tasks that you

must complete.

About this task

In addition to the tasks listed below, you can dene team areas to control artifact creation and

modication for specic components: see the Save Artifact and Save Link permission groups on the

Permissions page in the application administration. You might do this to maintain strict control over

changes to an artifact type's denition and the denitions of the artifact's attributes. For example, you

might give Authors specic permissions for Components A, B, and C in a project:

• Authors can create user requirements in Component A

• Authors cannot create system requirements in Component B, but they can modify the public tags and

the content of system requirements

• Authors can modify actors in Component C

For all other permissions, the settings apply to all the components in a project; you can't apply them to

specic components.

Related concepts

Team areas

Related tasks

Administering components and congurations in applications

Creating a team area

Related information

Cloning RM artifacts between components

Components

Components represent a collection of versioned artifacts within a project area. For example, instead of

working with all the artifacts from the project in one stream (for example, that represents a physical piece

called a Handheld Meter Reader), you can use a component to represent a smaller collection of artifacts

(for example, to represent a smaller physical piece such as a Sensor in the handheld meter reader).

You can split a project into multiple pieces called components. Each component is like a building block

that represents a physical or logical part of your project. Components make it easier to reuse and work

with parts of a project. After you plan and create components, organize project artifacts into them based

on your project needs, instead of working with all the artifacts in one collection (conguration).

Before version 6.0.3, the project area was the top-level container for artifacts. You couldn’t split a project

into smaller pieces. Each conguration (stream or baseline) in the project contained one version of each

artifact in the project. If you wanted smaller collections of project artifacts, you had to create projects to

correspond with each grouping, which had much administrative overhead.

Starting in version 6.0.3, the ability to split a project into ner-grained components gives you these

benets:

 Engineering Requirements Management DOORS Next

• It’s easier to create versions and variants of a product or system by reusing its parts.

You can quickly respond to market demands or changing regulations in different geographies.

• Teams can work independently on different components on different schedules.

For each IBM Engineering Lifecycle Management (ELM) application, carefully plan which components

to create, to ensure flexibility in assembling products and their variants. If you don’t plan, you will

encounter problems when you assemble the components into global conguration hierarchies that

represent products and their variants.

See the related topics for details, benets of using components, and examples.

Related concepts

GCM application: Creating the global conguration hierarchy

Related tasks

QM application: Administering components

RM application: Administering components

RM application: Cloning artifacts between components

Related information

GCM application: Creating a context to establish a work context

Dening your component strategy (Jazz.net article)

Organizing the components for your RM project

You can divide the artifacts in a project among multiple pieces called components. Each component is

like a building block that represents a physical or logical part of your project. Components are smaller

collections of artifacts that can be reused easily or delivered on independent schedules or to other teams.

Before you begin

• Ensure that you are familiar with components, project areas, congurations, baselines, and streams.

• Ensure that you are familiar with global congurations and personal streams (if your organization uses

them).

About this task

Although IBM Engineering Lifecycle Management (ELM) applications have ways of grouping artifacts

into smaller collections, such as Requirements Management (RM) modules and folders and Quality

Management (QM) test suites and test plans, you can’t easily mix and match them, reuse them, or deliver

them independently.

For example, managing congurations requires more attention if Team1 wants to work with Stakeholder

Requirements Baseline 1 and Functional Requirements Baseline 1, but Team2 wants to work with

Stakeholder Requirements Baseline 2 and Functional Requirements Baseline 1.

Now you can divide the different requirement types into separate components so that you can mix and

match them, and deliver them independently.

Consider using separate components for sets of artifacts when you’re in these situations:

• The collection of artifacts is intended for reuse in more than one larger assembly: more than one

product or product variant, or in more than one place in a complex product or system.

Examples: an engine control unit that is used in both the 2019 and 2020 models of a car; a screen used

for a car’s navigation system and its infotainment system.

• The collection of artifacts is delivered to another party as a separate delivery.

Examples: delivering an updated radio component to the team working on the luxury model of a car;

delivering a radio component to a third-party vendor so they can add proprietary satellite technology.

• The collection of artifacts is delivered by a separate team, or on a different cadence.

Administering

• The collection of artifacts has a separate delivery cycle (such as different test stages or approval

cycles) .

For each ELM application, carefully plan which components to create to ensure flexibility in assembling

products and their variants. If you don’t plan, you will encounter problems when you assemble the

components into hierarchies that represent products and their variants.

This topic follows the example of a car, which includes both physical pieces and software including an

engine, sunroof, infotainment system, brakes, and so on.

Components are smaller collections of artifacts

Before version 6.0.3, the project area was the container for artifacts. You couldn’t divide a project into

smaller pieces. Each conguration (stream or baseline) in the project contained one version of each

artifact in the project. Continuing with the car example:

• Each conguration in an RM Car project contained a version of all the stakeholder, safety, performance,

and environmental compliance requirements

• Each conguration in a QM Car project contained a version of all the safety, performance, and

environmental compliance tests

And so on.

If you wanted smaller collections of project artifacts, you had to create projects to correspond with each

collection, which had much administrative overhead.

Starting in version 6.0.3, a component becomes the container for artifacts. The ability to divide a project

into components gives you these benets:

• It’s easier to create versions and variants of a product or system by reusing its parts. You can quickly

respond to market demands or changing regulations in different geographies.

Example: While developing a luxury car with seat heaters and all-wheel drive that can withstand a harsh

climate, you can quickly respond to a market shift that demands a simpler, less expensive car with

fewer automated systems and sensors, and a different combination of existing parts.

• Teams can work independently on different components on different schedules. They can develop and

deliver new features or xes without affecting other teams working on other components.

Example: Replace a non-IoT fuel sensor with one that sends IoT data on fuel consumption back to

engineers. High consumption rates might indicate a problem that must be xed; engineers can then

develop and deliver the x to reduce overall fuel consumption. The teams working on other parts of the

car (infotainment, sunroof, and so on) are not interrupted and forced to update the stream (version of

the car) they are working in.

Team members with administrative roles dene and create components

In ELM applications (RM, QM, Change and Conguration Management (CCM)), administrators create

components. In the GCM application, a conguration lead typically creates components. On the

Permissions page in the application administration section, see the Conguration Management group

for the permissions related to managing components and congurations, and assign those permissions

based on your project needs.

Use components to organize the artifacts in your project

After you create a project in the GCM and ELM applications, follow these high-level steps to use

components to organize the logical and physical pieces of your project.

Procedure

1. Design and create components

 Engineering Requirements Management DOORS Next

a) Plan the components your project needs by thinking about the building blocks that make up your

product or system. You must plan them so that components do not share artifacts, or, overlap.

You’ll see an example later in this topic.

b) Organize any existing artifacts into the new components. In the RM and QM applications, this action

is called cloning, and is described later in this topic. If you clone shared artifacts into separate

components to avoid overlap, remember that in the RM application, you can link between artifacts

in different components.

c) For each component, create the congurations (streams and baselines) that teams need to do their

work. Each conguration of the component contains one version of each artifact in that component.

2. Assemble the relevant congurations of components to build the product or variant that you need.

Typically, a GCM conguration lead does this step.

a) Create the global congurations for the project.

b) Add the appropriate local congurations of components to the global congurations, to build the

hierarchy of congurations components for the project in the GCM application

Related concepts

Components

Components represent a collection of versioned artifacts within a project area. For example, instead of

working with all the artifacts from the project in one stream (for example, that represents a physical piece

called a Handheld Meter Reader), you can use a component to represent a smaller collection of artifacts

(for example, to represent a smaller physical piece such as a Sensor in the handheld meter reader).

Related tasks

Administering requirement components

In projects that are enabled for conguration management, as a conguration lead, you complete the

tasks that are related to managing components for your project.

“Cloning requirement artifacts” on page 250

Reorganize how artifacts are grouped in your project area by cloning them from one component into

another. When you clone an artifact, a new version is added to the stream of the component that you work

in.

Related information

Dening your component strategy (Jazz.net article)

Creating the global conguration hierarchy

1. Design and create components

About this task

Consider the building blocks that your project needs. For example, in an RM project for a Car, you might

have several types of requirements: stakeholder, safety, performance, environmental compliance. Each of

these types might be in their own module. You might decide to create a component that corresponds with

each module.

You can always create more components later if you need more building blocks, and reorganize the

artifacts again by cloning them into the new components.

When you clone artifacts from one component to another, to prevent team members from using the

incorrect versions of artifacts, consider archiving the component you clone from.

1a. Plan components so they don't contain the same artifacts

About this task

Each project artifact can be in only one component. When two components contain any version of the

same artifact, they overlap. You cannot add congurations of those components to the same global

conguration, and this might prevent you from building the version or variant that you need.

Administering

Consider a requirements project in which you’ve created ner-grained components and organized the

requirements from the initial project so that the new components contain the following artifact versions:

• Component A: requirement1-v1, requirement2–v1, requirement3–v1

• Component B: requirement1-v2, requirement4–v1, requirement5–v1

• Component C: requirement5-v2, requirement6–v1

• Component D: requirement1-v3, requirement7–v1

• Component D overlaps with A (both have versions of requirement1)

The following components overlap:

• Component A overlaps with B and D (all have versions of requirement1)

• Component B overlaps with A and C (B and A contain versions of requirement1; B and C contain

versions of requirement 5)

• Component C overlaps with B (both have versions for requirement5)

Note: Just because component A overlaps with B, and B overlaps with C, does not imply that A overlaps

with C.

Using the car example, you might have different categories of requirement: safety, performance,

stakeholder, and environmental compliance, but some requirements belong to multiple categories:

“Airbags must nish deploying within 0.025 seconds” might be considered both a safety and performance

requirement. To avoid overlap you must add it (by cloning it) to only one component.

You can’t add congurations of overlapping components to the same global conguration, so it is difcult

to build versions and variants of a product. Reconsider either the components you’ve dened or how

you’ve assigned artifacts to each component.

Preventing the overlap. You might organize the artifacts this way instead:

• Add requirement1 to component D only

• Add requirement5 to component C only

The components now contain these artifacts:

• Component A: requirement2–v1, requirement3–v1

• Component B: requirement4–v1

• Component C: requirement5-v2, requirement6–v1

• Component D: requirement1-v3, requirement7–v1

If you later decide that requirement1 should be in component A, you can clone it into that component, but

you’ll have to x the new overlap between A and D. Here’s how:

1. Create another component named E.

2. Clone requirement7 from component D to component E.

3. Archive component D so that its artifacts are no longer visible to team members.

Your components now have these artifacts:

Remember: When you clone an artifact, it creates a new version of it in the stream you clone into.

• Component A: requirement1-v4 (cloned requirement1-v3 from Component D), requirement2–v1,

requirement3–v1

• Component B: requirement4–v1

• Component C: requirement5-v2, requirement6–v1

• New: Component E: requirement7–v2 (cloned requirement7-v1 from component D)

• Archived: Component D: requirement1-v4, requirement7–v1 (archived to remove the overlap with

Component A)

 Engineering Requirements Management DOORS Next

Even though these are general guidelines, RM and QM have a few differences to consider when you

organize your artifacts into components as described in the next step.

1b. Organize existing artifacts and link to shared artifacts across components

About this task

You can create links between artifacts in different requirement components. For example, if two modules

share a requirement, you can clone the shared requirement into its own component to prevent overlap,

but still link that artifact to its related artifacts that are in other components.

Continuing with the car example, assume an initial project-level component in an RM project named Car,

which has the following artifacts:

• Module A: includes requirements R1, R2, and R-shared

• Module B: includes requirements R3, R4, and R-shared

You decide to create components to correspond with each module. If the global conguration that

represents a future version or variant of the car might need congurations of both modules, consider

cloning R-shared into its own component; otherwise, you won’t be able to add a conguration of Module A

and Module B to the same global conguration. The following steps elaborate on this example.

Procedure

1. In the RM Car project, a conguration lead denes ner-grained components for this project: Safety,

Performance, and Environmental. Each component contains an empty initial stream.

2. In the GCM application, a conguration lead creates a Car project. He then creates ner-grained

components such as Car2020, Engine, Infotainment System, Sunroof, and so on. Each component

contains an empty initial stream.

The team is currently building a product named “Car 2020”. The GCM conguration lead completes

these steps:

a) Open the Car 2020 initial stream.

b) Build the conguration hierarchy for the Car 2020 variant: He adds the initial stream of each of the

Safety, Performance, and Environmental components from RM.

3. An RM conguration lead reorganizes the artifacts in the RM Car project. He starts by cloning Module A

from the Car project-level component to the new Safety component.

a) He clones R1 and R2 into the initial stream of the Safety component.

b) He clones R-shared into the Environmental component, to prevent overlap between the Safety and

Performance requirements.

At this point, the following components overlap:

• Project-level component and the Safety component

• Project-level component and the Environmental component

The GCM conguration lead cannot add congurations of the overlapped components to the Car

2020 global conguration.

4. The RM conguration lead continues to reorganize artifacts by cloning Module B from the Car

component to the Performance component.

a) He clones R3 and R4 into the initial stream of the Performance component.

5. He creates the links from the R-shared artifact in the Environment component to its related artifacts in

the other components.

Administering

Results

At this point, the project-level component overlaps with the new Safety, Performance, and Environmental

components. The GCM conguration lead cannot construct the Car2020 stream to contain congurations

from the project-level component and any of the Safety, Performance, or Environmental components.

To remove this restriction, the RM conguration lead should clone all the artifacts from the project-level

component into ner-grained components, and then optionally archive the project-level component to

prevent team members from accessing the wrong versions.

1c. Create the congurations (streams and baselines)

About this task

After any existing artifacts are organized into components, the RM conguration lead can create the local

streams and baselines that teams need to work on the correct versions of the artifacts. For teams to get

a holistic view of all the artifacts in a project, and to see and create links between artifacts in other ELM

applications, they must work in a global conguration context.

2. Building the global conguration hierarchy

About this task

After components and congurations are created, and the artifacts are organized into the correct

components, teams can work on the artifacts and congurations for the version or variant.

The GCM conguration lead works with the RM (and other ELM) conguration leads to build and maintain

the hierarchies that teams need for the versions and variants of the product. For details, see the related

topics.

Creating components in the RM application

In projects that are enabled for conguration management, you can create components to represent sets

of versioned artifacts within a project area. For example, instead of working with all the artifacts from the

project in one stream, you can use a component to represent a smaller set of artifacts. You can use a

template to add properties to the component, or import them from another component.

Before you begin

• Conguration management must be enabled

for the project.

• You must be a conguration lead or have permission to create components.

• Reusing types and attributes from other components: If you plan to populate the new component either

by choosing a template or by importing a type system from another component, make sure that the

URIs in the template or type system are dened for these items:

– Artifact types

– Artifact attributes

– Attribute data types, including all enumeration type values

– Link types

For details, see the related tasks about templates or importing properties.

Reusing types and attributes makes these tasks easier:

– Cross-component linking by using the link type.

– Reporting in Report Builder: Make sure that the URIs and names of the preceding items are set and

have the same value across components. Report Builder then considers these items equivalent for

reporting.

 Engineering Requirements Management DOORS Next

For example, if Component1 and Component2 both use the Business Priority artifact attribute, make

sure the components use the name and URI values:

1. Click Administration > Manage Component Properties;

2. Click a tab that contains attribute types (Artifact Types, Artifact Attributes, Attribute Data Types,

Link Types, and so on).

3. Set the name in the Name eld and the URI in the URI eld. Typically, a URI looks like this:

https://hostname/domain/myLabel

4. Click Save.

For details, see the related task about managing project properties: although the procedures are for

project properties, the procedures for managing component properties are similar.

Procedure

1. Create components in one of these ways:

• From the All Projects view

a. Open a project from the All Projects view: https://example.com:9443/rm/web

b. Under a project name, click Show Components.

c. In the Components section, click Create Component.

• From the Home menu

a. Click a project name.

b. In the Components section, click Create Component.

• While working in a project

On the toolbar, click Administration

> Create Component.

• From the component editor

On the toolbar, click Administration > Manage Components and Congurations.

b. Click Browse Components, and click Create Component.

2. Optional: Select a template to add properties such as artifact types, attribute data types, link types,

and so on from another component. By using a template, you don't have to recreate the properties

manually.

• Remember, make sure the URIs are dened in the template, as described in the "Before you begin"

section.

• You can use a sample template provided in the product, or create or upload your own. See the

related template tasks for details.

Tip:

– To add URIs, edit the template properties.

– By default, most process templates do not contain URI values. You can edit process template

properties after you create a project area.

• If you don't select a template, no properties or artifacts are dened in the new component.

Results

• The system creates the component with the name that you specify, and an initial stream named

component_name Initial Development. If you selected a template, the component contains the

properties that the template denes.

Administering

• The component opens, and you can begin work in its initial stream.

Tip: If you created the component in the component editor, click Explore Component to begin work in

its initial stream.

What to do next

• You can now create artifacts in the component, or clone or copy them from other components. To help

you decide whether to clone or copy artifacts, see the table in the related task about cloning.

• Tag artifacts in components to further categorize them.

• View or manage the details of the new initial stream: in the component editor, click the stream name, or

choose an option from the Actions menu beside the stream name.

• To import more properties later, click Administration

> Manage Component Properties > Import

Component Properties; but remember, changes that you made to the type system of this component

will be overwritten.

Related tasks

RM sample templates

Importing properties from another RM project or component

Managing project properties in a requirements project

Adding tags to artifacts and viewing tagged artifacts

Related reference

“Requirements project templates” on page 48

Related information

Components

Dening your component strategy (Jazz.net article)

Cloning RM artifacts between components

Fixing overlapping components

After you clone artifacts, two components overlap if they have any artifacts in common, regardless of

those artifact versions. The system prevents you from adding congurations of those components to

the same global conguration. Fix the component overlap and then add the congurations to the global

conguration.

Before you begin

You must be an RM project administrator.

About this task

Consider a project that has a component called Sensor_US, and another component called Sensor_UK.

Several of the requirements are the same, so you clone them from a baseline of Sensor_US into a change

set that you will deliver to a stream of Sensor_UK. These components now overlap because they contain

the same artifacts, even if you haven't delivered the change set yet. You cannot add congurations of

these components to the same global conguration.

If you deliver the change set, you cannot x the overlap. You must create two or more empty components,

and clone the artifacts again so that each one exists in only one component.

Procedure

Complete one of the following sets of steps:

• If you cloned the artifacts into a change set but have not yet delivered it:

a. Discard the change set.

 Engineering Requirements Management DOORS Next

b. On the toolbar, click Administration > Manage Component Properties.

c. On the Conguration Management tab, under Refresh Component Overlap Data, click Refresh.

d. Optional: Create another change set, and clone into it a set of artifacts that does not overlap with

the conguration you clone from; then, deliver the change set.

• If you delivered the change set that contains the cloned artifacts:

a. Create two or more components.

b. Clone the artifacts again: into each component, clone a set of artifacts, making sure that each

artifact exists in only one component.

c. Optional: Archive the congurations that cause the overlap, so that other team members cannot do

additional work in them.

What to do next

You can now add congurations of the different components to the same global conguration.

Related tasks

“Creating components in the RM application” on page 74

In projects that are enabled for conguration management, you can create components to represent sets

of versioned artifacts within a project area. For example, instead of working with all the artifacts from the

project in one stream, you can use a component to represent a smaller set of artifacts. You can use a

template to add properties to the component, or import them from another component.

Related information

Components

Cloning RM artifacts between components

Archiving and restoring components in the RM application

Archive components that you no longer use or that are obsolete to simplify the list of components

that you see and prevent team members from adding congurations of those components to global

congurations. Archiving a component does not delete it. You can restore it when you need it again.

Before you begin

• Conguration management must be enabled for the project.

• You must be a conguration lead or have permission to archive and restore components.

About this task

You might archive components that are no longer in use, that were created for temporary use only or by

mistake, or whose artifacts were cloned to newer components.

When you archive a component, the system rst archives all of the congurations (streams and baselines)

of that component. Archived components and congurations are hidden from view in the application,

though you see archived congurations when they are referenced by an active conguration. Archived

congurations have a gray icon beside their name, as in this example of an archived stream:

You can show or hide archived components only from the Manage Components and Congurations >

Browse Components page.

You cannot edit archived components or congurations, and you cannot add archived congurations to

global congurations. Archived items are not displayed in search and query results and Report Builder

reports.

Administering

Procedure

1. Open a project from the Home menu

or the All Projects view: https://

example.com:9443/rm/web

2. On the toolbar, click Administration

> Manage Components and Congurations.

Details of the component you are working in are shown.

3. Optional: To work with a different component in the project, click the Browse Components

breadcrumb link and click the component name.

4. Complete the steps for the action you want to take.

• To archive components:

a. Beside the component name, click Archive this component so it is hidden from use

The component and its congurations are archived.

• To restore components:

a. Click the Browse Components breadcrumb link.

Click Show archived components

above the table.

c. Click the component name.

d. Beside the component name, click Restore this component .

The component and its congurations are now visible in the application.

What to do next

To return to the list of components, click the Browse Components breadcrumb link. To show or hide

archived components, click Show archived components or Hide archived components above

the table.

To resume work in the current project, click Artifacts on the toolbar. Check that the Current Project

Component and Current Conguration menus on the toolbar are set to the component and conguration

that you want to work in.

To resume work in another project, select it from the Home menu or the All Projects view.

Related tasks

“Showing and hiding archived components in the RM application” on page 78

Show and hide archived components from the Browse Components page. Archived components are

hidden from view in the application and you cannot use them until you restore them.

Related information

Components

Cloning RM artifacts between components

Showing and hiding archived components in the RM application

Show and hide archived components from the Browse Components page. Archived components are

hidden from view in the application and you cannot use them until you restore them.

Before you begin

Conguration management must be enabled for the project.

 Engineering Requirements Management DOORS Next

About this task

Components are archived for several reasons: they are no longer in use, created for temporary use only or

by mistake, or their artifacts were cloned to newer components.

Procedure

1. Open a project from the Home menu

or the All Projects view: https://

example.com:9443/rm/web

2. On the toolbar, click Administration > Manage Components and Congurations.

3. Click Browse Components.

4. To show or hide archived components, click Show archived components or Hide archived

components

above the table.

What to do next

To resume work in the current project, click Artifacts on the toolbar. Check that the Current Project

Component and Current Conguration menus on the toolbar are set to the component and conguration

that you want to work in.

To resume work in another project, select it from the Home menu

or the All Projects view.

Related information

Components

Cloning RM artifacts between components

Archiving and restoring components

Managing query workload

If your organization runs sophisticated or complex custom view queries, you might encounter issues with

server performance. These kinds of queries consume a signicant amount of memory and CPU time,

which slows down the server. This heavy query load results in the queries taking longer to complete than

the default duration. If you run several of these complex queries, or refresh queries that are already

running, the system can get overloaded and stop responding. A system administrator can prevent these

kinds of situations from happening by controlling and managing the query workload.

Before you begin

You must have administrator permission to view and modify server properties, and you must be in the

Requirements Management (RM) application.

About this task

Although you cannot cancel a running query, as an administrator, you can proactively manage the query

load on the server. You can monitor the current query work volume, queue length, average execution time,

and time spent waiting for the query to complete, and adjust the values for the query size and the thread

pool size.

When view queries are submitted, they are added to the queue. When the queue reaches the dened

maximum count, any additional queries are rejected, and a message is displayed that states that the

server is busy and to try again later.

The system also prevents duplicate queries from being added to the queue. For example, if you resubmit a

query because the rst one is taking too long to complete, the request is ignored.

Administering

The following types of operations are queued and controlled by the server:

• Running saved views

• Sorting and ltering on the Artifacts page

• Sorting and ltering on the Modules page

• Running dashboard widget queries

• Submitting requests to the OSLC query API

• Accessing internal system paths that leverage "view service"; for example, exporting to CSV

You can perform the following operations when the queue is full:

• Basic navigation on the Artifacts, Modules, and Collections pages

• Basic (default) queries on the Modules and Collections pages

• Creating, reading, and editing artifacts, including modules and collections

• Participating in reviews

• Creating, reading, and editing links, comments, folders, and tags

Procedure

• To view statistics about the thread pool, complete the following steps:

a) On the Administration menu , click Manage Server Administration.

b) On the RM Application Administration page, click Debug.

c) On the Statistics page, scroll down to the ThreadPools section and view the details for the

ViewQueryThreadPool component.

• To modify the size of the query queue and thread pool, complete the following steps:

a) On the Administration menu

, click Manage Server Administration.

b) On the RM Application Administration page, click Application and, under Conguration, click

Advanced Properties.

c) On the Advanced Properties page, scroll to the DOORS Next Grid Views Component section.

d) Click Edit and modify the current values for the query queue and the query thread pool.

The default query queue is 10 times the size of the thread pool value. The default query thread pool

size is 75% of the number of processors on the server, or a minimum of 4.

e) To save the updated values, click Preview.

Backing up and restoring the RM index les

The Requirements Management (RM) application uses Jazz Foundation Service (JFS) les for various

query and search operations; these les must be backed up. As the server administrator, you can use the

repository tools (repotools) commands to back up and restore the JFS indexes.

For information about the preferred steps for backing up and restoring the index les, see Backup and

restoration of Jazz Foundation Service index les for IBM Engineering Requirements Management DOORS

Next (DOORS Next) on the Deployment wiki.

Note: This process creates and restores backups of the JFS indexes only; it does not create a backup

of the DOORS Next database. For information about performing a full backup, see Backing up the IBM

Engineering Lifecycle Management (ELM) on the Deployment wiki.

 Engineering Requirements Management DOORS Next

Analyzing and validating TRS feeds

You can view the list of resources that were skipped from the Requirements Management (RM) data

source in the Lifecycle Query Engine (LQE). On the TRS Feed Diagnostics page, you nd out why the

resources were skipped, and decide which resources to ignore in the feed.

Procedure

1. Log in to the server administration page of your web client, for example: https://<host-

name>:<port number>/rm/admin.

2. On the Administration menu

, click Manage Server Administration.

3. In the top navigation pane, click TRS Feed Diagnostics.

4. To validate the TRS feed against the data in the repository, on the Validation page, click Validate >

Validate now. For more information, see Validating TRS feeds and the LQE index.

5. To see the list of skipped resources grouped by VDI codes, on the Skipped Resources page. The VDI

codes help you to determine why the resources are skipped by LQE. The VDI code denitions are

available on this Wiki page.

6. To ignore specic resources in the TRS feed, on the TRS feed ignore list page, click Select an action >

Ignore the selected resources, and then click Submit.

You can add resources back to the TRS feed by removing them from the ignore list. Select the

resources, and click Select an action > Remove the selected resources from the ignore list.

7. To share the list of skipped resources with IBM Support, on the Export Data page, click Export and

download.

Initialize the publish services

IBM Engineering Requirements Management DOORS Next (DOORS Next) have multiple reports. Each of

the reports has an Engineering Document Generation (.dta) report design le. The design les need to be

initialized to store them into the database. Each time when you upgrade to a newer version, you need to

run the publish initialize services.

Procedure

1. Log in to the server administration page of your web client, for example: https://<host-

name>:<port number>/rm/admin.

2. On the Administration menu

, click Manage Server Administration.

3. In the top navigation pane, click Debug.

Administering

4. In the left pane, under Services, click Publish Services.

5. On the Publish Service Actions page, click Initialize Service.

For more information, see Rational Reporting for Document Generation report from the API

documentation.

Extending product function

This section describes how to extend the functionality of the Requirements Management (RM)

application.

Related information

IBM Engineering Requirements Management DOORS Next Server API Documentation

Extending the Requirements Management (RM) application

You can enhance the Requirements Management (RM) application by authoring extensions for it. The

extensions can enhance productivity and are useful for analysis.

You can add the extensions to your mini dashboard and remove them as needed. Extensions are authored

by using a combination of JavaScript, HTML, and CSS les. The extensions access data within the RM

application by using an RM API.

For full details about the client extension capability, see Extending the Requirements Management

application on Jazz.net.

Migrating graphical artifacts created in the graphical editor browser add-on

As of version 6.0.3, the graphical editor browser add-on is no longer available. If you created graphical

artifacts by using the browser add-on and want to make changes to those artifacts, you can install and

use the graphical artifact migration utility to convert them.

The migration utility converts the artifacts that you created with the graphical editor browser add-on to

a format that can be used with the HTML-based diagram editor, which was introduced in version 6.0.

The utility is an OpenSocial gadget that server administrators can host, and then users can add to their

mini-dashboards in IBM Engineering Requirements Management DOORS Next (DOORS Next). It utilizes

 Engineering Requirements Management DOORS Next

the extensions API to read the model of an existing graphical artifact and convert it in-place to the newer

diagram format, which you can then edit.

For full details about the graphical artifact migration utility, see Extending the Requirements Management

application on Jazz.net.

Extending DOORS Next by using OSLC services

Open Services for Lifecycle Collaboration (OSLC) is a community that is standardizing the way that

lifecycle tools work together. IBM Engineering Requirements Management DOORS Next (DOORS Next)

supports the OSLC data sharing specication as a provider for the Requirements Management (RM)

domain and as a consumer of other domains in the IBM Engineering Lifecycle Management (ELM). Data

sharing is also supported by other RM tools that support OSLC integration, such as IBM Engineering

Requirements Management DOORS (DOORS).

The sharing of OSLC data between domains is based on a common set of resources, formats, and REST

architectural services.

The data sharing supports these transactions:

• Linking that is based on HTTP protocol

• Identication of resources by URIs

• Information retrieval that uses industry standard media types

DOORS Next supports OSLC data sharing with the domains and specications that are listed in the

following table.

Table 5. OSLC domains and

specications that DOORS Next supports

OSLC domain RM consumes RM provides

Change Management (CM) V1, V2 None

Quality Management (QM) V1, V2 None

Requirements Management (RM) V1, V2 V1, V2

Conguration Management None See Oasis Working Draft

Related information

OSLC overview

RM as an OSLC service consumer

The Requirements Management (RM) application in the IBM Engineering Lifecycle Management (ELM)

consumes common services that other OSLC domains provide for data sharing.

The RM application consumes services that these OSLC domains and specications provide:

• Change Management V1, V2

• Quality Management V1, V2

• Requirements Management* V1, V2

• Architecture Management V2

*Do not congure the RM application to consume its own OSLC interface. The support is for cross-

repository and cross-tool communication only.

RM consumes these OSLC core services that the supported domains provide:

• These services display delegated user-interface dialog boxes:

– Resource creation: Displays a dialog box that enables a user of a web application to create a resource

in an OSLC service provider.

Administering

– Resource selection: Displays a dialog box that enables a user of a web application to select a

resource that an OSLC service provider manages.

• User-interface previews (compact rendering, rich hover): Display summary information about linked

resources when a user hovers over a link.

Related information

OSLC Core Specication Version 3.0

OSLC Requirements Management 2.1

OASIS OSLC Change and Conguration Management specication

RM as an OSLC service provider

The Requirements Management (RM) application in the IBM Engineering Lifecycle Management (ELM)

provides user interface (UI) elements and operations to applications that consume services from the RM

domain for data sharing.

UI elements that RM provides

The RM application provides the following UI elements for other products to consume in compliance with

the RM domain specications V1 and V2:

• Delegated UI dialog box for the selection of requirement resources

• Delegated UI dialog box for the selection of requirement collection resources (views)

• Delegated UI dialog box for the creation of requirement resources

• UI previews (compact rendering, rich hover) at displayed links to requirement resources

• UI previews (compact rendering, rich hover) at displayed links to requirement collection resources

• Factory resource for the programmatic creation of requirement resources

OSLC operations that RM provides

The following table lists the operations that RM provides in compliance with the indicated RM domain

specications.

Table 6. OSLC operations that the RM application provides as an RM provider

Operation RM V1 RM V2 Oasis Working Draft

Service Discovery Yes Yes

POST for requirement

creation

Yes Yes

GET on a Requirement Yes Yes

GET on a Requirement

Collection

Yes Yes

Resource Shape No Yes

QUERY on Requirement

and Requirement

Collection

No Yes

QUERY on OSLC links No Yes

POST for baseline

creation

Yes

GET for baselines and

streams

Yes

84 Engineering Requirements Management DOORS Next

Note: For information about conguration management operations, refer to the Oasis Working Draft.

• The POST operation creates a requirement as the rst artifact in a requirements collection. POST is not

available at the database level of the service discovery tree.

• RM internal links are not included in the results of the V1 GET operation.

• RM external links are not included in the results of the V1 GET operation.

• RM internal outgoing links are included in the results of the V2 GET operation.

• RM external links are included in results for the V2 GET operation.

Modules that are located within a collection are not available to OSLC consumers through a GET

operation. An attempt to add a module to a collection through a PUT operation will fail.

For basic instructions for using OSLC in RM, see the article Using OSLC capabilities for requirements

management on Jazz.net.

Note: Content on Jazz.net is a development site that is governed by the Jazz.net Terms of Use and is

provided as-is without warranties of any kind.

For more information about the OSLC RM implementation in ELM and other products that are based on

Jazz technology, see the Open Services for Lifecycle Collaboration Workshop in the Library on the Jazz

Community Site. The workshop includes instructions and examples for the following RM topics:

• Introduction to the OSLC RM API

• Accessing OSLC RM APIs programmatically

For information about developing OSLC-compliant Eclipse applications, see the Eclipse Lyo web site

For information about enabling links between RM and other ELM applications and other RM tools, see

“Linking to development, design, test, and requirement artifacts” on page 201.

For information about conguring the integration with IBM Engineering Requirements Management

DOORS, see “Integrating the Requirements Management application and DOORS” on page 15.

Related information

OSLC Requirements Management Specication Version 1.0

OSLC Requirements Management Specication Version 2.1

Links across OSLC domains

The Requirements Management (RM) application in the IBM Engineering Lifecycle Management (ELM)

integrates with other application domains by using standard link types as implementations of the OSLC

specications.

OSLC link relationships

Table 7. Linking across domains from and to the RM application

Domain Link relationships in RM

Link relationships in external

applications

Change Management (CM)

RM artifacts can be linked to CM

artifacts by using one of these

link types:

Implemented By

Affected By*

Tracked By*

CM artifacts can be linked to RM

artifacts by using one of these

link types:

Implements

Affects*

Tracks*

Administering85

Table 7. Linking across domains from and to the RM application (continued)

Domain Link relationships in RM

Link relationships in external

applications

Quality Management (QM)

RM artifacts can be linked to QM

artifacts by using this link type:

Validated By

QM artifacts can be linked to RM

artifacts by using one of these

link types:

Validates (a requirement)

Validates* (a requirement

collection)

Requirements Management (RM)

RM artifacts can be linked to

external RM artifacts by using

one of these link types.

This link type is used for the

integration between the RM

application and IBM Engineering

Requirements Management

DOORS (DOORS) objects.

References

External RM artifacts can be

linked to RM artifacts by using

one of these link types.

This link type is used for the

integration between the RM

application and DOORS objects.

Referenced By

Architecture Management (AM)

RM artifacts can be linked to

AM artifacts by using these link

types:

Rened By Architecture Element

Traced By Architecture Element

Satised By Architecture Element

Derives Architecture Element

AM artifacts can be linked to

RM artifacts by using these link

types:

Renes

Trace

Satises

Derives From

*Support for this link relationship was added in V2 of the domain specications.

For more information about Architecture Management, see Overview of Rhapsody Model Manager.

Note: In projects that are enabled for congurations, links are directional and are owned by an

application. For more information about link ownership, see Overview of cross-application artifact linking.

Related tasks

Linking to development, design, test, and requirement artifacts

Additional OSLC integration services and requirements

Root services provides the entry point for the OSLC service discovery documents. OAuth security is

required for OSLC authentication.

Root services

Although the root services document is not part of the OSLC specication, it provides the entry point for

the OSLC service discovery documents and the conguration URLs that are needed to consume OSLC

services.

The root services document is located by a URL, based on the server location of the RM server:

https://host-name:9443/rm/rootservices. For example, if the RM server is installed at http://

rm.example.com/, then the root services document is at https://rm.example.com:9443/rm/

rootservices

 Engineering Requirements Management DOORS Next

Secure authentication

Security is required for OSLC and is provided by OAuth 1.0a. OAuth is an open protocol that provides

secure API authorization in a simple, standard method from desktop and web applications. To access

most OSLC URIs, including URIs for service discovery, requirements, requirement collections, you must

be an authenticated user. OAuth authentication is not required for the root services URI. For more

information, see the OAuth 1.0a Specication.

OASIS OSLC Change and Conguration Management Specication

For information on how to represent and recognize versioned artifacts and congurations, see the OASIS

OSLC CCM TC specication.

Managing

This section describes how to work with dashboards in the Requirements Management (RM) application.

Dashboards in the Requirements Management application

You can work with both project dashboards and personal dashboards in the Requirements Management

(RM) application. Project dashboards are composed of widgets that provide high-level overviews of

artifacts and requirements that are scoped to a specic RM project. Personal dashboards are useful

for tracking action items and workloads across projects, and to display other widgets, such as calendars,

time zone clocks, news feeds, and search engines.

If your project is enabled for conguration management, you can report on versioned artifacts using

conguration-related information in dashboard widgets.

Related concepts

Conguration Management

Related reference

Project Dashboard

A project dashboard in the Requirements Management (RM) application is composed of widgets that

provide high-level overviews of artifacts and requirements that are scoped to a specic RM project. Only

the members of a project can view its dashboard.

Related information

Personal dashboards

Managing dashboards

Composing and managing requirements

You can use the Requirements Management (RM) application to dene the requirements for your system

or application, and then manage those requirements by using mechanisms such as traceability links, tags,

attributes, and dashboards.

Related tasks

“Administering requirements projects or components” on page 21

Joining a requirements project

To join a requirements project, a project administrator must use the web client to add you to the project

as a team member. You can then use web client to open a project from your User Dashboard.

Before you begin

Before you start to work in the client, you must have a Requirements Management repository server

installed locally on your computer or have access to one on a network server. For information

Managing

on installing and conguring the server and client, see https://www.ibm.com/docs/en/elms/elm/7.0.2?

topic=SSYMRC_7.0.2/com.ibm.jazz.install.doc/topics/c_planning_install.html. If the team that you are

joining has a repository server on a network, contact the server administrator to get access information.

Related tasks

Creating requirement projects using the web client

Jazz project administrators can create projects and modify project structure and team membership.

Logging in to a requirements project repository

credentials that your administrator provides.

Before you begin

Obtain a URL and your user name and password from your project administrator.

Procedure

1. To log in, type the following URL into your browser address eld:

https://hostname:port number/rm/web/

In this example, hostname is the fully-qualied hostname of the server that your administrator

provided, and port number is the port number on that server. For example, enter a URL such as this:

https://myhost.com:9443/rm/web/

2. Log in using the user name and ID that your administrator provided. Authentication can be congured

to use an external LDAP registry, a custom/federated WebSphere Application Server user directory. For

more information, contact your administrator.

Results

The All Projects window opens, which lists all the projects of which you are a member. The All Projects

page has a page navigator when over 100 projects are displayed. You can use the page navigator at the

top of the page to see your projects in increments of 100.

Click Explore Dashboard to display the project dashboard or click Show Artifacts to open the project

Artifacts page.

Related information

Setting up User Management for the IBM Engineering Lifecycle Management (ELM) server

Project dashboards

A project dashboard in the Requirements Management (RM) application is composed of widgets that

provide high-level overviews of artifacts and requirements that are scoped to a specic RM project. Only

the members of a project can view its dashboard.

You can open a project dashboard on the All Projects page or from the Home menu. The dashboard can

be modied only by a user who has administrative access to the project.

To modify the number of columns that are shown on the dashboard, click the arrow on a tab and click

Layout. To add a page to a dashboard, click the Add New Tab icon.

To learn how to customize the project dashboard, see Adding and organizing content on a dashboard.

To add an extension to the mini dashboard using a URL, watch the following video.

Dashboard widgets

To modify the properties of a widget, click Settings on the widget heading menu. To modify the widget

title and color, click Appearance.

 Engineering Requirements Management DOORS Next

You can add widgets to your dashboard to customize your view of the projects that you are a member

of. If you are integrated with the IBM Engineering Lifecycle Management (ELM) applications, you can add

widgets to display RM artifacts that are linked to development and test artifacts. You can also add widgets

from the RM, Quality Management (QM), and Change and Conguration Management (CCM) applications

to your personal dashboards.

To add a widget, click Add Widget. Select a catalog and then click the Add Widget icon for the widget

to add. You can add multiple instances of a widget and customize its title and properties. Widgets are

organized in categories.

These widgets provide information about requirements projects:

• Projects Members: Lists all members of the project.

• Recent Changes: Lists recently modied artifacts in the project.

• Comments: Lists recent comments that are related to the project. You can lter the comments by those

that are addressed to you or those that you made.

• Reviews: Lists recently modied reviews in the project. You can limit the display to only your active

reviews or all active reviews. You can lter or group the results by status, role, or review name.

• Requirements View: Shows the result of a single view. The view is chosen from a list relative to a

particular requirements project.

• Requirements Tracing: List RM artifacts that link to CCM or QM applications. Linked development or

test artifacts are displayed as indented entries below each RM artifact.

To know more about Adding widgets to the widgets catalog, watch the following video.

Related concepts

“Reviews” on page 181

“Traceability” on page 199

Traceability is used to trace a project element to related project elements, especially those

related to requirements. Traceability helps determine that a requirement is satised from inception

through implementation and testing. Create traceability relationships by linking requirements to other

requirements and to development and test artifacts.

Related tasks

Creating personal dashboards

You can create an unlimited number of personal dashboards to suit different needs.

“Commenting on artifacts” on page 179

A comment is a textual discussion item that you can add to an artifact or an element within an artifact.

You can use comments to provide team feedback during the development of an artifact. In the web client,

comments are displayed in the Comments section of an artifact sidebar, in the Recent Comments section

of the Artifacts page sidebar, and in Recent Comments for Me on the user dashboard.

“Creating requirements projects” on page 26

Jazz project administrators can create projects and modify project structure and team membership.

Creating personal dashboards

You can create an unlimited number of personal dashboards to suit different needs.

About this task

You can customize personal dashboards to serve various purposes:

• Track action items, such as open high-severity work items, pending approvals, and new work items that

need to be triaged.

• Track workload in a project.

• Track workload across multiple projects, including those projects from other applications.

Managing

• Display useful widgets to help you work, such as calendars, time zone clocks, news feeds, and search

engines.

New dashboards are pre-populated with a set of widgets that are designed to help a user get started with

the dashboard. Personal dashboards are stored on the Jazz Team Server.

Important:

• To perform this task, you must have read/write access to the Jazz Team Server project area, which is

available to members of the JazzUsers repository group and most other groups. It is not available to

members of the JazzGuests group.

• If you change your user ID, your personal dashboard will not function properly.

Procedure

1. To create a personal dashboard, click the Home icon (

Note: If you previously created a personal dashboard, this action takes you to your default personal

dashboard. To create another personal dashboard, click Personal Dashboards > Create Dashboard.

2. In the Create Dashboard page, select the dashboard template, and click Next.

3. In the Select Project Area page, select the project area, and click Finish.

4. A dashboard is created with the default title Your-contributor-name’s Dashboard. If you have multiple

personal dashboards, you can create unique and descriptive titles for each one to prevent confusion.

To change this title, click the dashboard title, and then edit the text.

5. The dashboard is populated with a set of widgets. You can add, remove, organize, or edit widgets

to customize your personal dashboard. For more information about using widgets, see Adding and

conguring widgets.

6. Optional: To set any personal dashboard as the default, click the Set as default dashboard icon ( )

in the dashboard toolbar, and then click OK.

Optional: To access all of your personal dashboards, click the arrow next to the Home icon ( ) to

display the menu. All of the personal dashboards that you created are listed under Current Personal

Dashboards.

8. Optional: To share a personal dashboard and make it visible to a project or team, click the Sharing

Options icon ( ) in the toolbar, and then click OK to conrm sharing.

Important: Shared personal dashboards display in the All Personal Dashboards list (Dashboards >

All Personal Dashboards), and they can be displayed in search results in the web client. When a

personal dashboard is shared, the Shared dashboard icon ( ) is displayed next to the dashboard in

the Personal Dashboards menu.

9. Optional: To delete a personal dashboard, click the Delete icon ( ) in the dashboard toolbar.

Note: It is possible to delete all of your personal dashboards. If you do, you can create one by clicking

the Home icon ( ).

Dening requirements

You can use rich-text artifacts to dene requirements and requirements documents. You can also create

and link to supporting artifacts, such as business process diagrams, use case diagrams, and wireframes,

to elaborate requirements and put them in the broader context of the system and business processes.

Related tasks

“Administering requirements projects or components” on page 21

 Engineering Requirements Management DOORS Next

Creating artifacts

In a requirements project, you can create rich-text and graphical artifacts.

Before you begin

Before you can create an artifact, the artifact type must exist in the project. If you are an administrator,

you can view or create the artifact types for a project by clicking the Administration menu and

then clicking Manage Project Properties.

Note: If conguration management is enabled for your project, on the Administration menu, click

Manage Component Properties.

About this task

When you create an artifact, the artifact can be new or based on another artifact. You can also create an

artifact by extracting text from a text-based artifact. After you create an artifact, you can capture its URL

to make it easy for other team members to access it. Watch a video about creating requirement artifacts.

When you create an artifact by extracting text from a text-based artifact, the text that you extract

becomes a link to the new artifact. You select the text and then either use the toolbar or right-click the

text to create an artifact.

If you right-click the text and use the menu to create the artifact, you can quickly save the selected text as

a new artifact. However, this method uses a truncated form of the selected text as the artifact name and

uses the same artifact type and location as the initial artifact.

Procedure

• To create an artifact:

a) On the Artifacts page, click Create, and select an artifact type.

b) In the Create Artifact window, enter information about the new artifact and click OK.

You can also create artifacts from the Folder menu. You can click the pencil icon

or right-click

a folder in the Folder menu. The Create Artifact option on the Folder menu displays the preferred

artifact types.

• To create an artifact that is based on another artifact:

a) On the Artifacts page, select the check boxes of one or more artifacts that you want the new

artifact to be based on.

b) Click the pencil icon and click Duplicate Artifact.

c) In the Duplicate Artifact to Folder window, enter a new name for the artifact and choose a

destination folder.

d) Optional: To copy links and tags from the original artifact to the new one, select the corresponding

check boxes.

e) Optional: To create a link between the original artifact and the new one, select the corresponding

check box.

• To create an artifact by extracting text from a text artifact:

a) Open a text-based artifact and click Edit.

b) Highlight the text to base the new artifact on, and then complete one of these steps:

– Right-click the text and, on the menu, click either Save as New "Artifact" and Link or Save as

New "Artifact" and Insert.

– From the toolbar, click the Save Selection as New Artifact and Link icon or the Save Selection

as New Artifact and Insert icon.

Managing

c) Provide the information about the new artifact, click Finish, and then click Done.

Results

The newly created artifacts or content of the modules are stored by default in a folder. Use the drag-and-

drop action to move one or more folders and re-organize them. You can also double-click in the content

area of a text artifact or diagram artifact to put it into edit mode. After making the required changes save

the artifact.

To edit an artifact, you can double-click in the content area of a text artifact or diagram artifact, make

changes, and then save the artifact.

What to do next

After you create an artifact, you can capture the URL of the artifact to make it easy for your team members

to directly access the artifact. You can capture the URL in a format that includes both the artifact name

and ID. You can capture URLs in a rich hover from the Artifacts page, from dashboard widgets, or from the

full-text search widget.