After you complete this module, you should be able to do these tasks : – Explain the advantages and disadvantages of these artifact organization options: -– Folders -– Collection artifacts -– Text artifacts -– Module artifacts – Tag artifacts – Organize requirements by using folders

1. 1© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
© Copyright IBM Corporation 2013
Organizing requirements information
Contents
Module overview -2
Folders -3
Views: Get different perspectives of data -5
Collection artifact -6
Text artifacts -7
Module artifact -8
Tags -11
Creating tags -12
Adding tags to an artifact -13
Adding tags to a group of artifacts -14
Summary of benefits -15
Lab 1: Working with Folders -16
Lab 2: Creating and applying tags -17
Lab 3: Optional: Creating views at the module
level -18
Review -19
Module summary -20

2. 2© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
2 © Copyright IBM Corporation 2013
Module overview
After you complete this module, you should be able to
do these tasks :
 Explain the advantages and disadvantages of these artifact
organization options:
– Folders
– Collection artifacts
– Text artifacts
– Module artifacts
 Tag artifacts
 Organize requirements by using folders

3. 3© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
3 © Copyright IBM Corporation 2013
Folders
• Exist at the project level
• Organize requirements artifacts into a logical structure
• Along with sub-folders, can represent artifact hierarchies or
provide an organizing structure for a project or program
Team members with author or
administrator privileges can do
these activities:
 Move artifacts between folders
 Move folders within the project
 Create folders
 Rename folders
 Delete folders
When you create a project from a template,
folders can be predefined and created
automatically .
Team members with author or administrator
privileges can do these activities:
• Move artifacts between folders
• Move folders within the project
• Create folders
• Rename folders
• Delete folders
At the project level, artifacts can be organized in
folders
•Advantages:
• Folders organize artifacts in lists.
• Folders represent artifacts in the
form of a spreadsheet, one artifact
per row and attributes displayed in
columns
• You can display and edit artifact
content, attributes, and links in
columns.
• You can sort artifacts by content,
attribute, and link information.
• You can filter information by
attribute and link information.
• Folders and subfolders can provide
an ordered, logical structure for a
project.
• You can get different perspectives of
the data in a folder by using views.
•Disadvantages
• Folders lack peripheral and
supporting information.
• Folders lack continuity of
information that is hierarchical and
structured.
• An artifact can exist in only one
folder.
Organizing requirements information

4. 4© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
4 © Copyright IBM Corporation 2013
Folders for access control
• Permissions can be
assigned at the project
or team level.
• Team-level
permissions provide
granular control over
who can create and
modify artifacts,
folders, attributes, and
links.
• Team ownership can
be assigned at the
folder level to control
who can modify
artifacts in that folder.
All members of the project have read-access
to project artifacts. Read-access cannot be
restricted for project members.
Write permissions can be assigned at the
project level or at a team level. For more
granular control, use team-level permissions.
The project administrator can use team areas
to set location-based permissions.
Team-level permissions include these
permissions:
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.
If you do not have permission to do certain
actions in a project folder, you might not be a
member of the team area that owns that
folder.
Organizing requirements information

5. 5© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
5 © Copyright IBM Corporation 2013
Views: Get different perspectives of data
A view at the project level consists of column
layout, column groups, and filters on tags,
attributes, and folders.
You can select which
columns to display.
You can group data by criteria.
You can apply
filters by tag,
attribute, or folder.
Views can be shared
or personal.
A view at the project level consists of column
layout, column groups, and filters on tags,
attributes, and folders.
A view provides a perspective of the set of
project data.
You can be created views as needed, or
you can save them for later use as shared or
personal views.
Saved views are key productivity aids. You
can use saved views to get the right artifacts
(rows) and attributes and links (columns) into
view.
After you define filter criteria and select
columns to display, you can save a view.
In the view section, click Save. In the New
View window, name the view, select whether
the view is personal or shared, and then click
OK.
In the view section, click Save. In the New
View window, name the view, select whether
the view is personal or shared, and then click
OK.
You can update saved views in one of two
ways:
•Open the view, edit it, and then click Save.
•Click Update an existing view, select the
view to update, and then click OK.
Organizing requirements information

