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」

The Object Constraint Language (OCL) as the primary constraint language in model-driven software development is heavily used to specify static semantics of arbitrary languages and models. Models and constraints are therefore interconnected and depend on each other. On the one hand, daily work with models enjoys a good tool support, whereas, on the other hand, mature OCL tools are not widely spread but a niche. Unfortunately, during their life-time, the complexity of models rises and so do their OCL constraints. Thus, the gap between conventional modelling and OCL tools becomes obvious. This fact demands for OCL tool support to cope with the complexity. To bridge this gap, refactoring is well-suited and mighty. In this paper we discuss existing work, present a revised catalogue of OCL-exclusive refactorings and provide an implementation. We do not consider co-refactorings of OCL constraints and their constrained models.

/pdf/tool-supported-ocl-refactoring-catalogue-1agthiv0h6.pdf

Tool supported OCL refactoring catalogue

An Integrated OCL Development Environment (IDE4OCL) can significantly improve the pragmatics and practice of OCL. Therefore we started a comprehensive requirement analysis with the long term vision of a multisite IDE4OCL project. In this paper we present a feature model for the IDE4OCL vision based on this analysis. In an earlier work we identified domain concepts, tool–level interactions with IDE4OCL, and use cases for OCL developers including a set predefined features. In the second step, we asked the OCL community members for their feedback on our proposal. Around 100 researchers, tool developers and practitioners who gained experience with OCL have voted in an online–survey. The results gave us a valuable insight in the needs of OCL usage both in usual and advanced OCL applications. One of the important results is a collection of features that have been proposed additionally to our predefined features. We analysed all the comments of the participants of the survey and consolidated them into an extended set of IDE4OCL
features and eventually into a feature model.

/pdf/a-feature-model-for-an-ide4ocl-4u0i3zyvvy.pdf

A Feature Model for an IDE4OCL

We report on experience from teaching OO technology to undergraduate students. Before they can successfully tackle the projects they have to successfully shift to the OO paradigm, pick up a working knowledge of some OO language, learn and practice OOA and OOD, and get used to advanced ideas like patterns and frameworks. In order to relieve this heavy burden somewhat, we provided an object-oriented application framework as a common base for the projects. That way, the students are given an architecture which they have to adapt to their specific task instead of doing all the design by themselves. We also believe that this policy closely resembles the way beginners are integrated into on-going projects in practice. We describe the Java framework we used, the preparations for and the organization of the project course, educators' and students' experience and some ideas for developing this approach further.

/pdf/a-framework-based-approach-to-teaching-oot-aims-1h84ft7pss.pdf

A framework-based approach to teaching OOT: aims, implementation, and experience

The Object Constraint Language (OCL) as a part of the UML standard [1] is a formal language for defining constraints on UML models. We present a software platform for OCL tool support [2]. The platform is designed for openness and modularity, and is provided as open source. The goal of this platform is, for one thing, to enable practical experiments with various variants of OCL tool support, and then, to allow UML tool builders and users to integrate and adapt the existing OCL tools into their own environments. The Dresden OCL Toolkit provides the following tools:

Structure of the Dresden OCL Toolkit

This paper refers to 15 years experience in teaching object-oriented (OO) software development for undergraduate students. Our teaching approach includes modeling with UML and programming with Java. In a first course we introduce the students to OO analysis and OO design including using selected design patterns as well as to OO programming including UML2Java transformation based on small applications. In the subsequent project course students have to implement a mid-size application in a work-sharing software development process. Although the topics of the courses have basically not changed over the years we experimented with two basic didactic approaches in the introductory first course. The underlying issue is how should modeling and programming intertwine to educate both modelers and programmers. In this paper we evaluate both didactic approaches based on statistical results of written exams.

Birgit Demuth

Papers

Tool supported OCL refactoring catalogue

A Feature Model for an IDE4OCL

A framework-based approach to teaching OOT: aims, implementation, and experience

Structure of the Dresden OCL Toolkit

How should teaching modeling and programming intertwine