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: Enterprise Transformation Manifesto, ¶ 2.3(a)
“It is not possible to understand and master the Enterprise without first untangling its many aspects.”
Roughly speaking, there are two ways to cope with complexity:
The first way is known as the Cartesian approach and can apply as far as the system displays a unique and homogeneous nature. The second approach appears in system theory.
Regarding the enterprise, the complexity stems, to a large extent, from the combination of diverse concerns, the conflict between divergent interests and the coexistence of several cognitive universes. Consequently, we have to recognize the plurality of this reality.
Reality must be approached from several angles. The aspects are parts of the reality studied. Their separation meets both formal and practical requirements. The aspects are defined in such a way that every piece of information or every decision about the system finds a natural, unique spot.
On the contrary to a View or a point of view – which depends on who is looking –, the aspect belongs solely to the reality observed. The criteria used to define the aspects do not call on the types of actors involved in the transformation chain. They are concerned only with the object under study, called the Enterprise System. It is only secondarily that certain disciplines are defined as specialisms related to an aspect (for example: semantic modeling, logical architecture…).
Part of reality, which has been isolated for the sake of study, in accordance with its inner logic
In the context of Enterprise Architecture, an aspect is part of the enterprise reality, which has been isolated for the sake of study. Distinguishing the aspects is based on the “separation of concerns” principle that enables us to simplify the topics and to assign responsibilities more efficiently.