Business and logic charateristic in an collaborative situation

MISE 2.0 (for Mediation Information System Engineering, second iteration) project has been launched in 2009. The MISE 2.0 engineering approach is based on BPM (Business Process Management) and MDE (Model-Driven Engineering). Running a regular BPM approach on a specific organization consists in gathering structural, informational, and functional knowledge in order to design cartography of processes covering the behavior of the modeled organization. Regarding the MISE 2.0 project the BPM approach concerns a set of organizations and MDE helps in automatizing the different steps: i) Knowledge gathering (situation layer): collect information concerning the collaborative situation, ii) Processes cartography design (solution layer): design the processes according to the knowledge gathered and iii) MIS deployment (implementation layer): implement an IT structure able to run the processes cartography. Both the transitions between these layers are the hard-points of this approach: The first gap is managed at the abstract level of MISE 2.0 while the second one is managed at the concrete level of MISE 2.0. The current PhD is focused on the first issue: designing a relevant processes cartography from the modeled collaborative situation. However, this is usually a manual activity, which requires a large amount of work to draw the processes and their links. The current research works aim at building such collaborative process cartography in an automated manner. Our principles are (i) to gather the essential and minimum initial collaborative knowledge (e.g. partners, shared functions and collaborative objectives) in models, ii) to deduce the missing knowledge with the help of a collaborative metamodel, an associated ontology and transformation rules and iii) to structure the deduced knowledge in a collaborative process cartography thanks to dedicated algorithms

Caractérisation et logique d'une situation collaborative

Initié en 2009, le projet MISE 2.0 (deuxième itération du projet Mediation Information System Engineering) s’articule autour d’une approche BPM (pour Business Process Management) et d’une vision MDE (pour Model-Driven Engineering). La réalisation d’une démarche BPM classique au sein d’une organisation nécessite de recueillir une connaissance couvrant à la fois les aspects structurel, informationnel et fonctionnel afin de définir des modèles de processus caractéristiques du comportement de l’organisation. Concernant le projet MISE 2.0, l’approche BPM considérée concerne un ensemble d’organisations collaboratives. Quant à la composante MDE, elle est destinée à faciliter l’automatisation des différentes étapes de la démarche : i) Recueil de la connaissance (caractérisation de la situation) : Il s’agit de collecter les information concernant la situation collaborative considérée, ii) Déduction de la cartographie de processus collaboratifs (définition de la solution) : il s’agit de définit les processus collaboratifs adaptés à la situation collaboratives caractérisée au niveau précedent and iii) Déploiement du SI de médiation (implémentation de la solution) : il s’agit d’implémenter le SI de médiation sous la forme d’une plateforme informatique capable d’orchestrer les processus collaboratif définis. La problématique scientifique relève des deux transitions entre ces trois niveaux d’abstractions : la première transition est prise en charge au niveau abstrait de la démarche MISE 2.0 alors que la seconde est traitée au niveau concret. Les travaux de thèse dont il est ici question se focalisent sur le niveau abstrait : déduction d’une cartographie de processus collaboratifs satisfaisant la situation collaborative considérée. Ce type d’objectif relève généralement d’activités entièrement manuelles qui nécessitent une importante quantité de travail afin d’obtenir les modèles de processus escomptés. Les travaux de recherches présentés ambitionnent d’automatiser cette démarche. Le principe est le suivant : (i) recueil, sous la forme de modèles, de la connaissance nécessaire à la caractérisation de la situation collaborative (informations sur les partenaires, les fonctions qu’ils partagent et leurs objectifs), (ii) déduction de la connaissance complémentaire relative à la dynamique collaborative qui pourrait satisfaire ces objectifs selon les moyens disponibles (cette phase s’appuie sur un métamodèle collaboratif, sur l’ontologie associée et sur des règles de transformation) et (iii) structuration de cette connaissance générée sous la forme d’une cartographie de processus collaboratifs (grâce à des algorithmes dédiés). ABSTRACT : MISE 2.0 (for Mediation Information System Engineering, second iteration) project has been launched in 2009. The MISE 2.0 engineering approach is based on BPM (Business Process Management) and MDE (Model-Driven Engineering). Running a regular BPM approach on a specific organization consists in gathering structural, informational, and functional knowledge in order to design cartography of processes covering the behavior of the modeled organization. Regarding the MISE 2.0 project the BPM approach concerns a set of organizations and MDE helps in automatizing the different steps: i) Knowledge gathering (situation layer): collect information concerning the collaborative situation, ii) Processes cartography design (solution layer): design the processes according to the knowledge gathered and iii) MIS deployment (implementation layer): implement an IT structure able to run the processes cartography. Both the transitions between these layers are the hard-points of this approach: The first gap is managed at the abstract level of MISE 2.0 while the second one is managed at the concrete level of MISE 2.0. The current PhD is focused on the first issue: designing a relevant processes cartography from the modeled collaborative situation. However, this is usually a manual activity, which requires a large amount of work to draw the processes and their links. The current research works aim at building such collaborative process cartography in an automated manner. Our principles are (i) to gather the essential and minimum initial collaborative knowledge (e.g. partners, shared functions and collaborative objectives) in models, ii) to deduce the missing knowledge with the help of a collaborative metamodel, an associated ontology and transformation rules and iii) to structure the deduced knowledge in a collaborative process cartography thanks to dedicated algorithms

