You are on page 1of 12

Requirement # Unique Number: Non-Functional Requirement:

5 85898 Performance Requirement

Description: The system must be able to authenticate and validate members using the
RFID.
Rationale: The system should be able to identify members.

Originator: Sizwe Lethuli Chief Engineer


Fit Criterion: The recorded unique IDs must match with the correct user.

Customer 4 Customer Dissatisfaction: 2


Satisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Performance Requirement

Description: The performance of the RFID should be fast and accurate


Rationale: The system should be able to quickly and accurately store information.

Originator: Sizwe Lethuli Chief Engineer


Fit Criterion: The RFID must be able to accurately link the right to the right information.

Customer 4 Customer Dissatisfaction: 1


Satisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
3 85599 Performance Requirement

Description: The system will be able to handle large amounts of data.


Rationale: The system should be able to store a high number of books as well as users
without coming across any errors.

Originator: Priyank Parsotam Project Manager


Fit Criterion: The recorded books must correlate with the user database and must be
updated each time a book has been returned or removed.

Customer 4 Customer Dissatisfaction: 2


Satisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Performance Requirement

Description: The system should allow normal users to read the books information
Rationale: The system should be able to allow normal users to read basic information
about the books

Originator: Priyank Parsotam Project Manager


Fit Criterion: The recorded books must be shown as soon as the user has logged in
before checking out.

Customer 4 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Security Requirement

Description: The system distinguishes between users and admins


Rationale: The system can tell who is an admin and who is a normal user from the
RFID.

Originator: Onalerona Phuza Chief Executive


Fit Criterion: The system will retrieve the relevant information from the database to
determine who is an admin and who is a normal user.

Customer 4 Customer 2
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Security Requirement

Description: Normal users are not able to edit or modify anything.


Rationale: The system should not allow normal users to modify the book information
only their personal information.

Originator: Onalerona Phuza Chief Executive


Fit Criterion: When the user logs using his RFID the only information available to him
that allows modification is his personal information.

Customer 2 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Usability Requirement

Description: The system should allow normal users to read the books information
Rationale: The system should be able to allow normal users to read basic information
about the books

Originator: Ronewa Ndou Chief Finance


Fit Criterion: The recorded books must be shown as soon as the user has logged in
before checking out.

Customer 2 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Security Requirement

Description: The system prevents the hacking of user passwords.


Rationale: No one should be able to hack user passwords.

Originator: Ronewa Ndou Chief Finance


Fit Criterion: The system should prevent the hacking of user passwords through anti-
theft software.

Customer 4 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Performance Requirement

Description: Proper accountability for a users account.


Rationale: The system should prevent users from accessing or using another users
account.

Originator: Sizwe Lethuli Chief Engineer


Fit Criterion: The system would require the users RFID tag to enable the user to log off
his/her account.

Customer 2 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
6 858856 Security Requirement

Description: The system should be able to protect its database from a crash at any point in
time due to a virus or operating system failure.
Rationale: To be able to protect the stored database and prevent power failures.

Originator: Onalerona Phuza Chief Executive


Fit Criterion: The system should make regular backups of the database so that the
database is not lost and a UPS must be used in case I possible power supply
failures.
Customer 5 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Security Requirement

Description: The system would handle expected and non-expected errors.


Rationale: The system would be able to prevent loss of information and long downtime
period.

Originator: Priyank Parsotam Project Manager


Fit Criterion: To test this the system would need a built-in error testing to identify invalid
RFID tags.

Customer 4 Customer 2
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday


Requirement # Unique Number: Non-Functional Requirement:
5 85898 Usability Requirement

Description: The database is user friendly and easy to use for all users.
Rationale: The system database should be user friendly and easy for new users to
understand.

Originator: Ronewa Ndou Chief Finance


Fit Criterion: The database quality should be maintained in a way that is easily
understandable.

Customer 3 Customer 3
Satisfaction: Dissatisfaction:

Priority: High Conflicts: None


Supporting
Material:

History: Created 8 August 2017, Tuesday

You might also like