Search results

This study aims to explore the alignment between strategic plans of the Portuguese public higher education institutions (HEIs) and their perception of the integration of sustainability in education and curricula.

The strategic plans from 15 institutions were selected for content analysis; data about the integration of sustainability in education and curricula, from these HEI, were collected with an online questionnaire (self-report survey). Qualitative and quantitative analyses were performed.

Strategic plans of the Portuguese public HEIs seem to not be sufficiently aligned with self-assessment integration of sustainability in education and curricula.

The classifications used in the content analysis were constructed and revised by the authors to reduce coder interpretation issues and subsequent bias in the results. However, some subjectivity could remain. The analysis of strategic plans and self-report surveys answered by top management, or a technician, does not assess the practices and sustainability implementation in education and curricula.

This study allows the self-report of already-implemented practices to be compared to the planned strategy of HEI governance in Portugal as stated in their strategic plans.

An analysis and respective insights on the lack of connection between strategic planning and self-report practices about sustainability implementation, using Portugal as a case study.

The web service choreography description language (WS‐CDL) is a specification for describing multi‐party collaboration based on web services from a global point‐of‐view. WS‐CDL is designed to be used in conjunction with the web services business process execution language (WS‐BPEL or BPEL). As WS‐CDL is a new choreography language, there has been doubt about the feasibility of a transformation to BPEL. This article aims to show how BPEL process definitions of parties involved in a choreography can be derived from the global WS‐CDL model and what the limitations of such a derivation are.

The authors implemented a prototype of the mappings as a proof of concept.

The automatic transformation leverages the quality of software components interacting in the choreography as advocated in the model driven architecture (MDA) concept. The mapping reveals that some information has to be added manually to the generated BPEL, in particular, choice conditions and private activities.

A comprehensive evaluation of WS‐CDL with respect to the interaction patterns is still missing. As a resolution to this issue, the authors propose the modelling of choreographies by the help of a more abstract language – in the sense of being more independent of underlying technology – like UML 2.0 Activity Diagrams.

The automation of the mapping offers substantial speed‐up of the engineering process. Additionally, the automatic generation of BPEL stubs minimizes the risk of inconsistent process implementations by the parties.

The core contribution is to show how BPEL process definitions for parties involved in a choreography can be derived from a global WS‐CDL model.

The purpose of this paper is to provide a feature‐based characterization of version control systems (VCSs), providing an overview about the state‐of‐the‐art of versioning systems dedicated to modeling artifacts.

Based on a literature study of existing approaches, a description of the features of versioning systems is established. Special focus is set on three‐way merging which is an integral component of optimistic versioning. This characterization is employed on current model versioning systems, which allows the derivation of challenges in this research area.

The results of the evaluation show that several challenges need to be addressed in future developments of VCSs and merging tools in order to allow the parallel development of model artifacts.

Making model‐driven engineering (MDE) a success requires supporting the parallel development of model artifacts as is done nowadays for text‐based artifacts. Therefore, model versioning capabilities are a must for leveraging MDE in practice.

The paper gives a comprehensive overview of collaboration features of VCSs for software engineering artifacts in general, discusses the state‐of‐the‐art of systems for model artifacts, and finally, lists urgent challenges, which have to be considered in future model versioning system for realizing MDE in practice.

This paper aims to present a case study of the application of a methodology that represents an innovative strategy that integrates researches on interaction design and business process management with practical implications. This methodology is devoted to aligning the needs of enterprise system users with business processes (BPs).

This approach establishes an unbroken network of links between BPs, task models and abstract representations of user interfaces. Once the models are linked, it is possible to identify the impact that any change on these models may produce in other models. The main challenge is to organize the linked models according to the organizational context and manage those links with consistency in order to support improving process efficiency and user productivity. This approach has been applied in a large telecommunications organization during four months with its application in two different projects and validated with a cost‐benefit analysis.