6. 6© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
6 © Copyright IBM Corporation 2013
Collection artifact
Collection artifact
Collection artifact
A collection is an artifact of type collection.
A collection is a set of artifacts that you can group for a
specific purpose.
Collections represent information in the form of a
Spreadsheets.
A collection is different from a view, because a
collection is an artifact that contains a controlled set of
data that is not dynamically updated based of filter
criteria.
You might create a collection for these purposes:
• Produce a quick, informal group of artifacts.
• Identify a set of artifacts based on a common focus,
such as requirements and related artifacts for an
iteration, milestone, feature, function, team
ownership, or other related purpose.
• Capture a set of artifacts for reviews ,reports.
• Create a glossary ( collection of term artifacts ).
• Associate a set of requirements with a development
plan or test plan.
• Generate development work items and test cases
,based on requirements in the collection.
•Advantages:
• Collections organize artifacts in lists.
• You can display and edit artifact content, attributes,
and links in columns.
• You can sort artifacts by content, attributes, and
link information.
• You can filter information by attributes and link
information.
• An artifact can exist in one or more collection.
• You can get different perspectives of the data in a
collection by using views.
• Collections can include other collections to provide
an ordered, logical structure of artifacts.
• You can create artifacts while editing Create a
collection by adding individual artifacts
• You can baseline a collection and compare its
baselines
• Being an artifact, a collection has history that is
accessible for analysis .
• You can create a review of the collection and its
artifacts.
• You can export the collection contents to CSV
format.
• You can generate a document-style report in PDF,
Microsoft Word, HTML, or XSL-FO format.
•Disadvantages
• Collections lack peripheral and supporting
information.
• Collections lack informational hierarchy and
structure.
Organizing requirements information

7. 7© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
7 © Copyright IBM Corporation 2013
Text artifacts
Content :
Contains the main content of the
artifact.
Can include text, images, hyperlinks,
and embedded artifacts.
Text artifact
An artifact of format text is an artifact that uses the rich
text editor.
An artifact that is of format Text can be a piece of
information, a heading, a single requirement, or a
requirements document.
You can elaborate the content of such an artifact by using
rich-text. You can refer to other artifacts in the text
artifact by using hyperlinks or by embedding artifacts in
the text artifact.
In some projects, you can use a text artifact as a
requirements document, in place of a module or a
collection. In such projects, the text document links to or
embeds requirements. Those requirements are managed
at the project level in collections.
•Advantages
• You can quickly create a specification document by
using rich-text.
• Text artifacts present information logically and in
context.
• You can embed requirements in the artifact.
• Hyperlink out to requirements or other information
• New or existing artifacts can by hyperlinked or
embedded in one or more text artifacts
• You can create requirement artifacts while you edit.
• Being an artifact, it has history that is accessible for
analysis.
•Disadvantages
• Sorting is not supported.
• Filtering is not supported.
• Views are not supported. You cannot change the
perspective of data.
• Embedded or linked artifact attributes cannot be
displayed in columns and rows.
• Artifacts cannot be edited in place. For example,
you cannot edit links or attributes in place.
• Text artifacts do not provide scope for the
embedded artifact and this makes reuse difficult.
When you edit an embedded artifact, all edits are
applied to the base artifact at the project level,
including links, tags and comments.
• Usually, rich-text artifacts require the support of
one or more collections.

8. 8© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
8 © Copyright IBM Corporation 2013
Module artifact
Requirements Information
Graphics
Diagrams
Module
Artifacts are logically
and hierarchically
organized.
In the IBM Rational DOORS Next
Generation modules are the preferred
way to capture your requirements
specifications and work with artifacts.
A module is a special type of artifact format that
provides a logically and hierarchically structured
document of artifacts that are individually structured.
When a requirement is individually managed, you can
link directly to that requirement, track its history, and
more. A module looks like a spreadsheet; attributes and
link information are displayed in columns.
A module is different than an artifact of the Text format,
where contained requirements are not individually
managed and attributes cannot be revealed in columns.
A module is also different than a collection. In a
collection, you can group artifacts, but cannot organize
them logically and hierarchically.
•Advantages:
• A module looks like a document, but acts as a
spreadsheet.
• Modules present information logically and in
context.
• Modules present information hierarchically. You
can collapse, move, promote, demote, or remove
sections.
• Artifacts in a module are individually managed.
• Artifacts in a module can have hyperlinks or embed
other artifacts.
• You can create requirement artifacts while you edit.
• You can sort artifacts in modules.
• You can filter artifacts in modules.
• You can apply views to get different perspectives
of data.
• You can edit artifacts in place. For example, you
can edit an artifact’s links or attributes in context.
• Modules support the reuse of artifacts. The base
artifact, which is artifact at the project level, is
scoped within the module and has module-specific
tags, comments, and links.
•Disadvantages
• The initial editing of a module requires the creation
or addition of artifacts.
• You must manage the hierarchy of artifacts in a
module.

