1 / 43

New Recommendations on ODP

New Recommendations on ODP. Arve Meisingset Rapporteur Q15. Two Parts. Rev Rec. X.911 for Consent Enterprise Language Draft X.906 for review and comments Use of UML for ODP system specifications. Part I. X.911 Enterprise Language Ad. 1  Rev. Rev + Annex A and B. Enterprise Viewpoint.

williammendez
Download Presentation

New Recommendations on ODP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Recommendationson ODP Arve Meisingset Rapporteur Q15

  2. Two Parts • Rev Rec. X.911 for Consent • Enterprise Language • Draft X.906 for review and comments • Use of UML for ODP system specifications

  3. Part I • X.911 Enterprise Language • Ad. 1  Rev. • Rev + Annex A and B

  4. Enterprise Viewpoint • An enterprise specification of an ODP system is a description of that system and relevant parts of its environment. • The enterprise specification focuses on the scope and purpose of that system and the policies that apply to it in the context of its environment.

  5. Enterprise Language • Concepts, • structures, and • rules for • developing, representing, and reasoning about • a specification of an ODP system from the enterprise viewpoint

  6. System Concepts

  7. Community and Behav. Concepts

  8. Accountability Concepts

  9. Policy Concepts

  10. Viewpoint correspondences The specifier shall provide: – for each enterprise object in the enterprise specification, a list of those information objects (if any) that represent information or information processing concerning the entity represented by that enterprise object; – for each role in each community in the enterprise specification, a list of those information object types (if any) that specify information or information processing of an enterprise object fulfilling that role; ETC. to inf., comp. and engin. viewpoints

  11. Annex B Examples • e.com • Library

  12. Questions • Is URN an Enterprise Language? • May SDL and MSC be used to specify an Enterprise Viewpoint? • May eODL be used to specify every correspondence between Viewpoints? • Have we done enough to position the ITU languages? • Have we ensured compliance? • Is ODP relevant for ITU?

  13. Part II • Committee Draft • X.906 Use of UML for ODP system specifications • The RM-ODP family of standards is notation free, as well as model development method free. • There is no widely agreed approach to the structuring of UML specifications. • ISO/IEC 19501 is technically identical to the OMG specification formal/03-02-04, UML 1.4.1 - ISO format. • As an example, the UML Profile for EDOC (using the UML extensions mechanism) provides a bridge between the RM-ODP architecture for distributed systems and specific technologies, such as components, workflow, messaging, and web services.

  14. Scope • the expression of a system specification in terms of RM-ODP viewpoint specifications using defined UML concepts and extensions (e.g. structuring rules, technology mappings, etc.); • relationships between the resultant RM-ODP viewpoint specifications; • relationships between RM-ODP viewpoint specifications and model driven architectures such as the OMG MDA.

  15. Relationships between UOD, ODP specifications, and UML models

  16. RM-ODP viewpoints

  17. Correspondences between RM-ODP viewpoints

  18. MDA viewpoints and models • a computation independent viewpoint (CIM) that focuses on the requirements for the system; the details of the system are hidden or as yet undetermined; • a platform independent viewpoint (PIM) that focuses on the application specific behaviour of a system while hiding the details necessary for a particular platform. A platform independent view shows the part of the complete specification that does not change from one platform to another. A platform independent view may use a general purpose modelling language, or a language specific to the area in which the system will be used; • a platform specific viewpoint (PSM) that combines the platform independent viewpoint with an additional focus on the detail of the use of a specific platform by a system.

  19. ODP system specifications and MDA models

  20. Enterprise LanguageSee part I plus details, eg.

  21. Enterprise Language7.2 UML mappings • An ODP System is a special kind of enterprise object. It maps to UML with a class stereotyped as «EV_ODPSystem», see [7.2.5]. • The scope of an ODP system is the set of behaviours that the system is expected to exhibit, e.g. its roles. It does not, therefore, map to a single UML model element, but to the set of elements that represent its behaviour. • The field of application is a property of the enterprise specification as a whole, and maps to a text attribute (comment) of the UML model stereotyped as «Enterprise_Spec» which maps to the enterprise specification. • A community maps to a subsystem stereotyped as «EV_Community», in the name space of which will be the UML model elements mapping to its roles and the associated behaviour (communications, actions, steps and processes), as well as the UML model elements mapping to the policy and accountability concepts specific to the community. • ETC

  22. Enterprise Language7.3 UML profile

  23. Information LanguageConcepts

  24. Computational LanguageConcepts

  25. Computational Language Coreography

  26. Computational Language Composition

  27. DataDocument model

  28. Computational languageModel management

  29. Engineering languageBasic concepts

  30. Engineering languageChannels

  31. Engineering languageIdentifiers

  32. Engineering languageCheckpoints

  33. Logical and physical viewpoints

  34. Engineering LanguageEngineering objects

  35. Engineering LanguageClusters and capsules

  36. Engineering LanguageDomains

  37. Engineering LanguageNodes, components and objects

  38. Engineering LanguageDistribution tiers

  39. Technology LanguageModel

  40. Annex BExample specification

  41. StrategicQuestions ODP profile ? UML ITU profile Is UML just used as a meta-language – like BNF? Are ITU and ODP languages compeeting? Have they overlapping application domains? Should ITU and ODP lamguages be better co-ordinated?

  42. DataQuestions Layout Schema Contents Schema External Terminology Schema Concept Schema Internal Terminology Schema Distribution Schema Physical Schema Is ASN.1 least affected? Should ASN.1 be extended by class diagrams? Is ODP Information viewpoint too weak for a Data architecture?

  43. Repetitions and RefinementsQuestions • Is URN an Enterprise Language? • May SDL and MSC be used to specify an Enterprise Viewpoint? • Do SDL and MSC qualify as Computational languages? • May eODL be used to specify every/any correspondence between Viewpoints? • Have we done enough to position the ITU languages within ODP? • Have we ensured compliance? • Is ODP relevant for ITU?

More Related