In the context of Enterprise Architecture (EA) modeling, the lack of alignment between the computational models constitutes an organizational problem.The root cause of this problem is the low traceability capacity and the lack of synchronization between the computational models present in the EA.Among the negative impacts related to this problem are, for example, the obsolescence of the models and the difficulty of carrying out analyzes of impacts and decision making in scenarios of organizational changes.Thus, in order to provide the alignment, understanding and adaptation of the corporate environment, from the institutional strategic level to the operational level of Information Technology (TI), focusing on the information systems, an approach is proposed to enable the traceability and synchronization between the computational models.The proposed approach in this paper consists of a: (i) meta-model set comprising the strategic, tactical and operational levels of the EA; (ii) traceability model that supports configuration and change management, through the use of COBIT and ITIL best practices; (iii) transformation process of models that, through the application of the Model Driven Development (MDD), aims to provide the synchronization between the elements of the different models present in an EA.

Transformations are key artifacts in the MDD (Model Driven Development) approach: a software development project can be defined through a transformation chain converting source models into target models until code, enabling development process automation.Transformations can be complex and demand software processes, languages and techniques to improve their development in order to increase reuse, portability, correctness, and so on.In this context we propose a framework to develop model transformations using MDD.This paper presents a Model Transformation Profile (MTP) defined as the domain specific language of the framework.

Software engineering makes extensive use of models to provide a better understanding of artifacts produced during system development.Models are specified in modeling languages such as UML or using Domain Specific Languages.In this paradigm of development, metamodeling is essential because it is usually used to specify the abstract syntax of these languages.However, the design of metamodels is not a trivial task, it requires expertise in specific domains, language definition and abstraction capabilities.This paper provides a guide for metamodel design towards a metamodel development methodology based on some lessons learned from metamodel design experiences.

Collaborative Systems can be constructed through Software Product Line (SPL) with the support of the Model-Driven Development (MDD) approach. However, models generated as SPL artifacts usually present only feature classification. Such models neither express the purpose of each SPL artifact of the systems composition nor the way they were associated with the collaboration elements. Therefore, to support the analysis and design of collaborative systems it is relevant to classify artifacts with the support of a collaborative model. This paper describes a way a collaboration model can be used to construct a UML profile. This profile is applied to MDD models that represent collaboration artifacts, enhancing the classification, location and reuse of artifacts in order to support the development of Collaborative Systems.

Middleware infrastructure has been widely adopted to support the development and execution of collaborative systems. With these systems many challenges arise, those related to interoperability gained remarkable importance. This work aims to increase the semantic interoperability support in an infrastructure named Web-based Groupware Service-Oriented Architecture (WGWSOA) that uses middleware services to support the development and execution of collaborative systems. Services were built on this infrastructure to extend the interoperability semantic support. Evidences pointing to the validity of the proposed solution, to support the development and execution of collaborative systems, were produced through an experimental study.

The Web-based Groupware Service-Oriented Architecture (WGWSOA) is an infrastructure that uses middleware services to support collaborative system development. In addition, it aims to support the issue of semantic interoperability conflict resolution for middleware services in the construction of collaborative systems in heterogeneous environments. Interoperability is an essential requirement for service implementation that supports developments in these environments and as a result, this is an important factor for the interaction of user groups in collaborative systems. In this context, the goal of this paper is to describe a solution to widen semantic interoperability support in an infrastructure whose goal is to support collaborative system development and execution.

With the increasing communication demand among distributed collaborative applications, software developers are facing new challenges related to semantic interoperability issues. This article aims to present a solution based on a mediation service and ontology in order to support interoperability across specific middleware services. These services are part of a middleware infrastructure which was designed to support groupware development. To illustrate our proposal, we discuss some problems usually found when distributed groupware applications interoperation is required. Furthermore, we focus our evaluation on a mediation approach to support the interoperability in a middleware infrastructure.

Fulfilling composability and reusability requirements is one of the main challenges of service-oriented software engineering. This paper describes research which applies a MDA based-process to support the development of specific middleware services in WGWSOA infrastrucuture. This process aims to comply with EDOC and RM-ODP profiles in order to guide specific services development of an architecture based on middleware services for collaborative applications. We also evaluate if the process deployment could enhance composability and reusability requirements.

This paper aims to present an awareness service, named Aw2SOA, which was developed in order to support distributed groupware design in WGWSOA environment. It is a middleware specific service which was implemented according to SOA principles and aspect-oriented concepts. In groupware literature, service-oriented approach is suggested aiming to solve reuse and evolution requirements. However, awareness support is fulfilled by similar functionalities implemented in different modules. As a result, activities related to the maintenance and evolution of this matter cannot be considered as easy tasks. WGWSOA (Web- based Groupware Service-Oriented Architecture) is based on middleware services for collaborative applications.

Collaborative Systems are applications that demand for the distribution support of their resources. Usually, middle-wares have been deployed as a development platform for such applications. In spite of manipulating objects (documents, meetings, agenda, discussion list, etc.) with same semantics, it is not possible for an application to access both objects and data of another distinguishable application, even though they have been built by the use of the same middleware platform. The complexity of this scenario becomes larger when we idealize a project that demand for the interoperability of groupware applications developed by the use of distinct middlewares. The goal of this paper is to present an architecture based on middleware services -named WGWSOA (Web-based Groupware Service Oriented Architecture) -for Collaborative Systems. From this architecture, we hope to offer specific services in order to leverage the interoperability concerns of such systems.

Groups that work on cooperative applications frequently construct and provide documents. Although these environments manipulate the same kind of artifact (a document), they are not usually interoperable due to the implementation of different policies, protocols or infrastructure. Therefore, it is hard for users to use different collaborative systems to work on a single shared document and share several necessary information for the accomplishment of a collaborative authoring process that the involved tools offer separately. Towards such an interoperation, we propose the InterDOC (environment for supporting interoperability of collaborative document authoring tools) reference architecture and environment. Using InterDOC, a group of authors can write a document in their favorite environment and can then make this document available via InterDOC to another group of authors using another environment, or even a single user application. We use OMG MDA in order to obtain platform-independent reference architecture.