From c7ea2f2aa6d184139c346293a14b8564304acc05 Mon Sep 17 00:00:00 2001 From: Ben Hepworth Date: Thu, 3 Oct 2024 16:06:51 -0600 Subject: [PATCH 1/2] Add QoS Profile User Story --- .../API_documentation/QoSProfile_User_Story.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 documentation/API_documentation/QoSProfile_User_Story.md diff --git a/documentation/API_documentation/QoSProfile_User_Story.md b/documentation/API_documentation/QoSProfile_User_Story.md new file mode 100644 index 0000000000..23211ada96 --- /dev/null +++ b/documentation/API_documentation/QoSProfile_User_Story.md @@ -0,0 +1,10 @@ +# Quality-Of-Service-Profile (QoS Profile) User Story + +| **Item** | **Details** | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **_Summary_** | As an application developer, I want to be able to query the list of available Quality of Service (QoS) profiles. I can then use use one of the Qos Profiles to start a Quality On Demand (QoD) session with a Communication Service Provider (CSP). The QoS profile contains information regarding network requirements for an application such as stable latency or throughput. | +| **_Roles, Actors and Scope_** | **Roles:** Customer:Developer

**Actors:** Application service providers, hyperscalers, application developers.

**Scope:** | +| **_Pre-conditions_** | The preconditions are listed below:
  1. Customer:Developer is eligible to use the QoS Profile API, i.e. the Customer has successfully subscribed to the QoS Profile API on the platform of an API Provider
  2. The customer application has requested and received an access token for the required scopes of the API. Which specific authorization flows are to be used will be determined during onboarding process.
| +| **_Activities/Steps_** | **Starts when:** The customer application either makes a POST to retrieve the list of available QoS Profiles or a GET to see the individual details of a QoS Profile.

**Ends when:** When the user identifies the QoS Profile to use when creating a QoD session. | +| **_Post-conditions_** | None - this is an immutable API. | +| **_Exceptions_** | Several exceptions might occur during the QoS Profile API operations
- Unauthorized: Not valid credentials (e.g. use of already expired access token).
- Invalid input: Not valid input data to invoke operation (e.g. IP address format not as expected). | From e6db39f6d89f23ef7abe843d3247df07e32ff5f6 Mon Sep 17 00:00:00 2001 From: Ben Hepworth Date: Fri, 4 Oct 2024 06:30:34 -0600 Subject: [PATCH 2/2] Update from Application:Developer to API Consumer:Developer to align with Commonalities --- documentation/API_documentation/QoSProfile_User_Story.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/API_documentation/QoSProfile_User_Story.md b/documentation/API_documentation/QoSProfile_User_Story.md index 23211ada96..d1e1184ee2 100644 --- a/documentation/API_documentation/QoSProfile_User_Story.md +++ b/documentation/API_documentation/QoSProfile_User_Story.md @@ -3,8 +3,8 @@ | **Item** | **Details** | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **_Summary_** | As an application developer, I want to be able to query the list of available Quality of Service (QoS) profiles. I can then use use one of the Qos Profiles to start a Quality On Demand (QoD) session with a Communication Service Provider (CSP). The QoS profile contains information regarding network requirements for an application such as stable latency or throughput. | -| **_Roles, Actors and Scope_** | **Roles:** Customer:Developer

**Actors:** Application service providers, hyperscalers, application developers.

**Scope:** | +| **_Roles, Actors and Scope_** | **Roles:** API Consumer:Developer

**Actors:** Application service providers, hyperscalers, application developers.

**Scope:** | | **_Pre-conditions_** | The preconditions are listed below:
  1. Customer:Developer is eligible to use the QoS Profile API, i.e. the Customer has successfully subscribed to the QoS Profile API on the platform of an API Provider
  2. The customer application has requested and received an access token for the required scopes of the API. Which specific authorization flows are to be used will be determined during onboarding process.
| -| **_Activities/Steps_** | **Starts when:** The customer application either makes a POST to retrieve the list of available QoS Profiles or a GET to see the individual details of a QoS Profile.

**Ends when:** When the user identifies the QoS Profile to use when creating a QoD session. | +| **_Activities/Steps_** | **Starts when:** The customer application either makes a POST to retrieve the list of available QoS Profiles or a GET to see the individual details of a QoS Profile.

**Ends when:** When the API Consumer:Developer identifies the QoS Profile to use when creating a QoD session. | | **_Post-conditions_** | None - this is an immutable API. | | **_Exceptions_** | Several exceptions might occur during the QoS Profile API operations
- Unauthorized: Not valid credentials (e.g. use of already expired access token).
- Invalid input: Not valid input data to invoke operation (e.g. IP address format not as expected). |