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
(From the Latin “complexus, complecti”, contain, source: le Grand Robert)
Source: Enterprise Transformation Manifesto; paragraphs 2.1.a and 5.1
Enterprise complexity stems from the range of its aspects, the large number of its component parts, the huge variety of its know-how and knowledge, as well as the autonomy of willingness and action of its component parts – which are themselves complex systems (paragraph 2.1.b). If we neglect this complexity, it can lead to the wrong decisions being made and can alter the functioning and very being of the Enterprise (paragraph 2.1.c).
The complexity of the Enterprise System is both a strength and a risk. Complexity is a risk insofar as it requires an increasing amount of resources or it leads to an unmanageable situation (paragraph 5.1.a). The irreducible complexity of the Enterprise System allows it to adapt to a changing environment and to respond to new situations. This can be a real advantage, provided that it is controlled (paragraph 5.1.b).
Feature of a system made up of several elements linked by multiple relations and cannot be understood only as the sum of its parts
Source: General Guide, § 3.3
The first characteristic that comes to mind with regard to the enterprise is, without doubt, its complexity. This justifies applying a systemic approach to it. Why do we consider the enterprise as a complex object? Because, whatever its size or sector, it is made up of a large number of elements, particularly of a disparate type. The components are linked between themselves within a same category and between different categories. The relations between the components are part of the categories that must be specified. One essential factor that heightens the complexity lies with the autonomy of willingness and action of certain components – components which themselves can potentially be seen as complex systems.
Complexity is often perceived as a risk or, at least, a difficulty. It is also a strength: it shows the range of resources that the system has at its disposal. Its ability to invent and adapt is proportional to it. In the most advanced cases, the system has emerging properties that cannot be deduced from its composition. Does that mean that we should banish the expression “reduce complexity”? The complexity of a system, if it is real, is necessary and constitutes an asset that it should know how to take advantage of. Complexity should therefore be assumed by the system and respected by its designer.
To apprehend complexity, the traditional approach of top-down hierarchical decomposition (also known as Cartesian) is not the right solution. We opt for the systemic approach, which seeks the links between the separate elements and makes room for system-specific, emerging properties that are not possible to deduce from the sum of the parts. One characteristic often associated with complexity is uncertainty. The latter comes, in part, from the complexity itself and, to a greater extent sill, from the environment. We seek every possible means of reducing uncertainty, but we have to adapt the system and our action to an irreducible uncertainty, impossible to remove. Complexity is, moreover, an adaptive response to the uncertainty of the environment.
The result of complexity is to discourage action and generate resignation. The methodology appears exactly as the remedy to a failing imagination and abdication of will.