• Save
Overview of Capturing requirements
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Overview of Capturing requirements

on

  • 278 views

After you complete this activity, you should be able to:

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

Statistics

Views

Total Views
278
Views on SlideShare
278
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Overview of Capturing requirements Presentation Transcript

  • 1. Essentials of IBM Rational DOORS Next Generation V4.01Capturing requirements 1© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2013Capturing requirementsContentsRequirements come from many sources -2Capture requirements information -3
  • 2. Essentials of IBM Rational DOORS Next Generation V4.01Capturing requirements 2© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.2 © Copyright IBM Corporation 2013Requirements come from many sourcesDB DBSpreadsheetsModelsDocumentsFoldersDataEmailsImagesGlossariesHyperlinksRequirements come from manysources:• People in various project roles canprovide input and experiences tohelp drive requirements.• Input might come from manyplaces, including documents,pictures, and diagrams.The requirements managementapplication helps you elicitrequirements:•You can upload or import existingrequirements artifacts from differentsources to the requirementsmanagement application repository•You can capture requirementsspecifications and individually controland manage included artifacts.•You can define glossaries of termswhich provide consistency to yourproject•You can use graphical editors such asbusiness process diagrams, Use-case,Sketches and storyboards
  • 3. Essentials of IBM Rational DOORS Next Generation V4.01Capturing requirements 3© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.3 © Copyright IBM Corporation 2013Capture requirements informationYou 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 createartifacts, you mustdefine artifact types.In the RM application, artifact is a general termfor any object that is stored in the repository. Anyrequirement or requirement-related asset can berepresented as an artifact.By using the RM application, you can capturerequirements from different sources:•Upload files to the application or createrequirements directly in the application.•Create requirement artifacts by using OSLC-CLMactions. For example, you can link from a workitem to a requirement artifact. You might do thiswhen you want to create a storyboard to elaboratea user story.•Create a project from a template that containsrequirement artifacts.•Import artifacts by using the import wizard.• You can import requirements orrequirements-related information from a rich-text document, such as a Microsoft Word orOpenOffice document. Then, you can createrich-text artifacts directly from it. You mightimport requirements in this way if you do notneed to manage the data inside that artifact asindividual artifacts.• Alternatively, you can extract the data from adocument into rich-text artifacts such asheadings, images, requirements or otherrequirement-related information. During thisprocess, you can import the documentcontents into a module, which looks like arich-text artifact and contains the importedartifacts. The module maintains the logicalorder and hierarchy of the original document.In a module, artifacts can be individuallymanaged, each with its own set of attributes,links, tags, and comments.You can also import the contents of CSV files asartifacts.Requirements Interchange Format (ReqIF) issupported for importing or exchangingrequirements and associated metadata betweenrequirements tools or repositories. Importing aReqIF 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.01Capturing requirements 4© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.4 © Copyright IBM Corporation 2013Capturing requirementsFor capturing requirements we willfocus on: Project level– Upload artifacts– Create new artifact of a particularformat– Modify artifacts Module level– Capture/modify/reuse requirementsinformation– Organize requirements information Harvest information– ImportEven though multiple editors existwithin the RM application, the focuswill be the text editor and themodules. Remember that modulescontain other artifacts of any type, soknowing how to use the other editorsis very beneficial.