Incremental certification of cloud services

Cloud is becoming fast a critical infrastructure. However, several recent incidents regarding the security of cloud services clearly demonstrate that security rightly remains one of the major concerns of enterprises and the general public regarding the use of the cloud. Despite advancements of research related to cloud security, we are still not in a position to provide a systematic assessment of cloud security based on real operational evidence. As a step towards addressing this problem, in this paper, we propose a novel approach for certifying the security of cloud services. Our approach is based on the incremental certification of security properties for different types of cloud services, including IaaS, PaaS and SaaS services, based on operational evidence from the provision of such services gathered through continuous monitoring. An initial implementation of this approach is presented

If it ain’t broke, don’t fix it : An Abductive and Contextual Exploration of Maintenance Deferral

Objective: To create academic insights into how organisations approach and manage the maintenance of vendor-supplied information systems software. Approach: Three iterations of the Peircean Abduction methodology lead to the identification, conceptualisation, and application of new knowledge in vendor-supplied Information Systems (IS) maintenance deferral by means of undertaking a qualitative multiple-case study. The research goals are achieved through the appropriation and application of theories from Peircean Abduction and Systemic Functional Linguistics. Research questions: The following abductive statement is created through the application of the Peircean Abduction methodology: The surprising observation, “some organisations, having invested in a vendor-supplied IS software solution, defer the implementation of vendor-supplied maintenance”, is made; However, if “the existence of deterrents to maintenance, requiring a trigger event before the implementation of maintenance” were true, then “maintenance deferral” would be a matter of course. Hence there is a reason to suspect that “the existence of both deterrents, and of triggers” is true. From this abductive statement, three research questions are deduced. The first research question investigates the existence, characteristics and influence of deterrents; the second question investigates the existence, characteristics and influence of triggers. As a consequence of this approach, the final question provides a general understanding of IS maintenance deferral. Methodology: Following the implementation of a systematic literature review methodology, six themes are identified: 1. an acknowledgement that problems exist when considering vendor-supplied software maintenance; 2. deterrents as a driver in behaviour; 3. the occurrence of tipping-points which require vendor-supplied maintenance to be undertaken; 4. the consequences of deferral; 5. the value of maintenance; and 6. the formalisation of a maintenance lifecycle. Taking the insights arising from the systematic literature review, a multiple-case study following the pragmatic framework is constructed from data collected interviewing twelve participants across a diverse set of ten organisations. An abductive approach to this research topic creates opportunities for a comprehensive, well-grounded exploratory contribution to a scarcely investigated research domain. Major findings: The translation of Peircean abduction to an interpretative context generates a rich and substantive contribution to theory and practice. The existence of both deterrents and triggers are strongly supported, leading to the conclusion that maintenance deferral is a matter of course. The development of a new abductive and Systemic Functional Linguistic model enhances the knowledge of maintenance deferral and allows refinement of historical IS maintenance models. Finally, the application of Systems Thinking situates insights from the application of their mode within their respective organisational environments

The Evolution of IS Projects in Manufacturing Industries: The Case of Product Lifecycle Management

In this paper, we explore the evolution of product lifecycle management information systems projects in manufacturing industries over time. There is critical need because initiated projects routinely fail in terms of time, budget, or quality to which the academic discourse has not given adequate consideration. Therefore, we build up on an in-depth case study within the project setting of a leading European automotive supplier kicked-off in January 2016. As central results, the paper provides insights (1) how product lifecycle management information systems projects develop over time, (2) what may be underlying causes, and (3) which implications on project management may be deduced. In view of the limitations by the applied case study research strategy, we illumine the specifics of these information systems projects for scholars. For project managers, an overview on essential developments and their implications supports the successful project execution

Planning and Optimization During the Life-Cycle of Service Level Agreements for Cloud Computing

