![[object Object],[object Object],[object Object],[object Object],[object Object],Langage de modélisation unifié (UML®) ,[object Object],Modélisation des informations](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (12)
En vedette
En vedette (20)
Similaire à 7. information modelling
Similaire à 7. information modelling (20)
Dernier
Dernier (20)
7. information modelling
- 1. Organisation mondiale des douanes DES TRANSACTIONS TRANSFRONTIERES A GRANDE VITESSE Modèle de données de l’OMD Modélisation des informations
- 9. 1 er avant-projet de modèle
- 10. 2 ème avant-projet de modèle
- 14. 3ème avant-projet de modèle
- 15. Modélisation des informations Simplification des documents exigés Déclaration DocumentTransportConnexe DocumentSupplémentaire DocumentContratTransport Document DocumentDouanierPrécédent Facture changeReason.Code issue.date issueLocation.Identifier issuer.Identification reference.Code type.Code
- 16. Version 2 Diagramme de classe : Diagramme global multi-liens
- 21. Modélisation des informations et des processus opérationnels “ Ce n’est qu’un modèle” “ Et un modèle n’est jamais parfait” SOUVENEZ-VOUS :
- 22. Organisation mondiale des douanes Des questions ? DES TRANSACTIONS TRANSFRONTIERES A GRANDE VITESSE
Notes de l'éditeur
- The need for a formal methodology for dealing with data concepts and structures became apparent to the early builders of business processing systems. The concepts of data modeling were pioneered by the early practitioners of software engineering. No matter what approach is taken for building industry strength application software, data modeling is always attempted. The traditional approaches to software engineering (the waterfall method) and the moderns “agile” approaches – all use data modeling of some kind. Establishing the formal meaning of related and structured data: Primacy of unvarying underlying structures over process-defined views:
- data structure in an information system need not be complete but it should be accurate . The need for a formal methodology for dealing with data concepts and structures became apparent to the early builders of business processing systems. The concepts of data modeling were pioneered by the early practitioners of software engineering. No matter what approach is taken for building industry strength application software, data modeling is always attempted. The traditional approaches to software engineering (the waterfall method) and the moderns “agile” approaches – all use data modeling of some kind. Conceptually similar to class modeling: Data modelling identifies entity types – class modelling is focussed on classes. In data modelling, attributes are assinged to entities – whereas in class modelling attributes and operations are assinged to each class. Like between entities, there as associations between classes - relationships, inheritance, composition, and aggregation are all applicable concepts in data modeling – as in the case of data modeling. Establishing the formal meaning of related and structured data: Primacy of unvarying underlying structures over process-defined views:
- Exploring domain concepts with stake holders
- Anybody concerned with data oriented aspects of a project.