Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

The suitability of PRINCE2 for engineering infrastructure

The view that PRINCE2 was not suitable for application to infrastructure was identified in a study done for a separate purpose, namely, to examine project governance and methodology, which is not reported in this paper. It was asserted by several participants in interviews conducted with a sample of experienced practitioners across a range of industries and disciplines. This paper follows up on those comments by conducting an examination of PRINCE2 from an engineering infrastructure perspective to investigate the validity of this assertion. It takes a deductive, definitional approach to determine if there are any features in it that would cause difficulty for engineering infrastructure use. Seventeen features were examined, and 15 were found to have difficulty in application to the project management of engineering infrastructure. The remaining two found inconsistencies that were unlikely to cause too much difficulty. The features causing difficulty include non-generic terminology for the terms project, lifecycle and stage, using a product rather than a project-based process, use of an iterative product delivery process unsuited to predictive projects, use of a delivery process for all project phases, assumption of a board governance model with inappropriate accountabilities, lack of clarity around the use of the project plan, and absence of a lifecycle appropriate for engineering infrastructure, with PRINCE2 effectively self-declaring its need for a higher-level project lifecycle/ methodology from somewhere else. The paper concludes that PRINCE2 is quite poorly suited to managing engineering infrastructure projects and identifies that some of the reasons for this are likely to also cause difficulty for many ICT projects as well

The suitability of MSP for engineering infrastructure

This paper arose from empirical investigations of practitioner views of both governance and program definitions together with investigations of practitioner reference documents. These investigations indicated that some confusion had arisen in infrastructure project management as a result of approaches used in IT. This paper contributes to the literature evaluating project standards and methodologies by conducting an examination of the suitability of one such source (MSP) for use in engineering infrastructure program management. A deductive definitional approach is taken to identify features that could cause difficulty. Eight features were examined, and six were found to have difficulty in application to engineering infrastructure. The remaining two were found to be terminology differences that are unlikely to cause too much difficulty. The features causing difficulty include an inappropriate definition of a program, use of a non-generic process flow unsuitable for rolling programs, confusion of transformation projects with programs, the presumption of a board governance model, and confusion of large projects with programs. The paper concludes that MSP is quite poorly suited to managing rolling programs, whether they are in engineering infrastructure or IT. Various changes to MSP and PMI publications are recommended

A model for digital preservation repository risk relationships

The paper introduces the Preserved Object and Repository Risk Ontology (PORRO), a model that relates preservation functionality with associated risks and opportunities for their mitigation. Building on work undertaken in a range of EU and UK funded research projects (including the Digital Curation Centre , DigitalPreservationEurope and DELOS ), this ontology illustrates relationships between fundamental digital library goals and their parameters; associated rights and responsibilities; practical activities and resources involved in their accomplishment; and risks facing digital libraries and their collections. Its purpose is to facilitate a comprehensive understanding of risk causality and to illustrate opportunities for mitigation and avoidance. The ontology reflects evidence accumulated from a series of institutional audits and evaluations, including a specific subset of digital libraries in the DELOS project which led to the definition of a digital library preservation risk profile. Its applicability is intended to be widespread, and its coverage expected to evolve to reflect developments within the community. Attendees will gain an understanding of the model and learn how they can utilize this online resource to inform their own risk management activities

From internet architecture research to standards

Many Internet architectural research initiatives have been undertaken over last twenty years. None of them actually reached their intended goal: the evolution of the Internet architecture is still driven by its protocols not by genuine architectural evolutions. As this approach becomes the main limiting factor of Internet growth and application deployment, this paper proposes an alternative research path starting from the root causes (the progressive depletion of the design principles of the Internet) and motivates the need for a common architectural foundation. For this purpose, it proposes a practical methodology to incubate architectural research results as part of the standardization process

The role of use cases in development of a reference framework for interoperability of data exchange in agriculture

vokKVIKA

Grid simulation services for the medical community

The first part of this paper presents a selection of medical simulation applications, including image reconstruction, near real-time registration for neuro-surgery, enhanced dose distribution calculation for radio-therapy, inhaled drug delivery prediction, plastic surgery planning and cardio-vascular system simulation. The latter two topics are discussed in some detail. In the second part, we show how such services can be made available to the clinical practitioner using Grid technology. We discuss the developments and experience made during the EU project GEMSS, which provides reliable, efficient, secure and lawful medical Grid services

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version