Pondering on the Key Functionality of Model Driven Development Tools: The Case of Mendix

As the significant success of business enterprises, information system development becomes IT managers' concern to keep the balance between business and information system. The information system has an important role to deliver advantages to the business enterprises. To keep maintain these issues, information system should be developed to innovate the business process. However, in developing an information system, the information system process improvement may obtain the possibility of information system development failures. Therefore, to avoid the failures in implementing information systems there are some important factors. Those factors are called critical success factors (CSF). Therefore, this study observes the critical success factors (CSF) in information system development (ISD) projects. This systematic literature review discusses critical success factors in information system development. The method section determines the research question. It also describes how to collect and filter the data. The order of this research written is according to Preferred Reporting Items for Systematic Review and Meta-Analyses Checklist or also known as PRISMA Checklist. Therefore, to collect and filter the data, this systematic literature review uses Preferred Reporting Items for Systematic Review and Meta-Analyses method or also known as PRISMA method. There were 20 papers selected to help this research based on the filtering papers due to PRISMA flow diagram. Most of those papers are discussing information system development and the rest are about factors of information system development. The result section has two parts, which are study characteristics and study results. This systematic literature review concluded that there are five critical success factors in developing information system projects. Those critical success factors are people, project, organization, knowledge, and expertise. Those critical success factors are also supported by several items of each factor. Therefore, the output of this research is expected to satisfy the information system development projects to meet the organizations' need and reduce also possibly avoid the failures in information system development projects.

Model-Driven Development (MDD) is becoming increasingly popular as a choice for developing information systems. Tools that support the principles of MDD are also growing in number and variety of available functionality. MetaEdit+ is a meta-modeling tool used for developing Domain Specific Languages and is identified as an MDD tool. The Eclipse Modeling Framework (EMF) and Graphical Modeling Project (GMP) are two Eclipse projects that provide plug-ins to support the principles of MDD. In this paper, we report on our experience in using MetaEdit+ and the Eclipse plug-ins for developing a graphical editor for the unifying meta-model, which is an MDD approach that extends the traditional view of MDD to cover Enterprise Modeling. The two modeling environments are reviewed using quality areas that are identified by the research community as necessary in MDD tools. This report will provide useful insights for researchers and practitioners alike concerning the use of MetaEdit+ and the Eclipse plug-ins as MDD tools.

This paper focuses on 18 well-known recommended practices for information system (IS) development projects to assess their relative dissemination and effectiveness and to examine the role of standardization frameworks in promoting them. Findings from a survey of 97 information technology (IT) professionals show that most of these practices tend to be adopted, that they are associated with higher chances of success in IS development projects and that software process improvement models, project management maturity models and formal development methodologies tend to promote such practices. Findings show however some notable exceptions that may require to refine this existing set of recommended practices. Implications for research and practice are discussed.

The iterative and incremental development (IID) approach is widely adopted in information systems development (ISD) projects. While the IID approach has played an important role the management of many ISD projects, some of the key techniques have not received critical appraisal from the academic community. This paper aims to fill the gap and examines three such techniques through a case study. First of all, the gap between the theory of user participation and the reality of user’s lack of real influence on design and development is explored. The author proposes the concept of “participatory capture” to explain the side effect of user participation. Secondly, the assumption that evolutionary prototyping converges to a successful design is questioned. Thirdly, the side effect of the timeboxing technique is considered. The paper suggests that the IID approach represents the learning approach as categorized in Pich et al. (2002) and it might be ineffective in dealing with the significant uncertainties in ISD projects.

This chapter examines the causes of failure in a Web-based information system development project and finds out how complexity can lead a project towards failure. Learning from an Information System Development Project (ISDP) failure plays a key role in the long-term success of any organization desirous of continuous improvement via evaluation and monitoring of its information systems (IS) development efforts. This study reports on a seemingly simple (but only deceptively so) failed ISDP to inform the reader about the various complexities involved in ISDPs in general, and in developing countries in particular. An existing framework from contemporary research is adopted to map the complexities found in the project under study and the critical areas, which lead to the decreased reliability and failure in Web-based information system development, are highlighted.

