![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Mixing Modeling Methods Topic Summary: Created On: 15-Nov-2005 20:44 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Greetings,
The question is perhaps naive but I would like to know what happens or what can happen when we mix two different methods for modeling. I explain myself. I have a user who created a System Architecture diagram (Application tab), selected all its items by a CTRL+A, created a Use case diagram (UML tab), made a copy (CTRL-C), then made modifications on the Use Case. On the original diagram there were Locations and Data Store definitions which are not managed by UML. There started to have some errors, like repeating 5 times some names and presently it is impossible to open the Use Case diagram as we get a 'File Error with , Record length incorrect' message. I am almost sure the fact that bringing to UML symbols and definitions it cannot handle causes the problem but I want to hear a confirmation of this and at the same time I want to know about the general behaviour of SA when mixing two modeling methods is done. TIA, Michèle Dessureault Revenu Québec |
|
![]() |
|
![]() |
|
One should read 'ctrl+a' and 'ctrl+c' in the System Architecture Diagram and 'ctrl+v' in the Use Case diagram. |
|
![]() |
|
![]() |
|
SA does allow you to mix methodologies in that you can copy symbols from one diagram type onto another. There are some restrictions as to which symbols can go where. For example, if you try to copy Use Case diagram symbols onto a System Architecture diagram all of the use case symbols will be converted to plain rectangle symbols. The properties of the source symbol will be copied into the new rectangle symbol's graphic comment property with the following note appended:
This rectangle has been added to the diagram in
place of a Class symbol which
cannot be supported on a diagram of this type (System Architecture)
You can copy System Architecture symbols onto a Use Case diagram. The symbols can be edited and updated just as if they were on a System Architecture diagram.
Using SA 10.3 I haven't been able to reproduce any of the problems you describe.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.