Blog

  • Harmony MBE

    Harmony MBE

    Introduction

    Ah, HarmonyMBE, a concept that resonates with the elegant dance of nature’s fundamental forces. And also SysML, the Systems Modeling Language, a fascinating extension of UML specifically designed to tackle the complexities of systems engineering!
    Let me guide you through it as Richard Feynman might explain it, drawing upon the harmony of physics.

    What is HarmonyMBE?

    You see, my friend, in the intricate tapestry of the universe, there are underlying symmetries and patterns that govern the behavior of particles and energy. These symmetries are like the notes in a cosmic melody, forming the foundation of how the universe unfolds.

    HarmonyMBE, or Model-Based Engineering, is like a score sheet for orchestrating the complexities of engineering and design. Just as musical notes come together to create a beautiful composition, HarmonyMBE brings together various aspects of product development, from design to manufacturing, in a harmonious ensemble.

    Imagine observing the stars, galaxies, and planets in the night sky. Their movements are governed by the laws of physics, forming a cosmic ballet. In the same way, HarmonyMBE choreographs the movements of data, information, and processes in engineering and manufacturing, ensuring they align seamlessly.

    Symmetries in physics reveal deep connections between seemingly unrelated phenomena. Similarly, HarmonyMBE fosters a unified approach to design, analysis, and production. It’s like finding a unifying principle that simplifies complex engineering practices.

    Think of equations that describe the forces that shape the universe. HarmonyMBE offers a framework, a set of guidelines and tools, that describe the processes and interactions within the domain of engineering. It’s a language of efficiency and coherence, just as physicists use mathematics to unveil the secrets of nature.

    In physics, discoveries are made by recognizing patterns and relationships. HarmonyMBE enables engineers to recognize patterns in the design process, leading to improved efficiency and innovation. It’s about seeing the bigger picture while paying attention to intricate details, much like physicists study both the cosmos and the particles that make it up.

    Remember, my curious companion, HarmonyMBE is not just a tool – it’s a philosophy. It’s about embracing the interconnectedness of engineering endeavors, just as physicists embrace the interconnectedness of physical laws. It empowers us to create a symphony of design and production, where every note contributes to the brilliance of the whole.

    So, my friend, venture forth into the realm of HarmonyMBE, and let the symphony of engineering and design unfold with grace and precision, much like the symphony of the cosmos.

    What is SysML?

    You see, my friend, systems are like the grand symphonies of engineering. They are composed of interconnected elements that harmonize together to perform a specific function, just like the harmonious dance of particles and forces in the cosmos.

    SysML is like a conductor’s baton, a tool that allows engineers to orchestrate the diverse elements of a system in a clear and coherent manner. It builds upon the concepts of UML, much like modern physics builds upon classical physics, to address the intricate interactions and dependencies within systems.

    The language offers a set of specialized diagrams, akin to musical notations, that help engineers visualize the complex relationships between the components of a system. Just as a musical score conveys the melody, rhythm, and harmony of a piece, SysML diagrams express the structure, behavior, and interactions of the system elements.

    Imagine you’re observing the universe, trying to understand the celestial ballet of stars, planets, and galaxies. Similarly, SysML assists engineers in observing and comprehending the intricate dance of system elements – how they communicate, exchange information, and coordinate their actions to achieve a common goal.

    Sequence diagrams in SysML, for instance, reveal the dynamic interactions between different parts of the system over time, much like astronomers study the movements of celestial bodies over vast cosmic epochs.

    Just as physicists use mathematical equations to describe the laws of the universe, SysML offers a formal language for engineers to specify system requirements, constraints, and behaviors. It’s like a universal code that allows engineers from different disciplines to communicate and collaborate seamlessly, just as physicists worldwide converse using the language of mathematics.

    Remember, my curious friend, SysML is not a mere recipe book; it’s a guide to orchestrate your engineering symphony. It encourages creativity, innovation, and the pursuit of elegance in design, just as physicists seek the elegant equations that unlock the secrets of the cosmos.

    So, embrace SysML as your partner in unraveling the mysteries of complex systems, and let your engineering symphony resonate with brilliance and beauty. Now, go forth and compose your magnum opus of systems engineering!

    I hope this explains some of it. Happy Systems Modeling (preferably with Rhapsody)

    Walter van der Heiden walter@sodiuswillert.com

  • History of Harmony

    History of Harmony

    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.