I never used papyrus, but I just studied it.
The biggest difference that I see is that Papyrus seems to be basically a UML modeling tool. Code generation is a “side component” (the exact term from the penultimate page is a tutorial on the slide on using papyrus for beginners (2010-10-01)) .) Here fooobar.com/questions/660170 / ... ... it sounds complicated . I went through the Papyrus forum and tutorials and did not find anything useful related to code generation.
UML has traditionally been considered technology in the development phase of the Waterfall software development process, so when software is modeled in UML, implementation is a separate process. Not so with QM.
QM, unlike Papyrus, is not a general UML modeling tool; it is for modeling UML state diagrams for the sole purpose of compiling them in a tool for tracking C or C ++ code. As you know, QM is associated with QP, the state framework. QM creates code that uses QP.
QM is your fashion designer and IDE. The final source code that prohibits external libraries is 100% QM generated. When you graphically design your UML state diagrams, you must write C or C ++ code that executes when transitioning to / from your states. When you compile, QM combines your written code with its own generated code to create source files that you can compile immediately without any further changes.