Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic System Architect (steve huntington)
Decrease font size
Increase font size
Topic Title: SA SV-1 vs Visio
Topic Summary: Since I'm still waitong for tech support to finish answering my question, maybe someone in the forums can help.
Created On: 10-Jan-2006 15:56
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
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.
Answer This question was answered by Richard Fuchs, on Friday, January 13, 2006 1:21 PM

Answer:
Question: I am using SA 10.1.11 and we are developing a product line architecture and documenting it with DoDAF. The problem we are encountering is when we are trying to develop the SV-1 diagrams. We have components (modeled as system elements) that are reused in several places (by system entities, as well as being used outside of a system entity). But with the restrictions the tool is placing on us (sys component has to be in a sys element, which has to be in a sys entity, which has to be in a sys node, we cannot model what we are building. How can we resolve this problem without resorting to using SA as an expensive Visio? Tech Support Response(partial): Are they using the SV-7 properties? If yes, they could use USRPROPS to move the SA-v properties from Sys elements and components to System Entities (which is where they are in the ABM version), and forget the system elements and components all together. In the ABM version, there is no different between system entities (usually called 'systems') and system components; it is one definition type. All the SV-7 properties are in the system entity. Since all 3 interface lines have system data exchanges, this seems like the easiest way to go. Question: What SV-7 properties are they talking about? How do I make those changes and what else will that mess up down the line if I do make those changes? Tech Support Response:
 10-Jan-2006 15:56
User is offline View Users Profile Print this message


Richard Fuchs

Posts: 6
Joined: 30-Nov-2005

Answer Answer
Question: I am using SA 10.1.11 and we are developing a product line architecture and documenting it with DoDAF. The problem we are encountering is when we are trying to develop the SV-1 diagrams. We have components (modeled as system elements) that are reused in several places (by system entities, as well as being used outside of a system entity). But with the restrictions the tool is placing on us (sys component has to be in a sys element, which has to be in a sys entity, which has to be in a sys node, we cannot model what we are building. How can we resolve this problem without resorting to using SA as an expensive Visio? Tech Support Response(partial): Are they using the SV-7 properties? If yes, they could use USRPROPS to move the SA-v properties from Sys elements and components to System Entities (which is where they are in the ABM version), and forget the system elements and components all together. In the ABM version, there is no different between system entities (usually called 'systems') and system components; it is one definition type. All the SV-7 properties are in the system entity. Since all 3 interface lines have system data exchanges, this seems like the easiest way to go. Question: What SV-7 properties are they talking about? How do I make those changes and what else will that mess up down the line if I do make those changes? Tech Support Response:
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic System Architect forum.
There are currently 1 users logged in.
The most users ever online was 16 on 30-Oct-2008 at 14:46.
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.