Creating an artifact at the project level

Essentials of IBM Rational DOORS Next Generation V4.01
Creating an artifact at the project level 1© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Creating an artifact at the project level
© Copyright IBM Corporation 2013
Contents
Module overview -2
Web-client: Uploading artifacts -3
Lab 1: Uploading a file to create an artifact -4
Creating an artifact by using the wizard -5
Module gets created with a folder for their
artifacts -8
Create a module by copying an existing module-9
Editing artifacts at the project level on the
Artifacts page -10
Editing multiple artifacts simultaneously -11
Exporting artifacts -12
Lab 2: Optional: Creating requirements
information -13
Review -14
Module summary -15

2 © Copyright IBM Corporation 2013
Module overview
In this module, you work at the project level. After you
complete this module, you should be able to do these
tasks :
• Upload requirements information as a recourse
• Create an artifact at the project level
• Create an artifact from another artifact
• Edit artifact attributes at the project level
• Export requirements from the project to a comma-separated
values ( CSV) file

Capturing requirements - upload
Web client: Uploading artifacts
Uploaded files are stored as wrapped resource
artifacts. Upload files such as :
 Image files
 Video files
 Supporting documents
Select the folder to upload the
document to, click the Edit
menu, and then click Upload.
2
1
Examples:
You can upload a file by clicking Upload
from the Artifacts menu.
You can upload files from your file system to
a requirements project to make the files
available to other users. You can upload
several types of files, including Adobe®
PDF, Microsoft® Word ,Microsoft® Excel®,
image, CSV, and HTML.
When you upload a file, the file contents are
not imported and the file is not changed. The
upload process creates an artifact that
contains the uploaded file.
Upload resources that you intend to use for
reference or for use in other artifacts. For
example, you might upload a diagram from
your favorite brainstorming tool, a recording
of a web conference, an image that you plan
to use in a user interface sketch, or a
whiteboard snapshot from a brainstorming
meeting.
You can also link to files that you upload.
Uploaded files are treated as artifacts. For
example, you can include an uploaded file as
an artifact in a module.

Lab 1: Uploading a file to create an artifact
After you finish this lab, you
should be able to upload a file to
the Requirements Management
(RM) application and create an
artifact that encapsulates the file.

Creating an artifact by using the dialog
1
Click Create Artifact.
Alternatively , click the menu
arrow and click the type of
artifact to create. If the type is
not in the list, click More.
2
Type a name for the artifact. Select the
artifact type and format.
Indicate which folder to put the new
artifact in. Apply tags to the artifact . 3
4
Select this check box
to start working with
the artifact after it is
created .
This list
represents
artifact types
available for
the project.
You can also start the dialog by selecting a
project folder, clicking the Edit menu, and
clicking Create.
When you create an artifact by clicking the
menu arrow on the Create Artifact button,
you can see the full list of available artifact
types by clicking More.
Artifact types have defined sets of attributes.
When you select an artifact type, those
attributes are associated with the type.
You can select a format for the artifact
content. In general, artifact types can be
based on these formats:
• Text
• Collection
• User interface sketch
• Storyboard
• User interface part
• Use-case diagram
• Business process diagram
• Simple flow diagram
For rich-text requirement content that
contains text, images, and embedded
artifacts, use text format . This format is used
for specific artifacts types, including actors,
use-case specifications, user stories, features,
business goals, and glossary terms. Use the
part format to define aspects of the user
interface.
However, you can select the format for your
artifact. For example, if you want to express a
feature as a storyboard rather than as a rich-
text artifact, select Storyboard for the
artifact format. No matter which format you
use, the artifact is assigned the attributes that
are associated with the artifact type.
The example on the slide does not use an
artifact template. Artifact templates are
useful for creating artifacts with pre-
populated content and attributes. To create an
artifact by using an artifact template, select
the artifact template from the Template list.

Creating a module artifact using the dialog (1/2)
Create a module at the project level, just
as you would create any other artifact.
Alternatively, create a
module from the Modules
menu.
In this example, Requirements
Specification is a user-defined artifact
type of the Module format.
Working with modules

Create a module artifact using the dialog (2/2)
Artifact templates facilitate artifact
creation and promote consistency.
When you create an artifact,
choose the artifact template from
the Template list.
Example of a template
Note that the Artifact type is
Requirements Specification. This is
a name that the team decided on.
Notice the Artifact format is Module.

Module gets created with a folder for their artifacts
When a module is created, a folder is
also created as the default location for
the artifacts that are created while you
edit the module

Create a module by copying an existing module
Artifacts can exist in multiple
modules, so when copying a
module, you have options on
how the artifacts should be
handled..
From the edit menu of the artifact you
want to copy, select Copy Artifact
Artifact editing
options
Because a module contains other
artifacts, when you create a module
by copying an existing module, you
have an option to either duplicate all
included artifacts, or reuse them.

Editing artifacts at the project level on the Artifacts page
From the Edit menu, click Edit
Artifact.
1
When you are finished editing,
click the arrow next to the Save
icon, and click Save Artifact.
Edit the artifact on the page. 2
3
Make sure that the columns to edit are
displayed on the Artifacts page.

Editing multiple artifacts simultaneously
From the Edit menu, click Edit
Attributes.
1
Select attribute values, and then
click Save.
2
You can edit the attributes for multiple
artifacts at the same time. Select the artifacts
that you want to edit, and then click Edit the
attributes for “N” artifacts, where “N” is
the number of artifacts selected..

Exporting artifacts
You can export glossaries and other artifacts to a
CSV file.
You might need to export artifacts so that
external stakeholders can review artifacts or
have a printed copy of a set of requirements.

Lab 2: Optional: Creating requirements information
After you finish this lab, you
should be able to create
requirements artifacts at the
project level.

Review
 What is a benefit of using a
template to create artifacts
from?
 At the project level, is it possible
to simultaneously edit the
attributes of multiple artifacts?
 Will every project have the
same list of artifact types
available?

Module summary
In this module, you focused at the project level and
learned how to do these tasks :
 Upload requirements to created wrapped resources
 Create requirements artifacts using the:
 Create Artifact dialog
 One-click create function
 Export requirements
 Edit requirements artifacts in these ways:
• By editing the attributes of the artifacts
• By adding content to the artifacts

Creating an artifact at the project level

Recommended

More Related Content

What's hot (19)

Viewers also liked (15)

Similar to Creating an artifact at the project level (20)

More from IBM Rational software (20)

Recently uploaded (20)

Creating an artifact at the project level