+ONAP has two application level configuration and lifecycle management modules
+called SDN-C and App-C. Both provide similar services (application level
+configuration using NetConf, Chef, Ansible, RestConf, etc.) and lifecycle
+management functions (e.g., stop, resume, health check, etc.).
+They share common code from CCSDK repo. However, there are some differences
+between these two modules (SDN-C uses CDS only for onboarding and
+configuration / LCM flow design, whereas App-C uses CDT for the LCM functions
+for self service to provide artifacts storing in App-C Database).
+SDN-C has been used mainly for Layer1-3 network elements and App-C is
+being used for Layer4-7 network functions. This is a very loose
+distinction and we expect that over time we will get better alignment and
+have common repository for controller code supporting application level configuration
+and lifecycle management of all network elements (physical or virtual, layer 1-7).
+Because of these overlaps, we have documented SDN-C and App-C together.
+ONAP Controller Family (SDN-C / App-C) configures and maintains the health of L1-7
+Network Function (VNF, PNF, CNF) and network services throughout their lifecycle:
+
+- Configures Network Functions (VNF/PNF)
+- Provides programmable network application management platform:
+
+ - Behavior patterns programmed via models and policies
+ - Standards based models & protocols for multi-vendor implementation
+ - Extensible SB adapters such as Netconf, Ansible, Rest API, etc.
+ - Operation control, version management, software updates, etc.
+- Local source of truth
+ - Manages inventory within its scope
+ - Manages and stores state of NFs
+ - Supports Configuration Audits
+
+Controller Design Studio (CDS)
+------------------------------