Page Comparison

1- Brief Project Overview (brief as it should be known)

NBI stands for NorthBound Interface. It brings to ONAP a set of APIs that can be used by external systems such BSS for example. These APIs are based on TMForum and MEF

...

APIs

2- New component capabilities for

...

Honolulu-R8, i.e. the functional enhancements, if applicable

There are no planned Enhancement features for Honolulu, minor bug fix only.

3- New or modified interfaces

None

4- If they are modified, are they backwards compatible?

Not applicable, no modifications

6- Interface naming (point to an example)

https://docs.onap.org/projects/onap-externalapi-nbi/en/latest/offeredapis/offeredapis.html

7- Consumed API from other projects

8- Published API

9- Reference to the interfaces.

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

10- What are the system limits?

.

11- Involved use cases, architectural capabilities or functional requirements.

12- 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)

13-Test plan/Testing Strategy

1. Unit Testing
2. Dev-to-Dev Testing  and
3. Integration
   

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

1. Project Overview

NBI stands for NorthBound Interface. It brings to ONAP a set of APIs that can be used by external systems such BSS for example. These APIs are based on TMForum and MEF APIs 

1. Improvement to external swagger documentation with reference to ONAP API style guidelines

1. New or modified interfaces

   1. Modified : Service Order - additional internal support for macromode and activate/deactivate SO APIs

...