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
As opposed to other approaches (process design, business analysis, software development…), architecture is a discipline that tackles the system as a whole and over the long term. It takes an interest in the entire system and in the system in its entirety. Thus, architecture is concerned with the coherence and quality of the whole rather than with short-term deliveries. As such, it corrects the tendency for efforts to be dispersed by specific, local and short-term objectives. This is why architecture enables us to optimize investments by factorizing common elements and reducing redundancy.
In everyday language, “architecture” refers both to (a) a description of something to build or that already exists; (b) the design discipline of that which must be built. These twin notions – description and discipline – relate back to the classic dichotomy in methodology: product (“what”) / production (“how”).
The definition of the term “architecture” is too general for us to know precisely what job we are talking about. As is, it can be applied as much to the architecture of buildings as to enterprise architecture or IT architecture. Moreover, except for the architecture of buildings, we use the term “architecture” in a metaphorical way. It is therefore important to always specify the architecture application domain. In the context of enterprise methodology, this means indicating the aspect that the effort is focused on. This is how we define enterprise architecture as a design effort of the whole enterprise, all aspects together, whereas Business Architecture specializes in the “business” aspects, like logical architecture, technical architecture… focusing on the corresponding aspect.
For the Praxeme methodology, a particular architecture, as an artifact, is a model tackling the whole system. In general, it only deals with one aspect of the system, or a selection of aspects that are fixed by the Enterprise System Topology. To gather the main structuring decisions of an Enterprise System, we establish a “general architecture file”.
For more information, see IEEE 1471 (an IEEE norm to describe the intensive software architecture of a system).
Discipline that tackles a system in its entirety and examines its overall properties as well as its integration in its environment