Use Case Specification
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Use Case Specification as PDF for free.
More details
- Words: 3,212
- Pages: 16
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
Appendix 1-5 Use Case Specification
USE CASE SPECIFICATION
PRACTICUM STUDENTS PLACEMENT SYSTEM (PSPS)
PREPARED FOR: UNIVERSITY OF INFORMATION TECHNOLOGY
Faculty of Information Technology
SYSTEM NAME
DOCUMENT IDENTIFICATION
RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
1 / 15
Appendix 1-5
Use Case Specification
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
TABLE OF CONTENTS 1
USE CASE: LOGIN (PSPS_01) 1.1 BRIEF DESCRIPTION 1.2 PRE-CONDITIONS 1.3 CHARACTERISTIC OF ACTIVATION 1.4 FLOW OF EVENTS 1.4.1 Basic Flow (PSPS_01) 1.4.2 Alternative Flow 1.4.3 Exceptional Flow 1.5 POST-CONDITIONS 1.6 RULE(S) 1.7 CONSTRAINT(S)
5 5 5 5 5 5 5 6 6 6 6
2
USE CASE: REGISTRATION OF STUDENT INFORMATION (PSPS_02)
7
2.1 2.2 2.3 2.4
7 7 7 7 7 7 8 8 8 8
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 2.4.1 Basic Flow (PSPS_02) 2.4.2 Alternative Flow 2.4.3 Exceptional Flow 2.5 POST-CONDITIONS 2.6 RULE(S) 2.7 CONSTRAINT(S) 3
USE CASE: REGISTRATION OF COMPANY/EMPLOYER (PSPS_03) 3.1 BRIEF DESCRIPTION 3.2 PRE-CONDITIONS 3.3 CHARACTERISTIC OF ACTIVATION 3.4 FLOW OF EVENTS 3.4.1 Basic Flow (PSPS_03) 3.4.2 Alternative Flow 3.4.3 Exceptional Flow 3.5 POST-CONDITIONS 3.6 RULE(S) 3.7 CONSTRAINT(S)
9 9 9 9 9 9 10 10 10 10 10
4
USE CASE: MANAGE PRACTICUM PLACEMENT (PSPS_04)
11
4.1 4.2 4.3 4.4
15 11 15 15 15 15 15 16
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 4.4.1 Basic Flow (PSPS_04) 4.4.2 Alternative Flow 4.4.3 Exceptional Flow 4.5 POST-CONDITIONS DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
2 / 15
Appendix 1-5 4.6 4.7
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
5
Use Case Specification RULE(S) CONSTRAINT(S)
16 16
USE CASE: FEEDBACK FROM COMPANY (PSPS_05)
Error! Bookmark not defined.
5.1 5.2 5.3 5.4
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 5.4.1 Basic Flow (PSPS_05) 5.4.2 Alternative Flow 5.4.3 Exceptional Flow 5.5 POST-CONDITIONS 5.6 RULE(S) 5.7 CONSTRAINT(S)
Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined.
6
USE CASE: CHECK STATUS (PSPS_06) 6.1 BRIEF DESCRIPTION 6.2 PRE-CONDITIONS 6.3 CHARACTERISTIC OF ACTIVATION 6.4 FLOW OF EVENTS 6.4.1 Basic Flow (RVRS_06) 6.4.2 Alternative Flow 6.4.3 Exceptional Flow 6.5 POST-CONDITIONS 6.6 RULE(S) 6.7 CONSTRAINT(S)
22 22 22 22 22 22 23 23 23 23 23
7
USE CASE: APPLICATION OF POSTPONEMENT (PSPS_07) 7.1 BRIEF DESCRIPTION 7.2 PRE-CONDITIONS 7.3 CHARACTERISTIC OF ACTIVATION 7.4 FLOW OF EVENTS 7.4.1 Basic Flow (PSPS_07) 7.4.2 Alternative Flow 7.4.3 Exceptional Flow 7.5 POST-CONDITIONS 7.6 RULE(S) 7.7 CONSTRAINT(S)
22 22 22 22 22 22 23 23 23 23 23
8
USE CASE: APPROVAL OF POSTPONEMENT (PSPS_08) 8.1 BRIEF DESCRIPTION 8.2 PRE-CONDITIONS 8.3 CHARACTERISTIC OF ACTIVATION 8.4 FLOW OF EVENTS 8.4.1 Basic Flow (PSPS_08) 8.4.2 Alternative Flow 8.4.3 Exceptional Flow 8.5 POST-CONDITIONS 8.6 RULE(S) 8.7 CONSTRAINT(S)
22 22 22 22 22 22 20 20 20 20 20
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
3 / 15
Appendix 1-5
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
9
Use Case Specification
USE CASE: MANAGE PRACTICUM ASSESSMENT (PSPS_09) 9.1 BRIEF DESCRIPTION 9.2 PRE-CONDITIONS 9.3 CHARACTERISTIC OF ACTIVATION 9.4 FLOW OF EVENTS 9.4.1 Basic Flow (PSPS_09) 9.4.2 Alternative Flow 9.4.3 Exceptional Flow 9.5 POST-CONDITIONS 9.6 RULE(S) 9.7 CONSTRAINT(S)
21 21 21 21 21 21 22 22 22 22
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
4 / 15
Appendix 1-5
Use Case Specification
1 USE CASE: LOGIN (PSPS_01)
Log in
Student
1.1
BRIEF DESCRIPTION
This use case is initiated by the students. This use case will enable the student to enter their own ID and password, reset the password and cancel the login.
1.2
PRE-CONDITIONS The student has been registered before using the system.
1.3 CHARACTERISTIC OF ACTIVATION
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
Event Driven
1.4 FLOW OF EVENTS 1.4.1 Basic Flow (PSPS_01) This use case begins when the student inserts their student ID and password. The student then presses the “OK” button [A-1: Cancel] The system shall verify the student ID and password. [E-1: Invalid password and student ID]. The system shall display the Menu Panel on the screen. Student can change their password after they login to the system. [A-2: Reset password] 1.4.2 Alternative Flow A-1: The student can press “CANCEL” button anytime and the system shall automatically exit. A-2: The student can reset their password after login by press the “Reset” button and the system will display the old password.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
5 / 15
Appendix 1-5
Use Case Specification 1.4.3 Exceptional Flow E-1: Invalid Password and student ID (PSPS_01) The system shall prompt the student to enter the correct ID and password again until it’s verify by display the error message, “The ID and password entered are incorrect, please enter again your ID and password.” The system should prompt the student to press “Forgot Password” and insert their email address to view their password.
1.5 POST-CONDITIONS
The student be able to access the menus and use the system.
1.6 RULE(S)
The student shall register before login to the system. The student ID and password must be correctly entered. The password can be Uppercase or Lowercase letter. The password must length 4 until 8 character.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
1.7 CONSTRAINT(S) The student shall register before login. The student ID and password must be applicable when the student login. The student also can only enter the system after the login.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
6 / 15
Appendix 1-5
Use Case Specification
2 USE CASE: REGISTRATION INFORMATION (PSPS_02)
STUDENT
Registration of Student Information
Student
2.1
OF
BRIEF DESCRIPTION
This use case is initiated by the students. This use case will enable the student to add, remove, edit, view and print their personal information. Staff can view the student personal information.
2.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The student must login before using the system.
2.3 CHARACTERISTIC OF ACTIVATION Students demand.
2.4 FLOW OF EVENTS 2.4.1 Basic Flow (PSPS_02) This use case begins when the student enter their personal information page. The system shall display the empty personal information for the student. The student shall fill their information after press “Add” button to update their information. [A-1: Cancel] The student can press “Edit” to edit their information. [A-2: Remove] The student then presses the “OK” button to update it. [E-1: Cannot verify to proceed] The system shall then display the information that has been updated. The student can print their personal information. 2.4.2 Alternative Flow A-1: Cancel (PSPS_02) DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
7 / 15
Appendix 1-5
Use Case Specification
The student can press “Cancel” button if they does not want to add any information. The system shall automatically exit. A-2: Remove (PSPS_02) The student can press “Remove” button to remove their information. The system should automatically update. 2.4.3 Exceptional Flow E-1: Cannot verify to proceed (PSPS_02) The system will pop up the new window browser then display what the student must fill.
2.5 POST-CONDITIONS
The personal information of student shall be updated.
2.6 RULE(S)
The student must fill in the mandatory information.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
2.7 CONSTRAINT(S) Not Applicable
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
8 / 15
Appendix 1-5
Use Case Specification
3 USE CASE: REGISTRATION COMPANY/EMPLOYER (PSPS_03)
Registration of Company
Employer
3.1
OF
BRIEF DESCRIPTION
This use case is initiated by the employer. This use case will enable the employer to view, add, edit or remove their personal information. Staff can view the employer information once the employer register.
3.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The employer must be able to conduct practicum student at their company.
3.3 CHARACTERISTIC OF ACTIVATION Demand by the employer.
3.4 FLOW OF EVENTS 3.4.1 Basic Flow (PSPS_03) This use case will enable employer to add, edit or remove their register information. The system shall display the empty registration company form to be filling by the employer. The employer must press “Add” button to update their information. [A-1: Cancel]. The employer can press “Edit” button to edit their information. [A-2: Remove] The employer will press “OK” button to update their information. [E-1: Cannot verify to proceed] The system should display the update information.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
9 / 15
Appendix 1-5
Use Case Specification 3.4.2 Alternative Flow A-1: Cancel (PSPS_03) The employer can press “Cancel” button if they don’t want to update their information. The system shall automatically exit. A-2: Remove (PSPS_03) The employer can press “Remove” button if they want to remove any information. The system should update the information. 3.4.3 Exceptional Flow E-1: Cannot verify to proceed (PSPS_03) The system will pop up the new window browser then display what the company must fill.
3.5 POST-CONDITIONS
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
The company registration information should be updated by the system.
3.6 RULE(S)
The employer shall register and login to manage their company registration information.
3.7 CONSTRAINT(S) Not Applicable
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
10 / 15
Appendix 1-5
Use Case Specification
4 USE CASE: MANAGE PRACTICUM PLACEMENT (PSPS_05)
Manage Practicum Placement
Staff
4.1
BRIEF DESCRIPTION
This use case is initiated by the staff. This use case will enable the staff to match student and the company for placement.
4.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS Staff will be able to insert the student matric number for match process. The information of employer shall be updated before do matching. The information of student shall be updated before do matching.
4.3 CHARACTERISTIC OF ACTIVATION Staff’s demand
4.4 FLOW OF EVENTS 4.4.1 Basic Flow (PSPS_04) This use case begins when the staff enters the manage practicum placement page. The system shall display and guide the staff to insert the student matric no. inside the search box and press “Match” button. Staff can press “Accept” button to accept the company that match with the student. [A-1: Reject] Staff can press “Submit” button to send the company name to the match student status page. [A-2: Cancel] The system will determine the match student and company requirement. [E1: No matching found]
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
11 / 15
Appendix 1-5
Use Case Specification 4.4.2 Alternative Flow A-1: Reject (PSPS_04) Staff can press “Reject” button to reject the matching found. The system should do nothing until any action by the staff. A-2: Cancel (PSPS_04) The staff can press “Cancel” button. The system should do nothing until any action from the staff. 4.4.3 Exceptional Flow E-1: No matching found (PSPS_04) The system shall guide the staff to go to match manually page or the end of the system directly
4.5 POST-CONDITIONS
The student status should be updated automatically after staff submits the company name to them. The employer status should be updated automatically after staff accepts the student name for them.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
4.6 RULE(S)
The student matric number should insert correctly.
4.7 CONSTRAINT(S) The staff must wait until matching process complete.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
12 / 15
Appendix 1-5
Use Case Specification
5 USE CASE: FEEDBACK FROM COMPANY (PSPS_05)
Feedback
Employer
5.1
BRIEF DESCRIPTION
This use case is initiated by the employer. This use case will enable the employer to view the list student name that match for their company. They can accept or reject.
5.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The match list student name has been sent to the company information page.
5.3 CHARACTERISTIC OF ACTIVATION Event Driven (on employer’s demand)
5.4 FLOW OF EVENTS 5.4.1 Basic Flow (PSPS_05) This use case begins when the employer enters they information page and view the feedback information. The system should display the list of student name that match with they company requirement. Employer can press “Accept” button for each name. [A-1: Reject] Employer can click on the student name link to go to their information. [A-2: View Resume] Employer will press “OK” button to update the feedback. [A-3: Cancel] The system shall display the updated feedback automatically once the employer verify. [E-1: Cannot proceed] Staff can view the student list name and find the name that doesn’t belong in the placement.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
13 / 15
Appendix 1-5
Use Case Specification 5.4.2 Alternative Flow A-1: Cancel (PSPS_05) The employer presses “Cancel” button The system shall automatically exit. 5.4.3 Exceptional Flow E-1: Cannot proceed (PSPS_05) The employer must choose at least 1 student name for acceptance.
5.5 POST-CONDITIONS
The information of feedback shall be updated. The feedback should be seen by the staff.
5.6 RULE(S)
The employer must choose at least 1 student for their company. The employer can choose more than 1 student for their company.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
5.7 CONSTRAINT(S) Employer must accept at least 1 student to give their feedback
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
14 / 15
Appendix 1-5
Use Case Specification
6 USE CASE: CHECK STATUS (PSPS_06)
Check Status Student
6.1
BRIEF DESCRIPTION
This use case is initiated by the student. This use case will enable the student to view their status of company placement. Staff can view the student status.
6.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The staff must already send the company name to the student page.
6.3 CHARACTERISTIC OF ACTIVATION Student demand
6.4 FLOW OF EVENTS 6.4.1 Basic Flow (PSPS_06) This use case begins when the student select the check status page. The system shall display the company name in their status. [A-1: View] The student can only press “Accept” button to accept the company placement. Staff can view the students who accept the company. 6.4.2 Alternative Flow A-1: View (PSPS_06) The student should press “View” button to view about the company. The system shall automatically display the company page. 6.4.3 Exceptional Flow Not Applicable DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
15 / 15
Appendix 1-5
Use Case Specification
6.5 POST-CONDITIONS The system should maintain the student information without changing after they verify to accept the company for placement.
6.6 RULE(S)
The student can only accept for company. Those who didn’t get the company must begin from the first steps.
6.7 CONSTRAINT(S)
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
Not Applicable.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
16 / 15
Appendix 1-5 Use Case Specification
USE CASE SPECIFICATION
PRACTICUM STUDENTS PLACEMENT SYSTEM (PSPS)
PREPARED FOR: UNIVERSITY OF INFORMATION TECHNOLOGY
Faculty of Information Technology
SYSTEM NAME
DOCUMENT IDENTIFICATION
RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
1 / 15
Appendix 1-5
Use Case Specification
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
TABLE OF CONTENTS 1
USE CASE: LOGIN (PSPS_01) 1.1 BRIEF DESCRIPTION 1.2 PRE-CONDITIONS 1.3 CHARACTERISTIC OF ACTIVATION 1.4 FLOW OF EVENTS 1.4.1 Basic Flow (PSPS_01) 1.4.2 Alternative Flow 1.4.3 Exceptional Flow 1.5 POST-CONDITIONS 1.6 RULE(S) 1.7 CONSTRAINT(S)
5 5 5 5 5 5 5 6 6 6 6
2
USE CASE: REGISTRATION OF STUDENT INFORMATION (PSPS_02)
7
2.1 2.2 2.3 2.4
7 7 7 7 7 7 8 8 8 8
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 2.4.1 Basic Flow (PSPS_02) 2.4.2 Alternative Flow 2.4.3 Exceptional Flow 2.5 POST-CONDITIONS 2.6 RULE(S) 2.7 CONSTRAINT(S) 3
USE CASE: REGISTRATION OF COMPANY/EMPLOYER (PSPS_03) 3.1 BRIEF DESCRIPTION 3.2 PRE-CONDITIONS 3.3 CHARACTERISTIC OF ACTIVATION 3.4 FLOW OF EVENTS 3.4.1 Basic Flow (PSPS_03) 3.4.2 Alternative Flow 3.4.3 Exceptional Flow 3.5 POST-CONDITIONS 3.6 RULE(S) 3.7 CONSTRAINT(S)
9 9 9 9 9 9 10 10 10 10 10
4
USE CASE: MANAGE PRACTICUM PLACEMENT (PSPS_04)
11
4.1 4.2 4.3 4.4
15 11 15 15 15 15 15 16
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 4.4.1 Basic Flow (PSPS_04) 4.4.2 Alternative Flow 4.4.3 Exceptional Flow 4.5 POST-CONDITIONS DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
2 / 15
Appendix 1-5 4.6 4.7
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
5
Use Case Specification RULE(S) CONSTRAINT(S)
16 16
USE CASE: FEEDBACK FROM COMPANY (PSPS_05)
Error! Bookmark not defined.
5.1 5.2 5.3 5.4
BRIEF DESCRIPTION PRE-CONDITIONS CHARACTERISTIC OF ACTIVATION FLOW OF EVENTS 5.4.1 Basic Flow (PSPS_05) 5.4.2 Alternative Flow 5.4.3 Exceptional Flow 5.5 POST-CONDITIONS 5.6 RULE(S) 5.7 CONSTRAINT(S)
Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined.
6
USE CASE: CHECK STATUS (PSPS_06) 6.1 BRIEF DESCRIPTION 6.2 PRE-CONDITIONS 6.3 CHARACTERISTIC OF ACTIVATION 6.4 FLOW OF EVENTS 6.4.1 Basic Flow (RVRS_06) 6.4.2 Alternative Flow 6.4.3 Exceptional Flow 6.5 POST-CONDITIONS 6.6 RULE(S) 6.7 CONSTRAINT(S)
22 22 22 22 22 22 23 23 23 23 23
7
USE CASE: APPLICATION OF POSTPONEMENT (PSPS_07) 7.1 BRIEF DESCRIPTION 7.2 PRE-CONDITIONS 7.3 CHARACTERISTIC OF ACTIVATION 7.4 FLOW OF EVENTS 7.4.1 Basic Flow (PSPS_07) 7.4.2 Alternative Flow 7.4.3 Exceptional Flow 7.5 POST-CONDITIONS 7.6 RULE(S) 7.7 CONSTRAINT(S)
22 22 22 22 22 22 23 23 23 23 23
8
USE CASE: APPROVAL OF POSTPONEMENT (PSPS_08) 8.1 BRIEF DESCRIPTION 8.2 PRE-CONDITIONS 8.3 CHARACTERISTIC OF ACTIVATION 8.4 FLOW OF EVENTS 8.4.1 Basic Flow (PSPS_08) 8.4.2 Alternative Flow 8.4.3 Exceptional Flow 8.5 POST-CONDITIONS 8.6 RULE(S) 8.7 CONSTRAINT(S)
22 22 22 22 22 22 20 20 20 20 20
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
3 / 15
Appendix 1-5
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
9
Use Case Specification
USE CASE: MANAGE PRACTICUM ASSESSMENT (PSPS_09) 9.1 BRIEF DESCRIPTION 9.2 PRE-CONDITIONS 9.3 CHARACTERISTIC OF ACTIVATION 9.4 FLOW OF EVENTS 9.4.1 Basic Flow (PSPS_09) 9.4.2 Alternative Flow 9.4.3 Exceptional Flow 9.5 POST-CONDITIONS 9.6 RULE(S) 9.7 CONSTRAINT(S)
21 21 21 21 21 21 22 22 22 22
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
4 / 15
Appendix 1-5
Use Case Specification
1 USE CASE: LOGIN (PSPS_01)
Log in
Student
1.1
BRIEF DESCRIPTION
This use case is initiated by the students. This use case will enable the student to enter their own ID and password, reset the password and cancel the login.
1.2
PRE-CONDITIONS The student has been registered before using the system.
1.3 CHARACTERISTIC OF ACTIVATION
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
Event Driven
1.4 FLOW OF EVENTS 1.4.1 Basic Flow (PSPS_01) This use case begins when the student inserts their student ID and password. The student then presses the “OK” button [A-1: Cancel] The system shall verify the student ID and password. [E-1: Invalid password and student ID]. The system shall display the Menu Panel on the screen. Student can change their password after they login to the system. [A-2: Reset password] 1.4.2 Alternative Flow A-1: The student can press “CANCEL” button anytime and the system shall automatically exit. A-2: The student can reset their password after login by press the “Reset” button and the system will display the old password.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
5 / 15
Appendix 1-5
Use Case Specification 1.4.3 Exceptional Flow E-1: Invalid Password and student ID (PSPS_01) The system shall prompt the student to enter the correct ID and password again until it’s verify by display the error message, “The ID and password entered are incorrect, please enter again your ID and password.” The system should prompt the student to press “Forgot Password” and insert their email address to view their password.
1.5 POST-CONDITIONS
The student be able to access the menus and use the system.
1.6 RULE(S)
The student shall register before login to the system. The student ID and password must be correctly entered. The password can be Uppercase or Lowercase letter. The password must length 4 until 8 character.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
1.7 CONSTRAINT(S) The student shall register before login. The student ID and password must be applicable when the student login. The student also can only enter the system after the login.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
6 / 15
Appendix 1-5
Use Case Specification
2 USE CASE: REGISTRATION INFORMATION (PSPS_02)
STUDENT
Registration of Student Information
Student
2.1
OF
BRIEF DESCRIPTION
This use case is initiated by the students. This use case will enable the student to add, remove, edit, view and print their personal information. Staff can view the student personal information.
2.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The student must login before using the system.
2.3 CHARACTERISTIC OF ACTIVATION Students demand.
2.4 FLOW OF EVENTS 2.4.1 Basic Flow (PSPS_02) This use case begins when the student enter their personal information page. The system shall display the empty personal information for the student. The student shall fill their information after press “Add” button to update their information. [A-1: Cancel] The student can press “Edit” to edit their information. [A-2: Remove] The student then presses the “OK” button to update it. [E-1: Cannot verify to proceed] The system shall then display the information that has been updated. The student can print their personal information. 2.4.2 Alternative Flow A-1: Cancel (PSPS_02) DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
7 / 15
Appendix 1-5
Use Case Specification
The student can press “Cancel” button if they does not want to add any information. The system shall automatically exit. A-2: Remove (PSPS_02) The student can press “Remove” button to remove their information. The system should automatically update. 2.4.3 Exceptional Flow E-1: Cannot verify to proceed (PSPS_02) The system will pop up the new window browser then display what the student must fill.
2.5 POST-CONDITIONS
The personal information of student shall be updated.
2.6 RULE(S)
The student must fill in the mandatory information.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
2.7 CONSTRAINT(S) Not Applicable
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
8 / 15
Appendix 1-5
Use Case Specification
3 USE CASE: REGISTRATION COMPANY/EMPLOYER (PSPS_03)
Registration of Company
Employer
3.1
OF
BRIEF DESCRIPTION
This use case is initiated by the employer. This use case will enable the employer to view, add, edit or remove their personal information. Staff can view the employer information once the employer register.
3.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The employer must be able to conduct practicum student at their company.
3.3 CHARACTERISTIC OF ACTIVATION Demand by the employer.
3.4 FLOW OF EVENTS 3.4.1 Basic Flow (PSPS_03) This use case will enable employer to add, edit or remove their register information. The system shall display the empty registration company form to be filling by the employer. The employer must press “Add” button to update their information. [A-1: Cancel]. The employer can press “Edit” button to edit their information. [A-2: Remove] The employer will press “OK” button to update their information. [E-1: Cannot verify to proceed] The system should display the update information.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
9 / 15
Appendix 1-5
Use Case Specification 3.4.2 Alternative Flow A-1: Cancel (PSPS_03) The employer can press “Cancel” button if they don’t want to update their information. The system shall automatically exit. A-2: Remove (PSPS_03) The employer can press “Remove” button if they want to remove any information. The system should update the information. 3.4.3 Exceptional Flow E-1: Cannot verify to proceed (PSPS_03) The system will pop up the new window browser then display what the company must fill.
3.5 POST-CONDITIONS
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
The company registration information should be updated by the system.
3.6 RULE(S)
The employer shall register and login to manage their company registration information.
3.7 CONSTRAINT(S) Not Applicable
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
10 / 15
Appendix 1-5
Use Case Specification
4 USE CASE: MANAGE PRACTICUM PLACEMENT (PSPS_05)
Manage Practicum Placement
Staff
4.1
BRIEF DESCRIPTION
This use case is initiated by the staff. This use case will enable the staff to match student and the company for placement.
4.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS Staff will be able to insert the student matric number for match process. The information of employer shall be updated before do matching. The information of student shall be updated before do matching.
4.3 CHARACTERISTIC OF ACTIVATION Staff’s demand
4.4 FLOW OF EVENTS 4.4.1 Basic Flow (PSPS_04) This use case begins when the staff enters the manage practicum placement page. The system shall display and guide the staff to insert the student matric no. inside the search box and press “Match” button. Staff can press “Accept” button to accept the company that match with the student. [A-1: Reject] Staff can press “Submit” button to send the company name to the match student status page. [A-2: Cancel] The system will determine the match student and company requirement. [E1: No matching found]
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
11 / 15
Appendix 1-5
Use Case Specification 4.4.2 Alternative Flow A-1: Reject (PSPS_04) Staff can press “Reject” button to reject the matching found. The system should do nothing until any action by the staff. A-2: Cancel (PSPS_04) The staff can press “Cancel” button. The system should do nothing until any action from the staff. 4.4.3 Exceptional Flow E-1: No matching found (PSPS_04) The system shall guide the staff to go to match manually page or the end of the system directly
4.5 POST-CONDITIONS
The student status should be updated automatically after staff submits the company name to them. The employer status should be updated automatically after staff accepts the student name for them.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
4.6 RULE(S)
The student matric number should insert correctly.
4.7 CONSTRAINT(S) The staff must wait until matching process complete.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
12 / 15
Appendix 1-5
Use Case Specification
5 USE CASE: FEEDBACK FROM COMPANY (PSPS_05)
Feedback
Employer
5.1
BRIEF DESCRIPTION
This use case is initiated by the employer. This use case will enable the employer to view the list student name that match for their company. They can accept or reject.
5.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The match list student name has been sent to the company information page.
5.3 CHARACTERISTIC OF ACTIVATION Event Driven (on employer’s demand)
5.4 FLOW OF EVENTS 5.4.1 Basic Flow (PSPS_05) This use case begins when the employer enters they information page and view the feedback information. The system should display the list of student name that match with they company requirement. Employer can press “Accept” button for each name. [A-1: Reject] Employer can click on the student name link to go to their information. [A-2: View Resume] Employer will press “OK” button to update the feedback. [A-3: Cancel] The system shall display the updated feedback automatically once the employer verify. [E-1: Cannot proceed] Staff can view the student list name and find the name that doesn’t belong in the placement.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
13 / 15
Appendix 1-5
Use Case Specification 5.4.2 Alternative Flow A-1: Cancel (PSPS_05) The employer presses “Cancel” button The system shall automatically exit. 5.4.3 Exceptional Flow E-1: Cannot proceed (PSPS_05) The employer must choose at least 1 student name for acceptance.
5.5 POST-CONDITIONS
The information of feedback shall be updated. The feedback should be seen by the staff.
5.6 RULE(S)
The employer must choose at least 1 student for their company. The employer can choose more than 1 student for their company.
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
5.7 CONSTRAINT(S) Employer must accept at least 1 student to give their feedback
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
14 / 15
Appendix 1-5
Use Case Specification
6 USE CASE: CHECK STATUS (PSPS_06)
Check Status Student
6.1
BRIEF DESCRIPTION
This use case is initiated by the student. This use case will enable the student to view their status of company placement. Staff can view the student status.
6.2
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
PRE-CONDITIONS The staff must already send the company name to the student page.
6.3 CHARACTERISTIC OF ACTIVATION Student demand
6.4 FLOW OF EVENTS 6.4.1 Basic Flow (PSPS_06) This use case begins when the student select the check status page. The system shall display the company name in their status. [A-1: View] The student can only press “Accept” button to accept the company placement. Staff can view the students who accept the company. 6.4.2 Alternative Flow A-1: View (PSPS_06) The student should press “View” button to view about the company. The system shall automatically display the company page. 6.4.3 Exceptional Flow Not Applicable DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
15 / 15
Appendix 1-5
Use Case Specification
6.5 POST-CONDITIONS The system should maintain the student information without changing after they verify to accept the company for placement.
6.6 RULE(S)
The student can only accept for company. Those who didn’t get the company must begin from the first steps.
6.7 CONSTRAINT(S)
This document and the information it contains are property of School of Information Technology and confidential. They shall not be reproduced nor disclosed to any person except to those having a need to know them without prior written consent of School of Information Technology
Not Applicable.
DOCUMENT IDENTIFICATION Faculty of Information Technology
SYSTEM NAME RELIABLE VEHICLE RENTAL SYSTEM
DOCUMENT NO.
VERSION
1.0
PAGE
16 / 15
Related Documents
Use Case Specification
June 2020 16
Use Case
May 2020 11
Use Case
November 2019 37
Use Case
May 2020 15
Specification
November 2019 27
Use Case To Test Case
November 2019 34More Documents from ""
Psps Proposal
June 2020 11
Use Case Specification
June 2020 16
Ch04_project Integration Management
May 2020 17
Cara-cara Format Pc
June 2020 35
Project Charter
June 2020 21