Praxeme in a nutshell

Add a comment

Praxeme is an open source enterprise method that intends to bring together the various disciplines for analyzing and transforming the enterprise and its systems.
Launched in year 2004, the initiative for a public method is backed by many companies and organizations, such as SAGEM, SMABTP, the French Army and the French National Family Funding Office…
First of all, Praxeme provides a strong methodological framework, the Enterprise System Topology. This framework identifies eight aspects which enable a comprehensive description of the enterprise, from its strategy toward its transformation.
Modelers, enterprise architects, organization designers, software designers and IT architects will find in Praxeme a set of principles and methods, specially modeling techniques. Each aspect deals with a particular “view” of the enterprise or its information system. Praxeme provides us with detailed guidelines for UML modeling and MDA (see figure below).

The methodological framework at the core of Praxeme

The methodological framework at the core of Praxeme

The semantic aspect includes business objects, lifecycle of business objects, business rules, regulation… The semantic model expresses the core business knowledge, regardless of organizational or techniqal choices.
The pragmatic aspect deals with organizational choices, roles, business processes, work habits… Its representation is made of use cases, processes, and also models of organizational or administrative objects.

The Praxeme methodology strictly applies the principle known as “separation of concerns”. These two aspects – semantic and pragmatic – are enterprise business oriented, they do not integrate IS architecture such as SOA. The logical aspect shelters SOA style. It is the place for a strong logical architecture through components and services that are directly derived from semantic and pragmatic models. Praxeme proposed methods for SOA comply with the MDA standard (Model Driven Architecture). The software aspect derives from logical models and adds a technical UML profile to target the IT infrastructure, in particular programming languages (Java, C#, COBOL…) and XML. Components can be executed through a framework that is defined by a complete open source specification: the Virtual Engine for Praxeme (VEP). Several implementations of the VEP are possible: .NET, Java (in-house development or via a framework such as Spring), Cobol MVS, etc.

We believe that existing Information System, especially in large organizations, demand an in-depth overhaul. In order to manage and drive this kind of projects, we need a global enterprise method that provides us with the detailed guidelines for each aspect of the information system: semantic, pragmatic, SOA, software, VEP…

This entry is filed under foundation. And tagged with , , , . You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site.

  1. No Comments

Please leave these two fields as-is: