Design of a model-generated repository as a service for USDL

SAP and its research partners have been developing a lan- guage for describing details of Services from various view- points called the Unified Service Description Language (USDL). At the time of writing, version 3.0 describes technical implementation aspects of services, as well as stakeholders, pricing, lifecycle, and availability. Work is also underway to address other business and legal aspects of services. This language is designed to be used in service portfolio management, with a repository of service descriptions being available to various stakeholders in an organisation to allow for service prioritisation, development, deployment and lifecycle management. The structure of the USDL metadata is specified using an object-oriented metamodel that conforms to UML, MOF and EMF Ecore. As such it is amenable to code gener-ation for implementations of repositories that store service description instances. Although Web services toolkits can be used to make these programming language objects available as a set of Web services, the practicalities of writing dis- tributed clients against over one hundred class definitions, containing several hundred attributes, will make for very large WSDL interfaces and highly inefficient “chatty” implementations. This paper gives the high-level design for a completely model-generated repository for any version of USDL (or any other data-only metamodel), which uses the Eclipse Modelling Framework’s Java code generation, along with several open source plugins to create a robust, transactional repository running in a Java application with a relational datastore. However, the repository exposes a generated WSDL interface at a coarse granularity, suitable for distributed client code and user-interface creation. It uses heuristics to drive code generation to bridge between the Web service and EMF granularities.

Building a USDL repository as a service using MDE

The decision to represent the USDL abstract syntax as a metamodel, shown as a set of UML diagrams, has two main benefits: the ability to show a well- understood standard graphical representation of the concepts and their relation- ships to one another, and the ability to use object-oriented frameworks such as Eclipse Modeling Framework (EMF) to assist in the automated generation of tool support for USDL service descriptions.

Beyond MOF constraints : multiple constraint set metamodelling for lifecycle management

The management of models over time in many domains requires different constraints to apply to some parts of the model as it evolves. Using EMF and its meta-language Ecore, the development of model management code and tools usually relies on the meta- model having some constraints, such as attribute and reference cardinalities and changeability, set in the least constrained way that any model user will require. Stronger versions of these constraints can then be enforced in code, or by attaching additional constraint expressions, and their evaluations engines, to the generated model code. We propose a mechanism that allows for variations to the constraining meta-attributes of metamodels, to allow enforcement of different constraints at different lifecycle stages of a model. We then discuss the implementation choices within EMF to support the validation of a state-specific metamodel on model graphs when changing states, as well as the enforcement of state-specific constraints when executing model change operations.

Some reflections about P2M : the place of the mirror

The purpose of this paper is to provide some insights about P2M, and more specifically, to develop some thoughts about Project Management seen as a Mirror, a place for reflection…, between the Mission of organisation and its actual creation of Values (with s: a source of value for people, organisations and society). This place is the realm of complexity, of interactions between multiple variables, each of them having a specific time horizon and occupying a specific place, playing a specific role. Before developing this paper I would like to borrow to my colleague and friend, Professor Ohara, the following, part of a paper going to be presented at IPMA World Congress, in New Delhi later this year in November 2005. “P2M is the Japanese version of project & program management, which is the first standard guide for education and certification developed in 2001. A specific finding of P2M is characterized by “mission driven management of projects” or a program which harness complexity of problem solving observed in the interface between technical system and business model.” (Ohara, 2005, IPMA Conference, New Delhi) “The term of “mission” is a key word in the field of corporate strategy, where it expresses raison d’être or “value of business”. It is more specifically used for expressing “the client needs” in terms of a strategic business unit. The concept of mission is deemed to be a useful tool to share essential content of value and needs in message for complex project.” (Ohara, 2005, IPMA Conference, New Delhi) “Mission is considered as a significant “metamodel representation” by several reasons. First, it represents multiple values for aspiration. The central objective of mission initiative is profiling of ideality in the future from reality, which all stakeholders are glad to accept and share. Second, it shall be within a stretch of efforts, and not beyond or outside of the realization. Though it looks like unique, it has to depict a solid foundation. The pragmatic sense of equilibrium between innovation and adaptation is required for the mission. Third, it shall imply a rough sketch for solution to critical issues for problems in reality.” (Ohara, 2005, IPMA Conference, New Delhi) “Project modeling” idea has been introduced in P2M program management. A package of three project models of “scheme”, “system” and “service” are given as a reference type program. (Ohara, 2005, IPMA Conference, New Delhi) If these quotes apply to P2M, they are fully congruent with the results of the research undertaken and the resulting meta-model & meta-method developed by the CIMAP, ESC Lille Research Centre in Project & Program Management, since the 80’s. The paper starts by questioning the common Project Management (PM) paradigm. Then discussing the concept of Project, it argues that an alternative epistemological position should be taken to capture Page 2 / 11 the very nature of the PM field. Based on this, a development about “the need of modelling to understand” is proposed grounded on two theoretical roots. This leads to the conclusion that, in order to enables this modelling, a standard approach is necessary, but should be understood under the perspective of the Theory of Convention in order to facilitate a situational and contextual application.