DIDO-RA

How to Assesses Functional and Non-Functional Requirements

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 »

What are Non-Functional Requirements?

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 …

What are Non-Functional Requirements? Read More »

What are Functional Requirements?

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 …

What are Functional Requirements? Read More »

Governance Guides and Their Purpose

In addition to the legal documents governing the activities of a community of interest (CoI), many CoIs create a simple, easily understood guide to help its members maneuver through and understand all the governing statements contained in the statutes, charter, bylaws, parliamentary authority, special rules, custom practices, and standing rules associated with that particular CoI. …

Governance Guides and Their Purpose Read More »

What are DIDO Communities of Interest (CoI)?

As introduced in Section 2.1, a DIDO community is a community of interest (CoI) responsible for the architecture, design, implementation, maintenance, and eventual sunset (yes, all good things come to an end) of DIDO networks and its DIDO nodes. DIDO communities should have a well-documented, repeatable, traceable, transparent, and unbiased process that is managed and …

What are DIDO Communities of Interest (CoI)? Read More »

Why Governance Matters!

For practical reasons, the acronym Distributed Immutable Data Object (DIDO) represents a set of distributed computing technologies that focus on distributed data (i.e., blockchains, distributed ledgers, distributed file systems or distributed data). A major problem confronting the adoption of DIDO technologies is that it requires shifting away from corporate models of governance to an open …

Why Governance Matters! Read More »

What are the Technical Views of the DIDO RA?

Technical Views are intended to define at a high level the various components of larger DIDO systems. They outline generic parts, subparts, and interconnections of those parts and subparts for a DIDO system. For each part or subpart, a list of potential standards, best practices, and tools is provided. There are multiple views, subdivided into …

What are the Technical Views of the DIDO RA? Read More »