A software design is often modelled as a collection of UML diagrams. There is an inherent need to preserve their consistency, since these diagrams are subject to continuous changes due to successive refinements or evolutions. Contemporary UML tools provide unsatisfactory support for maintaining the consistency between different versions of UML diagrams. To solve this problem, an extension of th...

Software engineering uses UML diagrams as a standard technique for specification and development of software. Various UML diagrams are used for specification of different aspects of the application. Their interpretation, extension, revision and integration becomes awful difficult if developers use the full freedom of UML, apply their own semantics and do not agree an common parts. We propose an...

3.1 UML Language Architecture.............................................................................8 3.1.1 BASIC BUILDING BLOCKS OF UML ........................................................................9 3.1.2 RELATIONSHIPS...................................................................................................10 3.1.3 DIAGRAMS ...............................................

In this article we describe an approach towards increasing the robustness of the UML refinement machinery. The aim of this work is not to formalize the UML notation itself, but to substantiate a number of intuitions about the nature of possible refinement relations in UML, and even to discover particular refinement structures that designers do not perceive as refinements in UML.

Groupware is explicitly designed to support the cooperation among group members. The implementation of cooperation-aware groupware is supported by several object-oriented toolkits and frameworks, but there is no uni®ed way to model applications built on top of these. We have proposed UML-G as an extensible UML pro®le for modeling groupware and are in the process of turning it into a community e...

Due to its rich set of modeling concepts and its broad application spectrum the Unified Modeling Language (UML) has become widely accepted for modeling many aspects of software systems. Since UML is not related to any particular design method, each software development project has to establish its own modeling guidelines. Hence, tool support is needed for guiding the developer throughout the mo...

The Business Process Execution Language for Web Services (BPEL4WS) provides an XML notation and semantics for specifying business process behaviour based on Web Services. A BPEL4WS process is defined in terms of its interactions with partners. A partner may provide services to the process, require services from the process, or participate in a two-way interaction with the process. The Unified M...

Many UML CASE tools allow software engineers to draw diagrams and generate code skeletons from them. But often advanced users want to do more with their UML models, e.g., apply speci c design patterns, generate code for embedded systems, simulate the functional and non-functional behavior of the system, run validation tools on the model, etc. which are very di cult to do with the scripting faci...

The Unified Modeling Language (UML) has become the de facto standard for systems development and has been promoted as a technology that will help solve some of the longstanding problems in the software industry. However, there is still little empirical evidence supporting the claim that UML is an effective approach to modeling software systems. Indeed, there is much anecdotal evidence suggestin...

Different types of consistency of UML models have been described in the literature. The consistency of UML models with the UML static semantics, usually referred as wellformedness, and the consistency between different versions of the same model are among the most cited. The UML models’ well-formedness is a precondition for any other kind of consistency, being described by means of the UML abst...