DIDO Wiki dido:public:ra:1.4_req:2_nonfunc

4.3.8 Interoperability

Anonymous (anonymous@undisclosed.example.com) — 2021-08-11T13:27:50-0400

4.3.8 Interoperability Return to Non-Functional Requirements About Interoperability is a characteristic of a product or system whose interfaces are completely understood to work with other products or systems, present or future, in either implementation or access, without any restrictions. There are different levels of interoperability. As one moves up the interoperability levels, the degree of interoperability increases in difficulty. The m…

4.3.9 Elasticity

Anonymous (anonymous@undisclosed.example.com) — 2021-07-26T12:40:36-0400

4.3.9 Elasticity Return to Non-Functional Requirements About Cloud Elasticity also known as Elasticity “is the degree to which a system is able to adapt to workload changes by provisioning and de-provisioning resources in an autonomic manner, such that at each point in time the available resources match the current demand as closely as possible.

4.3.1 Portability

Anonymous (anonymous@undisclosed.example.com) — 2021-08-13T12:18:53-0400

4.3.1 Portability return to Non-Functional Requirements About Portability is the degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another. This characteristic is composed of the following sub-characteristics:

4.3.2 Reliability

Anonymous (anonymous@undisclosed.example.com) — 2021-08-09T14:34:52-0400

4.3.2 Reliability return to Non-Functional Requirements About Reliability is the degree to which a system, product or component performs specified functions under specified conditions for a specified period of time. This characteristic is composed of the following sub-characteristics:

4.3.10 Scalability

Anonymous (anonymous@undisclosed.example.com) — 2021-06-11T14:48:13-0400

4.3.10 Scalability Return to Non-Functional Requirements About Scalability is the ability of a system to accomplish more work while maintaining the quality (i.e., without degradation) of the products produced or services provided by the system. There are different ways to calculate the work produced or performed by the system, which usually depends on the kind of product produced or services rendered.

4.3.3 Maintainability

Anonymous (anonymous@undisclosed.example.com) — 2021-07-26T16:13:44-0400

4.3.3 Maintainability return to Non-Functional Requirements About Maintainability is the characteristic that represents the degree of effectiveness and efficiency with which a product or system can be modified to improve it, correct it or adapt it to changes in its environment and requirements. This characteristic is composed of the following sub-characteristics:

4.3.4 Securability

Anonymous (anonymous@undisclosed.example.com) — 2022-04-12T15:20:20-0400

4.3.4 Securability Return to Non-Functional Requirements About Return to Top Security is not a single “thing” that can be added to a system. To be truly secure, the entire End-to-End Solution (E2ES) needs to be secure and needs to be considered during the entire System Lifecycle. As shown in Figure , a layered approach is used to help isolate the security needs. Each layer represents a portion of the

4.3.5 Manageability

Anonymous (anonymous@undisclosed.example.com) — 2021-06-11T14:50:32-0400

4.3.5 Manageability Return to Non-Functional Requirements Manageability is most important during the second half of System Lifecycle phases (i.e. operation, maintenance, support). Manageability can greatly influence the recurring costs and can increase the chances of a failure. Often a system that is hard to manage is described as fragile since the smallest change can have dire consequences on the system's functionality.

4.3.6 Usability

Anonymous (anonymous@undisclosed.example.com) — 2021-08-06T17:08:16-0400

Justin Mifsud, Usability Metrics – A Guide To Quantify The Usability Of Any System

4.3.7 Performance

Anonymous (anonymous@undisclosed.example.com) — 2021-07-30T15:40:48-0400

4.3.7 Performance Return to Non-Functional Requirements About Performance is the ability of a system to accomplish the required functionality at or under the required specification limits. The limits are generally provided relative to time (i.e., so-many transactions per second, so-many updates per millisecond, so-many recorded entries per second, etc.) The specifications can also include accuracy, precision, precision or even efficiency of other dependent systems as requirements. The follow…