Hi All!

Our yearly MesConf will, like any other conferences, be held online. It is what it is.
There are some advantages too, no travel, no maximum number of people and you can show up how you want, just keep your camera off… 😉
it will be held on September 17 and we have room left for interested people.

There are interesting presentations from Prof. dr, Alois Zoitl (Professor for cyber-physical systems for Engineering and production), Stephanie Borgert (Speaker, Author and Furtherthinker) and Martin Reiss (Chief Software Architect from Thales railway)

Of course I will be there as well (Speaking about using AUTOSAR together with UML and SysML) and many more of the Experts from OOSE, SodiusWillert, SiSy, IBM and many others!

Here is the website (in German! Try to open with google translate if you want to read it in English)

The main message is here:

The subject is too important. Therefore, we will not skip the conference due to the corona risk, but will convert it into a one-day online conference.

MESCONF focuses on the benefits of modeling in the development of embedded systems. Another thematic pillar of MESCONF is model-based systems engineering (MBSE).

Our world is becoming more and more complex and dynamic. The constant change is one of the challenges for companies. Successful are those companies that can react flexibly and quickly to the changing requirements of the market with high-quality products.

We are convinced that modeling makes a crucial contribution to achieving this ability. We have formulated our values and convictions in a manifesto. At the conference we also want to talk and discuss the manifesto.

Tickets can be bought here at Xing.

I hope to 

Prologue

Hi All! It’s been a while since I wrote. Not much travelling these days, I was in Germany in the office last week and in Stuttgart (by car) but only briefly.
Work however continues and is even more than usual.
So not much time to write BLOG entries. Soon my first vacation in 3 years (too busy building a house…) will start. I promise to write some new stuff then…

XSD

This time I want to speak about something unexpected that you can do with Rhapsody: XSD (XML Schema Definition) import/export and editing with Rhapsody.
This is an add-on Tool (of course from SodiusWillert!!) That helps you deal with the normally textual and tiresome XSD files in a nice graphical way.

I added some of the pictures and explanations from our presentation, you can download the presentation here:

Rhapsody XSD – Key Features

If this is interesting for you, please contact me!

Happy XSD-ing with Rhapsody!

Walter van der Heiden (wvdheiden@sodiuswillert.com)

Prologue

Hi All! It’s been a while since I wrote. Not much travelling these days, I was in Germany in the office last week and in Stuttgart (by car) but only briefly.
Work however continues and is even more than usual.
So not much time to write BLOG entries. Soon my first vacation in 3 years (too busy building a house…) will start. I promise to write some new stuff then…

XSD

This time I want to speak about something unexpected that you can do with Rhapsody: XSD (XML Schema Definition) import/export and editing with Rhapsody.
This is an add-on Tool (of course from SodiusWillert!!) That helps you deal with the normally textual and tiresome XSD files in a nice graphical way.

I added some of the pictures and explanations from our presentation, you can download the presentation here:

Rhapsody XSD – Key Features

If this is interesting for you, please contact me!

Happy XSD-ing with Rhapsody!

Walter van der Heiden (wvdheiden@sodiuswillert.com)

Introduction

I don’t want to say much about Corona, Lockdown, Virus, COVID-19, Social Distancing and related subjects, there are enough other places where you can read enough about that topic. I was personally quite busy with all kinds of things (moving to a new house but also not traveling…) so it took me a while to get back writing.

Rhapsody 9.0

Yes!It is there! the long awaited Rhapsody 9.0. To be precise… the name is no longer “IBM Rational Rhapsody” but “IBM Engineering Systems Design Rhapsody”. Whatever….

Here is a brief summary of important changes:

• Windows 10 AppLocker Compliance
  The “Share” folder has been split up into “UserShare” which resides in the Rhapsody data folder and “Share” which is now in the (usually read-only) Rhapsody program files folder. You will find property files like SiteC++.prp in the “UserShare” folder now, while e.g. profiles and settings elivered with Rhapsody are in the Share folder.
• Framework Compilation
  Rhapsody standard frameworks like the „oxf” do not come as ready-to-use libraries anymore. They are built when needed or via menu entry “Code” => “Build Framework“.
• Dropped „Save As .rpy“ Support
  Attention: this is the first Rhapsody version that does not support to save in old Rhapsody format (.rpy) anymore.
• Support for property help that comes with profiles
  For example our latest C++ RXF uses this mechanism and makes it possible to see properties for the RXF in Rhapsody including the context sensitive help.
