3.

2 Detailed Use Case

Represents the in depth process involved in actualizing the modules listed in use case diagram all
the steps the user undertakes. The system responses to user interactions and alternative flow of
actions users may face.
3.2.1 Use Case UC1: Login

3.2.1.1 Name: Login

3.2.1.2 Scope: Paper Free CUI
3.2.1.3 Primary Actor: User
3.2.1.4 Description: User will login using the registration no or ID
Student: Student use Reg No for login
Faculty: Faculty use ID for Login
3.2.1.5 Stakeholders and Interests:
User: User will login using the registration no or ID
3.2.1.6 Preconditions:
Login Form UI must be opened
3.2.1.7 Success Guarantee (Post conditions):
User will successfully Login
3.2.1.8 Extensions:
Alternative Flow:
System displays a error message if user enter invalid Reg No or ID.

3.2.2 Use Case UC2: Verify Reg No

3.2.2.1 Name: Verify Reg No

3.2.2.2 Scope: Paper Free CUI
3.2.2.3 Primary Actor: Student
3.2.2.4 Description: It verify Reg no from database
3.2.2.5 Stakeholders and Interests:
Student: Verify Reg no from database
3.2.2.6 Preconditions:
Login Form must be opened , and student enter Reg no
3.2.2.7 Success Guarantee (Post conditions):
Student will successfully Login
3.2.1.8 Extensions:
Alternative Flow:
System displays a error message if Student enter invalid Reg No

3.2.3 Use Case UC3: Verify faculty ID

3.2.3.1 Name: Verify faculty ID

3.2.3.2 Scope: Paper Free CUI
3.2.3.3 Primary Actor: Faculty
3.2.3.4 Description: It verify ID from database
3.2.3.5 Stakeholders and Interests:
Faculty: Verify ID from database
3.2.3.6 Preconditions:
Login Form must be opened , and Faculty enter ID
3.2.3.7 Success Guarantee (Post conditions):
Faculty member will successfully Login
3.2.1.8 Extensions:
Alternative Flow:
System displays a error message if Faculty enter invalid ID

3.2.4 Use Case UC4: Submit Application

3.2.4.1 Name: Submit Application

3.2.4.2 Scope: Paper Free CUI
3.2.4.3 Primary Actor: Student, Faculty
3.2.4.4 Description: User Submit their application
3.2.4.5 Stakeholders and Interests:
User: User Submit their application
3.2.4.6 Preconditions:
Interface must be open, and user select application for submit
3.2.4.7 Success Guarantee (Post conditions):
User successfully submit their application

3.2.4 Use Case UC5: Select Application

3.2.5.1 Name: Select Application

3.2.5.2 Scope: Paper Free CUI
3.2.5.3 Primary Actor: Student, Faculty
3.2.5.4 Description: User Select application for submit
3.2.5.5 Stakeholders and Interests:
User: User Select application for submit
3.2.5.6 Preconditions:
Select application UI must be opened
3.2.5.7 Success Guarantee (Post conditions):
User successfully Select application
3.2.5.8 Extensions:
Alternative Flow:
System displays a message Please select a application

3.2.6 Use Case UC6: Enter Application Data

3.2.6.1 Name: Enter Application Data

3.2.6.2 Scope: Paper Free CUI
3.2.6.3 Primary Actor: Student, Faculty
3.2.6.4 Description: User enters application data for submit
3.2.6.5 Stakeholders and Interests:
User: User enters application data for submit
3.2.6.6 Preconditions:
Select application UI must be opened

3.2.6.7 Success Guarantee (Post conditions):

User successfully enter application data
3.2.6.8 Extensions:
Alternative Flow:
System displays a message Please enters application data first

3.2.7 Use Case UC7: Cancel Application under Process

3.2.7.1 Name: Cancel Application under Process