Though information systems development (ISD) projects use modularization as an approach to better manage complex tasks by decomposing them into simpler intra-project modules, we lack clearly established modalities for managing such modularized ISD projects. Adopting a control theory perspective and leveraging a case study research approach, we unearth the underlying “control mechanisms” that an organization leveraged to manage eight modularized ISD projects. Specifically, we explore the intra-project modular dependencies that the projects’ business requirement documents indicated and use results from semi-structured interviews with project members to identify the corresponding control mechanisms. Our results indicate that, in scenarios with a low level of intra-project modular interdependencies, formal outcome and formal behavior constitute the preferred control mechanisms. However, specific situations related to flexible project practices and volatile client requirements may minimize the level of formal outcome and formal behavior control mechanisms in such projects. A low level of interdependencies between intra-project modules minimizes the need for informal clan control; nonetheless, informal clan-control mechanisms may help team members understand project requirements in a shared manner. Projects with a high level of interdependencies between intra-project modules have a high level of informal clan control. However, in some situations, projects with a high level of intra-project modular interdependencies have a low level of informal clan control often due to time pressures. Organizations may govern projects with a high level of intra-project modular interdependencies and poor structures through an enabling control style. Organizations can effectively govern projects with a low level of intra-project modular interdependencies through authoritative control style except in the projects where they assign team members to multiple projects simultaneously. By leveraging control theory to examine the intra-project modular dependencies, we add to the ongoing discourse on control theory and ISD project governance.

The objective of the information system (IS) development project is to develop and modify systems that satisfy customers' and users' needs on schedule and within a budget. The early activities in information systems development, i.e. the front end of innovation in information systems, are recognized as critical and important steps; poor execution of these activities is an almost certain guarantee for a failure of the final IS product. However, there are many problems related to the early phases of IS development, and therefore this research paper presents a conceptual model for categorizing the problems in the front end of innovation in IS. Based on this conceptual model, we suggest that the activities in the early phases of information system development currently used in organizations do no work in large scale. In the directions for future research we discuss the need for new approaches in the front end of innovation in information systems.

Model Driven Development (MDD) requires proper tools to derive the implementation code from the application models. However, the integration of handwritten and generated code is a long-standing issue that affects the adoption of MDD in the industry. This article presents a model and code co-evolution approach that addresses such a problem a posteriori , using the standard collision detection capabilities of Version Control Systems to support the semi-automatic merge of the two types of code. We assess the proposed approach by contrasting it with the more traditional template-based, forward-engineering process, adopted by most MDD tools.

Enterprises today face many challenges related to lack of interoperability. Enterprise applications and software systems need to be interoperable in order to achieve seamless business across organisational boundaries and thus achieve virtual networked organisations. IEEE defines interoperability as “the ability of two or more systems or components to exchange information and to use the information that has been exchanged”. MDA is the OMG instantiation of an approach to software development kown as Model Driven Engineering (MDE) or Model Driven Development (MDD). MDD focuses on Models as the primary artefacts in the development process, with Transformations as the primary operation on models, used to map information from one model to another. There is presently an important paradigm shift in the field of software engineering that may have important consequences on the way information systems are built and maintained. Model-driven development (MDD), and in particular OMG's Model-Driven Architecture ® (MDA®), is emerging as the state of practice for developing modern enterprise applications and software systems. The MDD paradigm improves the way of addressing and solving interoperability issues compared to earlier non-modelling approaches. However, developing correct and useful models is not an easy task. We believe that there is a need for an interoperability framework that provides guidance on how MDD should be applied to address interoperability. A key to the success of MDD is the development of ontologies supporting the mapping from one model to another, either at the same level of abstraction or at different levels. Various approaches have been proposed and tested, starting from common ontologies, shared by all the models, to local ontologies, specific to each software. We propose here to discuss the applicability of MDD to the urban civil engineering (UCE) field. This should help to establish the requirements for ontologies to be applied for interoperability of systems commonly used in this domain. In the first section of this paper, we briefly introduce some key principles of the MDA approach and the role of ontologies in model transformation approaches. The following section describes the Model Driven Development (MDD) interoperability framework. The last part presents a way of applying the MDA techniques to urban civil engineering projects, with the objective of testing the feasibility and relevancy of the approach to this domain.

:Previous research on the development of information systems has focused on the conflicts among participants and the consequences of satisfactory resolution of those conflicts. In this paper, we test a model of conflict during system development [40, 41 J. As specified, the model proposed relationships among participation, influence, conflict, and conflict resolution. We extend the model to include project success as an outcome variable. A sample of84 participants in 17 system development projects in 3 organmltions was surveyed. Results support the portions of the model reported earlier [41 J, show a strong positive relationship between conflict resolution and project success, and show a modest positive relationship between participation and project success.

Relationship between the interactive use of control systems and the project performance: The moderating effect of uncertainty and equivocality

Information systems development projects are a significant expenditure of time, effort and money for many enterprises. Historically it has been estimated that 50-80% of projects fail to achieve their objectives for a variety of reasons. Researchers have identified numerous factors associated with system development failure. In this paper, we first synthesize the vast research regarding systems development risk factors and provide a framework that illustrates interactions between risk factors. The framework was used to develop an open-ended questionnaire that was answered by an inter-industry group of experienced systems development engineers and project managers. Analysis of their reports indicates that experienced professionals perceive that all risk factors (technical, resource, etc.) ultimately derive from organizationally-oriented factors, to be solved with organizational responses. This holistic viewpoint of risk assessment is counter to that of systems professionals more involved in day-to-day development decision making. For these developers, risks are more likely to be characterized as fitting into traditional discrete categories. This apparent dichotomy of risk importance was further investigated through an intra-organizational study which directly assessed how professionals recognize and treat risks in the development process. Results illustrate that a successful project environment may be characterised as one in which all systems professionals maintain a holistic view of organizational risk and that organizational culture, as opposed to experience, may predicate such an environment. Implications and future research directions are discussed.

Developing multi-purpose Human Language Technologies (HLT) pipelines and integrating them into the large scale software environments is a complex software engineering task. One needs to orchestrate a variety of new and legacy Natural Language Processing components, language models, linguistic and encyclopedic knowledge resources. This requires working with a variety of different APIs, data formats and knowledge models. In this paper, we propose to employ the Model Driven Development (MDD) approach to software engineering, which provides rich structural and behavioral modeling capabilities and solid software support for model transformation and code generation. These benefits help to increase development productivity and quality of HLT assets. We show how MDD techniques and tools facilitate working with different data formats, adapting to new languages and domains, managing UIMA type systems, and accessing the external knowledge bases.

User and developer common knowledge: Effect on the success of information system development projects

Companies need to rethink business processes, infrastructures, technologies, staff, etc. according to new demands, strategic goals, and changes in their environment. Information System evolution has been supported by the reengineering process. Since the models are now part of an increasing number of engineering processes and model-driven software development is a well-established paradigm to support information systems, the reengineering process could be improved with the incorporation of the model-driven development paradigm. This paper presents a model-driven organisational reengineering framework to support organisational improvement. The main idea is to get the most out of the existing proposals in model-driven development for the reengineering process (reverse engineering, improvement processes, and forward processes). Methods, techniques, model-driven tools, and perspectives for analysing information systems at a high level of abstraction are presented as a part of this proposal. A reference framework for the reengineering process is established to provide a consistent set of concepts that support the proposed framework. An illustrative example is introduced to present the feasibility of the proposal. The example illustrates the SuperStationery Co. case in order to present a reengineering process to align an existing desk application with a web application that fulfils the strategic goals of the company. Finally, we conclude with an analysis and discussion about lessons learned and future works.