• MinGW Environment Support
• IBM Product Renaming
  In most places „old product names“ have been adapted to match the IBM Engineering Lifecycle Management family product names.
• Under-the-Hood Improvements
  There are important improvements internally, which are not directly visible to the customer. The toolchain used for Rhapsody development has been upgraded, also libraries Rhapsody relies on are updated. This is a big step that will be the prerequisite for future Rhapsody improvements, especially regarding the user interface.
• And off course: Bugfixes
  Several problems reported by our customers and others have been addressed in that release, for details see IBM’s fix list.

Customers using the Embedded UML Studio (and a so-called ASL-license) can use our Download Portal to access Rhapsody 9.0: x86/x64.

Customers working with the RXF can check the support announcement for the RXF with Rhapsody 9.0 to see how they can easily upgrade.

RXF for C++ 7.11

And that’s not it…

We have just released the new version 7.11 of the Real-time eXecution Framework (RXF) for efficient UML code generation.
Those are the most important news:

• Dynamic Memory Usage for Events
  The RXF usually works with statically pre-allocated memory blocks for optimal and deterministic memory management of UML events (asynchronous messages). With the new version it is also possible to explicitly allow the usage of dynamic memory allocation from the heap, if matching  static memory pools are not available or full. By default, it still uses statically allocated memory pools.
   

• RXF Property Perspective and RXF Property Help in Rhapsody
  When using the RXF stereotype, you automatically get a „Willert RXF“ property perspective to see all relevant properties for framework configuration in a well organized way. You can select it instead of „All“/„Overridden“/etc. in the properties tab drop down list. Actually this came with an earlier version already, but since Rhapsody 9.0 and with the latest RXF release it is even more useful, as you can see the property description now right inside Rhapsody just like for any standard Rhapsody property (see screenshot above).
   
• ActiveClassTable
  It is now easier to keep an overview of all the threads (active classes) configured in your model:
   

• No Setup required, Relative Paths used
  There is no need to install a framework to a specific absolute directory anymore. You may move the RXF folder to another location. As long as the RXF profile is referenced correctly from your UML model, all tool paths will work. This also allows easier configuration management and maintenance of future project specific RXF updates using externals on your SCM. For details read the HTML documentation under Technology => Configuration-Management.
   
• MISRA Improvements and a Bugfix
  Most MISRA improvements have already found it’s way into earlier RXF releases, but still some minors could be improved. And a bug was fixed where timeout handling could be unprotected when using critical sections instead of mutexes.

Our C++ RXF is generic, it means you do not need to select a specific environment when you download it, but it contains components for different RTOSes, targets etc, so you can
make the selection when you deploy your model into an IDE. Here is a list of what is contained:

RTOS

• CMSIS (based on Keil-RTX)
• CMSIS2
• FreeRTOS
• embOS
• Linux
• OORTX (our non-preemptive, highly efficient runtime system)
• COORTX (non-preemptive, called periodically by your legacy software)
• QNXNeutrino
• ucOSII
• Windows

Target Hardware

• Any ARM Cortex via CMSIS layer
• AURIX TriCore (HighTec)
• Any target abstraction supported by an RTOS listed above
• PC (Windows, Linux)

Compiler

There are no compiler dependencies. Any C++98 (ISO/IEC 14882:1998) compatible compiler shall work. On our continuous integration build server the following compilers are always tested:

• Keil ARM V5
• Keil ARM V6
• Linux gcc
• ARM Cross-gcc
• Visual Studio 2017

IDE (Deployer Exporters)

• Keil μVision 5
• IAR Embedded Workbench 8
• Green Hills Multi
• Microsoft Visual Studio 2015/2017/2019
• Directory Exporter, covering Eclipse based IDEs and makefile centric builds like:
• TI’s Code Composer Studio
• NXP’s CodeWarrior
• Tasking VX
• gnu make
• CMAKE
• SCons

Do you need something else to support your environment? Just contact us and we can give details about how it can be supported.

RXF V6 Patch for Rhapsody 9.0 Compatibility Available

Also customers of the RXF V6 can use it with Rhapsody 9.0, please read our support announcement for the RXF with Rhapsody 9.0.

Exciting News for our RXF C Customers

We expect to release a version 7 for the C language in the next months with huge improvements. It will also be generic (no dedicated release for each tool and target combination required anymore), will not require a Setup and will have a completely new and optimized approach for ports and interfaces code generation in C! We will keep you up to date.

