1 / 11

Enhancing UML Diagrams for NML Working Group: A Comparative Analysis of Basic Classes

This document captures the brainstorming session of the NML Working Group focusing on UML diagrams and the comparison of basic class structures in different frameworks such as PerfSONAR, NDL, and cNIS. We explore the extension of basic classes using layer-specific information, the grouping of classes including nodes, interfaces, links, locations, and services, and various relationship types. The discussion includes considerations for maintaining the path within group classifications and the next steps for defining schema classes, validation, and tool selection for effective schema development.

hernando-norales
Download Presentation

Enhancing UML Diagrams for NML Working Group: A Comparative Analysis of Basic Classes

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. NML-WG discussion NML-WG: Monday brainstorming

  2. UML diagrams comparison Basic classes are further extended by using Layer information: • PerfSONAR basic classes: • Domain Node Port Link Path Network Service Location • NDL basic classes: • Administrative_domain Network_domain Device Interface Link Location Service • cNIS basic classes: • (generic) Node Link Interface Location. (Concept of basic class grouping to allow description of domains, networks, etc) NML-WG: Monday brainstorming

  3. Common classes Common classes: • Group (specialized with well known names: group type= administrative domain, network domain, path etc.) • Node/Device • Interface/Port • Link • Location • Service NML-WG: Monday brainstorming

  4. Group Group = abstract type that becomes specialized depending on elements we put it. Ordered and unordered group: General Path (a specialized ordered group): *** Link path: Domain path: Loose path: Domain (a specialized unordered group): Network domain Administrative domain VLAN domain *** do we want to keep Path in here (as it is the only type of ordered group we can think about) or should be moved out of Group (only unordered) NML-WG: Monday brainstorming

  5. Node/device Node: *** *** Extension of this class with layer-specific information might follow (layer1, layer2, layer3 node ….) NML-WG: Monday brainstorming

  6. Interface/port Interface/port: *** Every interface belongs to a node (for interdomain links the far end node may be unknown) Layer1 interface Fiber interface OTN interface …. Layer2 interface SONET interface Ethernet interface ….. Layer3 interface IPv4 interface ….. *** Are technology-specific interfaces (I.e Ethernet interface) subclasses of the layer interfaces (I.e. Layer2 interface) or subclasses of the generic interface? NML-WG: Monday brainstorming

  7. Link Link: • composed of two interfaces (start and end); • links are unidirectional; • links can/are hierarchically organized (a layer3 link = sum of to layer 2 links) *** • concept of link aggregation (serial links and parallel links) • Can be recursive *** how do Links and Paths (Link paths) relate to each other? Is the first a physical object and the second a logical object? NML-WG: Monday brainstorming

  8. Location Location: - Describe a physical point in space (by using geo-coords, street names ….) - A Node is one Location at the time, Links can pass through multiple Locations (I.e. they go through an ordered group of geo-coords) NML-WG: Monday brainstorming

  9. Service Service: Application service Network service ….. Are services offered at a Domain level (with Domain being a Group of Nodes) or by a Node or an Interface directly? What is the distinction between a Service and a capability? NML-WG: Monday brainstorming

  10. Common relationships How the classes related to each other: concept of one-to-one, one-to-many and many-to-one, any-to-any. Comprises, composed of, …are relationship blocks. One to one: One-to-many: Many-to many: Any-to-any: ‘self recursive’ and ‘composed of’. Are these are two distinguished ideas? self recursive is not a group; composed of represents a many to many relationship and is described by a group. NML-WG: Monday brainstorming

  11. Next steps • Definition of basic NML-WG schema classes and attributes • Validation against existing usecases • Which tools we will use to actually produce/write/develop the schema? • UML diagrams • RDF and XML as exchange formats: translations tools between the two. Best practice representation in RDF and XML of the basic ontologies. Adopters are free to choose other syntaxes as they wish. NML-WG: Monday brainstorming

More Related