After you complete this activity, you should be able to: - Explain some ways to harvest requirements from resource - Explain options for creating new requirements

1. Essentials of IBM Rational DOORS Next Generation V4.01
Capturing requirements 1© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
© Copyright IBM Corporation 2013
Capturing requirements
Contents
Requirements come from many sources -2
Capture requirements information -3

2. Essentials of IBM Rational DOORS Next Generation V4.01
Capturing requirements 2© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
2 © Copyright IBM Corporation 2013
Requirements come from many sources
DB DB
Spreadsheets
Models
Documents
Folders
Data
Emails
Images
Glossaries
Hyperlinks
Requirements come from many
sources:
• People in various project roles can
provide input and experiences to
help drive requirements.
• Input might come from many
places, including documents,
pictures, and diagrams.
The requirements management
application helps you elicit
requirements:
•You can upload or import existing
requirements artifacts from different
sources to the requirements
management application repository
•You can capture requirements
specifications and individually control
and manage included artifacts.
•You can define glossaries of terms
which provide consistency to your
project
•You can use graphical editors such as
business process diagrams, Use-case,
Sketches and storyboards

3. Essentials of IBM Rational DOORS Next Generation V4.01
Capturing requirements 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
Capture requirements information
You can create artifacts in several ways:
 Upload external files as wrapped resources
 Create artifacts
– Create Artifact wizard
– One-click artifact creation (web-client)
– Artifact templates
– OSLC-CLM actions
 Use artifacts to create artifacts
– Copy artifacts
– Create similar artifacts
– Save a selection as new artifact and link or embed the artifact
– Create a project by using a template that contains artifacts (Admin)
– Create artifacts from an upload file
 Import requirements
– Rich text document , Microsoft Word, Open Office, Open document
– CSV
– ReqIF (web client only)
Before you can create
artifacts, you must
define artifact types.
In the RM application, artifact is a general term
for any object that is stored in the repository. Any
requirement or requirement-related asset can be
represented as an artifact.
By using the RM application, you can capture
requirements from different sources:
•Upload files to the application or create
requirements directly in the application.
•Create requirement artifacts by using OSLC-CLM
actions. For example, you can link from a work
item to a requirement artifact. You might do this
when you want to create a storyboard to elaborate
a user story.
•Create a project from a template that contains
requirement artifacts.
•Import artifacts by using the import wizard.
• You can import requirements or
requirements-related information from a rich-
text document, such as a Microsoft Word or
OpenOffice document. Then, you can create
rich-text artifacts directly from it. You might
import requirements in this way if you do not
need to manage the data inside that artifact as
individual artifacts.
• Alternatively, you can extract the data from a
document into rich-text artifacts such as
headings, images, requirements or other
requirement-related information. During this
process, you can import the document
contents into a module, which looks like a
rich-text artifact and contains the imported
artifacts. The module maintains the logical
order and hierarchy of the original document.
In a module, artifacts can be individually
managed, each with its own set of attributes,
links, tags, and comments.
You can also import the contents of CSV files as
artifacts.
Requirements Interchange Format (ReqIF) is
supported for importing or exchanging
requirements and associated metadata between
requirements tools or repositories. Importing a
ReqIF file into the RM application a second time,
will merge and update the data as per the ReqIF.

4. Essentials of IBM Rational DOORS Next Generation V4.01
Capturing requirements 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
Capturing requirements
For capturing requirements we will
focus on:
 Project level
– Upload artifacts
– Create new artifact of a particular
format
– Modify artifacts
 Module level
– Capture/modify/reuse requirements
information
– Organize requirements information
 Harvest information
– Import
Even though multiple editors exist
within the RM application, the focus
will be the text editor and the
modules. Remember that modules
contain other artifacts of any type, so
knowing how to use the other editors
is very beneficial.