Introduction to UML

CASE tools known as Computer-aided software engineering tools is a kind of component-based development which allows its users to develop information systems. The main goal of case technology is the automation of the entire information systems development life cycle process using a set of integrated software tools
However the products we get from case tools are only a skeleton of the final product required and a lot of programming must be done by hand to get a fully finished, good product.

  • The Unified Modeling Language  is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct, and document the artifacts of a software-intensive system.
  • The UML is appropriate for modeling systems ranging from enterprise information systems to distributed Web-based applications and even to hard real time embedded systems. It is a very expressive language, addressing all the views needed to develop and then deploy such systems.
    The UML is a language for
·         Visualizing
·         Specifying
·         Constructing
·         Documenting
·  Visualizing:
  The UML is more than just a bunch of graphical symbols. Rather, behind each symbol in the UML notation is a well-defined semantics. In this manner, one developer can write a model in the UML, and another developer, or even another tool, can interpret that model unambiguously
·  Specifying:
   means building models that are precise, unambiguous, and complete.
·  Constructing:
  the UML is not a visual programming language, but its models  can be directly connected to a variety of programming languages
·  Documenting:
   a healthy software organization produces all sorts of artifacts in addition to raw executable code. These artifacts include
o   Requirements
o   Architecture
o   Design
o   Source code
o   Project plans
o   Tests
o   Prototypes
o   Releases
To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements:
1.      Things
2.      Relationships
3.      Diagrams

No comments:

Post a Comment