You are on page 1of 2

Name the advantage of UML .Explain why it is an advantage.

Advantages of UML:
UML is a most useful method of visualization and documenting software systems
design.UML uses object oriented design concepts and it is independent of specific
programming language. Unified Modeling Language is a popular technique for
documenting and modeling system .the UML uses set of symbols to represent graphically
the various components and relation ships with in the system and UML can be used for
business processing modeling and requirements modeling ,it mainly is used to support
object oriented system analysis and to develop the object models. Real time UML, this
method is the application of UML to design of real-time system. It represents the system
with structural and behavioral language models and those designing modeling include the
architectural mechanical and detailed design .Object oriented methodologies have
employed in the construction of the real time system.
Example:

Name a disadvantage of using UML .Explain why it is a


disadvantage.
Disadvantages of UML:

Still no specification for modeling of user interfaces.

Business rule specification a group exists for this within the OMG, so we should
see something in UML

Poor for distributed systems no way to formally specify serialization and object
persistence.

Example no way to specify that an object resides on a server process and shared
among instances of a running process.

UMLs main strength seems to be in its support for the development process. This seems
to be of limited interest to SoftFMEA where networks are concerned, but might it be
more valuable when considering software based components? If our interest is confined
to a systems logical architecture and behaviour we might only use the state and
interaction diagrams, where there are plenty of alternatives. UMLs usefulness seems
therefore to depend on whether it fits in well with an existing development process.
Its main weakness, from our point of view, is its lack of formality. Clearly to build an
executable model we need a formal language. Therefore we can presumably only use
UML if we underpin it with some formal semantics, such as those provided by a
proprietary tool, or possibly SDL. This leaves the question of why we would want to do
this. There are two possible reasons. One is that UML is used in a development process
and we wish to use it for our stage of this process for consistency and to avoid the user
translating work into a new language. The other related reason is simply that if users are
familiar with UML it might be worth keeping it, as a front end to a formal language.

You might also like