graph

Last updated: 2024-12-22 01:09:47.903141 File source: link on GitLab

graph

This whole package is proposed status and therefore documentation is missing, save for the proposed functionality part.

• Project README

• Release/Build Status

• Changelog

• License

• Contribution Guidelines

• Code of Conduct

• Secure Coding Guidelines

Table of Contents

• graph

  • Table of Contents

  • Specification

    • 1. Description

    • 2. Structure and organisation

    • 3. Class Diagram

      • Source

      • Rendered from source file

    • 4. Functionality

    • 5. Types

    • 6. Testing

    • 7. Proposed Functionality / Requirements

      • List of issues

      • Proposed functionalities

      • Data types

    • 8. References

      • Related research blogs

Specification

Description

TBD

Structure and organisation

TBD

Class Diagram

Source

graph class diagram

Rendered from source file

!$rootUrlGitlab = "https://gitlab.com/nunet/device-management-service/-/raw/main"
!$packageRelativePath = "/dms/orchestrator/graph"
!$packageUrlGitlab = $rootUrlGitlab + $packageRelativePath
 
!include $packageUrlGitlab/specs/class_diagram.puml

Functionality

TBD

Types

TBD

Testing

TBD

Proposed Functionality / Requirements

List of issues

All issues that are filed in GitLab related to the implementation of dms/orchestrator package can be found below. These include any proposals for modifications to the package or new functionality needed to cover the requirements of other packages.

• All issues mentioning Graph in this milestone

Proposed functionalities

TBD

Data types

• proposed LocalNetworkTopology more complex deployments may need a data structure, which considers local network topology of a node / dms -- i.e. for reasoning about speed of connection (as well as capabilities) between neighbors.

References

Related research blogs

TBD