1.

Describe the theory and real time applications of Unified Modeling Language
(UML).

Ans-

The Unified Modeling Language (UML)

The Unified Modeling Language (UML) defines the industry-standard notation and semantics
for object-oriented and component-based systems.  First published by theObject Management
Group (OMG) in 1997 it has undergone several revisions, the latest of which is UML 2.0.  The
strengths of the UML include:

 It is well defined
 It continues to evolve (albeit slowly)
 It is well accepted within the IT industry by both practitioners and tool vendors. 

Unfortunately the UML suffers from several challenges:

 The UML is overly complex, defining far more notation than what the average developer
wants or needs.  This problem is being addressed in UML 2.0 through the separation of
core notation from supplementary notation. 
 Enterprise architectural modeling with the UML is not well understood within the IT
community.  This is particularly frustrating because there have been some very good
books written about this topic, including Software Reuse (Jacobson, Griss, and Jonsson
1997), Business Component Factory (Herzum and Sims 2000), and Component-Based Product
Line Engineering With UML (Atkinson et. al. 2002).  In UML 2.0 it is finally recognized
that component diagrams, in addition to deployment diagrams, are architecture-level
artifacts so my hope is that practitioners will start using them as such (Ambler 2003). 
 The UML is not sufficient for business system development.  Figure 1, modified from The
Object Primer 3rd Edition, depicts several different categories of modeling and suggests
potential artifacts for each category.  This diagram is nowhere near complete, but you can see
that there are several critical models that the UML does not yet cover, including user interface
and data/persistence models (see A UML Profile for Data Modeling).  The UML is part of the
 picture but it isn’t the entire picture and IMHO needs to be extended.