How to translate SDL signal list to something similar in SysML?












0















This is not so much a programming question as it is a question about modelling. But you could argue that modelling is an integral part of programming.



In SDL it is possible to annotate "communication lines" between blocks (processes, services) with signal list. This is very convenient for developers because it informs them about which types of signals (messages in my case) a block either sends or accepts. (see also wikipedia on SDL and communication between blocks)



I can't find a similar notion in SysML. Either I've to introduce a new class for each signal and use a class (interface) to represent a list, or I need to define an interface class with methods, each representing a signal?



I was a bit surprised it is so difficult to find, because in the development of SysML, the ITU (i.e. the original makers of SDL) purportedly were a stakeholder in the definition of SysML.



I'm looking not for "something that works", but for a readily and widely accepted (say, canonical) way of defining signal lists for SysML blocks.



Anyhow, anyone any idea?



Thanks!



BTW: a suggestions for redirects to more appropriate SO sites is welcome.










share|improve this question



























    0















    This is not so much a programming question as it is a question about modelling. But you could argue that modelling is an integral part of programming.



    In SDL it is possible to annotate "communication lines" between blocks (processes, services) with signal list. This is very convenient for developers because it informs them about which types of signals (messages in my case) a block either sends or accepts. (see also wikipedia on SDL and communication between blocks)



    I can't find a similar notion in SysML. Either I've to introduce a new class for each signal and use a class (interface) to represent a list, or I need to define an interface class with methods, each representing a signal?



    I was a bit surprised it is so difficult to find, because in the development of SysML, the ITU (i.e. the original makers of SDL) purportedly were a stakeholder in the definition of SysML.



    I'm looking not for "something that works", but for a readily and widely accepted (say, canonical) way of defining signal lists for SysML blocks.



    Anyhow, anyone any idea?



    Thanks!



    BTW: a suggestions for redirects to more appropriate SO sites is welcome.










    share|improve this question

























      0












      0








      0








      This is not so much a programming question as it is a question about modelling. But you could argue that modelling is an integral part of programming.



      In SDL it is possible to annotate "communication lines" between blocks (processes, services) with signal list. This is very convenient for developers because it informs them about which types of signals (messages in my case) a block either sends or accepts. (see also wikipedia on SDL and communication between blocks)



      I can't find a similar notion in SysML. Either I've to introduce a new class for each signal and use a class (interface) to represent a list, or I need to define an interface class with methods, each representing a signal?



      I was a bit surprised it is so difficult to find, because in the development of SysML, the ITU (i.e. the original makers of SDL) purportedly were a stakeholder in the definition of SysML.



      I'm looking not for "something that works", but for a readily and widely accepted (say, canonical) way of defining signal lists for SysML blocks.



      Anyhow, anyone any idea?



      Thanks!



      BTW: a suggestions for redirects to more appropriate SO sites is welcome.










      share|improve this question














      This is not so much a programming question as it is a question about modelling. But you could argue that modelling is an integral part of programming.



      In SDL it is possible to annotate "communication lines" between blocks (processes, services) with signal list. This is very convenient for developers because it informs them about which types of signals (messages in my case) a block either sends or accepts. (see also wikipedia on SDL and communication between blocks)



      I can't find a similar notion in SysML. Either I've to introduce a new class for each signal and use a class (interface) to represent a list, or I need to define an interface class with methods, each representing a signal?



      I was a bit surprised it is so difficult to find, because in the development of SysML, the ITU (i.e. the original makers of SDL) purportedly were a stakeholder in the definition of SysML.



      I'm looking not for "something that works", but for a readily and widely accepted (say, canonical) way of defining signal lists for SysML blocks.



      Anyhow, anyone any idea?



      Thanks!



      BTW: a suggestions for redirects to more appropriate SO sites is welcome.







      sysml






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 '18 at 3:48









      nanitousnanitous

      375412




      375412
























          1 Answer
          1






          active

          oldest

          votes


















          0














          In SysML block element is consists of various compartments, one of such compartments is signal compartment where both input and output signals can be defined.



          In a case where you need to define a concrete subset of signals for a purpose of concrete communication case, you need to define an interface block and a corresponding port (proxy or not) that includes input and output signal that supposed to appear when a communication is occurred via the channel that block represents.



          In general, if you want to simplify a model and if you can afford such a simplification, an interface and a port could be omitted, then the whole block element can be treated as a "port" with an "interface" defined by its compartments. Such blocks then can be connected directly on IBD in a way to transmit only a subset of signals.



          I would like to recommend A Practical Guide to SysML, The Systems Modeling Language – Sanford Friedenthal, Alan Moore, Rick Steiner books as a massive source of practical explanations and examples of modeling approaches in a scope of SysML applications.






          share|improve this answer

























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385941%2fhow-to-translate-sdl-signal-list-to-something-similar-in-sysml%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            In SysML block element is consists of various compartments, one of such compartments is signal compartment where both input and output signals can be defined.



            In a case where you need to define a concrete subset of signals for a purpose of concrete communication case, you need to define an interface block and a corresponding port (proxy or not) that includes input and output signal that supposed to appear when a communication is occurred via the channel that block represents.



            In general, if you want to simplify a model and if you can afford such a simplification, an interface and a port could be omitted, then the whole block element can be treated as a "port" with an "interface" defined by its compartments. Such blocks then can be connected directly on IBD in a way to transmit only a subset of signals.



            I would like to recommend A Practical Guide to SysML, The Systems Modeling Language – Sanford Friedenthal, Alan Moore, Rick Steiner books as a massive source of practical explanations and examples of modeling approaches in a scope of SysML applications.






            share|improve this answer






























              0














              In SysML block element is consists of various compartments, one of such compartments is signal compartment where both input and output signals can be defined.



              In a case where you need to define a concrete subset of signals for a purpose of concrete communication case, you need to define an interface block and a corresponding port (proxy or not) that includes input and output signal that supposed to appear when a communication is occurred via the channel that block represents.



              In general, if you want to simplify a model and if you can afford such a simplification, an interface and a port could be omitted, then the whole block element can be treated as a "port" with an "interface" defined by its compartments. Such blocks then can be connected directly on IBD in a way to transmit only a subset of signals.



              I would like to recommend A Practical Guide to SysML, The Systems Modeling Language – Sanford Friedenthal, Alan Moore, Rick Steiner books as a massive source of practical explanations and examples of modeling approaches in a scope of SysML applications.






              share|improve this answer




























                0












                0








                0







                In SysML block element is consists of various compartments, one of such compartments is signal compartment where both input and output signals can be defined.



                In a case where you need to define a concrete subset of signals for a purpose of concrete communication case, you need to define an interface block and a corresponding port (proxy or not) that includes input and output signal that supposed to appear when a communication is occurred via the channel that block represents.



                In general, if you want to simplify a model and if you can afford such a simplification, an interface and a port could be omitted, then the whole block element can be treated as a "port" with an "interface" defined by its compartments. Such blocks then can be connected directly on IBD in a way to transmit only a subset of signals.



                I would like to recommend A Practical Guide to SysML, The Systems Modeling Language – Sanford Friedenthal, Alan Moore, Rick Steiner books as a massive source of practical explanations and examples of modeling approaches in a scope of SysML applications.






                share|improve this answer















                In SysML block element is consists of various compartments, one of such compartments is signal compartment where both input and output signals can be defined.



                In a case where you need to define a concrete subset of signals for a purpose of concrete communication case, you need to define an interface block and a corresponding port (proxy or not) that includes input and output signal that supposed to appear when a communication is occurred via the channel that block represents.



                In general, if you want to simplify a model and if you can afford such a simplification, an interface and a port could be omitted, then the whole block element can be treated as a "port" with an "interface" defined by its compartments. Such blocks then can be connected directly on IBD in a way to transmit only a subset of signals.



                I would like to recommend A Practical Guide to SysML, The Systems Modeling Language – Sanford Friedenthal, Alan Moore, Rick Steiner books as a massive source of practical explanations and examples of modeling approaches in a scope of SysML applications.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 31 at 7:23

























                answered Jan 31 at 7:17









                mastedmasted

                1,0412714




                1,0412714
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385941%2fhow-to-translate-sdl-signal-list-to-something-similar-in-sysml%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Tangent Lines Diagram Along Smooth Curve

                    Yusuf al-Mu'taman ibn Hud

                    Zucchini