3.2.7.2 Scope: Paper Free CUI
3.2.7.3 Primary Actor: Student, Faculty
3.2.7.4 Description: User can cancel their application before application submission
3.2.7.5 Stakeholders and Interests:
User: User can cancel their application before application submission
3.2.7.6 Preconditions:
Submit application UI must be open
3.2.7.7 Success Guarantee (Post conditions):
User successfully cancels application

3.2.8 Use Case UC8: View Notification

3.2.8.1 Name: View Notification
3.2.8.2 Scope: Paper Free CUI
3.2.8.3 Primary Actor: Student, Faculty
3.2.8.4 Description: User View notification after submit or cancel application
3.2.8.5 Stakeholders and Interests:
User: User View notification after submit or cancel application
3.2.8.6 Preconditions:
Login Form UI must be opened

3.2.8.7 Success Guarantee (Post conditions):

Player will successfully view notification

3.2.9 Use Case UC9: Manage User Account

3.2.9.1 Name: Manage User Account

3.2.9.2 Scope: Paper Free CUI
3.2.9.3 Secondary Actor: Admin
3.2.9.4 Description: Admin manage the users account
3.2.9.5 Stakeholders and Interests:
Admin: Admin manage the user account
3.2.9.6 Preconditions:
Application form submitted
3.2.9.7 Success Guarantee (Post conditions):
Admin successfully manage the users account

3.2.4 Use Case UC10: Manage Application Form

3.2.10.1 Name: Manage Application Form

3.2.10.2 Scope: Paper Free CUI
3.2.10.3 Secondary Actor: Admin
3.2.10.4 Description: Admin manage the application forms
3.2.10.5 Stakeholders and Interests:
Admin: Admin manage the application forms
3.2.10.6 Preconditions:
Application form submitted
3.2.10.7 Success Guarantee (Post conditions):
Admin successfully manage the application forms

3.2.11 Use Case UC11: Manage Application Request

3.2.11.1 Name: Manage Application Form

3.2.11.2 Scope: Paper Free CUI
3.2.11.3 Primary Actor: Faculty
3.2.11.4 Description: Faculty manage the user application requests
3.2.11.5 Stakeholders and Interests:
Faculty: Faculty manage the user application requests
3.2.11.6 Preconditions:
Application form submitted
3.2.11.7 Success Guarantee (Post conditions):
Faculty successfully manage the application request

3.2.12 Use Case UC12: Submit Attendance Form

3.2.12.1 Name: Submit Attendance Form

3.2.12.2 Scope: Paper Free CUI
3.2.12.3Primary Actor: Adviser
3.2.12.4 Description: Advisor Submit the attendance form to coordinate office
3.2.12.5 Stakeholders and Interests:
Advisor: Advisor Submit the attendance form to coordinate office
3.2.12.6 Preconditions:
Application form submitted
3.2.12.7 Success Guarantee (Post conditions):
Advisor successfully submit the attendance form

3.2.13 Use Case UC13: Accept Attendance Form

3.2.13.1 Name: Accept Attendance Form

3.2.13.2 Scope: Paper Free CUI
3.2.13.3 Secondary Actor: Coordination Office
3.2.13.4 Description: Coordination office accept attendance form
3.2.13.5 Stakeholders and Interests:
Coordination office: Coordination office accept attendance form
3.2.13.6 Preconditions:
Advisor Submit the attendance form
3.2.13.7 Success Guarantee (Post conditions):
Coordination office successfully accept attendance form

3.2.14 Use Case UC14: Notify Attendance marked

3.2.14.1 Name: Notify Attendance marked

3.2.14.2 Scope: Paper Free CUI
3.2.14.3 Secondary Actor: Coordination Office
3.2.14.4 Description: User receive a notification when attendance is marked
3.2.14.5 Stakeholders and Interests:
User: User receive a notification when attendance is marked
3.2.14.6 Preconditions:
Coordinate office accept attendance marked
3.2.14.7 Success Guarantee (Post conditions):
User successfully notify attendance marked