9. 9© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
9 © Copyright IBM Corporation 2013
Example of a module
Content pane: logically
and hierarchically
organized artifactsNavigation pane:
filters and views
Level 1 section
Level 2 section
The module is organized very similar
to the project level Artifacts page.
However, instead of using folders, a
module uses sections to logically and
hierarchically organize artifacts.
Organizing requirements information

10. 10© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
10 © Copyright IBM Corporation 2013
Module views: Changing perspectives of content
Stakeholder System Sub-system
Dropped?
Scope
creep?
Example: multi-level tracing
When you create a view, you can
save it for all of the modules. By
saving a view for all modules , you
can provide a consistent look when
you analyze relationships
Vies are a productivity tool. For
example, you can identify scope
creep or dropped requirements by
using a view that displays link
information in columns .
Remember that tags, links, and
comments in a module are scoped to
the module.
Organizing requirements information

11. 11© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
11 © Copyright IBM Corporation 2013
Tags
 Tags are simple words or
short phrases that you attach
to attributes.
 Tags are a powerful tool for
categorizing artifacts in a
project.
 With tags, you can filter
artifacts and create specific
views.
 Personal tags are available to
only the person who creates
them.
 Shared tags are available to
all users in a project.
Tags provide an easy way to
categorize artifacts, and are
especially useful for informal or
temporary designations.
Unlike an attribute, a tag is not part of
that artifact type.
Tags are an ad hock way to categories
artifacts. A tag can be applied on any
artifact
Organizing requirements information

12. 12© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
12 © Copyright IBM Corporation 2013
Creating tags
1
2
Click the Add New Tag icon.
a. Name the tag.
b. Click Shared or
Personal.
c. Click OK.
Organizing requirements information

13. 13© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
13 © Copyright IBM Corporation 2013
Adding tags to an artifact
Open an artifact and click the
Select Tags icon.
1
2
Select the tags to
apply, and then click
OK.
Option to
create new
tag.
To add a tag to an artifact, open the
artifact and click the Select Tags
icon. A new window will appear.
From that window, select the tags to
apply. You have an option to create a
new Tag, if the tags already provided
are not sufficient. Click OK to apply
the tags and exit the Select Tags
window.
Organizing requirements information

14. 14© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
14 © Copyright IBM Corporation 2013
Adding tags to a group of artifacts
Apply filters to display the
artifacts to tag. Select all
artifacts, and from the menu,
select Apply Tags to Artifacts.
Organizing requirements information

15. 15© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
15 © Copyright IBM Corporation 2013
Summary of benefits
Folder Collection Text Module
Looks like a document  
Acts like a spreadsheet   
Supports views   
Provides context to logically organized
artifacts
 
Supports the controlled grouping of
information
  
Supports the reuse of artifacts   
Provides scope for artifacts, such as links,
tags, and comments

Supports the sorting of included artifacts   
Supports the filtering of included artifacts   
Supports the in-place editing of included
artifacts
  
This table summarizes the different
options for organizing requirements
and identifies a few of their
advantages and disadvantages.
Organizing requirements information

16. 16© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
16 © Copyright IBM Corporation 2013
Lab 1: Working with Folders
After you finish this lab, you should be able to do these
tasks:
 Move artifacts to a folder
 Move a folder to a different
location
Organizing requirements information

17. 17© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
17 © Copyright IBM Corporation 2013
Lab 2: Creating and applying tags
After you finish this lab, you should be able to do these
tasks:
 Create and apply a shared tag.
 Filter artifacts by tags.
Organizing requirements information

18. 18© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
18 © Copyright IBM Corporation 2013
Lab 3: Optional: Creating views at the module level
After you finish this lab, you should be able to do these
tasks:
 Use filters to focus on specific artifacts
 Create a view at the module
level

19. 19© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
19 © Copyright IBM Corporation 2013
Review
 List a few ways in which
you can organize
requirements.
 What is a base artifact?
 When you organize
requirements, what are
some advantages and
disadvantages to using
these elements?
 Folders
 Collections
 Text artifacts
 Module

20. 20© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Organizing requirements information
20 © Copyright IBM Corporation 2013
Module summary
In this module, you learned that many methods exist for
organizing information. Before you start a project, you
must weigh the advantages and disadvantages of each
method.