I try to research every pages about UML. There none of impact about UML.. anyone have this experienced before? what i mean is the standard of terminology and diagramming itself.. and the reason why uml so important for the success of the object oriented...
views:
143answers:
4
+1
A:
Object orientation was in fact pretty succesful long before UML came along. However, it is convenient that a lot of programmers have been exposed to a common language - it makes it easier to communicate ideas. Before UML, one used to have pre-design meetings to explain the notatition to one's teams (I had to do this when using Jacobson's Objectory method prior to UML), nowadays you can assume (possibly wrongly, I admit) that they will have some familiarity with what you are talking about.
anon
2009-07-22 07:28:41
In practice I find that people's knowledge of UML is flaky, and generally limited to basics (and even then people often get it wrong). There's also that curious notion that _any_ object diagram is "UML" - I've met quite a few people who seem to be convinced that is the case - and, for example, thing that VS class designer produces UML output. All in all, I'd say that the impact is pretty low even for what you describe.
Pavel Minaev
2009-07-22 07:46:40
A:
The book "Agile Software Development, Principles, Patterns, and Practices" goes through many of the components of the UML diagrams and describe their use in designing an OO architecture. For some of the diagrams, the author's suggestions boiled down to "keep it simple". Use case diagrams, for example, is shafted in favor for just written use cases. An alternative for complex state diagrams is offered in the form of a state transition table.
At the beginning of the book, the author describes several principles for OO design, such as the dependency inversion principle and the single responsibility. Those have nothing to do with UML. UML is a communication tool which purpose is to allow one to visualise the architecture. Different components of UML has a different purpose- class diagrams for the architecture, object diagrams how objects interact with each other, sequence diagrams for interaction with objects (and itself) over time.
So is UML responsible for the success of OO design? I think UML coming along shows that OO design is worthwhile because UML is to used to present OO design. Same way with that Jackson diagram was used for structural programming.
Extrakun
2009-07-22 07:34:08
+2
A:
Before UML, each methodologist with a book to sell would invent their own notation. Some had triangles one way up for inheritance, some the other.
After UML, each methodologist with a book to sell invents a new type of UML diagram and gets it added to the standard.
soru
2009-07-22 08:17:46