Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Dermot

Pages: 1 ... 34 35 [36] 37 38 ... 40
In the latest Version: F8 | Options -  allows filtering by Connector type and direction.  This should allow differentiation between the Actor and the Requirements by setting the direction and type='Realization'.

I would suggest you look at the RTF filtering available in the latest version.  For more information see the section on filtering in the RTF whitepaper.

That can occurr if you have a table row above the header row that is set very short - and is not seeen, but I asume not.  I can only suggest you remove the table and replace it with a new 2 row table.

If there is a blank line under the table pre the next Section then this will set repitition of table headers - again best to look at the RTF whitpaper for more detail.

If you have a recent version (post 834) it should be just a matter of setting the RTF Section: Package::Diagram::Element - leave this blank to reflect the Package::Element layout.  See:
F8 | Include all Diagrms in Report -  must be ON.

This enables custom windows to be inserted as tabs in the Diagram View.

Yes  I am not sure I understand your reply either - This is where pictures in help files really do help ;-)
The original settings could have been set in the "List Level Properties"  when  "List Item" was selected rather than 'List Overide'.
As a work around perhaps set both to reflect the 1.1.1 rather than 1.0.0

This should work, however are you sure the: Paragraph | List Numbering | set at level 1 & 2  - IS the same for both Element & Package Sections as was set in: Edit | List and Overides | Edit List Level?

For this we reccomend a scheduled DBMS backup rather than a DBMS-> eap transfer.

There is also other documentation on this in the whitepaper on Requirements Management:

If you are reporting Requirements and the Use Case that Realise these, then it is best to use (in a table) the Connector::Source::element and Connector::Target::element to show the related Use Cases & in the Options set the Connector type to filter only "Realisation" (needs build 834+).
In reverse -  for Use Cases there is the Section:  External Requirements - that returns these explicitly.

This is already supported with Element.Files (see the element properties  tab) alternately you can use Linked Documents or Document Artifacts to store these internaly.

In terms of the nesting of Model Documents, that is not currently supported, however Elements (model Document Elements) can be "Copied" to other packages (Master Documents):
Select multiple Elements in a diagram:
 - Edit | Copy
 - Go to a new package/diagram
 - Edit | Paste Elements | As New
(Note: 841 - it doesn't work for a single selection - but I have submitted a bug report)

There is a full VB 6 program and code available for generating documents.  For the code see:

There is a routine in this - PasteDiagram() that is a good example.

Pages: 1 ... 34 35 [36] 37 38 ... 40