6 files changed, 53 insertions, 0 deletions
diff --git a/docs/state/development/design/index.rst b/docs/state/development/design/index.rst
deleted file mode 100644
index e69de29..0000000
--- a/docs/state/development/design/index.rst
+++ /dev/null
diff --git a/docs/state/development/index.rst b/docs/state/development/index.rst
new file mode 100644
index 0000000..7d1881f
--- /dev/null
+++ b/docs/state/development/index.rst
@@ -0,0 +1,47 @@
+=========================
+SDVState Developer Guide
+=========================
+
+The Top-level directory of consists following flies:
+
+.. code-block:: bash
+
+    sdvstate
+    ├── core
+    ├── settings
+    ├── tools
+    ├── validator
+    ├── state
+    ├── server
+    └── dockerfile
+
+``state`` is the entry point of the SDVState testing tool.
+
+``validator`` consists of different implementations of sdvstate tool. For example, one implementation can be for validation of Airship while others can validate TripleO, Kuberef and so on.
+
+``tools`` consists of any third party utilities code or other tools utilites maintained by the project.
+
+``settings`` consists of a bunch of yaml files with default configuration parameters used by SDVState tool. These settings can be overridden by the user in their conf-file. Precedence of settings loaded by SDVState tool: ``cli > env > conf-file > settings-dir``. Have a look at :doc:`settings tool <settings>` to see how settings are managed across SDVState tool.
+
+``core`` consists of all other code used to build the SDVState tool itself like displaying Reports, loading PDFs, etc..
+
+Managing Results
+^^^^^^^^^^^^^^^^
+SDVState maintains result-api module for managing results of checks. Located at ``sdvstate/tools/result_api``. Have a look at :doc:`Result API documentation <result_api>`
+
+Result of every check should have the format:
+
+.. code-block:: bash
+
+  {
+        "case_name": "name_of_check",
+        "category": "storage",
+        "criteria": "pass",
+        "details": { .. any number of values ..}
+  }
+
+Where criteria must be either ``pass`` or ``fail``. While ``details`` can have any value or values related to results. All four keys are mandatory while reporting the results of individual checks.
+
+All results are stored in ``results.json`` file which consists an array of check results.
+
+Note one of the result items in an array is the overall result which consists summary of all checks. It also consists of other details and matches the format of TestAPI of OPNFV. These are also the values that are exported to TestAPI by the tool.
+\ No newline at end of file
diff --git a/docs/state/development/overview/index.rst b/docs/state/development/overview/index.rst
deleted file mode 100644
index e69de29..0000000
--- a/docs/state/development/overview/index.rst
+++ /dev/null
diff --git a/docs/state/development/overview/result-api-architecture.png b/docs/state/development/result-api-architecture.png
index e464187..e464187 100644
--- a/docs/state/development/overview/result-api-architecture.png
+++ b/docs/state/development/result-api-architecture.png
diff --git a/docs/state/development/overview/result_api.rst b/docs/state/development/result_api.rst
index 6412c7d..6412c7d 100644
--- a/docs/state/development/overview/result_api.rst
+++ b/docs/state/development/result_api.rst
diff --git a/docs/state/development/overview/settings.rst b/docs/state/development/settings.rst
index 29068c5..806a29a 100644
--- a/docs/state/development/overview/settings.rst
+++ b/docs/state/development/settings.rst
@@ -36,3 +36,9 @@ all it’s sub-directory recursively in ascending order, hence if a
 configuration item exists in more than one file, then the setting in the
 file that occurs in the last read file will have high precedence and
 overwrite previous values. .
+
+
+Managing Settings
+^^^^^^^^^^^^^^^^^
+- Get ``value`` of ``key`` using ``settings.getValue(key)``
+- Set ``key, value`` using ``settings.setValue(key, value)``
+\ No newline at end of file