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: How to model SV2
Topic Summary: SA interpretation of SV2
Created On: 27-Mar-2008 09:57
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.
 27-Mar-2008 09:57
User is offline View Users Profile Print this message


Jesper Ryge Leth

Posts: 4
Joined: 30-Mar-2007

Hi,

I am wondering if anybody have any experience in creating MODAF SV-2a/b/c using System Architect.

I am particular interessted in SV-2b and how the ports and protocol stack should be represented. The only place there seem to be any notion of protocols are in the SV-4 system data exchange. Here it is only a text field and cannot have any reference to the TVs.

I might be mistaken bu there does not seem to be a reasonable way to represent the SV-2a/b/c in SA?

Generally the documentation on MODAF in SA is generally sparse (close to non-existent). Is there anybody who uses SA for MODAF and does anybody know of any resources, where you can find examples and documentation of using SA for MODAF
Report this to a Moderator Report this to a Moderator
 2-Apr-2008 12:23
User is offline View Users Profile Print this message


Morten Lund

Posts: 10
Joined: 29-Aug-2007

Good question Jesper!

- Morten
Report this to a Moderator Report this to a Moderator
 25-Jun-2008 15:48
User is offline View Users Profile Print this message


Imran Khan

Posts: 2
Joined: 14-Apr-2008

This is why I came on this forum, looking for precisly the answer to this question. Ther is no resonable way of doing this in SA to my knowledge The diagrams are also aweful, its like a 3 year old has been drawing pictures with Microsfot Paint.

Edited: 25-Jun-2008 at 15:49 by Imran Khan
Report this to a Moderator Report this to a Moderator
 26-Jun-2008 14:59
User is offline View Users Profile Print this message


Jesper Ryge Leth

Posts: 4
Joined: 30-Mar-2007

The information from the SV-2 is present throug the system data exhanges (SV-4 data flow). The system data exchanges can be attached to the system interfaces in the SV-1 (or SV-2b). I solved the issue by creating an SV-4 and defining the system dataexchanges needed. These are attached to the SV-1 system interfaces. I made a visual representation (on the SV-4) of the SV-2b that resembles the SV-2 from the MODAF documentation suite.

This solution is far from ideal and for the life of me I can't figure out why SA have SV-2 diagram types (other than to claim MODAF compliance), as they are identical to SV-1 diagrams.

With respect to the look of the diagrams, I can only agree. I wish it was possible to use the UML fucntionality of SA to create MODAF models.

On a side note: The lack of responses to MODAF specific questions on this board, and the maturity (or lack thereof) of the MODAF implementation and documentation leads me to conclude that we are only a few who are using SA for MODAF. This makes MODAF and SA a painful trial and error driven process.



Edited: 26-Jun-2008 at 15:01 by Jesper Ryge Leth
Report this to a Moderator Report this to a Moderator
 26-Jun-2008 20:30
User is offline View Users Profile Print this message


lou varveris

Posts: 32
Joined: 18-Jun-2005


Hi everyone,

Our MODAF implementation relies on the existing SV-2 diagram of DoDAF. SV-2a/b/c as you mention, use the UML 2 style representation of ports and System Architect didn't have UML 2 diagrams available when the MODAF support was initially specified.

We are in the process of specifying improvements to our MODAF support, including possible support UML-2-style ports. We are also in the process of updating the AcV-2 project timeline diagram for better ease of use and also to align it with metamodel changes of MODAF 1.2. These improvements are scheduled to be available in the next few upcoming releases.

If you have any other recommended changes to the MODAF area of the tool, please feed them back.

You can reach me at lou.varveris@us.ibm.com, or you can specify them here.

Lou
Report this to a Moderator Report this to a Moderator
 3-Jul-2008 09:11
User is offline View Users Profile Print this message


Imran Khan

Posts: 2
Joined: 14-Apr-2008

SV2 in SA as we all seem to agree is a painful process. After spending £10000 on SA licences I have now gone back to using Telelogic's free tool UML tool. As we all know, its not just about functionality, its about form aswell. Telelogic free tool is a million miles ahead in terms of aesthetics. Will Telelogic eventually produce that sort of quality interface? I hope now that IBM is on the scene, that SA will improve dramatically because I for one would never purchase it again in its current form.
Report this to a Moderator Report this to a Moderator
 8-Jul-2008 22:58
User is offline View Users Profile Print this message


lou varveris

Posts: 32
Joined: 18-Jun-2005

Thanks Imran, your feedback is very much appreciated and appologies for your current dissatisfaction. We are actively working on projects to improve SA's aesthetic usability, including its definition dialog interface, symbol metafile type supported, and various other facets of the user interface. You should see improvements coming in stages over the next few releases.

Edited: 8-Jul-2008 at 23:00 by lou varveris
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.