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
The term “object” has had strange fortunes. Referring to the most commonplace notion there is, as the most generic, it was not part of enterprise vocabulary. The object-oriented design and programming approach made it fashionable, from the 80s onwards, in the IT domain. In this context, the object (or class instance), when we take a close look at it, has an ambiguous status: both the IT representation of something (in a computer’s memory) and the actual thing that is represented. It very quickly became necessary to clarify things. The expression “business object” thus appeared to represent the object as seen by the actors of the enterprise, upstream therefore from IT. Then, the expression moved around on different levels. For example, it can be found in software to compare classes that, on the one hand reflect objects from the real world and, on the other hand, realize purely technical services.
Praxeme uses the expression to refer to objects of the world, whether they be external or internal to the enterprise. These objects can be physical: a person, goods, a machine or a weapon… In other cases, especially in the service sector, objects are abstractions: a contract, a service offering, an account…
We would like to simply say “object” but that would lead to confusion with how this term is understood in IT; hence the specification “business object”.
Concrete or abstract object, essential to the Enterprise System’s mission
In this definition, “business object” refers quite spontaneously to the semantic class, which is the means of representing the business object or its concept. Indeed, it is in this way that semantic modeling expresses the business fundamentals. Nevertheless, we also find objects of an organizational nature that we must take care to place in the pragmatic aspect.