...
| Requirements Name | Who proposed the requirement | Description | Who needs/will need the functionality | Stakeholders 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?" | maybe Sparky? | ? | ||||
| 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 | ? | ? | ||||
| 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
| ?? | Chesla Wechsler | ||||
| Dynamic schema updates | Ability do dynamically update schemas in a running schema service without downtime. Changes to the schema are persisted "forever" (assuming even after redeploy). |
| ? | SDC schema import | William Reehil /AT&T | Ability to import SDC TOSCA/CSAR schemas | ?Chesla Wechsler | |
| 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 |
...