![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Manage version (or migration) in SA Topic Summary: Created On: 6-Dec-2005 21:05 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I understand SA does not have version control. Just wonder, how do you guys manage the versioning or migration in practice?
For example, I want to show different version of a system diagram or application diagram in SA. Currently, I have to name them differently, like System V1.0, System V1.1. Do you guys do the same? Thanks. Mike |
|
![]() |
|
![]() |
|
This can become pretty tricky. If you simply version according to the name on a diagram, any changes that occur in a definition represented on both diagrams will be propogated to both diagrams. Therefore, you have a depiction of what things looked like in the past, but the underlying content is not guaranteed (nor are the names used).
Some options are to be very stringent in naming conventions of the definitions themselves, copying the definition if it needs to change. With the new history in 10.3 you may find some luck in seeing the changes since a date, or you may want to simply export the diagram to XML for safe keeping. |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.