The Graphical User Interface (GUI), as the most prevailing type of User Interface (UI) in today’s interactive applications, restricts the interaction with a computer to the visual modality and is therefore not suited for some users (e.g., with limited literacy or typing skills), in some circumstances (e.g., while moving around, with their hands or eyes busy) or when the environment is constrained (e.g., the keyboard and the mouse are not available). In order to go beyond the GUI constraints, the Multimodal (MM) UIs apear as paradigm that provide users with great expressive power, naturalness and flexibility. In this thesis we argue that developing MM UIs combining graphical and vocal modalities is an activity that could benefit from the application of a methodology which is composed of: a set of models, a method manipulating these models and the tools implementing the method. Therefore, we define a design space-based method that is supported by model-to-model colored transformations in order to obtain MM UIs of information systems. The design space is composed of explicitly defined design options that clarify the development process in a structured way in order to require less design effort. The feasability of the methodology is demonstrated through three case studies with different levels of complexity and coverage. In addition, an empirical study is conducted with end-users in order to measure the relative usability level provided by different design decisions.

Researchers in software engineering proposed design method for distributed applications to construct a set of communicating system components from a global behavior. The joint behaviors of these components must precisely satisfy the specified global behavior. The next concern is to transform the constructed models of these components into executable business processes by ensuring the exchange of asynchronous messages among the generated business processes. The introduction of Service-Oriented Architecture (SOA) has helped to achieve this goal. SOA provides high flexibility in composing loosely-integrated services that can be used among business domains to carry out business transactions; this composition is known as service orchestration. Moreover, SOA supports Model Driven Architecture (MDA) such that services modeled as UML Activity Diagrams (AD) can be transformed into a set of Business Execution Language (BPEL) processes. Many researchers discussed the transformation of UML AD and the Business Process Modeling Notation (BPMN) into BPEL. However, they did not discuss the practical limitations that some of these transformations impose. This thesis addresses the imitations of the transformation from UML AD to BPEL processes using the IBM Rational Software Architect (RSA). We showed here that the tool is unable to create the correct BPEL artifacts from UML AD components in certain cases, for instance when the behavior includes the alternative for receiving single or concurrent messages, a weak loop, or certain choice activities. Furthermore, we provided novel solutions to the transformations in these cases in order to facilitate the transformation from UML AD to BPEL.

Researchers in software engineering proposed design method for distributed applications to construct a set of communicating system components from a global behavior. The joint behaviors of these components must precisely satisfy the specified global behavior. The next concern is to transform the constructed models of these components into executable business processes by ensuring the exchange of asynchronous messages among the generated business processes. The introduction of Service-Oriented Architecture (SOA) has helped to achieve this goal. SOA provides high flexibility in composing loosely-integrated services that can be used among business domains to carry out business transactions; this composition is known as service orchestration. Moreover, SOA supports Model Driven Architecture (MDA) such that services modeled as UML Activity Diagrams (AD) can be transformed into a set of Business Execution Language (BPEL) processes. Many researchers discussed the transformation of UML AD and the Business Process Modeling Notation (BPMN) into BPEL. However, they did not discuss the practical limitations that some of these transformations impose. This thesis addresses the imitations of the transformation from UML AD to BPEL processes using the IBM Rational Software Architect (RSA). We showed here that the tool is unable to create the correct BPEL artifacts from UML AD components in certain cases, for instance when the behavior includes the alternative for receiving single or concurrent messages, a weak loop, or certain choice activities. Furthermore, we provided novel solutions to the transformations in these cases in order to facilitate the transformation from UML AD to BPEL.

Identical domain concepts reified in different (meta)modelling projects may be named, represented and connected differently. It turns out that a transformation defined for a particular metamodel cannot be directly used for another metamodel; that is, the reuse of transformations is restricted. To tackle this problem, in this dissertation, we propose a solution for automatically migrating legacy transformations. Such a transformation is adapted to the new metamodel that has a slightly different representation in comparison with the original one, while preserving the original semantics of the transformation. To this end, we first introduce MetaModMap, a Domain Specific Language that allows the description of the correspondences of intended semantics between the elements of two metamodels that model the same domain. Then we provide a rewriting mechanism using these user-defined correspondences to migrate the transformation automatically. The proposed solution uses a graph-based model typing relation that enables safe adaptations. Our approach has been prototyped with MOMENT2 and can be used with any framework based on the same graph transformation paradigm.

