The thing is since the unveiling of UML in the middle part of the 1990s, we've seen its application in the development of certain visual models for a variety of languages. While everyone knows that the most significant application by far is for object-oriented development in C++ and Java, there really is nothing in UML that says there's a need for the implementation in an OO language. Well in fact, if we look at history, a major factor for the creation of UML was the Ada language, which by the way isn't really completely OO.
By definition, UML is quite domain-independent and is also platform-agnostic. Anyway, it does have an extension mechanism called "profiles," the purpose of which is to support definitions of constraints and attributes of a target environment. Furthermore, the usual UML profile will be offering for the specification of "standard elements" beyond what is specified by the specific subset of the UML meta-model. "Standard element" for its part is actually a term utilized in the meta-model specification, describing a standard instance of a UML stereotype, which can tagged as either value or constraint.
The Link Between UML and PL/SQL
It is possible to contemplate on the development of PL/SQL specific UML models by using elements solely from the identified subset of the UML meta-model. But the visual development of PL/SQL is going to be facilitated through the application of a umlcode specific profile. The profile will then be designed to serve three general purposes. There are two primary elements that are intended to be the basis for UML development - Class and Interface. Because the two elements we just mentioned aren't found in PL/SQL, it is advantageous to define a group of stereotypes that are described to specialize on these base element and those that define the PL/SQL language.
A lot of PL/SQL constructs will be implementing a subset of the "expressibility" being allowed by UML. Additionally, UML allows using of name-values pairs or sometimes called as tagged values, which then can be utilized for the definition of specializations that are categorized outside normal class definitions. Tagged values for their part are used to define modifiers and conditions which may be specific to a targeted language. Defining of a profile for PL/SQL will integrate the definition of the set of all tagged values which may apply for PLSQL to UML.
Know that when the UML profile is specifically designed for a target language, any use of that profile will be limited to the design and construction segments of the development process. The intention is to retain as much of the concept of language independence of UML as possible. A good example of this is that using a UML profile for a language isn't really advised or recommended for a system or analysis model. Read http://edition.cnn.com/TECH/ for the latest tech news.
By definition, UML is quite domain-independent and is also platform-agnostic. Anyway, it does have an extension mechanism called "profiles," the purpose of which is to support definitions of constraints and attributes of a target environment. Furthermore, the usual UML profile will be offering for the specification of "standard elements" beyond what is specified by the specific subset of the UML meta-model. "Standard element" for its part is actually a term utilized in the meta-model specification, describing a standard instance of a UML stereotype, which can tagged as either value or constraint.
The Link Between UML and PL/SQL
It is possible to contemplate on the development of PL/SQL specific UML models by using elements solely from the identified subset of the UML meta-model. But the visual development of PL/SQL is going to be facilitated through the application of a umlcode specific profile. The profile will then be designed to serve three general purposes. There are two primary elements that are intended to be the basis for UML development - Class and Interface. Because the two elements we just mentioned aren't found in PL/SQL, it is advantageous to define a group of stereotypes that are described to specialize on these base element and those that define the PL/SQL language.
A lot of PL/SQL constructs will be implementing a subset of the "expressibility" being allowed by UML. Additionally, UML allows using of name-values pairs or sometimes called as tagged values, which then can be utilized for the definition of specializations that are categorized outside normal class definitions. Tagged values for their part are used to define modifiers and conditions which may be specific to a targeted language. Defining of a profile for PL/SQL will integrate the definition of the set of all tagged values which may apply for PLSQL to UML.
Know that when the UML profile is specifically designed for a target language, any use of that profile will be limited to the design and construction segments of the development process. The intention is to retain as much of the concept of language independence of UML as possible. A good example of this is that using a UML profile for a language isn't really advised or recommended for a system or analysis model. Read http://edition.cnn.com/TECH/ for the latest tech news.