Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Chapter & Verse on Requirements Modelling with SysML
Topic Summary:
Created On: 3-Jan-2007 16:45
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.
 3-Jan-2007 16:45
User is offline View Users Profile Print this message


Matthew Thomas

Posts: 35
Joined: 18-Jun-2007

I am looking for a good (preferably single point) practitioner's guide on the subject of requirements modelling with SysML. If it has a chapter on using DOORS and Rhapsody together that would make me

-------------------------
-----------------------
Matthew Thomas
Panasonic Manufacturing UK Ltd
Report this to a Moderator Report this to a Moderator
 14-Aug-2007 23:28
User is offline View Users Profile Print this message


Christopher Parris

Posts: 1
Joined: 6-Oct-2006

Most books available that reference SysML don't explain how to use it. They merely reference it in the introductory chapter.


Learning Tree may have a course on the subject, but SysML is so new that you may have to attend an OMG meeting and meet the group that put the standard together to get a better picture of the authors' intentions. [url]www.sysml.org[/url] has some links to some tutorials as well.

Hope this helps
Report this to a Moderator Report this to a Moderator
 16-Aug-2007 07:22
User is offline View Users Profile Print this message


Charlie Lane

Posts: 86
Joined: 16-Sep-2005

Peter has proposed an addition to the Harmony process that covers requirements modelling, an area that is known to be weak in the current Harmony deskbook. I would expect this to cover aspects such as the use of DOORS, both for source requirements and for flowed-down requirements from Rhapsody, BBSatisfy and WBSatisfy, marking of what parts of a Rhapsody model constitute the flowed-down requirements, non-functional requirements, ICDs, change management, etc.
I have offered to help by contributing some of the lessons we have learnt from our Harmony/SysML trial in Selex S&AS, but haven't heard what progress has been made. Currently we use an in-house guidelines document. If you see this thread, Peter, would you care to comment?

Regards, Charlie.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 1 users logged in.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.