Digital Advisor: Talha Jee Abbasi (BCS 27) Alvina Imtiaz (BCS 11) Amber Asghar (BCS 14)

Digital Advisor
Talha Jee Abbasi (BCS 27)

Alvina Imtiaz (BCS 11)
Amber Asghar (BCS 14)
Spring-2021
Supervised By
Dr. Ali Abbas
Department of Computer Science
university of Azad Jammu and Kashmir
University of Azad Jammu and Kashmir

APPROVAL CERTIFICATE
This project, entitled as “Digital Advisor” has been approved for the award of
Bachelors of Science in Computer Science
Committee Signatures:
Supervisor: __________________________
(Dr. Ali Abbas)
Project Coordinator: __________________________
(Dr. Wajid Abbasi)
Head of Department: __________________________
(Dr. Rabia Raiz)

Table of Contents
Contents
Chapter 1.............................................................................................................11
Introduction.........................................................................................................11
1.1. Useful Tools and Technologies..........................................................13
1.2. Project Work Break Down..................................................................14
Chapter 2.............................................................................................................16
Requirement Specification and Analysis............................................................16
2.1 Functional Requirements:......................................................................16
2.2 Non-Functional Requirements:..............................................................19
2.3 System Use Case Modeling...................................................................20
2.4 System Sequence diagram......................................................................72
Chapter 3.............................................................................................................93
System Design....................................................................................................93
3.1. Software Architecture:........................................................................94
3.2. Class Diagram.....................................................................................95
3.3. Sequence Diagram..............................................................................96
3.4. Entity Relationship Diagram.............................................................113
3.4. User Interface Design.......................................................................115
Chapter 4...........................................................................................................126
Testing..............................................................................................................126
4.1. Testing Methodology........................................................................126
4.2. Test Cases.........................................................................................126

List of Tables
Table 2.1: Functional Requirement....................................................................18
Table 2.2: Non-Functional Requirement............................................................19
Table 2.3: Admin Login.....................................................................................24
Table 2.4: Admin Manage Students...................................................................25
Table 2.5: Admin Create Student.......................................................................26
Table 2.6: Admin Read Student..........................................................................27
Table 2.7: Admin Delete Student......................................................................28
Table 2.8: Admin Update Student.....................................................................29
Table 2.9: Admin Manage Head Advisor..........................................................30
Table 2.10: Admin Create Head Advisor..........................................................31
Table 2.11: Admin Read Head Advisor............................................................32
Table 2.12: Admin Delete Head Advisor..........................................................33
Table 2.13: Admin Manage Employees............................................................34
Table 2.14: Admin Create Employee................................................................35
Table 2.15: Admin Read Employee...................................................................36
Table 2.16: Admin Delete Employee................................................................37
Table 2.17: Admin Update Employee...............................................................38
Table 2.18: Admin Manage Department...........................................................39
Table 2.19: Admin Create Department..............................................................40
Table 2.20: Admin Read Department................................................................41
Table 2.21: Admin Delete Department..............................................................42
Table 2.22: Admin Update Department.............................................................43
Table 2.23: Admin Manage Session Term........................................................44
Table 2.24: Admin Create Session Term...........................................................45
Table 2.25: Admin Read Session Term.............................................................46
Table 2.26: Admin Delete Session Term...........................................................47
Table 2.27: Admin Update Session Term..........................................................48
Table 2.28: Admin Manage Program................................................................49
Table 2.29: Admin Create Program...................................................................50
Table 2.30: Admin Update Program..................................................................51
Table 2.31: Admin Delete Program...................................................................52
Table 2.32: Admin Read Program.....................................................................53
Table 2.33: Head Advisor Read Department Students......................................54
Table 2.34: Head Advisor Manage Advisor......................................................55
Table 2.35: Head Advisor Create Advisor........................................................56
Table 2.36: Head Advisor Read Advisor...........................................................57

Table 2.37: Head Advisor Assign Students.......................................................58
Table 2.38: Head Advisor Create Announcement.............................................59
Table 2.39: Head Advisor Add comments........................................................60
Table 2.40: Head Advisor Read Previous History.............................................61
Table 2.41: Advisor Read Students...................................................................62
Table 2.42: Advisor Manage Announcement....................................................63
Table 2.43: Advisor Read Previous Meeting List.............................................64
Table 2.44: Advisor Read Previous History......................................................65
Table 2.45: Student Read Previous History.......................................................66
Table 2.46: System Generate Password.............................................................67
Table 2.47: System Email Account Details.......................................................68
Table 2.48: System Display Advisor.................................................................69
Table 2.49: System Deliver Reports..................................................................70
Table 2.50: System Display Previous Meeting List..........................................71
Table 4.1: Admin Login..................................................................................126
Table 4.2: Admin Login (Invalid email)..........................................................126
Table 4.3: Admin Login (Invalid Password)...................................................127
Table 4.4: Advisor Login.................................................................................127
Table 4.5: Add Advisor...................................................................................128
Table 4.6: Delete Advisor................................................................................128
Table 4.7: View Advisor..................................................................................129
Table 4.8: Update Advisor...............................................................................129
Table 4.9: Add Department.............................................................................130
Table 4.10: Update Department.......................................................................130
Table 4.11: Delete Department........................................................................131
Table 4.12: View Department..........................................................................131
Table 4.13: Create Meeting.............................................................................132
Table 4.14: Create CGPA Announcement.......................................................132
Table 4.15: Assign Advisor.............................................................................133
Table 4.16: View Previous Term History........................................................133
List of Figures
Figure 1: Work Breakdown Structure.................................................................14
Figure 3: Use case Diagram................................................................................23

Figure 4: SSD (Admin Login)............................................................................72

Figure 5: SSD (Admin Register Student)...........................................................73
Figure 6: SSD (Admin Read Students)...............................................................73
Figure 7: SSD (Admin Delete Student)..............................................................74
Figure 8: SSD (Admin Update Student).............................................................74
Figure 9: SSD (Admin Register Employee).......................................................75
Figure 10: SSD (Admin Read Employee)..........................................................75
Figure 11: SSD (Admin Delete Employee)........................................................76
Figure 12: SSD (Admin Update Employee).......................................................76
Figure 13: SSD (Admin Create Head Advisor)..................................................77
Figure 14: SSD (Admin Read Head Advisor)....................................................77
Figure 15: SSD ((Admin Delete Head Advisor))...............................................78
Figure 16: SSD (Admin Create Program)..........................................................78
Figure 17: SSD (Admin Read Program).............................................................79
Figure 18: SSD (Admin Update Program).........................................................79
Figure 19: SSD (Admin Delete Program)..........................................................80
Figure 20: SSD (Admin Create Department).....................................................80
Figure 21: SSD (Admin Read Department)........................................................81
Figure 22: SSD (Admin Delete Department).....................................................81
Figure 23: SSD (Admin Update Department)....................................................82
Figure 24: SSD (Admin Create Session Term)..................................................82
Figure 25: SSD (Admin Read Session Term).....................................................83
Figure 26: SSD (Admin Delete Session Term)..................................................83
Figure 27: SSD (Admin Update Session Term).................................................84
Figure 28: SSD (Head Advisor Read Student)...................................................84
Figure 29: SSD (Head Advisor Create Advisor)................................................85
Figure 30: SSD (Head Advisor Read Advisor)..................................................85
Figure 31: SSD (Head Advisor Assign Students)...............................................86
Figure 32: SSD (Head Advisor Read Previous Record).....................................86
Figure 33: SSD (Head Advisor Create Announcement).....................................87
Figure 34: SSD (Head Advisor Add Meeting Comments).................................87
Figure 35: SSD (Advisor Read Advisory Students)...........................................88
Figure 36: SSD (Advisor Read Previous Meetings)...........................................88
Figure 37: SSD (Advisor Create Announcement)..............................................89
Figure 38: SSD (Advisor Read Report Status)...................................................90
Figure 39: SSD (Student Login).........................................................................90
Figure 40: SSD (Students Read His Previous Meetings)...................................91
Figure 41: Class Diagram...................................................................................95

