R7 Guilin Architecture Review (template) - functional requirements

• Open

  

Brief Project Overview (brief as it should be known)

(Referenced to existing documentations is highly encouraged for the purpose of keeping this document up to date)

New component capabilities for Guilin, i.e. the functional enhancements, if applicable

New or modified interfaces

If they are modified, are they backwards compatible?

Interface naming (point to an example)

Consumed API from other projects

Published API

Reference to the interfaces.

(Reference to the the swagger.json file(s) whenever possible)

What are the system limits?

.

Involved use cases, architectural capabilities or functional requirements.

Listing of new or impacted models used by the project (for information only).

• Identify any High Level Information Model Requirements.   See: ONAP R7 Modeling High Level Requirements

  • Models based on information exchanges from Use Cases

  • Models documenting existing implementations

  • Forward looking models that may be implemented in future releases

• Describe how exposed APIs are mapped to information models

(list all the relevant Jira tickets)

Any other details that are specific to this functional enhancement or UseCase.