![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Object Number Format Topic Summary: Created On: 14-Mar-2005 19:44 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Our organization has decided that we will never have an Object Heading and an Object Number within the same requirement.
For example: 1 Object Heading 1 1.1 Object Heading 2 1.1.1 Object Heading 3 1.1.1.0-1 Object Text 1 1.1.1.1-1 Object Text 2 1.1.1.1-1.0-1 Object Text 3 I think the 0-1 makes it harder to read, especially when you've got nested requirements. Is there any way to format the Object Number differently? ------------------------- Charing Maher Systems Engineer, SAIC |
|
![]() |
|
![]() |
|
I agree that it is a bad thing to overload an object by having both text and heading.
Also, I would recommend that you never nest text objects. i.e. objects with Object Text should be leaf objects. I would use paragraph numbers (Object Number) for headings only. For Text objects use the absolute number. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I'd like to reopen this topic for discussion. We used a .CSV file to import a spreadsheet, and consequently made all the main subject as Object Text attributes instead of Object Headers. As a result of this, the object numbers start with 0.1 instead of 1 and then all nested object text items start looking like this.
0-1 First Object Text line 0-1.0-1 First nested Object Text line 0-1.0-2 Sibling of line above 0-1.0-2.0-1 First nested Object Text of line above. So what I'm gathering you might suggest would be to move the Object Text information to Object Header for at least some portions where there are obvious branches, but then use the Absolute Number for the leaves. The problem with this would be that if you need to move something to make a more logical sequence of objects, the absolute number does not change, while Object Numbers do change depending on the placement after or below. Just curious why there is the extra 0- in front of the Object Text attribute, and can a DXL script get rid of that so that it is more clear?? The numbering scheme lends to outlining which some people like for objects that you don't seem to be able to get expect with the Object Headings. Any thoughts?? ------------------------- Brenda Heiss Cornell |
|
![]() |
|
![]() |
|
Lets think "spec" and not database. If you have a section with a heading, followed by two paragraphs, followed by subordinate sections and their paragraphs. In MS-Word it looks like this:
1.2 Paint Paint shall be 1 Paint shall be 2 1.2.1 Inside Paint Inside paint shall be y 1.2.1 Outside Paint Outside paint shall be x That looks OK. Now try to assign "paragraph numbers" to the text-only objects. The "Paint shall be 1" paragraph cannot have number 1.2.1 since that's already correctly taken by the sub-section below. Thus, to number Text objects while preserving the natural ordering of Heading objects, Text object's paragraph numbers need an additional identifier; in this case "1.2-0.1". It gets real hairy when text objects are inserted under other text objects. You can see object numbers like 1.2-0.1.3-0.1-0.2. Now imagine an additional Text paragraph after the "Outside paint shall be x" (a level 4 object); but that really applies to "1.2" general paint requirements (that is, its a level 3 object). That's hopeless as far as the spec is conserned since a person cannot tell it applies further up. You should adopt policies that keep your modules ordered like a spec. Here's some policies: [] Heading objects's parents must be Heading objects <this prevents any heading with having a "-0." in its number>. [] Text object's can have a Text Object parent only when the 2nd is subordinate to the first; perhaps "shall be as the following list" at level 4 while the list is level 5. [] Text objects cannot have Heading Objects and previous Siblings. That is, the text children of an object must all come before all the Heading children of an object. [] Don't use paragraph numbers as requirement identifiers; use either the Object ID or come up with some scheme to develop your own "Requirement ID" or "Capability ID" attribute. Thus, you cannot refer to the "2nd paragraph in section 1.2", instead refer to requirement "MySpec_12". You may want to adopt the notion of an object's 'Title', which is [1] If its a Heading Object the title is the Number and Heading, e.g. "1.2 Paint". [2] If its a Text Object then the title is the title of the parent object with braces, e.g. the title of "Paint shall be 1" is "[1.2 Paint]". When I summarize Objects I routinely refer to both the object's ID and its Title: "[1.2 Paint] MySpec_12 Paint shall be 1". The correctly identifies the requirement as well tell the user its relative context, which folks often like. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Object Number Format
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.