dido:public:ra:1.4_req:1_func
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:1_func [2021/03/22 10:49] nick [Hardware Architecture] |
dido:public:ra:1.4_req:1_func [2022/08/31 15:32] (current) nick |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[dido:public:ra:1.4_req |Return to Requirements ]] | [[dido:public:ra:1.4_req |Return to Requirements ]] | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq]] 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. | + | [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq]] define the basic system behavior. Essentially, they are requirements stating what the system must do 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 system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements. Functional Requirements can be used during all phases of a project [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle| Lifecycle]] independent of the development model (i.e., [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]] or [[dido:public:ra:xapend:xapend.a_glossary:a:agile]]). In the Waterfall method, these requirements are generally specified early on in the process. In the Agile method, they can be applied throughout each [[dido:public:ra:xapend:xapend.a_glossary:s:sprint]] or applied during specific Sprints. | + | Functional Requirements are features that allow the system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements. Functional Requirements can be used during all phases of a project [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle| Lifecycle]] independent of the [[dido:public:ra:xapend:xapend.a_glossary:s:software_development_model]] (i.e., [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]] or [[dido:public:ra:xapend:xapend.a_glossary:a:agile]], etc.). In the Waterfall method, these requirements are generally specified early on in the process. In the Agile method, they can be applied derived during each [[dido:public:ra:xapend:xapend.a_glossary:s:sprint]] or applied during specific Sprints. |
| - | ===== Things to Consider When Designing Distributed systems ===== | + | The DIDO RA views functional requirements from the following perspectives: |
| - | * **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. | + | |
| - | https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.4_req:1_func#hardware_architecture | + | |
| - | ^ Functional Area ^ Comments ^ | + | |
| - | | [[dido:public:ra:1.4_req:1_func:platform|Which Platforms must be supported?]] | | | + | |
| - | | [[dido:public:ra:xapend:xapend.c_hwarch:1_embedded|Which Embedded Systems must be supported:]] | | | + | |
| - | | [[dido:public:ra:xapend:xapend.c_hwarch:1_embedded:subsystems|SubSystem | Which Standalone Subystems must be supported?]] | | | + | |
| - | | [[dido:public:ra:xapend:xapend.c_hwarch:1_embedded:standalone|Standalone | Which Standalone Systems must be supported?]] | | | + | |
| - | | [[dido:public:ra:xapend:xapend.c_hwarch:1_embedded:networked|Networked | Which Network Systems must be supported? ]] | | | + | |
| - | + | ||
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:server | Which servers must be supported?]] | + | |
| - | - [[dido:public:ra:xapend:xapend.c_hwarch:server:sw | Which software Servers must be supported?]] | + | |
| - | - [[dido:public:ra:xapend:xapend.c_hwarch:server:hw | Which hardware Servers must be supported?]] | + | |
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:desktop | Which desktop computers must be supported?]] | + | |
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:handheld | Which handheld computers must be supported?]] | + | |
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:super | Which supercomputers must be supported?]] | + | |
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:network | Which network computers must be supported?]] | + | |
| - | + | ||
| - | ==== Operating System ==== | + | |
| - | Nodes on the distributed network must be designed specifically for the operating system that runs on the node. So the distributed system needs to 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. | + | |
| - | * [[dido:public:ra:1.4_req:1_func:platform:os_arch | Which operating systems must be supported?]] | + | |
| - | + | ||
| - | ==== 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. | + | |
| - | * [[dido:public:ra:1.4_req:1_func:platform:net_arch | Which network platforms must be supported?]] | + | |
| - | * [[dido:public:ra:xapend:xapend.c_hwarch:network | Which networking architectures must be supported?]] | + | |
| - | * [[dido:public:ra:1.4_req:1_func:access | Which hnetworking access must be supported?]] | + | |
| - | + | ||
| - | ==== RunTime Libraries ==== | + | |
| - | RunTime functional requirements is to establish a RunTime Library that can communicate to with different operating/hardware platforms across the system. | + | |
| - | * [[dido:public:ra:1.4_req:1_func:platform:sw_arch | Which runtime environments must be supported?]] | + | |
| - | + | ||
| - | ==== Community/Development Tools ==== | + | |
| - | Tool functional requirements include making sure your system has all the necessary development, management, and operation tools for the project. | + | |
| - | * [[dido:public:ra:xapend:xapend.e_tools | Which support tools must be supported?]] | + | |
| - | **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. | + | |
| - | * [[dido:public:ra:1.4_req:1_func:platform:virtnodes | Which types of virtualization nodes must be supported?]] | + | |
| + | * [[dido:public:ra:1.4_req:1_func:platform]] | ||
| + | * [[dido:public:ra:1.4_req:1_func:access]] | ||
dido/public/ra/1.4_req/1_func.1616424596.txt.gz · Last modified: 2021/03/22 10:49 by nick
