Documentation

[Aztek3]

Here is a first version of the uml class diagram for this application (needs still some improvements, contains open questions):

editable file, if needed: klassendiagramm.zip

some questions regarding correct style (might need extra consultation with tutor):

• imported libraries needed for UML? --> No, only classes that we created
• some Objects are created by JS internally, they are always just instances of Object. Is it okay to give them names just for the UML even though that is not entirely accurate?
• usually an entry point of an application is the main() or run() method (I believe), is it ok to pretend the existence of such just for UML?
• stick to exact structure of JS objects (public variables of object) or pretend that there are actual getters/setters and design UML accordingly? --> Indication of getters setters would be preferable, just having a public attribute without explanation in UML is bad practice
• what name is best for the numerical variables? float,double,number...?

[stolsky]

That's my version. I used the JavaScript data types. The JavaScript modules behave like a Singleton class. klassendiagramm v2.zip

[Aztek3]

This was something i came up in the meantime...

Yours is visually definetly more appealing, though. In my opinion the lines from Index.js should be "-->" indicating dependency rather than association

[Aztek3]

Manual to the program Bedienungsanleitung.pdf Bedienungsanleitung.docx

Hope at least, thats ok. If not, let me know so I can improve on that