mrichomme | 59305b4 | 2020-12-01 18:23:57 +0100 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 |
| 2 | International License. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| 4 | .. _deprecated_usecases: |
| 5 | |
| 6 | :orphan: |
| 7 | |
| 8 | Deprecated Use Cases and Functional Requirements |
| 9 | ================================================ |
| 10 | |
| 11 | Each ONAP release deals with lots of use cases and functional requirements. |
| 12 | When possible, it is strongly recommended to automate the use cases. |
| 13 | In this case Integration team can take over the maintenance part of the use case. |
| 14 | If not automated, the use cases are fully under the responsibility of the use |
| 15 | case team and usually valid for the release the team was involved in. |
| 16 | However, these use cases, their artifacts remain in the repository. |
| 17 | Anyone can give a try even if the use cases are no more supported. |
| 18 | |
| 19 | This section deals with such use cases. |
| 20 | These use cases have been part of one release but have not been tested on the |
| 21 | last releases. They might fully deprecated or usable through minor adaptations. |
| 22 | The entry points are the use case owners. |
| 23 | |
| 24 | .. csv-table:: deprecated use case table |
| 25 | :file: ../files/csv/usecases-deprecated.csv |
| 26 | :widths: 50,20,10,20 |
| 27 | :header-rows: 1 |
| 28 | :delim: ; |