Search Results for "knowledge"

MSS Code Factory turns XML Business Application Models into source code by applying a knowledge base of expansion rule cartridges. Each cartridge of rules in the knowledge base defines the code to be produced for a particular language, tool, or combination thereof. A cartridge can also integrate the rules from other cartridges, so you can create a virtual cartridge that will produce all the code to support a given software stack that the rules provide.

SmartSlog (Smart Space Ontology) is a software/application development kit (SDK or ADK) for programming Smart-M3 agents (Knowledge Processors, KPs) that consume/produce smart space content according with its high-level ontological representation. SmartSlog applies the code generation approach: given an OWL ontology description, the ontology programming library is produced. The latter provides API to access the smart space via a Smart-M3 Semantic Information Broker (SIB) and data structures and functions to represent and maintain locally in KP code all ontology classes, relations, properties, and individuals. ...

...Cress diagrams are automatically translated into formal languages for rigorous analysis and verification, and are also automatically translated into implementation languages for deployment and validation. Cress aims to make service design as easy as possible without requiring specialist development knowledge. It simplifies service creation to drawing diagrams, clicking buttons and defining a few tool parameters. All key functions of Cress can be controlled from the Chive diagram editor. Cress is written using portable and widely used languages (Perl and Java). It can be extended by a developer for other kinds of services that can be characterised by activity flows.

Generating the files of an application with the help of a DSL (domain specific language) is very nice . . . provided the development of the DSL itself is not more complex than the application development itself. This workbench is based on the JSON templates and a so-called description file that lists the files to generate. It requires thus a minimum of knowledge and effort to manage the templates and the source specification. It provides a powerful multi-file editor that highlights the cross-references between the templates, the JSON object, the description list and the resulting files. For example, a simple click in an application file allows a developer to see where the clicked symbol does come from. ...

The Clump language proposes a natural evolution of the basic Object-Oriented paradigm revisiting the duality existing between the data and the knowledge. This implies a design based on Class-Oriented and Pattern-Oriented approaches in a same language