The DIDO Data Manipulation Language (DDML) is similar in functionality to the Data Manipulation Language (DML) found in Relational DataBase Management System (RDBMS). Its purpose is to manipulate the content of a DIDO (i.e., STORE) or to make queries about the content of the DIDO (i.e., SELECT)
The DIDO Data Definition Language (DDDL) is similar in functionality of the Data Definition Language (DDL) found in Relational Database Management System (RDBMS). Its purpose is to define the objects stored within the DIDO including the types, objects, oracles, exchanges, and aggregates, and smart contracts. DDDL Commands 2.4.1 DEFINE CONSTANT Command 2.4.2 CREATE TYPE …
What is the DIDO Data Definition Language (DDDL)? Read More »
The DIDO Lifecyle Language (DDLL) is responsible for controlling the Lifecycle of the DIDO instances distributed across the Nodes in the DIDO Network. The DDLL does not cover the System Lifecycle which is responsible for the system conception, design and development, production and/or construction, distribution, operation, maintenance and support, retirement, phase-out and disposal. Although there …
Below is a list of language constructs that might be useful for DIDO CLI implementation. JSON dido:public:s_cli:05_contents:01_prt:03_langconst:basic_dido_objects:json: Args Links Traces Block Class Call Contract Event JSON Log Class TOKEN Trace Transaction Class Naming Conventions Reserved Words Operators Operations Basic Types Constants Memory and Storage Basic DIDO Objects
A Distributed Immutable Data Objects (DIDO), by definition, is a Distributed System comprised of a network and a collection of nodes particpating in a Peer to Peer (P2P) network. Each node within the DIDO operates asynchronously and independently from all the others nodes. The nodes communicate changes in the state of the distributed objects managed …
The acronym DIDO stands for Distributed Immutable Data Object. It represents a class of concepts, activities and products that have become the trend Each word within the name is important Distributed – the class is distributed across many computers Immutable – the data it represents once written can not be changed (write once, read many …
An important part of having functional and non-functional requirements is access to a particular effort to determine if the effort complies with the requirements. The approach is slightly different between Functional and Non-Functional requirements. For Functional Requirements, it is important to think about what requirements need to be covered for a particular effort. For example, …
How to Assesses Functional and Non-Functional Requirements Read More »
Non-functional requirements are often incorrectly assumed rather than being explicitly defined by users. This can lead to problems towards the end of a project as the user expectations for non-functional requirements are not met. Many times, the developers dismiss non-functional requirements as non-testable and therefore not enforceable. This lack of specificity in non-functional requirements sets …
Functional Requirements define the basic system behavior. Essentially, they are requirements stating what the system does or must not do, and can be thought of in terms of how the system responds to inputs. Functional requirements usually define if/then behaviors and include calculations, data input, and business processes. Functional Requirements are features that allow the …
The term requirement first appeared in software engineering in the 1960s.1) The Business Analysis Body of Knowledge® version 2 from IIBA (BABOK),2) defines a requirement as having one or more of the following characteristics: A condition or capability needed by a stakeholder to solve a problem or achieve an objective. A condition or capability that …
A community based testing environment for the distributed world.
We know it’s annoying but we’re excited to share our knowledge and want to turn DIDO TE from prototype to full fledged product. To do so, we need to be our hero and show there’s interest.
