Page History

...

• ONAP R4+ Per-Project Models and API Specs
  • A&AI IM Reverse Engineering
    • Highlights of call on this topic briefly reviewed, including
      • Discussion and review of a 
      Reviewed and discussed a
      • 'graph graph' depiction of the A&AI model from some time ago.
      Also discussed
      • Discussed the 'model browser', which provides more of an attribute level view.  This tool converts json to UML
      • Previous attempts to run A
      tool that could convert json to uml
      • &AI model throught this tool were not successful
    • An alternative is to focus on key nodes, like Vnf Instance, and other nodes perhaps other nodes a hope away, and analyze, either with tools or manually.
    • Could we try Idea of trying to convert with a smaller file ?was discussed
• Use Case to Model Discussion
  • Ben presented evolving deck on this topic.
  • Discussed involvement of the project teams, ideally co-developing the IM model, refinements to the IM per feedback during build of the data model
  • Discussion of what words to use - launch, freeze, clean, approve, under change control versus will not change
  • Modeling swimlane was established for modeling team.   Model is implicitly information model
  • Data model goes under project team in swimlane
  • Items we want to track include
    • information model
    • data model
    • API
    • Code
  • It is important that the project team is engaged in the IM development
  • Ben will socialize with other teams regarding best terms to use.