Figure 42: SD (Admin Create Student)..............................................................96
Figure 43: SD (Admin Read Student)................................................................96
Figure 44: SD (Admin Delete Student)..............................................................97
Figure 45: SD (Admin Update Student).............................................................97
Figure 46: SD (Admin Create Head Advisor)....................................................98
Figure 47: SD (Admin Read Head Advisor)......................................................98
Figure 48: SD (Admin Delete Head Advisor)....................................................99
Figure 49: SD (Admin Create Employee)..........................................................99
Figure 50: SD (Admin Read Employee)..........................................................100
Figure 51: SD (Admin Delete Employee)........................................................100
Figure 52: SD (Admin Update Employee).......................................................101
Figure 53: SD (Admin Create Program)...........................................................101
Figure 54: SD (Admin Read Program).............................................................102
Figure 55: SD (Admin Delete Program)...........................................................102
Figure 56: SD (Admin Update Program)..........................................................103
Figure 57: SD (Admin Create Department)......................................................103
Figure 58: SD (Admin Read Department)........................................................104
Figure 59: SD (Admin Delete Department)......................................................104
Figure 60: SD (Admin Update Department)....................................................105
Figure 61: SD (Admin Create Session Term)...................................................105
Figure 62: SD (Admin Read Session Term).....................................................106
Figure 63: SD (Admin Update Session Term).................................................106
Figure 64: SD (Head Advisor Read Student)...................................................107
Figure 65: SD (Head Advisor Create Advisor)................................................107
Figure 67: SD (Head Advisor Read Advisor)...................................................108
Figure 68: SD (Head Advisor Assign Students)...............................................108
Figure 69: SD (Head Advisor Create Announcement).....................................109
Figure 70: SD (Head Advisor Read Announcements).....................................109
Figure 71: SD (Head Advisor Read Previous Announcements)......................110
Figure 72: SD (Advisor Read Students)...........................................................110
Figure 73: SD (Advisor Read Previous Mattings)............................................110
Figure 74: SD (Advisor Create Announcement)..............................................111
Figure 75: SD (Advisor Read Announcement Status)......................................112
Figure 76: SD (Advisor Read Previous Announcement).................................112
Figure 77: ER Diagram.....................................................................................113
Figure 79: User Sign in.....................................................................................115

Figure 80: Admin Dashboard...........................................................................116

Figure 81: Head Advisor Dashboard................................................................117
Figure 82: User Login.......................................................................................121

Chapter 1
Introduction
A “Digital Advisor” is a web application that is designed to facilitates university advisors
to communicate and convey their message it via call or SMS. This application is designed
for university advisors and their students.
1.1. Project Introduction

Our application will provide service of informing guardians about their child’s progress in
university by filtering out his personal and academic record. Personal record would be
used in case of meeting and announcement to establish a call or send an SMS to
concerned Person.
The first and most important feature of this application would be to establish an
automated call to guardian’s cell number and inform them about student progress via
audio stream on call or via SMS.
The other feature of this Application would be to arrange a meeting with group of
students on specified Data and Time. A string with appropriate message would be sent to
guardians of those students who have their CGPA below certain limit through call and
SMS by the system.
There would be a web admin panel where admin would be able to manage employees,
head advisor of all departments, program and session term. Additionally, Head Advisor of
a specific department would be able manage his department advisors and also schedule a
meeting with students and their supervisors.
The Supervisor would able to manage students under his advisory and will have the
option of call a meeting with them. Also, he can check the history of previous term. A
suggestion of free slots of student would also given to advisor so he can select meeting
time according to that.

1.2. Useful Tools and Technologies
PHP (Laravel), HTML, CSS, JavaScript, MySQL and services of SendPk and Twilio can
be used to develop this application.
Laravel is a web application framework with expressive, elegant

syntax.
PhpStorm provides Supports different languages like HTML, CSS,

Bootstrap, JavaScript and PHP.
MySQL database management system is a freeware environment

and can be use.

1.3. Project Work Break Down
Software Project
Implementation Testing
Requirement Design
Analysis
Requirement Talha jee abbasi Talha jee abbasi
Talha jee abbasi Talha jee abbasi
Gathering Alvina Imtiaz Alvina Imtiaz
Alvina Imtiaz Alvina Imtiaz
Amber asghar Amber asghar
Amber asghar Amber asghar
Talha jee abbasi
Alvina Imtiaz
Amber asghar
Database
Talha jee
abbasi
Identification of Logical Design Alvina
functional & non- Imtiaz
Business functional Alvina Imtiaz Amber
Scope Requirements asghar
Alvina Talha jee abbasi Amber asghar Test Case
Imtiaz Alvina Imtiaz Admin
Amber asghar Talha jee
Amber Alvina abbasi
asghar Imtiaz
Alvina Imtiaz
Head Amber asghar

advisor
Alvina
Interview Use Case imtiaz
Architecture
Alvina Imtiaz Alvina Imtiaz
Alvina Imtiaz Advisor
Amber asghar Amber asghar Alvina
Amber asghar imtiaz
Call
Talha
SMS
Amber
Email
Talha

Figure 1: Work Breakdown Structure
Chapter 2
Requirement Specification and Analysis

This chapter includes requirements, which are required for intended software. This chapter
explains how user will interact with system and how it will respond.
2.1 Functional Requirements:

The functional requirements of software that is being developed are as follows.
S.No Functional Requirements Types Status

1. The Admin will login into the system. Core Complete
2. Admin will manage Employees. Core Complete
3. Admin will manage head advisor. Core Complete
4. Admin will manage Students. Core Complete
5. Admin will Upload Student data through excel File. Core Complete
6. The Admin will manage program. Core Completed
7. The Admin will manage Session Term. Core Completed
8. The Admin will manage Departments. Core Complete
9. The System will provide mechanism for head advisor to get Intermediate Complete
his login credentials.
10. The System will Generate Email once an Employee is Intermediate Complete
assigned as Head advisor.
11. The Head Advisor will login into the system. Core Complete
12. The Head Advisor will see the list of students of his Core Complete
department.
13. The System will display the list of advisors. Core Complete
14. The Head Advisor will assign Advisor to student. Core Complete

15. The Head Advisor will also add himself as an Advisor and Core Complete
Assign Students to himself.
16. The Head Advisor will see the list of Students under his Core Complete
Advisory.
17. The Head Advisor will conduct meeting with all Students of Core Complete
Department.
18. The Head Advisor will conduct meeting with Students under Core Complete
his advisory.
19. The Head Advisor Will Generate Meeting Report. Core Complete
20. The Head Advisor Will Add Comments to Meeting Report. Core Complete
21. The Head Advisor will see the list of All Attendee of Core Complete
Meeting.
22. The Head Advisor will see the record of Previous Session Core Complete
Term.
23. The Head Advisor will able to see the free slots of student. Intermediate Complete
24. The System will send a list of students to an advisor via Core Complete
Email.
25. The System will send a SMS Message to students to inform Core Complete
about his advisor.
26. The System will generate the notification for meeting Core Complete
remainder.
27. The Advisor will login to System. Core Complete
28. The Advisor would be able to see list of students under his Intermediate Complete
advisory.
29. The Advisor will Conduct meeting with Students under his Core Complete
Advisory.
30. The Advisor will write different type of message for Core Complete
Guardians and Students.
31. The Advisor will able to see the list of delivered reports. Intermediate Complete
32. The Advisor will able to request system to resend Core Complete
undelivered reports.
33. The Advisor will see the record of Previous Session Term. Core Complete
34. The Advisor will able to see the free slots of student. Intermediate Complete
35. The System will generate list of undelivered reports. Core Complete