Applying this approach in large organizations has demonstrated that: every involved stakeholder is capable of understanding the whole approach in one working day; creating the models and linking them with the corresponding business process models takes around three men/day per core business process; and applying this approach brings up to 60 per cent of return on investment related to process improvement and user experience.

The main differentials of this methodology include using simple models; considering light actions; preserving the independence of technology; and adopting a human‐oriented approach assuring that every managed information impacts people and not only systems, thus enabling fast adaptation to the business dynamism.

The purpose of the paper is to present a service design (SD)-based methodology developed to help small and medium enterprises (SMEs) undertake organisational change.

This research used the design science research methodology, which enabled the creation of the Service Design for Organisational Change (SD4OCh) methodology. A real case study of a small service company specialised in neuropsychological disorders was used for the definition and validation of SD4OCh.

The main outcome of this study is the SD4OCh methodology, which is based on three key stages: diagnosis (knowing where to begin by detecting the organisation's strengths and weaknesses), innovation (improving the structure/processes and designing/redesigning services by employing a customer-centric approach), and implementation (enabling the definition of the route towards organisational change). There is also a transversal evaluation stage, which quantifies the organisational changes.

This study adds valuable knowledge to the service science research field and contributes to the awareness of the usefulness of SD theory within companies, especially those which are small and medium-sized, since those companies lack the tools and methods required to tackle organisational change, signifying that the challenges the companies confront are different to those of larger companies.

Although this is a SD-based research, the SD4OCh methodology was developed in order to enable companies to make holistic changes, namely, to innovate their services, structure, and processes, thus supporting and guiding organisational change.

The definition of modeling languages is a key‐prerequisite for model‐driven engineering. In this respect, Domain‐Specific Modeling Languages (DSMLs) defined from scratch in terms of metamodels and the extension of Unified Modeling Language (UML) by profiles are the proposed options. For interoperability reasons, however, the need arises to bridge modeling languages originally defined as DSMLs to UML. Therefore, the paper aims to propose a semi‐automatic approach for bridging DSMLs and UML by employing model‐driven techniques.

The paper discusses problems of the ad hoc integration of DSMLs and UML and from this discussion a systematic and semi‐automatic integration approach consisting of two phases is derived. In the first phase, the correspondences between the modeling concepts of the DSML and UML are defined manually. In the second phase, these correspondences are used for automatically producing UML profiles to represent the domain‐specific modeling concepts in UML and model transformations for transforming DSML models to UML models and vice versa. The paper presents the ideas within a case study for bridging ComputerAssociate's DSML of the AllFusion Gen CASE tool with IBM's Rational Software Modeler for UML.

The ad hoc definition of UML profiles and model transformations for achieving interoperability is typically a tedious and error‐prone task. By employing a semi‐automatic approach one gains several advantages. First, the integrator only has to deal with the correspondences between the DSML and UML on a conceptual level. Second, all repetitive integration tasks are automated by using model transformations. Third, well‐defined guidelines support the systematic and comprehensible integration.

The paper focuses on the integrating direction DSMLs to UML, but not on how to derive a DSML defined in terms of a metamodel from a UML profile.

Although, DSMLs defined as metamodels and UML profiles are frequently applied in practice, only few attempts have been made to provide interoperability between these two worlds. The contribution of this paper is to integrate the so far competing worlds of DSMLs and UML by proposing a semi‐automatic approach, which allows exchanging models between these two worlds without loss of information.

This paper aims to present how iterative round‐trip modelling between two different business process modelling tools can be enabled on a conceptual level. Iterative round‐trip modelling addresses model transformations between high‐level business and executable process models, and how to maintain these transformations in change time. Currently, the development of these process models is supported by different tools. To the authors' best knowledge, no coherent collaborative tool environment exists that supports iterative round‐trip modelling.

This paper is primarily based on a literature review of state‐of‐the‐art business to IT transformations regarding business process modelling. The architecture of integrated information systems (ARIS) and Cordys tools are used as an example case in this research. ARIS is a business process analysis (BPA) tool suited for analyzing and designing business processes, while the execution and monitoring of these processes is allowed by Cordys, a business process management suite (BPMS). The theory is used for transforming between ARIS event‐driven process chains from the business perspective and business process modelling notation in Cordys from the IT perspective.

A conceptual framework is proposed to couple a BPA and BPMS tool for round‐trip business process modelling. The framework utilizes concepts from the model‐driven architecture for structurally addressing interoperability and model transformations. Ensuring iterative development with two tools requires traceability of model transformations.

In many organizations, BPA and BPMS tools are used for business process modelling. These are in practice often two different worlds, while they concern around the same business processes. Maintaining multiple versions of the same process models across two tools is a considerable task, as they often are subject to design changes. Interoperability between a BPA and BPMS tool will minimize redundant activities, and reduce business to IT deployment time.

This research provides a theoretical base for coupling a BPA and BPMS tool regarding iterative round‐trip modelling. It provides an overview of the current state‐of‐the‐art literature of business process modelling transformations, and what is necessary for maintaining interoperability between tools. The findings indicate what is expected in tool support for iterative development in business process modelling from analysis and design to execution.

Managing components' resources plays a critical role in the success of systems' architectures designed for cyber–physical systems (CPS). Performing the selection of candidate components to pursue a specific application's needs also involves identifying the relationships among architectural components, the network and the physical process, as the system characteristics and properties are related.

Using a Model-Driven Engineering (MDE) approach is a valuable asset therefore. Within this context, the authors present the so-called Systems Architecture Ontology (SAO), which allows the representation of a system architecture (SA), as well as the relationships, characteristics and properties of a CPS application.

SAO uses a common vocabulary inspired by the Architecture Analysis and Design Language (AADL) standard. To demonstrate SAO's applicability, this paper presents its use as an MDE approach combined with ontology-based modeling through the Ontology Web Language (OWL). From OWL models based on SAO, the authors propose a model transformation tool to extract data related to architectural modeling in AADL code, allowing the creation of a components' library and a property set model. Besides saving design time by automatically generating many lines of code, such code is less error-prone, that is, without inconsistencies.

To illustrate the proposal, the authors present a case study in the aerospace domain with the application of SAO and its transformation tool. As result, a library containing 74 components and a related set of properties are automatically generated to support architectural design and evaluation.

Many features constitute an adaptive system such as user model, interface specification, business functionalities and service implementation. Context awareness is an important facet of service oriented application creation dealing with the gathering, use and representation of context information. Generally, user interfaces and services communities work separately on the adaptation process and do not converge. The aim of this work is to manage the system’s functionalities and the user interface that delivers data to the relevant consumer early since the design phase until the code generation.

The authors discuss how a unified method based on a model-driven architecture for adaptive user interface and pervasive service creation eases the work of designers and developers, limits incompatibility issues and supports dynamic generation of systems adapted to different contexts of use.

The proposed approach is able to support a semi-automatic ubiquitous application generation with service, behavior, presentation and content adaptation.

In this paper, the authors tackle context-awareness at two levels: system functionalities and user interface generation. The authors also tackle adaptation at the specification and implementation levels.

Enterprise systems (ESs) are hard to maintain, since they embed a large fraction of organisational data and tasks, which are often intertwined and highly interdependent. The purpose of this paper is to propose a methodology for enterprise resource planning (ERP) post-implementation change management to support business analysts during perfective maintenance.

The methodology draws a parallel line with engineering change management and considers the steps of mapping the dependencies among ES components, understanding the ripple effects of change, and defining metrics to quantify and assess the impact of change. The methodology is instantiated in the case of ERP systems, for which a tool has also been implemented and evaluated by ERP implementation experts.

Experts positively evaluated the proposed methodology. General design principles to instantiate the methodology in the case of systems other than ERP have been derived.

While existing ESs change management methodologies help to identify the need for change, the proposed methodology help to structure the change process, supporting the task of perfective maintenance in an efficient way.