In MongoDB this is the equivalent of RDBMS tables.  A Collection stores data in the form of JSON documents.  Other NoSQL document databases may call them 'Tables' still  And others call them 'Buckets'.


A set of Collections/Tables/Buckets


One of the outputs of the application.  In HTML, Markdown, or PDFformat.  It is dynamically generated by the application.

Entity Relationship diagram

The visual representation of the Collections and the possible Relationships between their fields.


Attributes of a Collection document.  These are simple attribute, as compared to Objects.

Hierarchical schema view

Hierarchical representation of a JSON document schema.

JSON Schema

JSON document describing the characteristics and constraints of another JSON document.  Similar to how an XSD schema describes an XML document.  More information regarding this standard can be found on


The atomic entity gathering all the concepts described herein and their related information.  The data about the model can be stored, retrieved, edited, documented.


Complex attributes such as arrays and sub-documents.


Detailed information about an entity: Database, Collections, Fields and Objects, and Relationships.  


This information is not explicitly declared in a NoSQL document database or application API.  The capability is however provided here to enrich the documentation and general comprehension of the model.  It describes the logical links between Fields of different Collections and their cardinality


Data example that are used to illustrate how a Field can be used.


The structure of Collections, as defined in JSON Schema and extensions.  It is an output of the application, to be used along with a validator to insure compliance of documents being submitted to storage in MongoDB Collections.


Another output of the application.  Starting with the upcoming version 3.2 of MongoDB, it is allowed to create validation rules associated with each Collection.