Uml / sequence / package / … diagram alternative for JavaScript and Electron application? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) The Ask Question Wizard is Live! Data science time! April 2019 and salary with experienceUML for javascript?What's the best UML diagramming tool?How to generate UML diagrams (especially sequence diagrams) from Java code?Generate UML Class Diagram from Java ProjectHow to draw a sequence diagram in a HTML pageHow to represent Javascript object creation with an UML class diagram?UML diagram for interacting state machinesUML design for a nodeJS web applicationAre packages allowed in UML 2.0 class diagrams?UML class diagrams in JavaUsing UML Diagrams as clickable objects
Multi tool use
How are presidential pardons supposed to be used?
Unable to start mainnet node docker container
Autumning in love
Can a zero nonce be safely used with AES-GCM if the key is random and never used again?
Writing Thesis: Copying from published papers
What LEGO pieces have "real-world" functionality?
What was the last x86 CPU that did not have the x87 floating-point unit built in?
Is there a documented rationale why the House Ways and Means chairman can demand tax info?
How is simplicity better than precision and clarity in prose?
I'm thinking of a number
Determine whether f is a function, an injection, a surjection
Who can trigger ship-wide alerts in Star Trek?
Is there folklore associating late breastfeeding with low intelligence and/or gullibility?
Fishing simulator
3 doors, three guards, one stone
Stop battery usage [Ubuntu 18]
Using "nakedly" instead of "with nothing on"
How to rotate it perfectly?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Area of a 2D convex hull
What did Darwin mean by 'squib' here?
Why don't the Weasley twins use magic outside of school if the Trace can only find the location of spells cast?
What items from the Roman-age tech-level could be used to deter all creatures from entering a small area?
What do you call a plan that's an alternative plan in case your initial plan fails?
Uml / sequence / package / … diagram alternative for JavaScript and Electron application?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
The Ask Question Wizard is Live!
Data science time! April 2019 and salary with experienceUML for javascript?What's the best UML diagramming tool?How to generate UML diagrams (especially sequence diagrams) from Java code?Generate UML Class Diagram from Java ProjectHow to draw a sequence diagram in a HTML pageHow to represent Javascript object creation with an UML class diagram?UML diagram for interacting state machinesUML design for a nodeJS web applicationAre packages allowed in UML 2.0 class diagrams?UML class diagrams in JavaUsing UML Diagrams as clickable objects
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
My question is if there are any kind of diagram I could draw in order to visualise and Electron / JavaScript application?
I would need alternative for the different uml diagrams, like class or package diagram but since JS is prototype-based and it's not like Java or C# I don't know what I could do.
The only one I might be able to make is a sequence diagram, but I should (probably must) make other diagrams as well.
javascript electron uml diagram class-diagram
add a comment |
My question is if there are any kind of diagram I could draw in order to visualise and Electron / JavaScript application?
I would need alternative for the different uml diagrams, like class or package diagram but since JS is prototype-based and it's not like Java or C# I don't know what I could do.
The only one I might be able to make is a sequence diagram, but I should (probably must) make other diagrams as well.
javascript electron uml diagram class-diagram
1
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07
add a comment |
My question is if there are any kind of diagram I could draw in order to visualise and Electron / JavaScript application?
I would need alternative for the different uml diagrams, like class or package diagram but since JS is prototype-based and it's not like Java or C# I don't know what I could do.
The only one I might be able to make is a sequence diagram, but I should (probably must) make other diagrams as well.
javascript electron uml diagram class-diagram
My question is if there are any kind of diagram I could draw in order to visualise and Electron / JavaScript application?
I would need alternative for the different uml diagrams, like class or package diagram but since JS is prototype-based and it's not like Java or C# I don't know what I could do.
The only one I might be able to make is a sequence diagram, but I should (probably must) make other diagrams as well.
javascript electron uml diagram class-diagram
javascript electron uml diagram class-diagram
asked Mar 22 at 7:39
ataniiatanii
1407
1407
1
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07
add a comment |
1
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07
1
1
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07
add a comment |
1 Answer
1
active
oldest
votes
First of all, you're not obliged to document everything in UML diagrams at all. Because working software is more important than comprehensive documentation. However, UML can be extremely useful to highlight some less trivial aspects of your software that can not be easily found in the code. And lmy advice would be to focus on these aspects.
Now what you should do in UML all depends on what you intend to represent in your model, and how you're using js.
UML distinguishes structure diagrams to show the static view on your software and behavioural diagrams to show its dynamics.
Structural diagrams
This could be less attractive to you, since JS is prototype-based and offers a great flexibility regarding the typing logic in contrary to the rather static class based view of UML.
Nevertheless, you could still benefit from the concept of classes and use class diagrams in order to show either your design intent (i.e. your mental view on the object categorisation) or the prototype used to instantiate objects (especially
if you design some objects to act essentially as prototype, making them de facto as representatives for classes). Of course, if your JS design is not at all object oriented, it would make no sense to map your program to OO concepts (see here).
Note that the legacy object diagram could make more sense for you, since it allows to explain the relations between objects rather than classes (see also here)
In both cases, you may be especially interest in usage dependencies that help to link the static elements (i.e. objects or classes) to the behavioural intent.
Finally package diagrams could be used for example to show the big picture of your .js
files and their dependencies. It's not in the sense of the traditional java packages, but could also be useful.
Behavioural diagrams
Here, I would pretend that all these diagrams could make sense for you.
The very first that comes to my mind is the sequence diagram. Because it helps to visualise expected interactions between several objects, and these are difficult to find out just by browsing through the code.
In some cases, the state machine diagram could help as well. This makes particular sense if the behaviour depends on some state variable, or if you want to show the full lifecycle of an object.
Finally, you can consider the activity diagram. These are especially useful if you want to show the flow of control or of objects across your system. If you're not familiar with them, and to simplify to the extreme, it's a kind of super-flowchart, but where the arrows not jus represent "next operation" but could also represent objects that are passed between operations.
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55294919%2fuml-sequence-package-diagram-alternative-for-javascript-and-electron-a%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
First of all, you're not obliged to document everything in UML diagrams at all. Because working software is more important than comprehensive documentation. However, UML can be extremely useful to highlight some less trivial aspects of your software that can not be easily found in the code. And lmy advice would be to focus on these aspects.
Now what you should do in UML all depends on what you intend to represent in your model, and how you're using js.
UML distinguishes structure diagrams to show the static view on your software and behavioural diagrams to show its dynamics.
Structural diagrams
This could be less attractive to you, since JS is prototype-based and offers a great flexibility regarding the typing logic in contrary to the rather static class based view of UML.
Nevertheless, you could still benefit from the concept of classes and use class diagrams in order to show either your design intent (i.e. your mental view on the object categorisation) or the prototype used to instantiate objects (especially
if you design some objects to act essentially as prototype, making them de facto as representatives for classes). Of course, if your JS design is not at all object oriented, it would make no sense to map your program to OO concepts (see here).
Note that the legacy object diagram could make more sense for you, since it allows to explain the relations between objects rather than classes (see also here)
In both cases, you may be especially interest in usage dependencies that help to link the static elements (i.e. objects or classes) to the behavioural intent.
Finally package diagrams could be used for example to show the big picture of your .js
files and their dependencies. It's not in the sense of the traditional java packages, but could also be useful.
Behavioural diagrams
Here, I would pretend that all these diagrams could make sense for you.
The very first that comes to my mind is the sequence diagram. Because it helps to visualise expected interactions between several objects, and these are difficult to find out just by browsing through the code.
In some cases, the state machine diagram could help as well. This makes particular sense if the behaviour depends on some state variable, or if you want to show the full lifecycle of an object.
Finally, you can consider the activity diagram. These are especially useful if you want to show the flow of control or of objects across your system. If you're not familiar with them, and to simplify to the extreme, it's a kind of super-flowchart, but where the arrows not jus represent "next operation" but could also represent objects that are passed between operations.
add a comment |
First of all, you're not obliged to document everything in UML diagrams at all. Because working software is more important than comprehensive documentation. However, UML can be extremely useful to highlight some less trivial aspects of your software that can not be easily found in the code. And lmy advice would be to focus on these aspects.
Now what you should do in UML all depends on what you intend to represent in your model, and how you're using js.
UML distinguishes structure diagrams to show the static view on your software and behavioural diagrams to show its dynamics.
Structural diagrams
This could be less attractive to you, since JS is prototype-based and offers a great flexibility regarding the typing logic in contrary to the rather static class based view of UML.
Nevertheless, you could still benefit from the concept of classes and use class diagrams in order to show either your design intent (i.e. your mental view on the object categorisation) or the prototype used to instantiate objects (especially
if you design some objects to act essentially as prototype, making them de facto as representatives for classes). Of course, if your JS design is not at all object oriented, it would make no sense to map your program to OO concepts (see here).
Note that the legacy object diagram could make more sense for you, since it allows to explain the relations between objects rather than classes (see also here)
In both cases, you may be especially interest in usage dependencies that help to link the static elements (i.e. objects or classes) to the behavioural intent.
Finally package diagrams could be used for example to show the big picture of your .js
files and their dependencies. It's not in the sense of the traditional java packages, but could also be useful.
Behavioural diagrams
Here, I would pretend that all these diagrams could make sense for you.
The very first that comes to my mind is the sequence diagram. Because it helps to visualise expected interactions between several objects, and these are difficult to find out just by browsing through the code.
In some cases, the state machine diagram could help as well. This makes particular sense if the behaviour depends on some state variable, or if you want to show the full lifecycle of an object.
Finally, you can consider the activity diagram. These are especially useful if you want to show the flow of control or of objects across your system. If you're not familiar with them, and to simplify to the extreme, it's a kind of super-flowchart, but where the arrows not jus represent "next operation" but could also represent objects that are passed between operations.
add a comment |
First of all, you're not obliged to document everything in UML diagrams at all. Because working software is more important than comprehensive documentation. However, UML can be extremely useful to highlight some less trivial aspects of your software that can not be easily found in the code. And lmy advice would be to focus on these aspects.
Now what you should do in UML all depends on what you intend to represent in your model, and how you're using js.
UML distinguishes structure diagrams to show the static view on your software and behavioural diagrams to show its dynamics.
Structural diagrams
This could be less attractive to you, since JS is prototype-based and offers a great flexibility regarding the typing logic in contrary to the rather static class based view of UML.
Nevertheless, you could still benefit from the concept of classes and use class diagrams in order to show either your design intent (i.e. your mental view on the object categorisation) or the prototype used to instantiate objects (especially
if you design some objects to act essentially as prototype, making them de facto as representatives for classes). Of course, if your JS design is not at all object oriented, it would make no sense to map your program to OO concepts (see here).
Note that the legacy object diagram could make more sense for you, since it allows to explain the relations between objects rather than classes (see also here)
In both cases, you may be especially interest in usage dependencies that help to link the static elements (i.e. objects or classes) to the behavioural intent.
Finally package diagrams could be used for example to show the big picture of your .js
files and their dependencies. It's not in the sense of the traditional java packages, but could also be useful.
Behavioural diagrams
Here, I would pretend that all these diagrams could make sense for you.
The very first that comes to my mind is the sequence diagram. Because it helps to visualise expected interactions between several objects, and these are difficult to find out just by browsing through the code.
In some cases, the state machine diagram could help as well. This makes particular sense if the behaviour depends on some state variable, or if you want to show the full lifecycle of an object.
Finally, you can consider the activity diagram. These are especially useful if you want to show the flow of control or of objects across your system. If you're not familiar with them, and to simplify to the extreme, it's a kind of super-flowchart, but where the arrows not jus represent "next operation" but could also represent objects that are passed between operations.
First of all, you're not obliged to document everything in UML diagrams at all. Because working software is more important than comprehensive documentation. However, UML can be extremely useful to highlight some less trivial aspects of your software that can not be easily found in the code. And lmy advice would be to focus on these aspects.
Now what you should do in UML all depends on what you intend to represent in your model, and how you're using js.
UML distinguishes structure diagrams to show the static view on your software and behavioural diagrams to show its dynamics.
Structural diagrams
This could be less attractive to you, since JS is prototype-based and offers a great flexibility regarding the typing logic in contrary to the rather static class based view of UML.
Nevertheless, you could still benefit from the concept of classes and use class diagrams in order to show either your design intent (i.e. your mental view on the object categorisation) or the prototype used to instantiate objects (especially
if you design some objects to act essentially as prototype, making them de facto as representatives for classes). Of course, if your JS design is not at all object oriented, it would make no sense to map your program to OO concepts (see here).
Note that the legacy object diagram could make more sense for you, since it allows to explain the relations between objects rather than classes (see also here)
In both cases, you may be especially interest in usage dependencies that help to link the static elements (i.e. objects or classes) to the behavioural intent.
Finally package diagrams could be used for example to show the big picture of your .js
files and their dependencies. It's not in the sense of the traditional java packages, but could also be useful.
Behavioural diagrams
Here, I would pretend that all these diagrams could make sense for you.
The very first that comes to my mind is the sequence diagram. Because it helps to visualise expected interactions between several objects, and these are difficult to find out just by browsing through the code.
In some cases, the state machine diagram could help as well. This makes particular sense if the behaviour depends on some state variable, or if you want to show the full lifecycle of an object.
Finally, you can consider the activity diagram. These are especially useful if you want to show the flow of control or of objects across your system. If you're not familiar with them, and to simplify to the extreme, it's a kind of super-flowchart, but where the arrows not jus represent "next operation" but could also represent objects that are passed between operations.
answered Mar 23 at 10:44
ChristopheChristophe
42.4k43681
42.4k43681
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55294919%2fuml-sequence-package-diagram-alternative-for-javascript-and-electron-a%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Zfi1mGEee P dWk
1
You can try npmjs.com/package/arkit
– xmojmr
Mar 22 at 7:59
Thank you :) This may be just what I need!
– atanii
Mar 22 at 8:07