Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Linking to object headers
Topic Summary: Linking to object headers
Created On: 10-Aug-2007 13:30
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 10-Aug-2007 13:30
User is offline View Users Profile Print this message


Alie Hagedoorn

Posts: 8
Joined: 3-Aug-2007

To give structure to my module I create headers with entities and under that text with attribute names.
In some cases I might want not have enough information to link to an attribute, and instead link to the entity being a object header. Are there any reasons why you should not link to object headers?

Report this to a Moderator Report this to a Moderator
 10-Aug-2007 13:44
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 206
Joined: 15-Jul-2005

Alie,

Generally, my rule is not to link to object headers because headers don't change much, but text does. Also, you don't test object headers, and object headers are not individual requirements.

But that's a general rule. You could have a use case header linked to a requirement. In this scenario, chances are the requirement engineer doesn't care if the use case has changed, but the tester definitely cares if the requirement has changed. At the same time, running the analysis wizard from the top down could show the requirements linked to the use/test case header, and if set up properly, you'd see which use/test cases failed, instead of which step failed.

It all depends on your needs. Ensure you know the limitations of linking to headers instead of individual objects. If you don't know, set up some dummy modules and do some tests with the analysis wizard.

-------------------------
Kevin Murphy
http://www.baselinesinc.com
The Requirements Management Experts
Report this to a Moderator Report this to a Moderator
 15-Aug-2007 20:12
User is offline View Users Profile Print this message


Alexander Almoian

Posts: 10
Joined: 13-Feb-2007

The question is ambiguous. Linking is to OBJECTS not Object Heading or any other attribute. Every Object has all attributes - Object Heading, Object Text, etc. and any or all can be populated. An Object can have both Object Heading and Object Text populated. Even Table cells have all attributes - they can have Object Heading and all other attributes. Linking to Objects which only have Object Text populated can make sense in your context.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.