36. The System will generate list of delivered reports. Core Complete
37. The System will generate call and send SMS to students or Core Complete
guardians upon advisor’s request.
38. The System will generate report of those students whose Core Complete
CGPA is below specified criteria.
39. The System will generate email for advisor if he forgot his Core Complete
login details.
40. The System will manage the advisor meeting with students Core Complete
and guardians.
41. The Student will login to System Core Complete
42. The Student will able to see his advisor. Core Complete
43. The Student will see the record of Previous Meetings. Core Complete
Table 2.1: Functional Requirement
2.2 Non-Functional Requirements:

Followings are the Non-functional requirements of the software shown in Table 2.2.
Non-Functional Requirements
1. The throughput cycle between any operation should be consistent.
2. The System should cancel call and dial next number after 2mins if no response is
received.
3. The system should be user friendly. The usability should be accurate.
Table 2.2: Non-Functional Requirement

2.3 System Use Case Modeling
A use case defines a set of use-case instances, where each instance is a sequence of
actions a system performs that yields an observable result of value to a particular actor.

Figure 2: Use case Diagram

Table 2.3: Admin Login
Use Case ID: Uc1
Use Case Name: Login
Created By: Alvina Imtiaz Last Updated By: Talha jee abbasi
Date Created: 10/11/2020 Last Revision Date: 4/9/2021
Actors: Admin
Description: The Admin can login to the system by entering the email and
password that is provided by system.
Trigger: Login button
Preconditions: Admin provides email and password into login form and click on
login button for login into the system.
Postconditions: Admin will be login into the system and then he will able to use
the system.
Normal Flow: Admin System
1: Admin open the System. The system provides

Admin login form.
2: Admin fill the form by System get the entered email
entering the email and and password and match it
password and press the Login with database, if it is correct
button. then he will login the Admin
Successfully.
Alternative Flows: Admin cancel the login request.
Exceptions: 1. The form is empty (Null pointer Exception).

2. The database is not responding or database connection is
not created.
3. The System is not responding.
Table 2.4: Admin Manage Students
Use Case ID: Uc2
Use Case Name: Manage Students

Created By: Alvina imtiaz Last Updated By: Talha jee abbasi
Actors: Admin
Description: The Admin can manage all students. He will read, add, modify
and delete all students.
Trigger: Manage Students Tab
Preconditions: Admin click on Manage Students Tab.

Postconditions: Admin will enter into the manage student page and he/she will
view the students list. He/she also get the add new student,
update and delete student option.
1: Admin clicks Manage The system provides the List of

student tab. all registered students. The
system also provides the add
new student option, edit and
delete student option also.
2: Admin click on any option. System display the new page
according to selected option.
Alternative Flows: Admin cancel Manage students request.
Exceptions: 1. The System is not responding.

Table 2.5: Admin Create Student
Use Case ID: Uc2.1
Use Case Name: Create Student
Actors: Admin
Description: The Admin can Register new student by entering the

registration_number, name, phone_number, email, CNIC, GPA,
CGPA, DOB, credit_Hour, department and program in system.
Trigger: Add Student (+) Icon
Preconditions: Admin click on Manage Students Tab. After that he/she will click on
Add Student (+) Icon from Manage student Tab Page.
Postconditions: Admin will fill the Student registration form by entering the
registration_number, name, phone_number, email, CNIC, GPA,
CGPA, DOB, credit_Hour, department and program in the
registration form. After that admin click the Create New Student
button to register the student.

student Tab. all registered students. The
2: Admin click on Add Student System display the student
(+) Icon. registration form.
3: Admin will fill the Student System will save the student
registration form by entering record in database.
the registration_number,
name, phone_number, email,
CNIC, GPA, CGPA, DOB,
credit_Hour, department and
program in the registration
form and press the Create
New Student button.
Alternative Flows: Admin cancel student registration form.

2. The form is empty (Null pointer Exception).

not created.
Table 2.6: Admin Read Student
Use Case ID: Uc2.2
Use Case Name: Read Student
Actors: Admin
Description: The Admin can Read or Watch the list of all registered students.
Trigger: Manage Student Tab
Preconditions: Admin click on Manage Students Tab. After that the system display
the list of all students with edit and delete options.
Postconditions: Admin will view or check the registered students list.
1: Admin clicks Manage The system provides the list of

student Tab. all registered Students.
Alternative Flows: Admin cancel the read student request.

not created.

Table 2.7: Admin Delete Student
Use Case ID: Uc2.3
Use Case Name: Delete Student
Actors: Admin
Description: The Admin can delete registered students.

Trigger: Delete button
Preconditions: Admin click on Manage Students Tab. After that read the student
that are registered.
Postconditions: Admin will select student that shown in list by clicking Delete
button. After clicking the button confirm or cancel the deletion
from pop up.

2: Admin click on delete System display the pop up for
button from list. confirmation of student.
3: Admin select confirm from System will delete the student.
pop up.
Alternative Flows: Admin cancel the delete student from pop up.

not created.

Table 2.8: Admin Update Student
Use Case ID: Uc2.4
Use Case Name: Update Student
Actors: Admin
Description: The Admin can update the registered student data by selecting
the student. Admin will enter the new data in the required fields
(registration_number, name, phone_number, email, CNIC, GPA,
CGPA, DOB, credit_Hour, department and program) on the
update student form.
Trigger: Update student button
Preconditions: Admin click on Manage Students Tab. After that he will click on Edit
student button from the list.
Postconditions: Admin will select student form list by clicking edit button and enter
the new data in the required fields (registration_number, name,
phone_number, email, CNIC, GPA, CGPA, DOB, credit_Hour,
department and program) on the update student form. After
entering new data press update Student button.

2: Admin click on Edit button System display the update
from list. student form.
3: Admin fill the student System will update the student
update form by entering new
data (registration_number,
name, phone_number, email,
CNIC, GPA, CGPA, DOB,
credit_Hour, department and
program)
Alternative Flows: Admin cancel the update form.

not created.

Table 2.9: Admin Manage Head Advisor
Use Case ID: Uc3
Use Case Name: Manage Head Advisors
Actors: Admin
Description: The Admin can manage all Head Advisors. He / She will create
new Head Advisor, read registered Head Advisors and Delete
Head Advisors.
Trigger: Manage Advisors Tab
Preconditions: Admin click on Manage Advisors Tab.

Postconditions: Admin will enter into the manage Advisor Page and read the list of
all registered advisor. Admin also get the option of create and
delete head advisor.
1: Admin clicks Manage Advisor The system provides the list of

Tab. all registered head advisors.
The system also gives the
option of create new head
advisor or delete old head
advisor.
2: Admin click on any System display the result
operation (create or delete) against selected operation.
from list.
Alternative Flows: Admin cancel Manage Advisor request.