Software evolution refers to continuous change that a software system endures from inception to retirement. Each change must be efficiently and tractably propagated across models representing the system at different levels of abstraction. Model synchronization activities needed to support the systematic specification and analysis of evolution activities are still not adequately identified and formally defined. In our research, we first introduce a formal notation for the representation of domain models and model instances to form the theoretical basis for the proposed model synchronization framework. Besides conforming to a generic MOF metamodel, we consider that each software model also relates to an application domain context (e.g., operating systems, web services). Therefore, we are addressing the problems of model synchronization by focusing on domain-specific contexts. Secondly, we identify and formally define model dependencies that are needed to trace and propagate changes across system models at different levels of abstraction, such as from design to source code. The approach for extraction of these dependencies is based on Formal Concept Analysis (FCA) algorithms. We further model identified dependencies using Unified Modeling Language (UML) profiles and constraints, and utilize the extracted dependency relations in the context of coarse-grained model synchronization. Thirdly, we introduce modeling semantics that allow for more complex profile-based dependencies using Triple Graph Grammar (TGG) rules with corresponding Object Constraint Language (OCL) constraints. The TGG semantics provide for fine-grained model synchronization, and enable compliance with the Query/View/Transformation (QVT) standards. The introduced framework is assessed on a large, industrial case study of the IBM Commerce system. The dependency extraction framework is applied to repositories of business process models and related source code. The extracted dependencies were evaluated by IBM developers, and the corresponding precision and recall values calculated with results that match the scope and goals of the research. The grammar-based model synchronization and dependency modelling using profiles has also been applied to the IBM Commerce system, and evaluated by the developers and architects involved in development of the system. The results of this experiment have been found to be valuable by stakeholders, and a patent codifying the results has been filed by the IBM organization and has been granted. Finally, the results of this experiment have been formalized as TGG rules, and used in the context of fine-grained model synchronization.

Object-oriented analysis and design approach has become the mainstream of today¡¦s systems development technique. The Timing Diagram and State Machine Diagram from the Unified Modeling Language (UML) are becoming the major tools for modeling the platform independent model (PIM) of an embedded system. Once these two diagrams are constructed, the results can then be transformed into its platform specific model and template code based on the model driven architecture (MDA) approach. However, the detailed guideline for the transformation from Timing Diagram and State Machine Diagram to the template code is lacking. Therefore, this study presents a methodology which provides guidelines for the transformation from State Machine Diagram and Timing Diagram to template code for the embedded system. The research methodology is articulated using the design science research methodology. A usability evaluation with a real-world embedded system case is performed to demonstrate its applicability. The results indicated that with this proposed method, the system developer can effectively transform the PIM of an embedded system into its template code.

Automotive embedded systems used much in the main body control system. Also because the system needs to meet functional requirement, environment requirement, timing requirement, interface requirement and Failure Mode and Effects Analysis (FMEA) so it is necessary to have an automotive embedded systems modeling methodology. Therefore, this study proposes an automotive embedded systems modeling methodology which combines MDA and UML, and detailed description of the model diagram used by each modeling phase and the diagram modeling method and steps. System development team can be clearly implemented in accordance with the methods and steps for automotive embedded system modeling. The methodology also can be used as the communication standard of the system development team. Systems modeling during system modular can promote module reuse rate in order to enhance the efficiency of system development. The methodology of this study is based on design science research methods, usability evaluation of the modeling methodology is implemented for the modeling of demand for Parking aid control unit, the PIM modeling and code conversion. With prove the availability of this modeling methodology. From the results of the assessment system development team can be based on the methodology of modeling methods and procedures to express the results in line with the needs and systems analysis and design of automotive embedded systems and convert the system operating platform and code.

Today, modeling the software with unified modeling language (UML), model driven architecture (MDA) concept, and computer-aided software engineering (CASE) tool are the main trend for the objected-oriented systems analysis and design. Furthermore, to enhance the degree of transformation automation and design reuse in the system development process, object constraint language (OCL) is used in UML modeling to specify the navigation, constraint, operation specification, and so forth. However, the guideline for using OCL in class diagram specification and its transformation to JAVA code is lacking. This research presents an approach utilizing the OCL to specify the constraint and operation specification for the class diagram when modeling the platform independent model (PIM), which can then be transformed into the JAVA platform specific model (PSM) and code using a CASE tool. A real-world case using the integrated techniques is presented and a CASE tool is used to illustrate the concepts, application, and the advantages of using the proposed approach. With this approach, the system developer can transform PIM into PSM and code automatically and thereby enhance the efficiency of system development.

This study presents a systematic methodology which integrated the model driven architecture with object-oriented technique to transform the user interface (UI) platform independent model (PIM) into Web-based UI platform specific model (PSM), and then into code model. A real-world case using the integrated techniques is presented and the Rational Rose is used to illustrate the concepts, application, and the advantages of using the proposed methodology. With this approach, the system developer can transform UI PIM into Web-based UI PSM and code automatically and thereby enhance the efficiency of system development.

Today, unified modeling language (UML) has become a standard modeling language in object-oriented systems analysis and design. Over the past few years a considerable effort has been made in synthesizing UML, MDA (model driven architecture), design patterns and CASE tool to increase the productivity of the system development. Specifying the design patterns with object constraint language (OCL) has become a main trend in this area. This study classifies the OCL expressions and design patterns and presents a method to specify each design pattern with the OCL and UML when modeling the platform independent model which can then be transformed into the platform dependent model, and to a code model. A real-world case using the integrated techniques is presented and a CASE tool is used to illustrate the concepts, application, and the advantages of using the proposed approach. With this approach, the system developer can transform PIM into code automatically and thereby enhance the efficiency and reusability of system development.