Deposits of clastic carbonate-dominated (calciclastic) sedimentary slope systems in the rock record have been identified mostly as linearly-consistent carbonate apron deposits, even though most ancient clastic carbonate slope deposits fit the submarine fan systems better. Calciclastic submarine fans are consequently rarely described and are poorly understood. Subsequently, very little is known especially in mud-dominated calciclastic submarine fan systems. Presented in this study are a sedimentological core and petrographic characterisation of samples from eleven boreholes from the Lower Carboniferous of Bowland Basin (Northwest England) that reveals a >250 m thick calciturbidite complex deposited in a calciclastic submarine fan setting. Seven facies are recognised from core and thin section characterisation and are grouped into three carbonate turbidite sequences. They include: 1) Calciturbidites, comprising mostly of highto low-density, wavy-laminated bioclast-rich facies; 2) low-density densite mudstones which are characterised by planar laminated and unlaminated muddominated facies; and 3) Calcidebrites which are muddy or hyper-concentrated debrisflow deposits occurring as poorly-sorted, chaotic, mud-supported floatstones. These

Phd by thesis

According to W. Edwards Deming, American companies require nothing less than a transformation of management style and of governmental relations with industry. In Out of the Crisis, originally published in 1982, Deming offers a theory of management based on his famous 14 Points for Management. Management's failure to plan for the future, he claims, brings about loss of market, which brings about loss of jobs. Management must be judged not only by the quarterly dividend, but by innovative plans to stay in business, protect investment, ensure future dividends, and provide more jobs through improved product and service. In simple, direct language, he explains the principles of management transformation and how to apply them.

Out of the Crisis

The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

[서평]「The Unified Modeling Language User Guide」

An important decision that must be taken by anyone designing a course involving (object oriented software) modelling is what tool support, if any, to use. Options include picking an industrial strength modelling tool, using a tool specifically designed for educational use, or eschewing tool use altogether in favour of pencil and paper. The best answer will depend on many factors, including the prior experience of the students (and staff), the length and organisation of the course, and the learning objectives. Moreover, decisions on tools have an impact on other aspects of course design. In this informal paper, the result of discussion at the MODELS Educators’ Symposium 2013, we survey previous work on this question, discuss our own experience, and draw out some key issues that someone designing a new course involving modelling must consider.

/pdf/tool-use-in-software-modelling-education-nael7xek8x.pdf

Tool Use in Software Modelling Education.

Since the first OMG specification of the Unified Modeling Language (UML), the Object Constraint Language (OCL) has been used for the definition of well-formedness rules in the UML specification. These rules have been specified within the early OCL years, when no appropriate tooling existed. Thus, they could not be checked for syntactical and static semantics correctness. In this paper we present an analysis of the static correctness of all OCL rules specified in the UML 2.3 superstructure document. We categorise found errors and propose changes for both the UML specification process and the OCL language to improve the UML specification’s correctness in future versions.

/pdf/uml-is-still-inconsistent-how-to-improve-ocl-constraints-in-30tfvmp1kc.pdf

UML is still inconsistent! How to improve OCL Constraints in the UML 2.3 Superstructure

The eXtensible Markup Language (XML) and its related technologies provide a promising tool for the implementation of transformations of UML models, not only for research prototypes but also for the interaction of different commercial CASE tools. We report on our experiments with XML query and transformation languages in the context of object-oriented software development. Especially we use the XML Metadata Interchange Format (XMI) as a tool for the transformation of object-oriented models. We outline XMI based scenarios in the forward and reverse engineering of different applications. As an example, we show how XMI and a standardized XML query/transformation language such as XSLT can be used for the generation of SQL database schemas based on UML models, and for design recovery from legacy code. 1 Introduction Since the Unified Modeling Language (UML) is rapidly becoming an accepted standard for software modeling, technologies for mechanical transformations of UML models become increasingly important. There are many different applications for transformation of UML models, e.g. for bridging between different subsets or variants of the language, for code generation in forward engineering, or for capturing model information in backwards engineering. In this paper, we report on experiments on a general technology applicable for all these purposes. The XML Metadata Interchange Format (XMI) was proposed in response to an Object Management Group (OMG) Request for a Stream-based Model Interchange format. The main purpose of XMI is to enable easy interchange of data and metadata between UML modeling tools and between tools and metadata repositories in distributed heterogeneous environments. XMI integrates three key industry standards: (1) XML - eXtensible Markup Language, a W3C standard [23] that provides the universal format for structured documents and data on the Web; (2) UML - Unified Modeling Language, the OMG modeling standard [4], [19] for specification, visualization, construction, and documentation of object-oriented systems; (3) MOF - Meta Object Facility, a CORBA-compliant architecture for defining and sharing semantically rich metadata in distributed heterogeneous environments which is used as OMG modeling and metadata repository standard [18]. Our intention is to use XMI for bridging the gap between different CASE tools and different software/database paradigms both in forward and reverse engineering. We present

Experiments with XMI Based Transformations of Software Models

Business rules should improve the human communication inside of an enterprise or between business partners and must be therefore independent of implementations in IT systems. As a long-term goal, business rules should be guaranteed by all IT applications of an enterprise. A first step to define and to standardize what business rules are is an OMG initiative to specify a metamodel for business rules and the vocabulary on which business rules are defined. The result of OMG's effort is the SBVR (Semantics of Business Vocabulary and Business Rules) specification that we took as starting point of our investigations to automate business rules. There are multiple ways for transforming business rules. In this paper we show how SBVR based vocabulary and rules can be translated by model transformation chains into Semantic Web Languages. In our approach we use OWL and R2ML (REWERSE Rule Markup Language). Both are languages with a high potential for a broad usage in future rule-based applications.

/pdf/an-approach-for-bridging-the-gap-between-business-rules-and-eo45qqxm71.pdf

An approach for bridging the gap between business rules and the semantic web

The UNICORE grid system provides a seamless, secure and intuitive access to distributed grid resources. In recent years, UNICORE 5 is used as a well-tested grid middleware system in production grids (e.g. DEISA, D-Grid) and at many supercomputer centers world-wide. Beyond this production usage, UNICORE serves as a solid basis in many European and International research projects and business scenarios from T-Systems, Philips Research, Intel, Fujitsu and others. To foster ongoing developments in multiple projects, UNICORE is open source under BSD license at SourceForge. More recently, the new Web services-based UNICORE 6 has become available that is based on open standards such as the Web services addressing (WS-A) and the Web services resource framework (WS-RF) and thus conforms to the open grid services architecture (OGSA) of the open grid forum (OGF). In this paper we present the evolution from production UNICORE 5 to the open standards-based UNICORE 6 and its various Web services-based interfaces. It describes the interface integration of emerging open standards such as OGSA-BES and OGSA-RUS and thus provides an overview of UNICORE 6.

Birgit Demuth

Papers

Tool Use in Software Modelling Education.

UML is still inconsistent! How to improve OCL Constraints in the UML 2.3 Superstructure

Experiments with XMI Based Transformations of Software Models

An approach for bridging the gap between business rules and the semantic web

Web Services Interfaces and Open Standards Integration into the European UNICORE 6 Grid Middleware