Table 2.10: Admin Create Head Advisor
Use Case ID: Uc3.1
Use Case Name: Create Head Advisor
Actors: Admin
Description: The Admin can create new Head Advisor by entering the
employee Name, department and program.
Trigger: Create Head Advisor button
Preconditions: Admin click on Manage Advisor Tab. After that he will click on
register Head Advisor (+) icon.
Postconditions: Admin will fill the Advisor registration form by entering the Name,
department and program. When click on create Head Advisor
button the system will generate head advisor.
Admin System
Normal Flow:
advisor.
2: Admin click on register Head System display the Head
Advisor (+) icon. Advisor registration form.
3: Admin will fill the Advisor System will save the Head
registration form by entering Advisor record in database.
the Name, department and
program in the registration
form and press the Create
Head Advisor button.
Alternative Flows: Admin cancel Head Advisor registration form.

2. The form is empty (Null pointer Exception).
not created.
Table 2.11: Admin Read Head Advisor
Use Case ID: Uc3.2

Use Case Name: Read Head Advisor
Actors: Admin
Description: The Admin can Read or Watch the list of all registered Head
Advisors.
Trigger: Manage Head Advisor Tab
Preconditions: Admin click on Manage Head Advisor Tab. After that he will read all
Registered Head Advisors list.
Postconditions: Admin will view or check the registered Advisors list.

Alternative Flows: Admin cancel the read Head Advisor request.

not created.

Table 2.12: Admin Delete Head Advisor
Use Case ID: Uc3.3
Use Case Name: Delete Head Advisor
Actors: Admin
Description: The Admin can delete Head Advisor.

Preconditions: Admin click on Manage Head Advisors Tab. After that he will click
on delete button from the list.
Postconditions: Admin will press the delete button and confirm or cancel the
deletion of Head Advisor.
1: Admin clicks Manage Head The system provides the list of

Advisor tab. all registered head advisors.
advisor.
2: Admin click on delete System display the
button from list. confirmation pop up.
3: Admin select confirm System will delete Head
button. Advisor according to admin
request.
Alternative Flows: Admin cancel the delete list.

not created.
Table 2.13: Admin Manage Employees
Use Case ID: Uc4

Use Case Name: Manage Employees
Actors: Admin
Description: The Admin can Manage the employees. Admin can create, read,
update and delete the employee.
Trigger: Manage Employee Tab
Preconditions: Admin can click on Manage Employee Tab.

Postconditions: Admin will read the list of registered employees. Admin can create
new employee, delete and update the existing employees.
1: Admin Click on Manage The system provides the list of

Employee Tab. all registered employees. The
system also provides the option
of create, edit and delete the
employee.
2: Admin can select any option System will perform the
(create, delete and update) to operation according to
perform any operation. selection.
Alternative Flows: Admin cancel the Manage Employee tab.

2. The database is not responding.
Table 2.14: Admin Create Employee
Use Case ID: Uc4.1
Use Case Name: Create Employee

Actors: Admin
Description: The Admin can create or register the new employee by entering
the name,email, gender, address, phone_number, image, role,
session_term, department, CNIC, designation in the registration
form.
Trigger: Create New Employee button

Postconditions: Admin will read the list of registered employees. Admin can create
new employee by entering the employee data in registration form.

of create, edit and delete the
employee.
2: Admin can click on Create System will display the
New Employee (+) icon, registration form.
3: The Admin can enter the The System will register the
name, email, gender, address, new employee in the database.
phone_number, image, role,
session_term, department,
CNIC, designation in the
registration form.
Alternative Flows: Admin cancel the create new employee.

Table 2.15: Admin Read Employee
Use Case ID: Uc4.2
Use Case Name: Read Employee
Created By: Alvina imtiaz Last Updated By: Alvina imtiaz
Actors: Admin
Description: The Admin can Read the list of registered employees.

Trigger: Manage Employee Tab.

Postconditions: Admin will read the list of registered employees. Admin can
perform the action like delete of update the register employees.

of edit and delete the
employee.
Alternative Flows: Admin cancel the read registered employees.

Table 2.16: Admin Delete Employee
Use Case ID: Uc4.3
Use Case Name: Delete Employee
Actors: Admin
Description: The Admin can Read the list of registered employees and delete
the employees from the list.
Trigger: Delete button.

Postconditions: Admin will read the list of registered employees. Then admin can
click on Delete button and delete the employee after the
confirmation.

employee.
2: Admin can click on Delete The system will display the
button from list against confirmation pop up with
employee. confirm or close option.
3: The admin can select the The system will remove the
confirm button for deleting employee from the system
employee. records.
Alternative Flows: Admin cancel the employee delete.

Table 2.17: Admin Update Employee
Use Case ID: Uc4.4
Use Case Name: Update Employee
Actors: Admin
Description: The Admin can Read the list of registered employees and Update
the employees from the list.
Trigger: Update button.

Postconditions: Admin will read the list of registered employees. Then admin can
click on update button and update the employee after entering the
new data into the registration form.


employee.
2: Admin can click on Edit The system will display the
button from list against update form.
employee.
3: The admin can enter the The system will Update the
new data in to the form and employee record in the system.
click on Update Employee
Button.
Alternative Flows: Admin cancel the employee update.

Table 2.18: Admin Manage Department
Use Case ID: Uc5
Use Case Name: Manage Departments
Actors: Admin
Description: The Admin can Manage the Departments. Admin can create,
read, edit and delete the departments.
Trigger: Department Tab
Preconditions: Admin need to click on the Department Tab.

Postconditions: Admin can read the Departments list and also create new
department, edit and delete the existing departments.

1: Admin clicks on Department The system provides
Tab The list of registers
departments. It also displays
the list of create new
department, delete
department and update
department.
2: Admin can select the one System perform any action
option (create, Delete and against the selected operation.
update).
Alternative Flows: Admin cancel the Department Tab.
Exceptions:
not created.
Table 2.19: Admin Create Department
Use Case ID: Uc5.1
Use Case Name: Create Department
Actors: Admin
Description: The Admin can Create the new Department by entering the
name of department and description of department in the
creation form.
Trigger: Create New Department Button

Postconditions: Admin can read the Departments list and also create new
department.
1: Admin clicks on Department The system provides

Tab The list of registers

departments. It also displays
the list of create new
department, delete
department and update
department.
2: Admin can select the (+) System display the
icon from Department Tab department creation form.
page.
3: Admin can enter the name The system can create of save
and description of department the department data in the
in the form and click Create records of system.
New Department Button.
Alternative Flows: Admin cancel the new department creation.
Exceptions: 1. The database is not responding or database connection is
not created.
Table 2.20: Admin Read Department
Use Case ID: Uc5.2
Use Case Name: Read Department
Actors: Admin
Description: The Admin can Read the list of Departments that already exists
in the system.
Trigger: Department Tab

Postconditions: Admin can read the Departments list and also delete or edit the
department.
1: Admin clicks on Department The system provides the list of

Tab the departments with edit and
delete option.

Alternative Flows: Admin cancel the Department Tab.
not created.
Table 2.21: Admin Delete Department
Use Case ID: Uc5.3
Use Case Name: Delete Department
Actors: Admin
Description: The Admin can Delete the department.
Trigger: Delete Button

Postconditions: Admin can read the Departments list and also delete the
department.

delete option.
Button. confirmation pop up with
close and confirm option.

