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 class diagram is an indispensable part of object modeling. The diagram is not the model, but a partial, biased illustration of it. Once finished, the class model represents the whole substance of the system, both data and processes. (These two notions of data and processing do not belong to the semantic aspect but burgeon over IT terminology. In the semantic aspect, preference is given to the terms: information, action, transformations and associations of objects.)
Each diagram is realized with a communication goal in mind. It only presents the elements which contribute to this objective. Diagrams must be readable: size will be limited to a sheet of A4 paper and rules such as the famous magic number seven can be applied. This rule summarizes the work of G. Miller in experimental psychology: a good structure – from a presentation point of view – is made up of about seven elements (give or take two).
However, at least for the modeler or developer's needs, a class diagram can exceed these limits and even contain the whole of the model. It follows that this diagram will then be known as the class model. It will not necessarily be part of the file, but constitutes a tool to find one's way around the model.
UML diagram that shows a collection of declarative (static) UML model elements such as classes and types, with their contents and relationships