Not a complete Harmony
Contrary to the name there are different versions of Harmony.
- HarmonySE
‘Classic’ method. Uses standard ports by default but can use proxy ports. Use Case models are built as separate Rhapsody models and then merged after the architectural analysis phase back into a single model. - HarmonySWE
‘Classic’ method for Software. Use Case models are built as separate Rhapsody models and then merged after the architectural analysis phase back into a single model. - Harmony aMBSE
Uses proxy ports. Use case models are built as separate packages in the same Rhapsody model. Merging of use cases is performed in the same model which can lead to conflicts.
Further info and detailed guidebooks for both can be found here:
https://www.ibm.com/docs/en/rhapsody/9.0.1?topic=secsyscontroller-harmony-process - HarmonyMBE (tbd)
Work in progress. Based on the previous two iterations, HarmonyMBE aims to simplify the workflows and reduce the need for merging or consolidation whist still allowing parallel development.
Why
Well… it started in the I-Logix days there was Harmony-SE (Systems Engineering) by Peter Hoffmann and Harmony-SWE (Software Engineering) by Bruce Powel Douglass.
After Telelogic took over I-Logix, the work on both continued and newer versions were released. When IBM took over and Peter Hoffmann left, it was time to create a new version. Which was picked up by Bruce Powel Douglass and Andy Lapping.
Lots of helpers were created to help users to apply Harmony as easy as possible.
The last version of Harmony is now Harmony MBE, made by Andy Lapping. Work on that is still in progress.