Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Requirement NameWho proposed the requirementDescriptionWho needs/will need the functionalityStakeholders affected or to be consulted
Provide schema per partes

William Reehil/AT&T

For example, say Sparky just needs to know the attributes of the x node, it should not have to load the entire configuration file in XML format to find out that information. Ideally it should just be able to ask the schema service "What are the attributes of the x node in JSON format?"
  1. Sparky
  2. GraphGraph Chatbot (Future)
  3. GraphGraph UI (Future)
  4. Any mS needing schema information without the need to process whole OXM (lightweight UIs & mS)

Tier 2

Operations Users

Software Engineers

A&AI Onboarders (Devs)


Schema modifications hub

William Reehil  /AT&T

Then taking this a step further we would like to leverage this service to act as the central hub of schema modifications
?

?

Adding schemas at runtime

William Reehil /AT&T

ability to consume new schema dynamically, without downtime
A&AI platform & development architects and Tier 2 to mitigate downtime of the platform when processing new SDC models for clients to interact with.

Every A&AI client

(20+ clients)

Tier 2

Interface support

William Reehil /AT&T

interface to validate proposed schema changes
??
Input format support

William Reehil /AT&T

Ability to import SDC TOSCA/CSAR schemas as well as

ability to provide the schema via flexible document formats (OXM, TOSCA etc.)

A&AI platform & development architects to centralize the authoring/modification of the model across all applications.Chesla Wechsler
Dynamic schema updates

CT Paterson /Amdocs

William Reehil and Manisha Aggarwal /AT&T

Keong Lim / Huawei

Ability do dynamically update schemas in a running schema service without downtime. Changes to the schema are persisted "forever" (assuming even after redeploy).


  1. According to CT Paterson this functionality would be appreciated by an unknown Amdocs customer
  2. According to William Reehil this step is a preparation for "SDC model → A&AI target architecture"
  3. According to Keong Lim it would make development of CCVPN use case easier as changes can be made dynamically
?
Support non-standard schemas

CT Paterson /Amdocs

Support standard and non-standard schemas, as some customers may have different schemas altogether. In terms of usage is related to the requirements Dynamic schema updates

According to Distillation of requirements this functionality would be appreciated by an unknown Amdocs customer


  • No labels