Search results for "Metamodeling"

showing 10 items of 66 documents

Metamodel specialization based DSL for DL lifecycle data management

2020

A new Domain Specific Language (DSL) based approach to Deep Learning (DL) lifecycle data management (LDM) is presented: a very simple but universal DL LDM tool, still usable in practice (called Core tool); and an advanced extension mechanism, that converts the Core tool into a DSL tool building framework for DL LDM tasks. The method used is based on the metamodel specialisation approach for DSL modeling tools introduced by authors.

Domain-specific languageSIMPLE (military communications protocol)business.industryComputer scienceData managementDeep learning020207 software engineering02 engineering and technologyUSableMetamodelingDigital subscriber lineSoftware_SOFTWAREENGINEERINGSpecialization (logic)0202 electrical engineering electronic engineering information engineeringArtificial intelligencebusinessSoftware engineeringProceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedings
researchProduct

Towards DSL for DL Lifecycle Data Management

2020

A new method based on Domain Specific Language (DSL) approach to Deep Learning (DL) lifecycle data management tool support is presented: a very simple DL lifecycle data management tool, which however is usable in practice (it will be called Core tool) and a very advanced extension mechanism which in fact converts the Core tool into domain specific tool (DSL tool) building framework for DL lifecycle data management tasks. The extension mechanism will be based on the metamodel specialization approach to DSL modeling tools introduced by authors. The main idea of metamodel specialization is that we, at first, define the Universal Metamodel (UMM) for a domain and then for each use case define a …

Domain-specific languagebusiness.industryComputer scienceData managementDeep learningUSableDomain (software engineering)MetamodelingDigital subscriber lineSoftware_SOFTWAREENGINEERINGSpecialization (functional)Artificial intelligencebusinessSoftware engineering
researchProduct

THE METAMODEL: A STARTING POINT FOR DESIGN PROCESSES CONSTRUCTION

2010

The construction of ad-hoc design processes following the Situational Method Engineering (SME) paradigm is currently carried out by adopting a set of phases for which, until now, no well defined techniques and guidelines have been established. The consequence is that organizations are very dependent on method designers' skills. In this paper, we propose an approach based on SME for constructing customized agent oriented design processes. Our approach adopts the metamodel as the most important factor leading to the selection and assembly of method fragments and an algorithm for establishing the instantiation order of metamodel elements. The algorithm makes the proposed approach repeatable a…

EngineeringComputer Networks and Communicationssituational method engineeringUSableSet (abstract data type)Artificial IntelligenceFactor (programming language)Metamodelcomputer.programming_languageSettore ING-INF/05 - Sistemi Di Elaborazione Delle InformazioniPoint (typography)business.industrySituational Method Engineering.Multi-agent systemMethod engineeringComputer Graphics and Computer-Aided DesignMetamodelingdesign processMulti-agent systemSystems engineeringDesign processDesign ProceSoftware engineeringbusinesscomputerSoftwareInternational Journal of Software Engineering and Knowledge Engineering
researchProduct

A comparative review of CASE shells: A preliminary framework and research outcomes

1993

Abstract Because of rigidity and weak support of the user's native methods and methodologies in existing CASE tools, there is a growing need for customizable CASE tools (CASE shells). The nature of CASE shells is different from ordinary CASE tools supporting a fixed set of methods. With CASE shells, organizations can define tools to support their own methods, instead of choosing a tool that supports them. Existing CASE shells have different features and architectural principles that make them appropriate for different tasks. Obviously, a framework for comparing them is needed. In this paper we develop one such framework. It takes into account different tasks in customization and the effecti…

EngineeringInformation Systems and Managementbusiness.industryComputer aidRigidity (psychology)Architectural principlesManagement Information SystemsPersonalizationMetamodelingSystems engineeringComputer-aided software engineeringSoftware engineeringbusinessSet (psychology)Information SystemsInformation & Management
researchProduct

Semantics of UML 2.0 Activity Diagram for Business Modeling by Means of Virtual Machine

2005

The paper proposes a more formalized definition of UML 2.0 Activity Diagram semantics. A subset of activity diagram constructs relevant for business process modeling is considered. The semantics definition is based on the original token flow methodology, but a more constructive approach is used. The Activity Diagram Virtual machine is defined by means of a metamodel, with operations defined by a mix of pseudocode and OCL pre- and postconditions. A formal procedure is described which builds the virtual machine for any activity diagram. The relatively complicated original token movement rules in control nodes and edges are combined into paths from an action to action. A new approach is the us…

