In this thesis we will examine a telecom industry case, where combining synchronous and asynchronous interfaces causes problems. A solution to the problem is being presented in form of an interface controller framework that is based on patterns of common functionality of interface controllers. The solution is implemented using four different implementation methods (Java, Erlang, XDE, Executable UML), and compared in lines of code, performance and throughput. / I rapporten undersöks ett fall i telekominudstrin, där kombinerandet av synkrona och asynkrona interface orsakar problem. En lösning på problemet är presenterat i form av ett framework för interface controllers som är baserat på mönster som beskriver den gemensamma funktionaliten i interface controllers. Lösningen är implementerad med hjälp av fyra olika implementeringsmetoder (Java, Erlang, XDE och Executable UML), där rader kod och prestanda jämförs. / pt00cbj@student.bth.se pt00psa@student.bth.se

One of the main notational contexts in which model-driven software development has been studied is the Unified Modeling Language (UML), the de facto standard in software modelling. The current trend in software development is not just towards the use of models, but the use of executable models. In 2006, the Object Management Group issued a Request for Proposal (RFP), soliciting the definition of an Executable UML Foundation, with a fully specified executable semantics. The purpose of such a version of UML is to make the advantages of executable models available to UML users by enabling "a chain of tools that support the construction, verification, translation, and execution" of models. An oft-voiced criticism of UML is its lack of a formal, unambiguous description of its semantics. In an effort to improve the support for model-driven development, especially with respect to executable modelling, the UML 2 specification introduced a novel three-layer semantics architecture. This architecture provides a stratification of the description of UML models that clearly separates 'low-level' behavioural specification mechanisms, such as actions, from 'high-level' behavioural formalisms, such as activities, state machines and interactions. Although UML describes the effect of actions, it does not provide either the concrete syntax or the formal semantics of an action language. Our research focuses on a top-to-bottom slice of the three-layer architecture. We formally define the execution semantics of two-thirds of UML actions, including the most complicated actions---invocation actions. Our formal definition is expressed in terms of state changes to a global state machine representing an executing UML model. Our work provides an alternate formalization to that of the current submission to the RFP and could be used to enhance that submission. To validate our formal semantics and to determine the usefulness of the three-layer architecture, we have created an interpreter for UML actions and activities. This interpreter was designed in accordance with the complex token passing semantics of UML and provides analysis capabilities that have been successfully used to identify problems even in published activity diagrams. In effect, we have created a tool that supports the construction, verification and execution of a subset of UML models, namely activities. Our handling of this slice of the three-layer architecture is a preliminary step to realizing the grander vision of general executable (and analyzable) models. / Thesis (Ph.D, Computing) -- Queen's University, 2009-01-12 20:16:47.738

One of the inevitable negative effects of software evolution is design erosion. Refactoring is a technique that aims at counteracting this phenomenon by successively improving the design of software without changing its observable behaviour. Design erosion occurs also in the context of executable UML models, i.e. models that are detailed enough to be automatically compiled to executable applications. This thesis presents results of a study on applying refactoring to the area of maintenance of executable UML models. It contains an overview of recent approaches to UML model refactoring and to executable modelling, followed by identification of refactoring areas in models built in Telelogic TAU, a state-of-the art UML CASE tool. It proposes a systematic approach to specification of both executable UML model refactorings as well as associated bad smells in models. Additionally, it shows how refactorings can be implemented in Telelogic TAU.

The Master's thesis presents specification, analyze and design phase of software development. The most stress is putted on Model Driven Development. It contains brief description of almost all UML 2.0 diagrams (use case diagram, class diagram, sequence diagram, activity diagram, state chart, component diagram and deployment diagram). Those principles have been extended to executable UML which can be used for model-driven software architecture. The design of such architecture is one of the current projects of Faculty of Information Technology, BUT. The part of that project is statechart simulator. The thesis discusses whole design of state chart simulator system step by step. It starts with specification, walk thought use case diagram and class diagram to collaboration diagram. In the last chapter, we mention the biggest implementation problems and specificities of Squeak Smalltalk programming language. Finally, it considers possibilities for extension and it evaluates results.