designumlweb-development
UML has a jungle of Diagrams.
Profile Diagrams, Class Diagrams, Package Diagrams…
However, (IMH-and-not-too-experienced-O) I quite see that doing each and every diagram is overkill.
Therefore, which UML Diagrams are more suitable in a web context, more expecificly a blog (we want to build it from scratchs).
I understand that just because I used UML Diagrams does not imply that our code would be great and brilliant… but, it certainly would be better than just unplanified code…
The most important insight about how thread executions happen can be depicted by what is known as sequence diagram. Here is an example from wikipedia
This diagram essentially draws the list of events along with a direction over a vertical single line often called lifeline. In this case, each thread is an owner of it's own life line. The diagram allow representation all types of events such as synchronous, asynchronous etc.
The other most important thing in such systems is the state-charts or state-diagrams. Usually, this applies only if the model is represented as a state machine. However, in most multi threaded systems (where threads are non-trivial) it is best that they are designed to function with isolated algorithms for different states.
There are other diagram types like interaction diagram and communication diagram but i think trying to draw sequence diagram and state diagrams will put maximum clarity.
First thing you have to do is to decide about the semantics of your UML packages. UML does not define any clear semantics, you have to define one that suits your needs.
For example, a package could be a layer in your software (i.e. model layer, view layer, controller layer), so if that is the semantics you pick, this will obviously fit to MVC. I guess that is not the semantics you have in mind, otherwise you would not see any problem here.
A different possible semantics is a namespace, a component, a library, the deployment packaging, or whatever things you want to group together. This is a different point of view, and may or may not conform to the MVC view. If this it doesn't, you may consider making two diagrams, one showing the MVC view and one showing your specific package view.
Best Answer
As a general guideline:
Some diagram types (e.g. timing diagram) have rather specialized uses, others tend towards a level of detail where actual code does a better job (e.g. sequence diagrams), and others yet seem to be intended for gigantic projects but have questionable utility even there (package diagrams? Any IDE can show you your packages).