FOS: Computer and information sciencesComputer Science - Programming LanguagesSemantics (computer science)Computer scienceProgramming languageActivity diagramBusiness process modelingSecurity tokencomputer.software_genreMetamodelingComputational Engineering Finance and Science (cs.CE)Unified Modeling LanguageVirtual machineComputer Science - Computational Engineering Finance and SciencePseudocodecomputercomputer.programming_languageProgramming Languages (cs.PL)
researchProduct

Metamodel Specialization for DSL Tool Building

2016

Most of domain-specific tool building and especially diagram editor building nowadays involves some usage of metamodels. However normally the metamodel alone is not sufficient to define an editor. Frequently the metamodel just defines the abstract syntax of the domain, mappings or transformations are required to define the editor. Another approach [8] is based on a fixed type metamodel, there an editor definition consists of an instance of this metamodel to be executed by an engine. However there typically a number of functionality extensions in a transformation language is required. The paper offers a new approach based on metamodel specialization. First the metamodel specialization based …

FlowchartTheoretical computer scienceComputingMethodologies_SIMULATIONANDMODELINGComputer scienceProgramming languagecomputer.software_genreTransformation languagelaw.inventionMetamodelingDomain (software engineering)Unified Modeling LanguageSoftware_SOFTWAREENGINEERINGlawAbstract syntaxSpecialization (logic)Class diagramSoftware_PROGRAMMINGLANGUAGEScomputercomputer.programming_language
researchProduct

Metamodeling editor as a front end tool for a CASE shell

1992

Customizable Computer Aided Software Engineering (CASE) tools, often called CASE shells, are penetrating in the market. CASE shells provide a flexible environment to support a variety of information systems development methods. CASE shells are often cumbersome to use and in practice few people can model and implement methods in them. To overcome these problems we have developed a graphical metamodeling environment called MetaEdit and a method modeling interface to the CASE shell RAMATIC. Using this interface the methodology engineer can develop graphical models in RAMATIC's model definition language and then easily generate the resource files that control the operations of RAMATIC. MetaEdit…

Front and back endsEngineering drawingComputer engineeringInterface (Java)Computer scienceShell (computing)Information systemObject typeGraphical modelComputer-aided software engineeringMetamodeling
researchProduct

Multi-data models translations in interoperable information systems

1996

Interoperation of heterogeneous and autonomous information systems has traditionally been hampered by semantic differences in their data models. In this paper, we address the problem by defining a methodology called TIME, which is based on an extensible meta model. Its key features are: a set of meta-types which can be used to represent the syntax and the semantics of data modeling concepts, a knowledge base of transformation rules that map a meta-type into other meta-types, and an inference engine which uses the transformation rules to translate schema from source to target models. The extensibility of the meta-model is achieved by organizing the meta-types into a generalization hierarchy …

InteroperationInformation retrievalKnowledge basebusiness.industryComputer scienceInteroperabilityRelational modelInformation systemInference enginebusinessData modelingMetamodeling
researchProduct

XML Enabled Metamodeling and Tools for Cooperative Information Systems

2001

The development of tools to support semantic resolution is a key issue in the design of heterogeneous interoperable information systems. This paper presents a methodology and a data model translator toolkit, called X-TIME, for the design and management of interoperable information systems. X-TIME combines a metamodelling approach and XML features to provide support for automated design of wrappers or semantic reconciliators. It is a flexible semantics oriented approach that takes into account several important characteristics of interoperable information systems, including extensibility and composability. Extensibility requires a translation scheme that can easily integrate new data models.…

Knowledge representation and reasoningData modelComposabilitycomputer.internet_protocolComputer scienceDistributed computingInteroperabilityRelational modelInformation systemcomputerXMLData modelingMetamodeling
researchProduct

Method Engineering: Current research directions and implications for future research

1996

In this study we investigate method engineering research by classifying studies into three contexts: technology, language and organization. Within each context we examine research bias, research outcomes and use of alternative research methods. This survey reveals the inherent bias of ME research towards tool and language development at the cost of empirical studies. We lack investigations of why organizations develop their own “variants” of system development methods, and how they manage their method engineering efforts. These observations lead us to suggest some directions for future research, which relate both to actual research questions and to the use of complementary research methods.

Language developmentSystem developmentEngineeringEmpirical researchbusiness.industryManagement scienceMethod engineeringContext (language use)Research questionsbusinessMetamodeling
researchProduct