3: Admin can select the confirm The system will remove the
for deleting the department. department from the list.
Alternative Flows: Admin cancel the Department delete from pop up.
not created.
Table 2.22: Admin Update Department
Use Case ID: Uc5.4
Use Case Name: Update Department
Actors: Admin
Description: The Admin can Update the department.
Trigger: Update Button

Postconditions: Admin can read the Departments list and also Update the
department.

delete option.
2: Admin can click on Update The system will display the
Button. update form.
3: Admin can enter the The system will update the

department new data and click department record from the
on update department button. system.

Alternative Flows: Admin cancel the Department update.
not created.
Table 2.23: Admin Manage Session Term
Use Case ID: Uc6
Use Case Name: Manage Session Term
Actors: Admin
Description: The Admin can the mange the session term by creating, reading
updating and deleting the session term.
Trigger: Term Tab
Preconditions: Admin click on Term Tab
Postconditions: Admin will view or check the list of Session Terms and create
update and delete the session terms.
1: Admin can click on Term Tab The system provides the list of
session terms and also provide
the create, update, delete
option.
2: The admin can select one The system can perform the
option. operation according to
selected option.
Alternative Flows: Admin can cancel the Term Tab.

not created.
Table 2.24: Admin Create Session Term
Use Case ID: Uc6.1
Use Case Name: Create Session Term
Actors: Admin
Description: The Admin can Create the new session term by entering the
term number in the creation form.
Trigger: Create New Term button
Postconditions: Admin will view or check the list of Session Terms and create the
new session terms.
option.
2: The admin can select (+) icon The system can display the
from the Term Tab page. term Creation form.
3: Admin can enter the term The system will create the new
number in form and click on session term in the database.
Create New Term Button.
Alternative Flows: Admin can cancel the new term creation.

not created.
Table 2.25: Admin Read Session Term
Use Case ID: Uc6.2
Use Case Name: Read Session Term
Actors: Admin
Description: The Admin can Read the session terms that already stored in
the database.
Trigger: Term Tab
Postconditions: Admin will view or check the list of Session Terms.
session terms with the edit
and delete option.
Alternative Flows: Admin can cancel the Term Tab.

not created.

Table 2.26: Admin Delete Session Term
Use Case ID: Uc6.3
Use Case Name: Delete Session Term
Actors: Admin
Description: The Admin can Read the session terms list and delete the
session term that shown in the list.
Postconditions: Admin will view or check the list of Session Terms and delete the
session term by clicking the delete button.
option.
button against term in list. confirmation box with close
and confirm button.
3: The admin can select the The system will delete the
confirm button. term from the database.
Alternative Flows: Admin can cancel the Term delete from pop up.

not created.

Table 2.27: Admin Update Session Term
Use Case ID: Uc6.4
Use Case Name: Update Session Term
Actors: Admin
Description: The Admin can Read the session terms list and update the
session term that shown in the list.
Trigger: Update button
Postconditions: Admin will view or check the list of Session Terms and Update the
session term by clicking the update button.
option.
2: Admin can click on Update The system will display the
button against term in list. update form for session term.
3: The admin can enter the The system will update the
term new data and click on term record in the database.
Update term button
Alternative Flows: Admin can cancel the Term update.

not created.

Table 2.28: Admin Manage Program
Use Case ID: Uc7
Use Case Name: Manage Programs
Actors: Admin
Description: Admin can Manage the programs by creating new programs,

reading programs, deleting and updating the programs.
Trigger: Program Tab
Preconditions: Admin click on Program tab.
Postconditions: System provide the list of registered programs with create, delete
and edit option.
1: Admin can click on the The system displays the list of

Manage Program Tab. registered programs with
create new program, edit and
delete program option.
2: Admin can select one option. The system performs the
action according to selected
option.
Alternative Flows: Admin cancel the Program Tab.

not created.

Table 2.29: Admin Create Program
Use Case ID: Uc7.1
Use Case Name: Create Programs
Actors: Admin
Description: Admin can create the new program by entering the program
title, abbreviation and department in the creation form.
Trigger: Create New Program button.
Postconditions: System provide the form in which user need to enter the program
details and click on Create new program button.

2: Admin can select (+) from The system will display the
the program tab page. program creation form.
3: Admin can enter program The system will create the new
title, abbreviation and program in the database.
department and click on Create
New Program button.

not created.
Table 2.30: Admin Update Program
Use Case ID: Uc7.2

Use Case Name: Update Programs
Actors: Admin
Description: Admin can Update the new program by entering the new
program title, abbreviation and department in the creation
form.
Trigger: Update Program button.
Postconditions: System provide the form in which user need to enter the program
new details and click on Update program button.

2: Admin can select update The system will display the
button. program update form.
3: Admin can enter program The system will update the
new data and click on Update program in the database.
Program button.
Alternative Flows: Admin cancel the Program update.

not created.

Table 2.31: Admin Delete Program
Use Case ID: Uc7.3
Use Case Name: Delete Programs
Actors: Admin
Description: Admin can view the program and click on delete button against
program for deleting it.
Trigger: Delete button.
Postconditions: System provide the list of programs and admin can select on the
delete button.

2: Admin can select delete The system will display the
button. confirmation box with confirm
and cancel button.
3: Admin can click on the The system will delete the
confirm button. program from database.
Alternative Flows: Admin cancel the Program delete by close button.

not created.
Table 2.32: Admin Read Program
Use Case ID: Uc7.4

Use Case Name: Read Programs
Actors: Admin
Description: Admin can view the program list that already stored in the
system.
Trigger: Program Tab.
Postconditions: System provide the list of programs with edit and delete button.

Manage Program Tab. registered programs with edit
and delete program option.

not created.
Table 2.33: Head Advisor Read Department Students
Use Case ID: Uc8
Use Case Name: Read Department Student

Created By: Talha jee abbasi Last Updated By: Amber asghar
Actors: Head Advisor
Description: The Head Advisor can check the list of students of his
department. He / She also check the student by Assign or Non-
Assign Students.
Trigger: All Students Tab
Preconditions: Head Advisor click on All Students Tab.
Postconditions: Head Advisor can see all students of department. It can also filter
students by assign and un assign students.
Normal Flow: Head Advisor System
1: Head Advisor clicks All The system provides the List of

Students Tab. all students of departments. It
also provides the option of
Assign and Unassign students.
2: Head Advisor can select The system will display list of
Assign or un Assign Students if students according to option
he/she want filter. selected.
Alternative Flows: Head Advisor close the All Students Tab.

not created.
Table 2.34: Head Advisor Manage Advisor
Use Case ID: Uc9
Use Case Name: Manage Advisor

Description: The Head Advisor Can Manage the advisors by assigning/

creating new advisor, reading the advisors that already
assigned.
Trigger: Assign Advisor Tab
Preconditions: Head Advisor click on Assign Advisor Tab.
Postconditions: Head Advisor can see list of all assigned advisor. The head advisor
also creates new head advisor and also add the more students in
previous advisor.
1: Head Advisor clicks Assign The system provides the List of

Advisor Tab. all assigned or created
advisors. It also provides the
option of create new advisor
or assign students to already
created advisors.
2: Head Advisor can select one The system will perform the
option. action according to the
selected option.
Alternative Flows: Head Advisor close the Assign Advisor Tab.

not created.
Table 2.35: Head Advisor Create Advisor
Use Case ID: Uc9.1
Use Case Name: Create Advisor
Description: The Head Advisor Can create or assign advisor to students.

Trigger: Assign Advisor in Term
Postconditions: Head Advisor can see list of all assigned advisor. Then the Head
Advisor can click on (+) from page and enter the advisor name,
starting range and ending range in form.