Ein Service Level Agreement (SLA) ist ein elektronischer Vertrag zwischen dem Kunden und dem Anbieter eines Services. Die beteiligten Partner kl aren ihre Erwartungen und Verp ichtungen in Bezug auf den Dienst und dessen Qualit at. SLAs werden bereits f ur die Beschreibung von Cloud-Computing-Diensten eingesetzt. Der Diensteanbieter stellt sicher, dass die Dienstqualit at erf ullt wird und mit den Anforderungen des Kunden bis zum Ende der vereinbarten Laufzeit ubereinstimmt. Die Durchf uhrung der SLAs erfordert einen erheblichen Aufwand, um Autonomie, Wirtschaftlichkeit und E zienz zu erreichen. Der gegenw artige Stand der Technik im SLA-Management begegnet Herausforderungen wie SLA-Darstellung f ur Cloud- Dienste, gesch aftsbezogene SLA-Optimierungen, Dienste-Outsourcing und Ressourcenmanagement. Diese Gebiete scha en zentrale und aktuelle Forschungsthemen. Das Management von SLAs in unterschiedlichen Phasen w ahrend ihrer Laufzeit erfordert eine daf ur entwickelte Methodik. Dadurch wird die Realisierung von Cloud SLAManagement vereinfacht. Ich pr asentiere ein breit gef achertes Modell im SLA-Laufzeitmanagement, das die genannten Herausforderungen adressiert. Diese Herangehensweise erm oglicht eine automatische Dienstemodellierung, sowie Aushandlung, Bereitstellung und Monitoring von SLAs. W ahrend der Erstellungsphase skizziere ich, wie die Modellierungsstrukturen verbessert und vereinfacht werden k onnen. Ein weiteres Ziel von meinem Ansatz ist die Minimierung von Implementierungs- und Outsourcingkosten zugunsten von Wettbewerbsf ahigkeit. In der SLA-Monitoringphase entwickle ich Strategien f ur die Auswahl und Zuweisung von virtuellen Cloud Ressourcen in Migrationsphasen. Anschlie end pr ufe ich mittels Monitoring eine gr o ere Zusammenstellung von SLAs, ob die vereinbarten Fehlertoleranzen eingehalten werden. Die vorliegende Arbeit leistet einen Beitrag zu einem Entwurf der GWDG und deren wissenschaftlichen Communities. Die Forschung, die zu dieser Doktorarbeit gef uhrt hat, wurde als Teil von dem SLA@SOI EU/FP7 integriertem Projekt durchgef uhrt (contract No. 216556)

Towards an Ontological Foundation of Services Science: The General Service Model

Despite the ubiquity of services, there is still no consensus ontheir exact nature and structure. This consensus, however, isnecessary to unambiguously describe and trade servicesphysically as well as in an Internet of Service. To make someprogress towards a shared conceptualization, we present in thispaper a general service model based on the DOLCE foundationalontology. In our understanding, a service is essentially composedof a service process whose core actions (delivered by a serviceproducer to a service consumer) comply with the exposeddescription of a service provider’s commitment. Each servicebelongs to a larger service system process which obeys legal andpricing constraints. We illustrate the model’s usefulness andrelevance by the means of a continuous example

Contribución a la estimulación del uso de soluciones Cloud Computing: Diseño de un intermediador de servicios Cloud para fomentar el uso de ecosistemas distribuidos digitales confiables, interoperables y de acuerdo a la legalidad. Aplicación en entornos multi-cloud.

184 p.El objetivo del trabajo de investigación presentado en esta tesis es facilitar a los desarrolladores y operadores de aplicaciones desplegadas en múltiples Nubes el descubrimiento y la gestión de los diferentes servicios de Computación, soportando su reutilización y combinación, para generar una red de servicios interoperables, que cumplen con las leyes y cuyos acuerdos de nivel de servicio pueden ser evaluados de manera continua. Una de las contribuciones de esta tesis es el diseño y desarrollo de un bróker de servicios de Computación llamado ACSmI (Advanced Cloud Services meta-Intermediator). ACSmI permite evaluar el cumplimiento de los acuerdos de nivel de servicio incluyendo la legislación. ACSmI también proporciona una capa de abstracción intermedia para los servicios de Computación donde los desarrolladores pueden acceder fácilmente a un catálogo de servicios acreditados y compatibles con los requisitos no funcionales establecidos.Además, este trabajo de investigación propone la caracterización de las aplicaciones nativas multiNube y el concepto de "DevOps extendido" especialmente pensado para este tipo de aplicaciones. El concepto "DevOps extendido" pretende resolver algunos de los problemas actuales del diseño, desarrollo, implementación y adaptación de aplicaciones multiNube, proporcionando un enfoque DevOps novedoso y extendido para la adaptación de las prácticas actuales de DevOps al paradigma multiNube

New Sales and Buying Models in the Internet: App Store Model for Enterprise Application Software

Whereas electronic marketplaces had been established years ago to distribute different kinds of software, they have become subject of public interest given the success of “app store” models in business-to-consumer (B2C) environment, especially for mobile device software. The expectation of a consumer grade buying experience, cloud deployment models and the disaggregation of software bundles to smaller and more focused offerings are fostering the app store model also for enterprise software. In this article, a classification of buying situations for enterprise application software is introduced reflecting organizational buying processes between the transactional and the consultative sales / buying model. In that context, the article outlines the role of electronic marketplaces and Internet-based sales infrastructures detailed in a practical case example