Diagrams in UML notation

UML dia­grams and the way they are used, since the very begin­ning of this nota­tion, have aroused emo­tions and waves of con­flict­ing com­ments. The reas­on for this is the high level of abstrac­tion of the ana­lys­is stage and mod­el­ling as a dis­cip­line, and the fairly wide­spread mis­un­der­stand­ing of the essence of this nota­tion. This is com­poun­ded by the huge dif­fer­ence between what we call ana­lys­is and object-ori­ented design (OOAD) and object-ori­ented pro­gram­ming lan­guages (OOP).UML nota­tion is mis­takenly treated by many people as just anoth­er set of sym­bols for cre­at­ing illus­tra­tions. Most developers I know feel that these dia­grams do noth­ing to help them, and they are gen­er­ally right, because the qual­ity and con­tent of much of the doc­u­ment­a­tion pro­duced with UML, is poor, and such doc­u­ment­a­tion is actu­ally use­less to the soft­ware vendor.

Source: Dia­gramy w not­acji UML – Jarosław Żeliński IT-Consulting

Leave a Reply

Your email address will not be published. Required fields are marked *