That’s it! Happy modeling with Rhapsody!

Walter van der Heiden ( wvdheiden@sodiuswillert.com )

Introduction

I don’t want to say much about Corona, Lockdown, Virus, COVID-19, Social Distancing and related subjects, there are enough other places where you can read enough about that topic. I was personally quite busy with all kinds of things (moving to a new house but also not traveling…) so it took me a while to get back writing.

Rhapsody 9.0

Yes!It is there! the long awaited Rhapsody 9.0. To be precise… the name is no longer “IBM Rational Rhapsody” but “IBM Engineering Systems Design Rhapsody”. Whatever….

Here is a brief summary of important changes:

• Windows 10 AppLocker Compliance
  The “Share” folder has been split up into “UserShare” which resides in the Rhapsody data folder and “Share” which is now in the (usually read-only) Rhapsody program files folder. You will find property files like SiteC++.prp in the “UserShare” folder now, while e.g. profiles and settings elivered with Rhapsody are in the Share folder.
• Framework Compilation
  Rhapsody standard frameworks like the „oxf” do not come as ready-to-use libraries anymore. They are built when needed or via menu entry “Code” => “Build Framework“.
• Dropped „Save As .rpy“ Support
  Attention: this is the first Rhapsody version that does not support to save in old Rhapsody format (.rpy) anymore.
• Support for property help that comes with profiles
  For example our latest C++ RXF uses this mechanism and makes it possible to see properties for the RXF in Rhapsody including the context sensitive help.
• MinGW Environment Support
• IBM Product Renaming
  In most places „old product names“ have been adapted to match the IBM Engineering Lifecycle Management family product names.
• Under-the-Hood Improvements
  There are important improvements internally, which are not directly visible to the customer. The toolchain used for Rhapsody development has been upgraded, also libraries Rhapsody relies on are updated. This is a big step that will be the prerequisite for future Rhapsody improvements, especially regarding the user interface.
• And off course: Bugfixes
  Several problems reported by our customers and others have been addressed in that release, for details see IBM’s fix list.

Customers using the Embedded UML Studio (and a so-called ASL-license) can use our Download Portal to access Rhapsody 9.0: x86/x64.

Customers working with the RXF can check the support announcement for the RXF with Rhapsody 9.0 to see how they can easily upgrade.

RXF for C++ 7.11

And that’s not it…

We have just released the new version 7.11 of the Real-time eXecution Framework (RXF) for efficient UML code generation.
Those are the most important news:

• Dynamic Memory Usage for Events
  The RXF usually works with statically pre-allocated memory blocks for optimal and deterministic memory management of UML events (asynchronous messages). With the new version it is also possible to explicitly allow the usage of dynamic memory allocation from the heap, if matching  static memory pools are not available or full. By default, it still uses statically allocated memory pools.
   

• RXF Property Perspective and RXF Property Help in Rhapsody
  When using the RXF stereotype, you automatically get a „Willert RXF“ property perspective to see all relevant properties for framework configuration in a well organized way. You can select it instead of „All“/„Overridden“/etc. in the properties tab drop down list. Actually this came with an earlier version already, but since Rhapsody 9.0 and with the latest RXF release it is even more useful, as you can see the property description now right inside Rhapsody just like for any standard Rhapsody property (see screenshot above).
   
• ActiveClassTable
  It is now easier to keep an overview of all the threads (active classes) configured in your model:
   

• No Setup required, Relative Paths used
  There is no need to install a framework to a specific absolute directory anymore. You may move the RXF folder to another location. As long as the RXF profile is referenced correctly from your UML model, all tool paths will work. This also allows easier configuration management and maintenance of future project specific RXF updates using externals on your SCM. For details read the HTML documentation under Technology => Configuration-Management.
   
• MISRA Improvements and a Bugfix
  Most MISRA improvements have already found it’s way into earlier RXF releases, but still some minors could be improved. And a bug was fixed where timeout handling could be unprotected when using critical sections instead of mutexes.

Our C++ RXF is generic, it means you do not need to select a specific environment when you download it, but it contains components for different RTOSes, targets etc, so you can
make the selection when you deploy your model into an IDE. Here is a list of what is contained:

RTOS

