Reqs
Regeln und Definitionen zum ReqManagement
Regeln und Definitionen zum ReqManagement
Kartei Details
| Karten | 30 |
|---|---|
| Sprache | Deutsch |
| Kategorie | Informatik |
| Stufe | Andere |
| Erstellt / Aktualisiert | 14.06.2017 / 14.11.2019 |
| Weblink |
https://card2brain.ch/box/20170614_reqs
|
| Einbinden |
<iframe src="https://card2brain.ch/box/20170614_reqs/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Percentage of planned “up time” during which system is actually available and fully operational
Measure of how well system resources are utilized (bandwidth, disk space, CPU, etc.)
Indicates how much effort is required to add new capabilities to the product, aka extensibility, augmentability, expandability, and scalability
Precluding unauthorized access, preventing information loss, data privacy, system protection from viruses
Indicates how easily the system can exchange data or services with other systems
Indicates the probability the software will execute for a long time without failure. Measures include length of time until a defect is revealed, defect density, and % of correctly performed operations
Degree to which a system can perform correctly when confronted with invalid data, unexpected operating conditions, defects in connected HW/SW
Also referred to as “ease of use,” it is easier to use the software than not, measures the effort required to prepare input, operate the system, interpret output
Indicates how easy it is to correct or make a change to the software component
Effort required to migrate a piece of software form one operating environment to another
Indicates the extent a software component can be used in other systems other than that in which it was originally developed
Ease with which software components or integrated product can be tested to find defects
