REL-1: The mean time between failures of the Pifaro system components shall be at least 200 hours.
REL-2: No more than 5 experimental runs out of 1,000 can be lost because of system failures.
6.6.2 Robustness
ROB-1: The system shall able to correct minor typing errors on PURL address and direct users to correct URLs.
ROB-2: If the system fails before users successfully create and save PURLs to the system, the system shall recover it being edited as of, at most, one minute prior to the failure the next time the same user log in to Pifaro system.
ROB-3: All parameters shall have default values specified, which system shall use them if a parameter’s input data is missing or invalid.
6.6.3 Availability
AVL-1: The Pifaro system shall be available …show more content…
AVL-3: The Pifaro system shall always maintain for minimum maintenance duration and could get fixed as soon as possible.
6.6.4 Integrity
INT-1. After performing a data and document backup, the Pifaro system shall verify the backup copy against the original and report any discrepancies.
INT-2. The Pifaro system shall protect against the unauthorized creation, deletion, or modification of PURLs.
INT-3. The Pifaro system shall confirm daily that the system executables have not been modified by the addition of unauthorized code.
INT-4: All data stored in Pifaro system should be backed up in case system breaks down.
INT-5: All users need to log in to system before taking …show more content…
FLE-2: No more than 5% of original code need to be changed in order to implement new capacity of Pifaro system.
6.6.6 Usability
USE-1: The Pifaro system shall allow infrastructure staff and research groups to create and manage PURLs with simple interactions.
USE-2: 95% of new Pifaro system users shall able to create and manage PURLs on Pifaro system without errors on their first try.
USE-3: New users of Pifaro system shall able to manage using it with a simple learning tutorial within 30 minutes.
USE-4: The Pifaro system shall respond to any user request within 1 second.
USE-5: The Pifaro system shall show creation/deletion confirmation messages to users within 2 seconds after users submit their requests to system.
6.6.7 Interoperability
IOP-1. The Pifaro system shall be able to import any valid and secure PURL structure from tools.
IOP-2: The Pifaro system shall easily transfer stored data/information to DSA system.
6.6.8 Testability
TES-1. The development environment configuration shall be identical to the test configuration environment to avoid irreproducible testing failures.
TES-2. A tester shall be able to configure which execution results are logged during
REL-2: No more than 5 experimental runs out of 1,000 can be lost because of system failures.
6.6.2 Robustness
ROB-1: The system shall able to correct minor typing errors on PURL address and direct users to correct URLs.
ROB-2: If the system fails before users successfully create and save PURLs to the system, the system shall recover it being edited as of, at most, one minute prior to the failure the next time the same user log in to Pifaro system.
ROB-3: All parameters shall have default values specified, which system shall use them if a parameter’s input data is missing or invalid.
6.6.3 Availability
AVL-1: The Pifaro system shall be available …show more content…
AVL-3: The Pifaro system shall always maintain for minimum maintenance duration and could get fixed as soon as possible.
6.6.4 Integrity
INT-1. After performing a data and document backup, the Pifaro system shall verify the backup copy against the original and report any discrepancies.
INT-2. The Pifaro system shall protect against the unauthorized creation, deletion, or modification of PURLs.
INT-3. The Pifaro system shall confirm daily that the system executables have not been modified by the addition of unauthorized code.
INT-4: All data stored in Pifaro system should be backed up in case system breaks down.
INT-5: All users need to log in to system before taking …show more content…
FLE-2: No more than 5% of original code need to be changed in order to implement new capacity of Pifaro system.
6.6.6 Usability
USE-1: The Pifaro system shall allow infrastructure staff and research groups to create and manage PURLs with simple interactions.
USE-2: 95% of new Pifaro system users shall able to create and manage PURLs on Pifaro system without errors on their first try.
USE-3: New users of Pifaro system shall able to manage using it with a simple learning tutorial within 30 minutes.
USE-4: The Pifaro system shall respond to any user request within 1 second.
USE-5: The Pifaro system shall show creation/deletion confirmation messages to users within 2 seconds after users submit their requests to system.
6.6.7 Interoperability
IOP-1. The Pifaro system shall be able to import any valid and secure PURL structure from tools.
IOP-2: The Pifaro system shall easily transfer stored data/information to DSA system.
6.6.8 Testability
TES-1. The development environment configuration shall be identical to the test configuration environment to avoid irreproducible testing failures.
TES-2. A tester shall be able to configure which execution results are logged during