advisors. It also provides the
option of create new advisor
or assign students to already
created advisors.
2: Head Advisor can select (+) The system will display the
from Head Advisor Tab page. registration form
3: Head Advisor enter the The system will create the
name, starting range, ending advisor.
range in the form and click
Create Advisor in Term button.
Alternative Flows: Head Advisor cancel the advisor creation.

not created.
Table 2.36: Head Advisor Read Advisor
Use Case ID: Uc9.2
Use Case Name: Read Advisors
Description: The Head Advisor Can read the all created head advisors and
check their students.
Trigger: Assign Advisor Tab

Postconditions: The system will display the list of all already registered or created
advisors list those or under the head advisor.

advisors.
Alternative Flows: Head Advisor cancel the advisor creation.

not created.
Table 2.37: Head Advisor Assign Students
Use Case ID: Uc9.3
Use Case Name: Assign Students
Description: The Head Advisor can assign more students to already created
Advisor.
Trigger: Assign More Student

Postconditions: The system will display the list of all already registered with
Assign more Student option against each advisor.
1: Head Advisor clicks Assign The system will display the list
Advisor Tab. of create Advisor with Assign
more students button.
2: Head Advisor can select the The System will display the
Assign more student Button. form.
3: The Head Advisor can enter The system will assign the
one or more students one by one student against that advisor.
and click the Assign Student
button.
Alternative Flows: Head Advisor cancel the Assign more student.

not created.
Table 2.38: Head Advisor Create Announcement
Use Case ID: UC10
Use Case Name: Create Announcement
Description: The Head Advisor can create the announcement for meeting or
CGPA.
Trigger: Process Button
Preconditions: Head Advisor click on Meeting Tab.
Postconditions: The Head Advisor can create the meeting by providing the
information in Announcement Form.

1: Head Advisor clicks Meeting The system displays the
Tab announcement form.
2: The Head Advisor can enter The system will create the
the data for Meeting or enter meeting and store it in the
the data for CGPA system.
Announcement and press the
process button.
Alternative Flows: Head Advisor cancel the announcement creation.

not created.
Table 2.39: Head Advisor Add comments
Use Case ID: UC11
Use Case Name: Add Comments
Description: The Head Advisor can add the comments on the generated
reports.
Trigger: Add Comments Button.
Preconditions: Head Advisor click on Meeting Report Tab.
Postconditions: The Head Advisor can view the list of meetings and add the
comments on it.
1: Head Advisor clicks Meeting The system displays the list of

Report Tab generated reports. It also
shows the add comments

button against each report.
2: The Head Advisor can select The system will display the
the Add Comments button. comment box.
3: The head advisor writes the The system will add the
comment in comment box and comment against selected
click the Add Comment button. report.
Alternative Flows: Head Advisor cancel the add comment.

not created.
Table 2.40: Head Advisor Read Previous History
Use Case ID: UC12
Use Case Name: Read Previous History
Created By: Talha jee abbasi Last Updated By: Talha jee abbasi
Description: The Head Advisor can read the previous session Terms History.
It also views the reports against it.
Trigger: Previous Term History Tab
Preconditions: Head Advisor click on Previous Term History Tab
Postconditions: The Head Advisor can view the list records against selected
session terms and also check reports history against that term.
1: Head Advisor clicks Previous The system displays the list of

Term History Tab. previous history according to
selected term. It also displays
the Report button.
2: The Head Advisor can select The system will display the list
the Report button to view the of reports.

reports against single advisor
of that term,
Alternative Flows: Head Advisor cancel Previous terms history.

not created.
Table 2.41: Advisor Read Students
Use Case ID: Uc13
Use Case Name: Show Students
Created By: Amber asghar Last Updated By: Alvina imtiaz
Actors: Advisor
Description: The Advisor Can see the list of all students under his advisory.
Trigger: Advisory Student Tab
Preconditions: Advisor click on Advisory Student Tab
Postconditions: The system will display the list of all students those are under his
advisory.
Normal Flow: Advisor System
1: Advisor clicks on Advisory The system provides the List of

Students tab all students under his advisory
with detail.
Alternative Flows: Advisor cancel the Advisory students Tab.

not created.
Table 2.42: Advisor Manage Announcement
Use Case ID: UC14
Use Case Name: Manage Announcement
Actors: Advisor
Description: The Advisor can manage or create the announcement for

meeting or CGPA.
Trigger: Process Button
Preconditions: Advisor click on Meeting Tab.
Postconditions: The Advisor can create the meeting by providing the information
in Announcement Form.
1: Advisor clicks Meeting Tab The system displays the

announcement form.
2: The Advisor can enter the The system will create the
data for Meeting or enter the meeting and store it in the
data for CGPA Announcement system.
and press the process button.

Alternative Flows: Advisor cancel the announcement creation.

not created.
Table 2.43: Advisor Read Previous Meeting List
Use Case ID: UC15
Use Case Name: Previous Meetings List
Actors: Advisor
Description: The Advisor can read the list of previous meetings.

Trigger: Meeting Report Tab.
Preconditions: Advisor click on Meeting Report Tab.
Postconditions: The Advisor can view the list of meetings that created already.
Normal Flow: Advisor System
1: Advisor clicks Meeting The system displays the list of

Report Tab generated reports. It also
shows the add comments
button against each report.
2: The Head Advisor can select The system will perform action
any option. against that option
Alternative Flows: Advisor cancel the previous meetings list.

not created.
Table 2.44: Advisor Read Previous History
Use Case ID: UC16
Use Case Name: Read Previous History
Actors: Advisor
Description: The Advisor can read the previous session Terms History. It also
views the reports against it.
Preconditions: Advisor click on Previous Term History Tab
Postconditions: The Advisor can view the list records against selected session
terms and also check reports history against that term.
1: Advisor clicks Previous Term The system displays the list of

History Tab. previous history according to
selected term. It also displays
the Report button.
2: The Advisor can select the The system will display the list
Report button to view the of reports.
reports against single advisor
of that term,
Alternative Flows: Advisor cancel Previous terms history.

not created.
Table 2.45: Student Read Previous History
Use Case ID: UC17
Use Case Name: Previous Meeting History
Created By: Talha jee abbasi Last Updated By: Alvina imtiaz
Actors: Student
Description: The Student can see who is her advisor and also see the
previous history of all terms.
Preconditions: Student click on Previous Term History Tab
Postconditions: The Student can view the name of his advisors and list of all
meetings reports.
Normal Flow: Student System
1: Student clicks Previous Term The system displays the list of

History Tab. previous history term wise.
Alternative Flows: Student cancel Previous terms history.

not created.

Table 2.46: System Generate Password
Use Case ID: Uc18
Use Case Name: Generate Password
Actors: System
Description: The System generate the password against Registered

employees. When admin register the employee the system
automatically generates the random password against
employee
Trigger: Create Employee
Preconditions: Receive the employee Registration request by admin.

Advisor must be registered.
Postconditions: Generate the password against employee username.
Normal Flow: System
1: System receive the employee Registration Request.

2: System Registered the employee and generate the password
against username.
Alternative Flows: System denied / reject the request.

not created.

Table 2.47: System Email Account Details
Use Case ID: Uc18.1
Use Case Name: Email Account Details
Actors: System
Description: The System email the employee account information

(username, password) to employee after generating the
password.
Trigger: Register Advisor button
Preconditions: Receive the employee Registration request by admin.

