Monday, 5 March 2018
interim fix: 8.3-RAT-RHAPSODY-IFix2 published by dev team
The second iFix for Rhapsody 8.3 was release. Try this link.
INCOSE MBSE WORKING GROUP - MAR 20
I'm planning to go to the next INCOSE UK MBSE WG session in case anybody wants to meet up.
Saturday, 3 March 2018
Feedback from Rhapsody in C and Mastering MBSE with SysML training's in Jan/Feb
I'm doing a training roughly once a month now, predominantly private courses (although HORIBA MIRA are still organizing public MBSE/Rhapsody training's). This was my feedback from a 4 day training in Jan(from 8 of 13 that responded) that was an example of bespoke training:
"The discussions and knowledge of the instructor meant we could tailor context to our needs"
"The hands-on labs with individual laptops really helped reinforce the theory. The training material handouts were well organised"
This was from a 3-day MBSE training in February to 9 participants (completely new to the topics):
"It was a great 3 day programme. As a business development manager, I thought I wouldn't learn anything (new ;)), but, yes, it was a great learning experience. Could grasp many new stuff."
"Group exercises, challenges and practical implementations alongside theoretical understanding made the training interesting and fun. A wide range of topics were covered in a short span of time".
The main thing I've been learning (yes, learning is 2 way) is the value of including more group work and unguided challenges, i.e. things where participants have to put into practice the theory and get chance to ask the questions that arise from this.
I've also learnt that although 3 day training with SysML and Rhapsody gives a good grounding, there's value in adding the additional day (i.e. 4 days is better if you want to cover both in detail).
"The hands-on labs with individual laptops really helped reinforce the theory. The training material handouts were well organised"
This was from a 3-day MBSE training in February to 9 participants (completely new to the topics):
"Group exercises, challenges and practical implementations alongside theoretical understanding made the training interesting and fun. A wide range of topics were covered in a short span of time".
The main thing I've been learning (yes, learning is 2 way) is the value of including more group work and unguided challenges, i.e. things where participants have to put into practice the theory and get chance to ask the questions that arise from this.
I've also learnt that although 3 day training with SysML and Rhapsody gives a good grounding, there's value in adding the additional day (i.e. 4 days is better if you want to cover both in detail).
Wednesday, 31 January 2018
Mastering MBSE training now updated to 8.3
I have now updated my Mastering MBSE with OMG SysML and IBM Rational Rhapsody to Version 8.3 of Rhapsody. I've also delivered it! Another delivery is planned next week.
Don't forget that Rhapsody 8.3 also has an iFix. This may be important when deploying with Rhapsody Model Manager (RMM). Training on this latter capability together with Rhapsody and DOORS Next Generation (NG) using OSLC is planned.
Don't forget that Rhapsody 8.3 also has an iFix. This may be important when deploying with Rhapsody Model Manager (RMM). Training on this latter capability together with Rhapsody and DOORS Next Generation (NG) using OSLC is planned.
Sunday, 28 January 2018
Rhapsody Tip #29 - Understanding UML standard ports vs. SysML proxy ports (Intermediate)
With coming up to 30 videos posted it's a little harder to find quick wins, so this one goes into a little more detail (i.e. took a lot more work).
One of the key topics in my instructor-led SysML and MBSE training is getting to grips with different types of ports and interfaces in UML/SysML models. While SysML introduces two new ports in 1.3, full and proxy, there may be still models where standard and flow ports may be a better choice, or projects that predate the new port forms. Choosing the right one is crucial to value but depends a lot on context, and constraints, and needs. This silent video based on a new lab in my instructor-led 3 and 4 day training contrasts UML standard ports with SysML proxy ports, a new type of port in SysML 1.3 on-wards. It highlights some, but not all, of the key differences.
I'm planning a follow up video on (pre-SysML 1.3) flow ports vs proxy ports, a topic which I feel is important for automotive systems engineering, in particular. As always, there are pros and cons ;-).
One of the key topics in my instructor-led SysML and MBSE training is getting to grips with different types of ports and interfaces in UML/SysML models. While SysML introduces two new ports in 1.3, full and proxy, there may be still models where standard and flow ports may be a better choice, or projects that predate the new port forms. Choosing the right one is crucial to value but depends a lot on context, and constraints, and needs. This silent video based on a new lab in my instructor-led 3 and 4 day training contrasts UML standard ports with SysML proxy ports, a new type of port in SysML 1.3 on-wards. It highlights some, but not all, of the key differences.
I'm planning a follow up video on (pre-SysML 1.3) flow ports vs proxy ports, a topic which I feel is important for automotive systems engineering, in particular. As always, there are pros and cons ;-).
Sunday, 14 January 2018
Updated install guide for Rational Rhapsody 8.3
Just updated my install guide for Rational Rhapsody 8.3, incl. how to get iFix 001 and getting it working for executable MBSE.
This detailed guide includes:
1. Obtaining and installing IBM Rational Rhapsody Version 8.3 as an evaluation (assuming that's what you're doing).
2. Installing all editions and modifying the rhapsody.ini to desired default.
3. Obtaining and installing any iFixes for Rhapsody from IBM Fix Central.
4. Downloading, installing and testing the minimal Cygwin gcc+ compiler for use in system simulation.
5. Downloading, installing and testing my SysMLHelper profile for automotive-based executable mbse (see executablembse.com)
6. Tweaks that help the Gateway add-in work better with huge DOORS project structures.
This detailed guide includes:
1. Obtaining and installing IBM Rational Rhapsody Version 8.3 as an evaluation (assuming that's what you're doing).
2. Installing all editions and modifying the rhapsody.ini to desired default.
3. Obtaining and installing any iFixes for Rhapsody from IBM Fix Central.
4. Downloading, installing and testing the minimal Cygwin gcc+ compiler for use in system simulation.
5. Downloading, installing and testing my SysMLHelper profile for automotive-based executable mbse (see executablembse.com)
6. Tweaks that help the Gateway add-in work better with huge DOORS project structures.
Supported features in Rhapsody 64-bit in the 8.3 release
IBM updated it's list of features supported by Rhapsody in 64 bit: http://www-01.ibm.com/support/docview.wss?uid=swg27038779
Most notable is that code-centric mode and action language support was added in 8.3 to a list that includes: Rational Rhapsody Architect for Software, Reverse engineering, Round-tripping, RTC direct integration, and (notably) Rational Rhapsody ReporterPlus.
Note: Since the RTC direct integration is not constrained by 32-bit MSSC support this makes the 64-bit Rhapsody a candidate for deployment with the Team Concert direct integration.
The only thing missing from my perspective is Webify (web-enabling a model). Note: I have found that 64 bit will also make some assumptions about Cygwin compiler chain being 64 bit but if this occurs then it is quickly resolved with a property setting.
Most notable is that code-centric mode and action language support was added in 8.3 to a list that includes: Rational Rhapsody Architect for Software, Reverse engineering, Round-tripping, RTC direct integration, and (notably) Rational Rhapsody ReporterPlus.
Note: Since the RTC direct integration is not constrained by 32-bit MSSC support this makes the 64-bit Rhapsody a candidate for deployment with the Team Concert direct integration.
The only thing missing from my perspective is Webify (web-enabling a model). Note: I have found that 64 bit will also make some assumptions about Cygwin compiler chain being 64 bit but if this occurs then it is quickly resolved with a property setting.
Subscribe to:
Posts (Atom)