Site temporairement indisponible.
Modus, the method
All pages in Modus rubric Approach to pragmatic aspect Approach to semantic aspect Batches Processing in Service Architecture Business Architecture Creating the methodological repository Deriving the logical data model from the business model General Guide Geographic Aspect Geographic Aspect Guide Hardware Aspect Guide Innop: a process for innovative projects Innop: Methodological Transition Innop: the "Consolidation" phase Innop: the "Crystallization" phase Innop: the "Dissemination" phase Innop: the "Exploration" phase Innop: the "Implementation" phase Innop: the "Initiation" phase
Opus, the product
"Reality" domain All pages in Opus rubric Geographic Aspect Hardware Aspect Logical Aspect Opus, the Product Physical Aspect Pragmatic Aspect Scoping Semantic Aspect Software Aspect Technical Aspect Value Chain
Thesaurus, the terminology
? Abstraction Principle Accountability Action Activity Activity domain Actor Agility Analyze Approach Arbitration Architecture Architecture Principle Aspect Association Auditability Automaton blank page Business Architecture Business fundamentals Business object Business repository Class Diagram Class Properties Complexity
Syllabus, the spreading
Build for Change through Enterprise Architecture Le Praxeme Institute et Modelio Open Source "Business Architecture & Transformation" "La transformation des SI - SOA, API, micro-services : comment s'y prendre ?" "Le Référentiel de description de l'entreprise" "Praxeme &... Terminology" "Praxeme Skills" training course 2-page Flyer A classification of skills based on the Enterprise reality A complete method for modeling organizations and systems A method applicable to all sectors of activity A method supported by a community Agility Road for the SOA Journey Agility Road for the SOA Journey Aider à transformer les entreprises All pages in Syllabus rubric An open method An open method available for use An open source method to address the needs of IT departments
Corpus, the library
All pages in Corpus rubric Architect Business Activity Monitoring Business Analyst Business Architecture Business Owner Corpus, the library Decision Maker - Executive Enterprise Arcitecture Finance IT Architecture Manager Methodologist Project Manager Project Owner - Provider Recrutez des docteurs pour booster votre entreprise Researcher SOA Topic Trainer
Focus, the objectives and the organization
Chorus, the community
All pages in Chorus rubric Chorus, the community College of Contributors College of Translators Contributions From Companies Ecosystem Join the Praxeme Institute! Joined effort of C2P and the Praxeme Institute Partners Pierre CALVANESE Praxeme Actors Praxeme Authors Praxeme Institute Board Members Praxeme Institute Statutes Praxeme Workgroups Praxeme's Ecosystem Registered Companies Semantic Modellers College Stay informed
Apparatus, the tooling
Opera, the operations
All pages in Opera rubric Application References of the method Events Mind On Top OBC Open Business Concepts (OBC) Opera, the operations Parameters to be updated Presentation Suggestions Box The PxData project Thierry BIARD's thesis
Introduction to the notion
Source: General Guide, § 5.4
Praxeme proposes a holistic approach to complex systems (enterprises, organizations, Product systems, etc.). This approach, completed by its architectural aim, argues in favor of a central mechanism: the enterprise description repository (or RDE).
The enterprise (or system) description repository contains all the elements collected during the work to describe it. These elements are structured in accordance with the chosen architectures.
The models serve the investments that have a short- or medium-term objective. The continuity principle translates the intention to increase their effects by including them in a more extensive effort to build the system in the long term. This course of action relies on the enterprise description repository, the central mechanism whose structure mirrors the architecture decisions and into which the models flow, project after project.
This repository plays a pivot role in the transformation. It materializes the will to administrate the investments at the enterprise level and not only on the project level. It embodies the continuous effort with a view to achieving the architecture target. Around this mechanism, the interactions between transformational activities will have to be reviewed.
Repository containing all elements gathered in the course of the work carried out to describe the Enterprise System
The EDR is the common pot into which the representations, which result from the transformation efforts, flow. It must be visible at an enterprise level, that is to say not only for an operation, be it a big program, and not only restricted to a function (like the IT department). It should be “anointed” by management and have sufficient communication around it, so that the actors of the transformation turn to it to help fuel their thinking. All information and decisions are stored there and positioned according to the architecture rules. It is an accelerator for transformation projects. The first level of its structure is none other than the representation framework. The following levels take up the architecture decisions for all aspects. The internal model of the EDR, more specifically the tooling that creates it, is the metamodel of the method.