• CMSIS (based on Keil-RTX)
• CMSIS2
• FreeRTOS
• embOS
• Linux
• OORTX (our non-preemptive, highly efficient runtime system)
• COORTX (non-preemptive, called periodically by your legacy software)
• QNXNeutrino
• ucOSII
• Windows

Target Hardware

• Any ARM Cortex via CMSIS layer
• AURIX TriCore (HighTec)
• Any target abstraction supported by an RTOS listed above
• PC (Windows, Linux)

Compiler

There are no compiler dependencies. Any C++98 (ISO/IEC 14882:1998) compatible compiler shall work. On our continuous integration build server the following compilers are always tested:

• Keil ARM V5
• Keil ARM V6
• Linux gcc
• ARM Cross-gcc
• Visual Studio 2017

IDE (Deployer Exporters)

• Keil μVision 5
• IAR Embedded Workbench 8
• Green Hills Multi
• Microsoft Visual Studio 2015/2017/2019
• Directory Exporter, covering Eclipse based IDEs and makefile centric builds like:
• TI’s Code Composer Studio
• NXP’s CodeWarrior
• Tasking VX
• gnu make
• CMAKE
• SCons

Do you need something else to support your environment? Just contact us and we can give details about how it can be supported.

RXF V6 Patch for Rhapsody 9.0 Compatibility Available

Also customers of the RXF V6 can use it with Rhapsody 9.0, please read our support announcement for the RXF with Rhapsody 9.0.

Exciting News for our RXF C Customers

We expect to release a version 7 for the C language in the next months with huge improvements. It will also be generic (no dedicated release for each tool and target combination required anymore), will not require a Setup and will have a completely new and optimized approach for ports and interfaces code generation in C! We will keep you up to date.

That’s it! Happy modeling with Rhapsody!

Walter van der Heiden ( wvdheiden@sodiuswillert.com )

I’ve been in the USA for quite some times. But Nashville was new, never been there before. So I increased my State count to 39! 11 to go.
The cheapest flight I could get was from Hannover. Via Amsterdam (which is closer to me, but don’t skip a leg, that’ll cost you….amazing in this time of saving the environment….)
So I got on the plane to AMS early for the stopover to… Toronto! I’ve been there before, twice. Nice city! There I would get on a plane to Nashville.

I was in Nashville for the Kick-off Conference of our beloved USA partner 321-Gang.

After the Kick-Off there was, luckily, some time left to visit Florida, a real must in winter time 😉 After 3 nice warm days I was on the way back ( ;-( ;-( ;-( ) But that was less easy then I thought… Again I would fly via Toronto but the plane coming from Toronto had a delay (Cause: medical Emergency…)
The information on the duration of the delay was very fuzzy. I tried to find out an alternative way to fly home but there was no real alternative.
So I gambled on the original flight that was earlier then expected.
It was, for hours and hours, on the tipping point of “Not going to make it” and “Just in Time”. I hate that.
To cut a long story short: The fact that I had to cross customs in Canada made me miss my plane.
So I had to spend another 24 hours in Canada. With only T-Shirts. And with -13ºC outside…
Luckily KLM was very, extremely good and they shifted my flight (They didn’t have to, i was on the cheap non-refundable flight) WestJet (Canada air-carrier operating for Delta) did not want to reimburse my Hotel costs.. “Use your insurance”…. Yeah I will.

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

Reverse and Roundtrip

In the last versions of Rhapsody we receive an increasing number of complaints about issues with Reverse and/or Roundtrip Engineering.

Issues

The issues are:

• Reverse Engineering seems to start but does not give a result.
• “Populate Diagram” is missing in the “Operation” menu

Rhapsody Version/License

A possibility is that your license is too old. What?? But everything works fine, except….
That is correct. Your old license also works for newer Rhapsody versions, I don’t understand that either, i’d link that to newer versions and support payments but hey, I know nothing about that….
So, exactly right. In some version of Rhapsody there was an entry added in the license file for Reverse/Roundtrip. Adding this solves the problem. You can generate a new license file in the License Key Center. (If you have a support contract with SodiusWillert (or Sodius or Willert or event somewhere else) we’ll help you.

32/64-bit

Most of these problems are related to the 32/64-bit version of Rhapsody. Due to some historic reasons the 64-bit version of Rhapsody lacked a lot of options that the 32-bit version had.
Also because of the way Windows is built, it is not easy to almost impossible to start 32-bit apps from 64-bit apps and vice-versa.

Solution

You can install both the 32-bit and the 64-bit version of Rhapsody even from the same install version. Remember that you then also need both Service Packs if you upgrade!
Then you can start 32-bit if you want to do stuff that involves any roundtrip or reverse engineering and use the 64-bit for everything else. Models are interchangeable.

So. That’s it. Have fun modelling with Rhapsody

Walter van der Heiden (wvdheiden@sodiuswillert.com)

I’ve been in the USA for quite some times. But Nashville was new, never been there before. So I increased my State count to 39! 11 to go.
The cheapest flight I could get was from Hannover. Via Amsterdam (which is closer to me, but don’t skip a leg, that’ll cost you….amazing in this time of saving the environment….)
So I got on the plane to AMS early for the stopover to… Toronto! I’ve been there before, twice. Nice city! There I would get on a plane to Nashville.

I was in Nashville for the Kick-off Conference of our beloved USA partner 321-Gang.

After the Kick-Off there was, luckily, some time left to visit Florida, a real must in winter time 😉 After 3 nice warm days I was on the way back ( ;-( ;-( ;-( ) But that was less easy then I thought… Again I would fly via Toronto but the plane coming from Toronto had a delay (Cause: medical Emergency…)
The information on the duration of the delay was very fuzzy. I tried to find out an alternative way to fly home but there was no real alternative.
So I gambled on the original flight that was earlier then expected.
It was, for hours and hours, on the tipping point of “Not going to make it” and “Just in Time”. I hate that.
To cut a long story short: The fact that I had to cross customs in Canada made me miss my plane.
So I had to spend another 24 hours in Canada. With only T-Shirts. And with -13ºC outside…
Luckily KLM was very, extremely good and they shifted my flight (They didn’t have to, i was on the cheap non-refundable flight) WestJet (Canada air-carrier operating for Delta) did not want to reimburse my Hotel costs.. “Use your insurance”…. Yeah I will.

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

• 

Reverse and Roundtrip

In the last versions of Rhapsody we receive an increasing number of complaints about issues with Reverse and/or Roundtrip Engineering.

Issues

The issues are:

• Reverse Engineering seems to start but does not give a result.
• “Populate Diagram” is missing in the “Operation” menu

Rhapsody Version/License

A possibility is that your license is too old. What?? But everything works fine, except….
That is correct. Your old license also works for newer Rhapsody versions, I don’t understand that either, i’d link that to newer versions and support payments but hey, I know nothing about that….
So, exactly right. In some version of Rhapsody there was an entry added in the license file for Reverse/Roundtrip. Adding this solves the problem. You can generate a new license file in the License Key Center. (If you have a support contract with SodiusWillert (or Sodius or Willert or event somewhere else) we’ll help you.

32/64-bit

Most of these problems are related to the 32/64-bit version of Rhapsody. Due to some historic reasons the 64-bit version of Rhapsody lacked a lot of options that the 32-bit version had.
Also because of the way Windows is built, it is not easy to almost impossible to start 32-bit apps from 64-bit apps and vice-versa.

Solution

You can install both the 32-bit and the 64-bit version of Rhapsody even from the same install version. Remember that you then also need both Service Packs if you upgrade!
Then you can start 32-bit if you want to do stuff that involves any roundtrip or reverse engineering and use the 64-bit for everything else. Models are interchangeable.

So. That’s it. Have fun modelling with Rhapsody

Walter van der Heiden (wvdheiden@sodiuswillert.com)

Introduction

Every year, the start of December, it is time for the yearly reunion for Embedded Software Developers. It is called ESE Kongress (yes, in German) and is held in the “Stadthalle Sindelfingen”.
This is near Stuttgart and home of Daimler Benz, the makers of Mercedes.

ESE is organized by Microconsult and Elektronik Praxis, a training company, and a publishing company, for 12 years they started doing that.
I’ve been on all of them and I really like the event.
It is smaller than the Embedded World but that is exactly the charm of it, the noise is limited, there is time to speak in-depth with visitors, the presentations are controlled and contain no or just a really little bit of marketing, the information depth is very good.

Because we have a table there I traveled by car with a booth full of folders, flyers, roll-ups and more.

The highlight of the ESE is, of course, the Table Football Tournament… And the Developer party but in the daytime, it was Johannes Trageser’s presentation “Do you still draw or are you already generating code”.

Rhapsody

Some Rhapsody news. Version 9 is on the way. There is no fixed release date but it will be “any moment now”.

My colleague Wolfgang Sonntag has solved a long year problem…. The Rhapsody #$%^&* Editor that adds whitespace if you do not click on the start of the line.

It turns out that there is an option that prevents that. Just right-click in the editor, open the properties, go to the “misc” tab and tick the option “Confine caret to text” (Don’t ask….)

Questions still stay…. why isn’t that the default? Why does somebody think that “confine caret to text” is something people look for when they want to change the whitespace behavior of the editor?

For the “new” Rhapsody users… here you can also switch on the line numbers. Please choose decimal and “1” as Start at….

These settings are not stored in the model… and also not in Rhapsody.ini. The Editor is an open-source editor that stores its settings in the registry. “HKEY_CURRENT_USER\Software\Telelogic\Rhapsody 8.4\Code Window-Ansi”. “SELBOUNDS” is the key that controls this.

Anyway… this solves it. Better late than never. It works also for fields in the statecharts (Yes! also the guard!!!)

Have fun editing in Rhapsody without extra whitespace!

Walter van der Heiden ( wvdheiden@sodiuswillert.com )

Bordeaux

This time not Nantes… but Bordeaux. OK, first Nantes, there was some work to be done, but after that there was room for some personal time-off.
A friends 50th birthday was there and had to be celebrated big time.

His wife rented an old castle (France has about a million of these) where the celebration would take place. We celebrated heavily… drank a lot of wie.
We also visited a Safran Farm, of course, a vinyard and an old village wit ha magnificant church (No photo’s allowed, sorry.)

Absolute and relative paths.

Unfortunately the default in Rhapsody is to use absolute paths. And it will use absolute when in doubt.

There are 3 properties that control the switch from Absolute to Relative:

1. General::Model::PathInProjectList, this is the path that models have in a prject list (“Workspace”

2. General::Model::ReferenceUnitPath, this is the path where units are stored. When this is relative paths are stored relative to the model directory.

3. C_ReverseEngineering::Main::useCodeCentricAbsolutePath, is a new property to indicate if reverse engineered sources are stored absolute or relative

Use Rhapsody Workspace

A bit hidden is the posibility to use multiple projects inside one open Rhapsody. It is in the menu under “File”, there is “Insert Project >” and then “New…” or “Existing…”. Selecting a Rhapsody project will shift both the open project and the newly openened project under a “Projects” folder.
One of the projects (The last opened) is writable (or “active”), indicated by the BOLD name and all others are read-only, indicated by the (RO) behind the name.
You can right-click the project and select “Set as Active Project” to switch to another project.

Copy Paste

It is now possible to copy or link elements fro one project in another project. Beware: You can only copy units (Rhapsody elements that are save in their own file, indicated by the small decorator icon in the left lower corner, grey or red)
Just drag and drop will create a reference, indicated with a (REF) behind the name, holding CTRL during the drag and drop will create a real copy.

Absolute vs Relative

This is where property “1” comes into play. This defines how the paths are stored when you have multiple models in one workspace. When you leave Rhapsody with a workspace open, Rhapsody will ask you if the project-list must be saved.
It will save a file in the directory of the first project. The paths to each one of
the projects will be stored according to the setting of the property “1” in that project.
You can edit the project file by hand, you can even move the project file (Take care that you keep the project paths correctly!) but there is a nicer way to do this: just rght-click on the Folder “Projects” then select “Edit Unit”. There you can edit the name of the file and the location. You should then figure out how you want to store the paths to the model. My Tip: only use absolute if you are absolutely sure that the paths will be the same on all computers of all people involved in the project. Otherwise: use relative!

Unit

A unit is, as mentioned, a Rhapsody model element that is stored in a seperate file. My advice is to keep the default settings (That are good, for a change…) and only take packages, components and the project file as a unit ( project.rpy(x), component.cmp(x) and package.sbs(x), the last two are stored in the project_rpy directory )
Property “2” defines how these paths are stored, here also use relative unless you are absolutely sure you can use absolute.

Conclusion

Bordeaux is fantastic, we had a great weekend and we will definitely return there someday.
Use relative unless absolute will work for you, make sure you have the same setting in all projects!
Using multiple projects in a workspace is perfect if you have divided your model in seperate parts that are included in each other.

Remember: Everything is relative, absolutely!

Keep modeling with Rhapsody! wvdheiden@sodiuswillert.com

Walter.