| Standard id | Standard | Clasification |
|---|---|---|
| DAT.DM.001 | Use latest version of DBMS to serve business and technical requirements. • Recommended RDBMS are o IBM DB2 o MariaDB o Mysql o Oracle o Postgresql o SQL Server and o Other popular and reliable DBMS • Recommended NoSQL: o Cassandra o HBase o MongoDB and o Other popular and reliable NoSQL • Recommended Distributed DBMS: o CockroachDB and o Other popular and reliable distributed DBMS |
Mandatory |
| DAT.DM.002 | Use DBMS that supports ODBC for non-Java based applications. As ODBC drivers are implemented by various vendors, it would be advisable to identify DBMS that support the latest stable version of the ODBC. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.DD.001 | Use one or more of the following notations for data modelling: (a) Unified Modelling Language (UML) (b) Barker's Notation (c) Information Engineering. |
Recommended |
| DAT.DD.002 | Use Unicode standard to support the worldwide. | Mandatory |
| DAT.DD.003 | Use CCDS (Citizen Core Data Structure) to manage citizen profile. CCDS is maintained by cabinet division. https://cabinet.gov.bd/site/page/ed80fa01-4477-4d43-99ac-5d836dadb3a1/ |
Mandatory |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.ELT.001 | ELT tools should be used in scenarios where large amounts of data need to be moved, transformed, enriched, and/or merged from multiple data sources to a target source. An example of this is the loading of data from source systems into a data warehouse. | Recommended |
| DAT.ELT.002 | ELT processes should be scheduled so that they do not impact the operations and end users of the source systems they are extracting from. | Recommended |
| DAT.ELT.003 | The ELT process should encourage to move the data from the source to the ELT environment quickly and should access the source only once. The target architecture should ensure re-use of a single data copy from production sources to minimize resource utilization on the source system. | Recommended |
| DAT.ELT.004 | The artefacts of ELT processes (e.g., scripts, SQL code, data mappings, etc.) should be kept in a repository and managed so that lineage of the data produced from those processes is traceable. | Recommended |
| DAT.ELT.005 | ELT processes should encourage use of a centralized metadata repository to ensure data quality and integrity. | Recommended |
| DAT.ELT.006 | ELT processes should provision for a facility to perform standard centralized data quality checks with required and optional checks which may be decided by the target system. | Recommended |
| DAT.ELT.007 | ELT processes should provision for a storage mechanism for clean data thus eliminating the need for new processes to re-source data recheck values or re-compute derived values. | Recommended |
| DAT.ELT.008 | Whenever applied, ELT tool should be preferred over ETL tools. | Mandatory |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.ETL.001 | ETL tools should be used in scenarios where large amounts of data need to be moved, transformed, enriched, and/or merged from multiple data sources to a target source. An example of this is the loading of data from source systems into a data warehouse. | Recommended |
| DAT.ETL.002 | ETL processes should be scheduled so that they do not impact the operations and end users of the source systems they are extracting from. | Recommended |
| DAT.ETL.003 | The ETL process should encourage to move the data from the source to the ETL environment quickly and should access the source only once. The target architecture should ensure re-use of a single data copy from production sources to minimize resource utilization on the source system. | Recommended |
| DAT.ETL.004 | The artefacts of ETL processes (e.g., scripts, SQL code, data mappings, etc.) should be kept in a repository and managed so that lineage of the data produced from those processes is traceable. | Recommended |
| DAT.ETL.005 | ETL processes should encourage use of a centralized metadata repository to ensure data quality and integrity. | Recommended |
| DAT.ETL.006 | ETL processes should provision for a facility to perform standard centralized data quality checks with required and optional checks which may be decided by the target system. | Recommended |
| DAT.ETL.007 | ETL processes should provision for a storage mechanism for clean data thus eliminating the need for new processes to re-source data recheck values or re-compute derived values. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.MM.001 | Element: Element description. | Recommended |
| DAT.MM.002 | Creator : Person or organization primarily responsible for creating the intellectual content of the resource-e.g., authors in the case of written documents, and artists, photographers, etc. in the case of visual resources. | Recommended |
| DAT.MM.003 | Publisher : The entity (e.g., agency, including unit/branch/section) responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. | Recommended |
| DAT.MM.005 | Rights Management : A rights management statement or an identifier that links to a rights management statement. | Recommended |
| DAT.MM.006 | Title : The name given to the resource, usually by the creator or publisher. | Recommended |
| DAT.MM.007 | Subject : The topic of the resource. Typically, this will be expressed as keywords or phrases that describe the subject or content of the resource. Controlled vocabularies and formal classification schemes are encouraged. | Recommended |
| DAT.MM.008 | Date : A date associated with the creation or availability of the resource. | Recommended |
| DAT.MM.009 | Identifier : A string or number used to uniquely identify the resource. Examples for networked resources include URLs, Purls, and URNs. ISBN or other formal names can be used. | Recommended |
| DAT.MM.010 | Description : A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. | Recommended |
| DAT.MM.011 | Source : The work, either print or electronic, from which this object is derived (if applicable). Source is not applicable if the present resource is in its original form. | Recommended |
| DAT.MM.012 | Language : The language of the intellectual content of the resource. | Recommended |
| DAT.MM.013 | Relation : Relationship to other resources-e.g., images in a document, chapters in a book, or items in a collection. | Recommended |
| DAT.MM.014 | Coverage : Spatial locations and temporal duration characteristic of the resource. | Recommended |
| DAT.MM.015 | Type : The category of the resource, such as home page, novel, poem, working paper, technical report, essay, or dictionary. | Recommended |
| DAT.MM.016 | Format : The data format of the resource, used to identify the software and possibly hardware that might be needed to display or operate the resource-e.g., postscript, HTML, TXT, JPEG, or XML. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.DS.001 | Prepare a data classification document following Data Protection Act of Bangladesh. | Mandatory |
| DAT.DS.002 | Use cryptographic techniques for encryption of sensitive data. The reference standards for cryptography include Advance Encryption Standard (AES) with minimum 256 bits key strength. | Mandatory |
| DAT.DS.003 | Databases should not be accessible directly from external network. | Mandatory |
| DAT.DS.004 | Use Security controls to ensure aggregation (value of disclosed data) and inference (confidentiality). | Mandatory |
| DAT.DS.005 | Use DBMS that supports at least the following security controls: (a) Data access as an intended privilege (b) Key management and encryption (c) Integrity constrains such as domain constraints, attribute constraints, relation constraints, and database constraints (d) High availability implementation, backup, restoration and data replication (e) Database log and policy enforcement |
Mandatory |
| DAT.DS.006 | Data destruction shall be done using degaussing (NIST 800-88 guidelines for Media Sanitization), data overwriting (Bruce chneier algorithm, DOD 5220.22-M, Peter Gutmann Secure Deletion) etc. | Mandatory |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.DBA.001 | Data Archiving shall support integrity checking through hashing, audit logging and regulatory compliance. | Mandatory |
| DAT.DBA.002 | Strict security policies should be established for archived data to prevent unauthorized access and data loss. | Mandatory |
| DAT.DBA.003 | Use ISO 15489-1 for records management. | Recommended |
| DAT.DBA.004 | Use the Dublin Core metadata element set for resource description based on ISO 15836. | Recommended |
| DAT.DBA.005 | Use portable document format for document management based on ISO 32000-1. | Recommended |
| DAT.DBA.006 | Use ISO/TR 18492 for long-term preservation of electronic document-based information. | Recommended |
| DAT.DBA.007 | Use Open Archival Information System (OAIS) to establish a system for archiving information for both digitalized and physical. This framework is based on ISO 14721. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.MSEB.001 | Use XML Schemas 1.0 and above or JSON schema 01 or above to manage and overall Enterprise Schema. | Mandatory |
| DAT.MSEB.002 | Use Metadata Object Facility (MOF) to define, manipulate and integrate metadata and data in a platform independent manner. | Mandatory |
| DAT.MSEB.003 | Support Resource Description Framework (RDF) framework for describing and interchanging metadata based on resource, properties and statements definitions. | Recommended |
| DAT.MSEB.004 | Support Common Warehouse Metamodel (CWM) to enable interchange of warehouse and BI metadata between warehouse tools, warehouse platforms and warehouse Metadata repositories in distributed heterogeneous environments. | Recommended |
| DAT.MSEB.005 | Support Common Warehouse Metamodel Metadata Interchange Patterns to add semantic context to the interchange of Metadata in terms of recognized sets of objects or object patterns. | Recommended |
| DAT.MSEB.006 | Use the set of standards produced by ISO/TC 211 that supports the understanding and usage of geographic information. | Recommended |
| DAT.MSEB.007 | Support Open Geospatial Consortium (OpenGIS) Simple Feature that provides a way for application to access spatial data in RDBMS. There are three standards available – CORBA, SQL and OLE/COM. | Recommended |
| DAT.MSEB.008 | Use Open GIS Geography Markup Language Encoding Standard (GML 2, GML 3) for transfer and storage of geographic information. | Recommended |
| DAT.MSEB.009 | Support Open GIS Web Map Service (WMS), Web Feature Services (WFS) and Web Coverage Service (WCS) specifications which specify protocols that provide uniform access by HTML clients to maps rendered by WMS enabled map servers on the internet. | Recommended |
| DAT.MSEB.010 | Support Open GIS Catalogue Services Interface Standards (CAT) to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. | Recommended |
| DAT.MSEB.011 | Support Open GIS Keyhole Markup Language (KML) Service for geographic visualization, including annotation of maps and images. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.BIG.001 | Follow ISO/IEC TR 20547 to describe the framework of the big data reference architecture and the process. | Mandatory |
| DAT.BIG.002 | Follow ISO/IEC TR 20547 to provide examples of big data use cases with application domains and technical considerations. | Mandatory |
| DAT.BIG.003 | Follow ISO/IEC TR 20547 to specify security and privacy aspects applicable to the big data reference architecture (BDRA). | Mandatory |
| DAT.BIG.004 | Follow ISO/IEC TR 20547 to define two architectural viewpoints (user view and functional view) of big data ecosystem. | Mandatory |
| Standard id | Standard | Clasification |
|---|---|---|
| DAT.IDES.001 | Use Extensible Markup Language (XML 1.0 or XML1.1) as a preferred data exchange standard. | Recommended |
| DAT.IDES.002 | Support the following standards for exchange of textual data: (a) Extensible Markup Language (XML 1.0 or XML 1.1) for most applications. (b) Support Comma Separated Value (CSV) for legacy applications. (C) Support JSON formatted data. |
Recommended |
| DAT.IDES.003 | Support the following standards for exchange of image data: (a) Joint Photographic Experts Group (JPEG) for photography images. (b) Graphics Interchange Format (GIF) for internet images due to its small size and support for animation. (c) Tagged Image File Format (TIFF) for scanned Images. (d) Portable Network Graphic (PNG) for internet images which require increased color depth compared to GIF. |
Recommended |
| DAT.IDES.004 | Support the following standards for exchange of video and audio data: (a) Moving Pictures Expert Group (MPEG-1 to MPEG-4) for most audio and video applications. (b) 3rd Generation Partnership Project (3GPP and 3GPP2) for audio and video over 3G mobile Networks. |
Recommended |
| DAT.IDES.005 | Support the file transfer through client file transfer and Server File transfer – FTP server. | Recommended |
| DAT.IDES.006 | Use Web Service Description Language as an XML based interface definition language to describing the functionality offered by a SOAP web service | Recommended |
| DAT.IDES.007 | Use Web Services Security (WS-Security, WSS) as an extension to SOAP (Simple Object Access protocol) to apply security to Web services | Recommended |
| DAT.IDES.008 | Use JSON as a Integration framework for defining, interchanging, manipulating and integrating JSON data and objects. | Recommended |
| DAT.IDES.009 | Use JSON_QUERY for selecting nodes from an JSON document. | Recommended |
| DAT.IDES.010 | Use JSON_QUERY to design query collections for XML data. | Recommended |
| DAT.IDES.012 | Use Message queues and mailboxes for inter-process communication (IPC), or for inter-thread communication within the same process. | Recommended |
| DAT.IDES.013 | Use directory service to stores, organizes, and provides access to information in a computer operating system's directory. | Recommended |