Sidebar
Table of Contents
4.4.1 Functional Requirements Assessment
Things to Consider When Designing Distributed systems
- Note: Because these are Functional Requirements, they need to be written specifically for the system being specified in the proposal or solicitation.
In DIDO, the following areas minimally cover Functional Requirements:
Hardware Architecture
The goal of hardware functional requirements is to decide which hardware architectures are going to be supported and which, if any, will be left out.
Operating System
Nodes on the distributed network must be designed specifically for the operating system that runs on the node. So the distributed system must support more than one operating system. But too many OSs can cause the support and maintenance of the system to be more difficult and costly.
Network
A distributed system is a collection of networked nodes, that run on networking equipment all connected using wireless or USB connections. Network functional requirements is to decide which platform, devices, and permissions are used throughout the system.
RunTime Libraries
RunTime functional requirements is to establish a RunTime Library that can communicate to with different operating/hardware platforms across the system.
Community/Development Tools
Tool functional requirements include making sure your system has all the necessary development, management, and operation tools for the project.
Note: The tool list provided is not exhaustive.
Virtualized Nodes
Utilizing Virtual Nodes in a distributed system can provide flexibility because a virtual node can run on many hardware/operating system platforms. Virtual Node functional requirements entail determining which type of virtual node is necessary for the system.
Data
Every node based on its roles, manages and controls data. The data within the node is classified as either: ledger data, ancillary data, or external data. Regardless of the clas of data sotred on a node, it is often controlled by regulatons, Policies and Procedures.
