Add non functional requirement table for guilin

Issue-ID: INT-1776

Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: Iff17dc50cefb9c4fc5a9e752c560b98b35974129
[Update status of my requirements]
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>

1 files changed, 3 insertions, 20 deletions

diff --git a/docs/docs_usecases.rst b/docs/docs_usecases.rst
index f86fc6b11..a8efb0d63 100644
--- a/docs/docs_usecases.rst
+++ b/docs/docs_usecases.rst
@@ -5,24 +5,7 @@
 
 :orphan:
 
-Deprecated Use Cases and Functional Requirements
-================================================
+.. toctree::
+   :maxdepth: 1
 
-Each ONAP release deals with lots of use cases and functional requirements.
-When possible, it is strongly recommended to automate the use cases.
-In this case Integration team can take over the maintenance part of the use case.
-If not automated, the use cases are fully under the responsibility of the use
-case team and usually valid for the release the team was involved in.
-However, these use cases, their artifacts remain in the repository.
-Anyone can give a try even if the use cases are no more supported.
-
-This section deals with such use cases.
-These use cases have been part of one release but have not been tested on the
-last releases. They might fully deprecated or usable through minor adaptations.
-The entry points are the use case owners.
-
-.. csv-table:: deprecated use case table
-    :file: ./files/csv/usecases-deprecated.csv
-    :widths: 50,20,10,20
-    :header-rows: 1
-    :delim: ;
+   usecases/deprecated_usecases.rst