employee must be registered.
System Generate the password against advisor username.
Postconditions: Email the account details to advisor.
Normal Flow: System
1: System receive the employee Registration Request.

2: System Registered the employee and generate the password
against username.
3: System Email the account details (username, password) to
advisor.
Alternative Flows: System not send the email

not created.

Table 2.48: System Display Advisor
Use Case ID: Uc19
Use Case Name: Display employees
Actors: System
Description: The System fetch the registered employee from database when
Admin, head advisor or advisor request and display the list of
that employees to them.
Trigger: Read button
Preconditions: Receive the request for display employee.

The employee must be registered.
Postconditions: System fetch the employee from database and display it to user.
Normal Flow: System
1: System receive the Request.

2: System fetch the employee from database.
3: System display the employee.

not created.
Table 2.49: System Deliver Reports

Use Case ID: Uc20
Use Case Name: Deliver Reports
Actors: System
Description: The System will deliver the reports whose status is 0. It

delivered according to selected medium Call or SMS.
Trigger: Deliver Report
Preconditions: Reports must be existing in system records.

Postconditions: System fetch the reports from database and deliver it to students
according to selected medium.
Normal Flow: System
1: System Check the Reports automatically in the records.

2: If system found any report in record with status 0then it
delivers it to student.
3: After delivering the report it updates the status of report. In
case of call it update according to user response.

not created.
Table 2.50: System Display Previous Meeting List
Use Case ID: Uc21
Use Case Name: Display Previous Meetings

Actors: System
Description: The System fetch the previous meetings from database that
held between Advisor, Head Advisors and students. System
show the meetings list to advisor or Head Advisor.
Trigger: Previous Meeting List
Preconditions: Receive the Advisor or Head Advisor request for display previous
meetings.
Postconditions: System fetch the meetings from database and display it to advisor
or head Advisor.
Normal Flow: System
1: System receive the Advisor or Head Advisor Request for

Previous meetings.
2: System fetch the all meetings from database.
3: System display the meetings list to advisor or Head Advisor.

not created.
1.5 System Sequence diagram

Figure 3: SSD (Admin Login)

Figure 4: SSD (Admin Register Student)
Figure 5: SSD (Admin Read Students)

Figure 6: SSD (Admin Delete Student)
Figure 7: SSD (Admin Update Student)

Figure 8: SSD (Admin Register Employee)
Figure 9: SSD (Admin Read Employee)

Figure 10: SSD (Admin Delete Employee)
Figure 11: SSD (Admin Update Employee)

Figure 12: SSD (Admin Create Head Advisor)
Figure 13: SSD (Admin Read Head Advisor)

Figure 14: SSD ((Admin Delete Head Advisor))
Figure 15: SSD (Admin Create Program)

Figure 16: SSD (Admin Read Program)
Figure 17: SSD (Admin Update Program)

Figure 18: SSD (Admin Delete Program)
Figure 19: SSD (Admin Create Department)

Figure 20: SSD (Admin Read Department)
Figure 21: SSD (Admin Delete Department)

Figure 22: SSD (Admin Update Department)
Figure 23: SSD (Admin Create Session Term)

Figure 24: SSD (Admin Read Session Term)
Figure 25: SSD (Admin Delete Session Term)

Figure 26: SSD (Admin Update Session Term)
Figure 27: SSD (Head Advisor Read Student)

Figure 28: SSD (Head Advisor Create Advisor)
Figure 29: SSD (Head Advisor Read Advisor)

Figure 30: SSD (Head Advisor Assign Students)
Figure 31: SSD (Head Advisor Read Previous Record)

Figure 32: SSD (Head Advisor Create Announcement)
Figure 33: SSD (Head Advisor Add Meeting Comments)

Figure 34: SSD (Advisor Read Advisory Students)
Figure 35: SSD (Advisor Read Previous Meetings)

Figure 36: SSD (Advisor Create Announcement)

Figure 37: SSD (Advisor Read Report Status)
Figure 38: SSD (Student Login)

Figure 39: SSD (Students Read His Previous Meetings)

3.1. Class Diagram
The class diagram describes the attributes and operations of a class and the constraints
imposed on the system. The class diagrams are widely used in the modeling of object-
oriented systems because they are the only UML diagrams, which can be mapped directly
with object-oriented languages:
Figure 41: Class Diagram

3.3. Sequence Diagram
Sequence Diagram describe the behaviors of classes within the system in a visual manner
enabling us to document and validate our logic. It is used for both analysis and design
purpose.
Figure 42: SD (Admin Create Student)
Figure 40: SD (Admin Read Student)

Figure44: SD (Admin Delete Student)
Figure45: SD (Admin Update Student)

Figure46: SD (Admin Create Head Advisor)
Figure47: SD (Admin Read Head Advisor)

Figure48: SD (Admin Delete Head Advisor)
Figure49: SD (Admin Create Employee)

Figure50: SD (Admin Read Employee)
Figure51: SD (Admin Delete Employee)

Figure52: SD (Admin Update Employee)
Figure53: SD (Admin Create Program)

Figure54: SD (Admin Read Program)
Figure55: SD (Admin Delete Program)

Figure56: SD (Admin Update Program)
Figure56: SD (Admin Create Department)

Figure57: SD (Admin Read Department)
Figure58: SD (Admin Delete Department)

Figure59: SD (Admin Update Department)
Figure60: SD (Admin Create Session Term)

Figure61: SD (Admin Read Session Term)
Figure62: SD (Admin Update Session Term)

Figure63: SD (Head Advisor Read Student)
Figure64: SD (Head Advisor Create Advisor)
Figure65: SD (Head Advisor Read Advisor)

Figure66: SD (Head Advisor Assign Students)
Figure67: SD (Head Advisor Create Announcement)

Figure68: SD (Head Advisor Read Announcements)
Figure69: SD (Head Advisor Read Previous Announcements)
Figure70: SD (Advisor Read Students)

Figure71: SD (Advisor Read Previous Mattings)
Figure72: SD (Advisor Create Announcement)

Figure73: SD (Advisor Read Announcement Status)
Figure74: SD (Advisor Read Previous Announcement)

3.4. Entity Relationship Diagram
Figure75: ER Diagram
3.5. User Interface Design

User Sign in:
Figure75: User Sign in
Admin Dashboard:
Figure 41: Admin Dashboard

Head Advisor Dashboard:
Figure 42: Head Advisor Dashboard
4.1. Software Description

Following are the major modules that are being developed in this Project.

 Admin Login

Figure 43: User Login

Chapter 4
Testing
Software Testing is defined as an activity to check whether the actual results match the
expected results and to ensure that the software system is defect free. It involves execution of
a software component or system component to evaluate one or more properties of interest.
4.1. Testing Methodology

Testing plan makes sure that the deliverable product is robust and stable. Our adopted testing
methodology is “unit testing”. The goal of unit is to segregate each part of program and test
that the individual parts are working properly. Unit testing has proven its value in that a large
percentage of defects are identified during its use.
4.2. Test Cases

 Admin login
Table 5.51: Admin Login
Date: 17/07/2021 Tested By: Talha jee abbasi

System: Digital Advisor Environment: Chrome
Objective: Admin Login Test ID: 1
Version: 1.1 Testing Type: Unit
Input:
Username: talhajee321@gmail.com
Password: 123
Expected Result: Login Successful

Actual Result: Admin Successfully Logged In into system
Table 5.52: Admin Login (Invalid email)

Objective: Admin Login Test ID: 2
Input:
Username: alvina123@gmail.com
Password: 12345
Expected Result: Login Failed

