Hey I already made my 7 used cases and the project I worked on is in quotes belo
ID: 3741218 • Letter: H
Question
Hey I already made my 7 used cases and the project I worked on is in quotes below, all I need to know is how to incorporate my non functional requirments . How do I incorporate or structure or organize the non functional parts into my project? The non functional parts or quality I came up with availability , portability , maintain ability , security , and constraints of the design incorporated with the library PLS
"UC1: Borrow Item
Pre Conditions : Patron has a verified profile with the library.
Basic Flow of Events
1.FR1. The system shall be able to accept input details of a patron
1.FR2. The system shall be able to search for a patron in database given above details
1.FR3. The system shall be able to search for an item in Library inventory system
1.FR4. The system shall be able to update the given patron profile status
1.FR5. The system shall be able to update the current library inventory system 1.FR6. The system shall be able to maintain a a log of items borrowed
Alternative Flow of Events
After step 1 if the customer is not verified , he can create a profile, so he can access the resources of the library.
Post Condition
Patron has been added to the system and verified, and can borrow items.
UC2: Return Item
Pre Conditions- An item was borrowed, and should be returned by the due date.
Basic Flow of Events
2.FR1. The system shall be able to accept input details of a patron
2.FR2. The system shall be able to search for a patron in database given above details
2.FR3. The system shall be able to calculate the late fee for a patron returning an item
2.FR4. The system shall be able to update the given patron profile status
2.FR5. The system shall be able to update the current library inventory system
2.FR6. The system shall be able to maintain a a log of items returned
2.FR7. The system shall be able to process a late fee request
2.FR8. The system shall be able to reject an invalid return request
Alternative flow of Events
After step 3, if the item is not returned by the due date, the calculation for the late fee is will be activated. And Patron will be banned from accessing the library system, and eventually can’t access the library, as his database will be saved, that they did not return an item.
Post Condition
Item was returned on time, and saved in the database. Item was returned late, fee calculated and saved to the database. If item not returned, fee calculated, and depends if the patron can access the library, and use its resources.
UC3: Sign On
Precondition- Patron already has verified with the account the library.
Basic Flow of Events
3.FR1. The system shall be able to maintain a database of current patrons
3.FR2. The system shall be able to update the database with new patron details 3.FR3. The system shall be able to check current patron database given patron details
3.FR4. The system shall be able to display error message in case patron details not found in database
3.FR5. The system shall be able to maintain log of patrons currently signed into the system
Alternative flow of Events
After step 4, if the patron can not access its system, and error message will pop up. It will be saved how many times the customer tried to access the system, and this will be seen by data administrator, and added to the error event log. Through an extended case it will be seen if the customer forgot their password, or banned from entering the system, or simply did not create an user account. After determination of the customer status, they will be dealt with accordingly.
Post Condition
The user had an account, and can sign on, if they can’t sign on, it will go to an extended case, where customer will be emailed from library system, to change their password for user account.
UC4: Create User Account
Pre Condition- The user must fill out all the information required to have an account with the library, and agree to its term of services.
Basic Flow of Events
4.FR1. The system shall be able maintain a database of patrons
4.FR2. The system shall provide a user interface for patron details input
4.FR3. The system shall be able to accept user input from front-end interface
4.FR4. The system shall be able to store the acquired information in patron database
4.FR5. The system shall be able to access stored patron account information
4.FR6. The system shall be able to edit stored patron account information
Alternative flow of Events
In step 6, if the patron account info changes , say for example their address , the system will take into consideration , and give recommendations for other libraries the customer can go to. Or if in step 6, if the patron did not give a clear account information, the system will ask for the customer to edit the parts of the account information that needs to be edited.
Post Condition
The user has an account, and can enter the library , check out items, and utilize library other services.
UC5:View User Directory
Precondition- user information is already in the system libraries database
Basic Flow of Events
5.FR1. The system shall be able to maintain a database of patrons
5.FR2. The system shall allow access to patron database given admin authentication
5.FR3. The system shall provide front-end interface to view user data for system admin
5.FR4. The system shall encapsulate user data from non-admins
Alternative flow of Events
In step 2, if the system does not have access patron database, then the system will go directly to step 4, and encapsulate user data from non-admin
Post Condition
The system has an account of the profiles of the customers, and a database of what items are being borrowed and returned, and the system knows what items to order based on database and inventory account.
UC6:Edit User Account
Pre Condition- user has an account, edits and changes of the customer or their address is incremented to the database of the library, so the system has the most current and accurate information
Basic Flow of Events
6.FR1. The system shall be able maintain a database of patrons
6.FR2. The system shall provide a user interface for patron details input
6.FR3. The system shall be able to accept user input from front-end interface
6.FR4. The system shall be able to store the acquired information in patron database
6.FR5. The system shall allow access to patron database given admin authentication
6.FR6. The system shall allow edit of patron information given admin authentication
6.FR7. The system shall encapsulate user data from non-admins
Alternative flow of Events
In step 3, if the system can not accept user input from front-end interface, then the system will go directly to step 7 and shall encapsulate user data from non-admins
Post Condition
The system has accurate information on the user profile of the customers making transaction with the library, and the accurate information is being stored to the library system.
UC7:Delete User
Pre-Condition- User has a verified account, and wants to now delete their account
Basic Flow of Events
7.FR1. The system shall be able maintain a database of patrons
7.FR2. The system shall provide a user interface for patron details input
7.FR3. The system shall be able to accept user input from front-end interface
7.FR4. The system shall be able to store the acquired information in patron database
7.FR5. The system shall allow access to patron database given admin authentication
7.FR6. The system shall allow edit of patron information given admin authentication
7.FR7. The system shall encapsulate user data from non-admins
7.FR8. The system shall allow user profile deletion given admin authentication
7.FR9. The system shall be able to check item borrowed status of profile to be deleted
7.FR10. The system shall reject a delete request if items have not been returned
7.FR11. The system shall update database after delete request has been processed successfully.
Alternative flow of Events
In step 10, the system will reject a delete request if items has not been returned. In extended case , the system will remind the user that they still have a borrowed item. The user must pay a fee or return the item, and this will be calculated and registered into the system’s database , and then the customer will be allowed to delete their account and this will processed and updated into the system successfully.
Post Condition
The user was able to delete their account successfully, and was updated and processed into the system’s database successfully.
Explanation / Answer
Non Functional Requirements capture: