Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 1© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 2© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 3© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 4© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 5© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 6© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 7© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 8© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 9© Copyright IBM Corporation 2013Cour...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 10© Copyright IBM Corporation 2013Cou...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 11© Copyright IBM Corporation 2013Cou...
Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 12© Copyright IBM Corporation 2013Cou...
Upcoming SlideShare
Loading in...5
×

Basic concepts and terminology for the Requirements Management application

382

Published on

After you complete this module, you should be able to do these tasks :
- Explain the difference between Jazz™ Team Server and the Requirements Management (RM) application
- Describe the basic concepts and terminology in the RM application
- Identify tasks that the team must do before starting a requirements management project with IBM® Rational® DOORS Next Generation or IBM® Rational® Requirements Composer

Published in: Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
382
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Basic concepts and terminology for the Requirements Management application"

  1. 1. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 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 2013Basic concepts and terminology for the RequirementsManagement applicationContentsModule overview -2Requirements Management Project -3Key RM application concepts -4Artifact formats and editors -5Anatomy of an artifact -6Every artifact is of a particular artifact type -7Before you begin -9Managing requirements projects -10Review -11Module summary -12
  2. 2. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 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 2013Module overviewAfter you complete this module, you should be able todo these tasks : Explain the difference between Jazz™ Team Server and theRequirements Management (RM) application Describe the basic concepts and terminology in the RMapplication Identify tasks that the team must do before starting arequirements management project with IBM® Rational®DOORS Next Generation or IBM® Rational® RequirementsComposer
  3. 3. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 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 2013Jazz Team ServerRequirements Management (RM) projectRM projectQM projectRM projectDM projectJazzTeamServerfriendToolwith OSLCsupportToolwith OSLCsupportCM projectProjectAdministration atthe Jazz levelAdministration atthe project levelThe RM project is part of Jazz TeamServer. Therefore, someadministration tasks, such as creatingusers and creating projects, arehandled at the Jazz Team Serverlevel. Other tasks occur at the level ofthe RM project.The current focus of this course is theRM project.
  4. 4. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 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 2013Key RM application conceptsArtifactsFolder structureRM projectAttributes Created on, Modified by, Priority,Clarity, Status, Verification method, …LinksTagsCommentsA project area refers to project artifactsand stores the relationships betweenthese artifacts.Artifact is a general term for somethingthat is part of a project, such as a specificrequirement, or a diagram, or otherinformation.In a project, folders are used to organizeartifacts.Each artifact has a set of attributes,which you can use to record and trackdata about an artifact. Artifacts arecustomizable. Artifact values can betracked by the system or entered by you.You can use attributes to organizeartifacts and manage projects.By using links, you can createrelationships between requirementsartifacts. Links are mechanisms forreferring to related information. Youcreate some links manually; however,other links are created automaticallywhen you complete certain tasks. Linksare useful for managing projects.You can categorize artifacts by using tags. Then, you can use tags to filter andcreate different views of artifacts.A comment is a textual discussion itemthat is associated with an artifact or anelement in an artifact. Comments areuseful for providing team feedbackduring the development of an artifact.You can comment on an artifact as awhole and on specific elements in theartifact.
  5. 5. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 5© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.5 © Copyright IBM Corporation 2013Artifact formats and editorsArtifacts can be of a variety of formats. Aformat specifies what type of information theartifact will carry and the editor what will beused to capture that information.•Text – for individual textual requirements,headings, information, embedding imagesor pdf or other artifacts, or even completeRich text requirements specification•Module – for creating hierarchicallyorganized requirements specifications thatlooks like rich text documents and act asspreadsheets when necessary. All contentwithin the module are individuallymanaged within the module.• Business process diagram – fordescribing business objectives, activitiesand processes•Use-case diagram – to describe userinteraction with the system•User interface Sketch – for creating a amock-up of a graphical user interface thatsupports the design of an application.•Screen Flow – to represent a sequence ofuser-driven software processes as a seriesof graphical user interfaces•User interface Part – as reusable set ofuser interface elements that you can use topopulate sketches and storyboards.•Storyboard - frame-by-frame depiction ofa user scenario that consists of sequentiallynumbered frames on a timeline.•Collection – for grouping artifacts for aspecific purpose
  6. 6. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 6© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.6 © Copyright IBM Corporation 2013Anatomy of an artifactThe location showswhere the artifact isstored.The formatspecifies thestructure ofthe artifactcontent.The artifacttype classifiesthe artifact andprovides aconsistent setof attributesand preferredlink types foreach specifictype.Some attributes aregenerated automatically.Others can be edited.Links representrelationshipsbetweenartifacts.Unique IDTagsArtifact content Title or summaryArtifacts can be in one ormore modules.
  7. 7. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 7© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.7 © Copyright IBM Corporation 2013Every artifact has a typeArtifact type(User defined)DefaultFormatGlossary? Attributes Preferred linktypesRequirementsspecificationModule • Approved by• Approver positionInformation TextActor Text True • StatusUse CaseDiagramUse-CaseDiagram• StatusBusiness Goal Text • Priority• StatusSystemRequirementText • Accepted• Clarity• Mitigates• Satisfies• Satisfied byVision Text • Status• Product OwnerUse CaseSpecificationText • Status• Product OwnerThe above tables lists a few artifact types,attributes and link types that are defined inthe examples we are using in this course. Outof the box, such artifact types, attributes, andlink types would not exist.Artifact types are defined by theadministrator of the RM project and arebased on defined and supported editors,attributes, and preferred link types.Attributes can also be defined by theadministrator , based on the predefined anduser-defined types. They can be single ormulti valued. They can be based on a drop-down list, or be limited between a range.There are some predefined links types butmore can be defined by the administrator.It is important for the team to understand theartifact types as they capture requirementsinformation. Assigning the correct link typeto the requirement information will bringwith it a default editor, attributes, preferredlink types, and the possibility of the artifactbeing used in a glossary.For example, the vision document,stakeholder requirements document, andsystem specification can all be of theRequirements Specification type, andtherefore have the same attributes.However, even though artifacts of typeBusiness Goal, Vision, information, andstakeholder requirement have text as theirdefault format, the different artifact typesallow for type specific attributes andpreferred link types.
  8. 8. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 8© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.8 © Copyright IBM Corporation 2013Artifact format - ModuleRequirementsInformationGraphicsDiagramsModuleIn a module, artifacts arelogically and hierarchicallyorganized.Base Artifact: An artifactoutside a module.Artifacts are the project level areorganized in folders. The artifact at theproject level are referred to as a BaseArtifact.Module is a special type of artifactformat, that contains other artifacts in alogical and hierarchical manner. Amodule looks like a rich text documentand like a spreadsheet revealing attributesand their value directly in columns. In theimage, we see two columns; the maincontent of the module, and the attributeID.The artifacts inside a module, areindividually managed. Individuallymanaged artifacts means that containedartifacts can be edited, links can becreated directly to the individualrequirement, history is tracked forchanges to the individual requirement,and more.A Base Artifact may be used in one ormore module. A module provides scopeto the artifacts it contains. So if anartifact in a module acquires links, tags,or comments, those will be relevant to theartifact inside the module, and they donot effect the base artifact. If the baseartifact gets links, comments or tags,those links will appear everywhere theartifact is used.Organizing requirements information
  9. 9. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 9© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.9 © Copyright IBM Corporation 2013Before you beginThe team must make a few decisions: What kind of information will be collected?– Determine artifact types, attribute types, attributes… How will this information be related?– Determine link typesThe administrator must complete these tasks: (Jazz administrator) Create users (Jazz administrator) Assign licenses Assign access*1 Assign users to projects Create link types, artifact types,and attributesArtifact types classify requirementsinformation. You capturerequirements information in artifacts.When you create an artifact, youmake it of a particular artifact type.This in turn automatically assigns it adefault editor, a defined set ofattributes and preferred link types.Available Artifact types, their defaultformat, attributes, and preferred links,are defined during the projectconfiguration. Project administratorscan create custom artifact types,attributes, data types, and link types.*1Within a project area, a user who isdesignated as Administrator has read-write access for that project area, anddoes not require any Jazzadministration privileges. For moreinformation refer to the informationcenter, topic: “Understandinglicenses, permissions, and accesscontrol”
  10. 10. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 10© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.10 © Copyright IBM Corporation 2013Managing requirements projectsYou can answer critical questions about your project byusing requirements artifact attributes, tags, and tracerelationships (links). Have all stakeholder needs been sufficiently elaborated? Which features are assigned to this iteration? Which features are high customer priorities? Which requirements will be affected by a change? Which use cases or user stories are completed? Are any high-priority requirements blocked by open defects? Are any requirements not covered by development workitems or test cases? What is the current status of this project?To manage a project, you must be able toanswer questions such as these during theproject lifecycle.
  11. 11. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 11© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.11 © Copyright IBM Corporation 2013Review What kind of information isstored in a requirementsmanagement project? What are artifact attributesused for? What are links? What is a base artifact? What is a module? What are some activities thata team has to consider prior toworking with the requirementsmanagement application?
  12. 12. Essentials of IBM Rational DOORS Next Generation V4.01Basic Concepts and terminology 12© Copyright IBM Corporation 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.12 © Copyright IBM Corporation 2013Module summaryIn this module, you learned basic terminology andconcepts that are used in the RequirementsManagement application.

×