Actual Result: Error: Invalid User.
Table 5.53: Admin Login (Invalid Password)

Objective: Admin Login (Invalid) Test ID: 3
Input:
Email: alvina123@gmail.com
Password: tfyft5
Expected Result: Login Failed

Actual Result: Error: Invalid User/Password
 Advisor Login
Table 5.54: Advisor Login

Objective: Advisor Login Test ID: 4
Input:
Email: talha@gmail.com
Password: 123123
Expected Result: Login Successful

Actual Result: Advisor Successfully Logged In into system
 Add New Advisor

Table 5.55: Add Advisor

Objective: Add Advisor Account Test ID: 5

Input:
Name: Talha
Username: Talha123
Email: talhajee321@gmail.com
Password: abc123
Phone No: 03426055451
Extension: 22
Designation: Professor
Gender: Male
Department: Computer Science
Expected Result: Advisor Added Successfully
Actual Result: Message Display: Advisor Added Successfully
 Delete Advisor
Table 5.56: Delete Advisor

Objective: Delete Advisor Account Test ID: 6
How Test Case was Generated: Admin Clicked on “Advisor Drop down menu” and select
Delete Advisor option to Delete Advisor from list.
Expected Result: Advisor Record Deleted Successfully
Actual Result: Dialogue Box: Confirmation Message to Delete Data
 View Advisor
Table 5.57: View Advisor

Objective: View Advisor list Test ID: 7
How Test Case was Generated: Admin Clicked on “Advisor Drop down menu” and select
All Advisor option to View list of all Advisors.

Expected Result: Display List of All Advisors
Actual Result: Shown List of All Advisor
 Edit Advisor
Table 5.58: Update Advisor

Objective: Update Advisor Test ID: 8
How Test Case was Generated: Admin Clicked on “Advisor Drop down menu” to see list
of all Advisors and Click on Update advisor.
Inputs:
Name: Talha jee abbasi
Username: Talha jee abbasi123
Email: Talha jee abbasi@gmail.com
Phone No: 03406055451
Extension: 22
Designation: Professor
Gender: Male
Department: Computer Science
Expected Result: Update Advisor

Actual Result: Message: Update Data Successfully
 Add Department
Table 5.59: Add Department

Objective: Add Department Test ID: 9
How Test Case was Generated: Admin Clicked on “Department Drop down menu” to see
list of all Departments and Click on Add Department.
Inputs:
Department Name: Computer Science

Abbreviation: CS
Expected Result: Department Added
Actual Result: Message: Department Added Successfully
 Update Department
Table 5.60: Update Department

Objective: Update Department Test ID: 10
list of all Department and Click on Edit Department.
Inputs:
Department Name: Computer Science
Abbreviation: CS
Expected Result: Department Updated
Actual Result: Message: Department Update Successfully
 Delete Department
Table 5.61: Delete Department

Objective: Delete Department Test ID: 11
list of all Department and Click on Delete Department.
Expected Result: Department Deleted

Actual Result: Message: Department Deleted Successfully

 View Department
Table 5.62: View Department

Objective: View Department Test ID: 12
list of all Advisors and Click on View Department.
Expected Result: Display List of All Departments

Actual Result: Shown List of All Departments
 Create Meeting
Table 5.63: Create Meeting

Objective: Create Meeting Test ID: 13
How Test Case was Generated: Advisor or Head Advisor Clicked on Meeting Tab and fill
meeting form and press process button.
Inputs:
Purpose: Meeting
Announcement To: Amber asghar, Alvina imtiaz, Talha jee abbasi
Date: 7/19/2021
Start Time: 8:00 AM
End Time: 9:00AM
Venue: B1
Announcement Type: Call/SMS

Message: “You need to mee with his supervisor”
Expected Result: Create and Display Meeting in Record

Actual Result: Meeting Created Successfully
 Create CGPA Announcement

Table 5.64: Create CGPA Announcement

Objective: Create Cgpa Announcement Test ID: 14
How Test Case was Generated: Advisor or Head Advisor Clicked on Meeting Tab and fill
meeting form and press process button.
Inputs:
Purpose: Meeting
Announcement To: Muhammed Mudassar, Alvina imtiaz, Talha jee abbasi
Announcement Type: Call/SMS
Announcement Template: Default/Write Now
Message: “You have obtained 2.7 Cgpa.”
Expected Result: Create and Display Meeting in Record

Actual Result: Meeting Created Successfully
 Assign Advisor
Table 5.65: Assign Advisor

Objective: Assign Advisor to Students Test ID: 15
How Test Case was Generated: Head Advisor Clicked on “Assign Advisor Tab” to assign
the advisor to students.
Inputs:
Advisor: Alvina imtiaz
Starting Range: BCS163017
Ending Range: BCS163032
Expected Result: Display All students Against Advisor

Actual Result: Assign Advisor Successful (Display all assigned Students)

 Previous Term History
Table 5.66: View Previous Term History

Objective: View Previous History of Terms Test ID: 16
How Test Case was Generated: Advisor or Head Advisor Clicked on “Previous Term
History” to see list of all Reports.
Expected Result: Display List of All Reports and Advisors

Actual Result: Shown List of All Reports and Advisors

Digital Advisor: Talha Jee Abbasi (BCS 27) Alvina Imtiaz (BCS 11) Amber Asghar (BCS 14)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Digital Advisor: Talha Jee Abbasi (BCS 27) Alvina Imtiaz (BCS 11) Amber Asghar (BCS 14)

Uploaded by

Copyright:

Available Formats

Digital Advisor

Talha Jee Abbasi (BCS 27)

Department of Computer Science

university of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

Bachelors of Science in Computer Science

(Dr. Ali Abbas)

Project Coordinator: __________________________

(Dr. Wajid Abbasi)

Head of Department: __________________________

(Dr. Rabia Raiz)

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

Figure 3: Use case Diagram................................................................................23

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

Figure 79: User Sign in.....................................................................................115

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

1.1. Project Introduction

University of Azad Jammu and Kashmir

Laravel is a web application framework with expressive, elegant

PhpStorm provides Supports different languages like HTML, CSS,

MySQL database management system is a freeware environment

University of Azad Jammu and Kashmir

Head Amber asghar

University of Azad Jammu and Kashmir

Requirement Specification and Analysis

2.1 Functional Requirements:

S.No Functional Requirements Types Status

2. Admin will manage Employees. Core Complete

3. Admin will manage head advisor. Core Complete

4. Admin will manage Students. Core Complete

6. The Admin will manage program. Core Completed

7. The Admin will manage Session Term. Core Completed

8. The Admin will manage Departments. Core Complete

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

Table 2.1: Functional Requirement

2.2 Non-Functional Requirements:

3. The system should be user friendly. The usability should be accurate.

Table 2.2: Non-Functional Requirement

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

University of Azad Jammu and Kashmir

Use Case ID: Uc1

Use Case Name: Login

Date Created: 10/11/2020 Last Revision Date: 4/9/2021

Trigger: Login button

Normal Flow: Admin System

1: Admin open the System. The system provides

Exceptions: 1. The form is empty (Null pointer Exception).

Table 2.4: Admin Manage Students

Use Case ID: Uc2

Use Case Name: Manage Students

University of Azad Jammu and Kashmir

Date Created: 10/11/2020 Last Revision Date: 4/09/2021

Preconditions: Admin click on Manage Students Tab.

1: Admin clicks Manage The system provides the List of

Alternative Flows: Admin cancel Manage students request.

Exceptions: 1. The System is not responding.