UML Diagram

[norfaezah]

I just want to know whether UML Diagram is needed in Web Page?

Thank You.

[Nepomuk]

UML diagrams are used to visualize the connections between objects. As long as you don't use any languages like Java or PHP that use Objects, you won't need UML diagrams. And even if you do use Java or PHP, you don't automatically have to use UML Diagrams, but they do help sometimes.

HTML, JavaScript and CSS do not have objects.

Greetings,
Nepomuk

[gits]

... HTML, JavaScript and CSS do not have objects. ...

they have! objects ... the entire browser and even the documents have objects ... so you have the Browser-Object-Model (BOM) - the window-object, navigator object with attributes and methods - and the Document-Object-Model (DOM) - nodes with attributes and methods ... and for javascript: you could use it very Object-Oriented including inheritance, polymorphism, public, private data etc. ... so to use/need UML for web-based projects, even for the UI-related things ... you should know the requirements and the 'size' of the project. the only thing that you cannot really do is to generate code or skeletons for the script-languages ... but i guess that this will change in the future due to the massive use of AJAX-Frameworks for example. currently we have a codebase of over 400000 loc javascript-code at work and it would be very useful to have UML-diagrams for all that ... so we just started to create them now, to help us to reverse engineer, refactor or just formal describe things that are not well maintainable without documentation ...

kind regards

[Nepomuk]

they have! objects ... the entire browser and even the documents have objects ... so you have the Browser-Object-Model (BOM) - the window-object, navigator object with attributes and methods - and the Document-Object-Model (DOM) - nodes with attributes and methods ... and for javascript: you could use it very Object-Oriented including inheritance, polymorphism, public, private data etc. ... so to use/need UML for web-based projects, even for the UI-related things ... you should know the requirements and the 'size' of the project. the only thing that you cannot really do is to generate code or skeletons for the script-languages ... but i guess that this will change in the future due to the massive use of AJAX-Frameworks for example. currently we have a codebase of over 400000 loc javascript-code at work and it would be very useful to have UML-diagrams for all that ... so we just started to create them now, to help us to reverse engineer, refactor or just formal describe things that are not well maintainable without documentation ...

kind regards

OK, shouldn't have said so without further research... ^^

Greetings,
Nepomuk

[gits]

no problem ... this is just a common sense of webdevelopment ... and it just changed very dynamically over the last 2 years with all that web2.0/ajax-stuff ... that lead from a 'web-site-scripting' to a more real 'web-site-programming' style ... even when i think that this words don't really describe what i mean ... basicly i think i would rather say that there is no real difference anymore when projects exceed a critical size ...

kind regards