Add Human Interfaces Doc

Change-Id: I36675bc2940cc12ab6d48e3be8da7b8e5a5e49c9
Issue-ID: HOLMES-66
Signed-off-by: GuangrongFu <fu.guangrong@zte.com.cn>

1 files changed, 11 insertions, 2 deletions

diff --git a/docs/platform/human-interfaces.rst b/docs/platform/human-interfaces.rst
index e8501d0..d73c6cc 100644
--- a/docs/platform/human-interfaces.rst
+++ b/docs/platform/human-interfaces.rst
@@ -3,13 +3,22 @@
 
 Human Interfaces
 ----------------
-Provide info on the targeted user, interface types, ports/protocols to access, etc.
 
 Target Users
 ^^^^^^^^^^^^
 
+The human interfaces provided in the Amsterdam release by Holmes is intended for the developers rather than the end users.
+
 Interface Type
 ^^^^^^^^^^^^^^
 
+The interfaces of Holmes is more like a Swagger GUI, which is supported by MSB and used by the developers or system engineers for debugging or testing. They could use the GUI instead of the ``curl`` command or Postman to call the RESTful APIs of Holmes.
+
 Access
-^^^^^^
\ No newline at end of file
+^^^^^^
+
+Go to the MSB interface with a browser, using the address ``http://${msb-ip}:${msb-port}/iui/microservices/default.html``. Select the "API Service" tab (which is opened by default), then you can see all the registered microservices. Click on the microservice block of which the name is *holmes-rule-mgmt* and the APIs will be displayed in the browser. Select the corresponding interface and details will be expanded. Users could use the interface to send http request to the Holmes server to perform health check or other operations on the rules.
+
+.. image:: images/swagger-gui-for-holmes.png
+
+**Direct calling of the APIs in the engine management module of Holmes is not recommended becasue it would cause data inconsistency between the rule managment module and the engine management module. All rules related operations should be only conducted on the rule management module.**