SEMESTER MANAGEMENT
SYSTEM
CS333
ObjectOriented Analysis and Design
Assignment No. 3
USE CASES
Name:
Areeb Arshad
Roll No:
181400149
Submitted to:
Sir Fakhur Lodhi
<Semester Management System>
Table of Contents
1.
2.
Problem Statement
2
Domain Analysis
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2
2
2
3
3
3
3
Introduction
Glossary
General Knowledge about domain
Customer & User
Environment
Tasks & procedures currently performed
Competing software
3.
Scope
4
4.
Specific Requirements
4
4.1
4.2
4
4
Page 1
ofo1
sd 5
Functional Requirements
Quality requirements
<Semester Management System>
1. Problem Statement
Semester management software aims at facilitating instructors and HODs in performing their
routine tasks related to semester efficiently and quickly. Semester management software will be
user friendly and will be time saving. Semester management system will serve its users
throughout the semester. It will overcome the flaws of existing software.
2. Domain Analysis
2.1 Introduction
A semester is Half-year term in a school or university, typically lasting for fifteen to eighteen
weeks, during which academic activities are performed.
Semester management software is a crucial module of university management system. It will
make the routine chores lot easier. Such a system is needed which would automate semester
work so that its users can perform their work smoothly. The motivation for doing domain
analysis is that it helps in creating better software by having comprehensive knowledge of
domain and better communication with the client. It will make the work easier. Domain analysis
also helps the developer to anticipate modifications in software in future and hence creating
software accordingly.
Our aim is to construct new software by analyzing the previous one.
2.2 Glossary

Course credit
A course credit is a unit that gives weight to the value, level or time requirements of an
academic course taken at a school or other educational institution.

ID
University management generate unique number for each student.
2.3 General Knowledge about domain
A semester starts when students get their selves registered into specified courses. Timetable
is provided to the students. Students attend the lecture according to the timetable in selected
rooms. Instructor marks the attendance of the students in every lecture. Instructor takes
assessments of the students either on paper or in lab or through some other way. After
grading them the marks are entered in students’ database. Instructor can modify or update the
attendance as well as assessments. Midterm and final term examination is organized by
examination department. Instructor uploads their marks. At the end of the semester teacher
assign grades to the students according to their performance throughout the semester.
Grading could be relative or absolute.
Many extracurricular activities are also performed throughout the semester.
Head of department do some specific tasks during semester, which are different from that of
teachers:
 Take decision what type of courses should offer in the semester.
 Decide pre-requisite of the courses.
 Solve problems of the students either related to degree or others.
Page 2
ofo1
sd 5
<Semester Management System>
 Can access student data and can check registered courses, academic record and
timetable.
Critical issue
One of the most critical issues is that regular teacher cannot access the previous academic
record of the student unlike head of department. He should have access to the academic
record of pre-requisite course so that he could teach students in a much better way.
2.4 Customer & User
Customer
Gift University
User
Users of semester management system will be
 Instructors
 Head of departments (HODs)
2.5 Environment
Desktop computers are used for software operations. New software will operate on the existing
one.
2.6 Tasks & procedures currently performed
The procedures that are currently used by GIFT UNIVERSITY will help in deciding what
functions we have to implement in our software. Current semester management system can
be used by faculty and HODs to have access to the student’s attendance, examination and
semester records.
 In GIFT UNIVERSITY the current semester management system provide the well
defined interface for attendance. Teachers login the system by their id for attendance
of class students and also modify attendance.
 Teachers can update and modify marks.
 Teachers can view the timetable of a class.
 Teacher can make the outline of whole semester, can update and modify.
 Teacher has access to share server and keep useful data for the students there.
 Head of department (HOD) see all courses which are offered in his department and
teachers name who teach those courses.
 Head of department (HOD) can view the student previous academic record.
 Head of department (HOD) of the related department have more rights than a teacher.
2.7 Competing software
Many universities have different soft wares to get this job done. Every software has its different
specifications and qualities. Similar software is being used in UPC, UOG etc.
Page 3
ofo1
sd 5
<Semester Management System>
3. Identify Scope:
The motivation of making this system is to facilitate the professors and HODs
in their routine tasks by automating the manual tasks. This will help in marking
attendance, assessments, and making the course outline and also can modify it. This
system provides more rights to HODs than regular teachers as they can view all
academic record, attendance record, time table of all students and also which teacher is
teaching which course. HODs can also assign teachers to the courses by using this
system.
The main focus is that this system will allow the teachers to see the previous
record of their students of pre-requisites courses which is not available in previous
system. Teachers can also share data regarding to the courses in share server by using
this system. Moreover, Registration of students, timetable scheduling, organization of
mid and final exams is not included in the scope of this system.
4. Specific Requirements:
1. Software Interface
1.1. Software Requirements:
1. Browser: Mozilla Firefox, Internet Explorer, Google Chrome of latest versions to
run the system online.
2. Database:
 MySQL Database for online.
 Sql Database for windows application.
It will use to create the structure of the data to be stored.
3. Server:
 Xamp Server for Web System.
 Microsoft Sql Server for Windows Application.
This will our server where we store our data.
4. Language:
 Html, CSS, Bootstrap for front-end, PHP for back-end programming, SQL
(Structured Query Language) for database. These will be used for
developing web application.
 .Net (C#) for windows application.
2. Hardware Interface:
1. Computers:

At least 4GB, Hard Disk: At least 80 GB, Processor: At least 2.9 GHz Processor
We need computers to run windows application so that teacher can also run the
application without internet access.
2. Input Devices: Mouse, Keyboard when use operating system

Page 4
ofo1
sd 5
Keyboard and mouse are used to give input to the computer to add information to
the system.
<Semester Management System>
3. Mobile:

Teacher/HOD can use system online via web application using google browser
using mobile phone and can perform his/her tasks.
3. User Interface:
1. Login: First Teacher/HOD see the login panel, here he will enter his id and password,
and then he will click on Log in button. If the system authorize him/her, the system
will appear a dashboard. The system will display dashboard according to the user
means if HOD logged in, he/her find another dashboard because HODs have more
access. Moreover, if the system unauthorized the teacher, system will generate an error
message window.
2. View time table: If the teacher needs to view time table, he will click on time table
icon then a new window will appear that will show time table of student in table form.
3. View teacher’s Courses: If the HOD needs to view teacher’s offered courses
into his department, he will click on teacher course detail icon then a new
window will appear that will show teacher detail in data form.
4. Mark Attendance: If the teacher want to mark attendance he will click the icon. After
that he will chose the class, time, course and section. After that he/she can present all
or absent all the students and can mark the attendance one by one. After that he/she
will save the attendance by clicking save button.
5. Update Attendance: If teacher want to update the attendance, system will ask to
authorize by sending pin to his/her email. After authorizing successfully, he can update
the attendance by selecting class, course, and section.
6. Mark Assessment: If the teacher want to mark assessment he will click the icon. After
that he will select the assessment type and then enter total marks. After that teacher
will enter obtained mark of every student. After that he/she will save the assessment by
clicking save button.
7. Update Assessment: If teacher want to update the assessment, system will ask to
authorize by sending pin to his/her email. After authorizing successfully, he can update
the assessment by selecting that assessment. And will update by clicking on button.
8. Course Outline: First, teacher will write the course outline on word file. After that
teacher will upload that file on the system. If he want to update the file, he will edit
that file and re-upload the file to the system.
9. Pre-requisites course record: If teacher want to see his/her student pre-requisites
course grades, he will click the icon and the list of pre-requisites courses with their
grades, point etc. will appear in tabular form.
10. Academic Record: If HOD want to see the academic record of the student in his/her
department he can see it by clicking record icon. All student list with semester will
appear. When he/she select a student, the whole academic record with courses and
grades will appear in tabular form.
4. Attributes of different modules:
4.1. Attendance will have these attributes:
4.1.1.
Student Id
4.1.2.
Student Name
4.1.3.
Course Name
4.1.4.
Course Code
4.1.5.
Section
4.1.6.
Date
Page 5
ofo1
sd 5
<Semester Management System>
4.1.7.
Class Time
4.1.8.
Present/Absent Status
4.1.9.
No. of classes conducted
4.2. Assessments will have attributes:
4.2.1.
Student Id
4.2.2.
Student Name
4.2.3.
Course Name
4.2.4.
Course Code
4.2.5.
Date
4.2.6.
Assessment type (quiz, viva, exam, etc.)
4.2.7.
Total Marks
4.2.8.
Obtain Marks
4.2.9.
Percentage
4.2.10. Section
4.3. View Timetable details will have these attributes:
4.3.1.
Teacher name
4.3.2.
Course Name
4.3.3.
Course Code
4.3.4.
Room
4.3.5.
Timing
4.3.6.
Section
4.4. View Academic record details will have these attributes
4.4.1.
Student Name
4.4.2.
Student Id
4.4.3.
Degree Name
4.4.4.
Number of Semester have Studied
4.4.5.
Studied Courses Name
4.4.6.
Point
4.4.7.
Grades
4.4.8.
GPA
4.4.9.
CGPA
4.5. Outline details will have these attributes
4.5.1.
Teacher Name
4.5.2.
Course Name
4.5.3.
Course Code
4.5.4.
Credit Hours
4.5.5.
Books Name
4.5.6.
Assessment Rules
4.5.7.
Lecture Wise Topic name
4.6. Course details will have these attributes
4.6.1.
Course Name
4.6.2.
Course Code
4.6.3.
Pre-requisites Courses name
4.6.4.
Credit Hours
4.7. Student Course details will have these attributes
4.7.1.
Student Id
4.7.2.
Student Name
4.7.3.
Current Course Name
4.7.4.
Completed Pre-requisites Courses Name
Page 6
ofo1
sd 5
<Semester Management System>
4.7.5.
Credit Hours
4.7.6.
Grade
4.8. Teacher’s Offered Courses will have these attributes
4.8.1.
Teacher Name
4.8.2.
Teacher Id
4.8.3.
Course Name
4.8.4.
Course Code
4.8.5.
Section
4.8.6.
Department
4.1 Business Requirements (possible):
BR-01: System should ask for authentication of user before accessing to the system.
BR-02: Teacher should be able to mark, update or remove assessments of different types of all
students and update it.
BR-03: Teacher should be able to mark or update attendance of all students.
BR-04: Portal should include an option to view time table for teachers.
BR-05: Portal should have an option to view teachers and offered courses detail.
BR-06: Teacher should be able to share data into the share server using this system.
BR-07: System should have an option to view the performance of students in the pre requisite
of the courses.
4.2 User Requirements (possible):
UR-01: As a teacher, I shall be able to login into the system.
UR-02: As a teacher, I shall be able to mark the attendance of the students.
UR-03: As a teacher, I shall be able to mark the assessment of the students.
UR-04: As a teacher, I shall be able to update the attendance of the students.
UR-05: As a teacher, I shall be able to update the assessment of the students.
UR-06: As a teacher, I shall be able to create the course outline.
UR-07: As a teacher, I shall be able to update the course outline.
UR-08: As a teacher, I shall be able to share data into share server.
UR-09: As a teacher, I shall be able to see my time table.
UR-10: As a teacher, I shall be able to see student’s pre-requisites course record.
UR-11: As a teacher, I shall be able to upload the mid-term and final exams result.
UR-12: As a HOD, I shall be able to view the academic record of all students.
UR-13: As a HOD, I shall be able to view the teacher’s offered courses detail.
UR-14: As a HOD, I shall be able to view the students’ timetable.
UR-15: As a HOD, I shall be able to view the registered courses detail of each student in his
department.
UR-16: As a HOD, I shall be able to add decided courses and pre-requisites courses detail to
the system.
Page 7
ofo1
sd 5
<Semester Management System>
4.3 Functional Requirements:
FR-01: System shall provide the facility to mark the attendance of the students.
FR-02: System shall provide the facility to mark the assessment of the students.
FR-03: System shall provide the facility to update the attendance of the students.
FR-04: System shall provide the facility to update the assessment of the students.
FR-05: System shall provide the facility to create the course outline.
FR-06: System shall provide the facility to update the course outline.
FR-07: System shall provide the facility to share data into share server.
FR-08: System shall provide the facility to see teachers their time table.
FR-09: System shall provide the facility to see student’s pre-requisites course record.
FR-10: System shall provide the facility to upload the mid-term and final exams result.
FR-11: System shall provide the facility to view the academic record of all students.
FR-12: System shall provide the facility to view the teacher’s offered courses detail.
FR-13: System shall provide the facility to teacher to login the system.
FR-14: System shall provide the facility to HODs to see students’ time table.
FR-15: System shall provide the facility to HODs to see students’ registered courses.
FR-16: System shall provide the facility to HODs to add courses and pre-requisite courses.
4.4
NFR (Quality requirements):
NFR-01: System shall authorize the login system of very teachers and HODs.
NFR-02: System shall require teacher’s university email address or phone number for
recovering password.
NFR-03: System shall show all the registered student ids while marking attendance,
assessment, and uploading marks.
NFR-04: System shall not allow to add negative number in total marks in assessments.
NFR-05: System shall not allow to add greater number in obtained marks than total marks
in assessments.
NFR-06: Time Table shall display all the subject names, sections, teacher name and the
timing of lecture and break time.
NFR-07: System shall automatically detect the date while marking the attendance and
assessments.
NFR-08: System shall provide responsive interface to user.
NFR-09: System shall be consistent in every action.
NFR-10: System shall obtain username and password before accessing the share server.
NFR-11: System shall show the list of possible teachers that can teach a specific course to
HODs.
NFR-12: System shall restrict the teacher to enter the marks of all students.
NFR-13: System shall restrict the teacher to mark the attendance of all students.
NFR-14: System shall be user friendly.
NFR-15: System shall be efficient.
NFR-16: System shall authorize the teacher before updating the assessments and attendance.
Page 8
ofo1
sd 5
<Semester Management System>
5. Use Cases
5.1 Login
Use Case ID:
Use Case
Name:
Created By:
Date Created:
Lg-01
Log in
Areeb Arshad
March 12th, 2021
Actor:
Description:
Triggers:
Preconditions:
Postconditions:
Priority:
Frequency of Use:
Normal Course of
Events:
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
Page 9
ofo1
sd 5
Last Updated By: Null
Date Last Null
Updated:
1. Teachers
2. HODs
The objective of this feature is to authorize the user. It will not allow
everyone to sign in in the system and do different tasks. HODs have
more facilities than teachers.
When a user wants to have the access of this system and want to do
different tasks.
1. User shall enter his/her username and password
2. User will click on login button.
1. After login, a dashboard will appear according to the user
(HODs or teacher).
High
Maximum
1. The System will display fields to enter username and
password.
2. User will enter id.
3. User will enter password.
4. User will click on login button.
5. System will authorize the data from the database.
6. A dashboard will appear.
7. The use case ends.
5A1: System cannot authorize the user
1. System will generate an error message that display, “You
enter invalid username/password. Enter again!”
2. The use case return to step 1.
None
1. System must authorize the login action.
2. System must not redirect the login action and shall provide
security.
3. The user can hide and unhide the password.
1. Database is working properly.
2. User login data is in database.
<Semester Management System>
5.2 Mark Attendance
Use Case ID: MrkAttnd-01
Use Case Mark Attendance
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to mark attendance of their classes.
Triggers: The teacher indicates that he/she wants to mark attendance of the
students.
Preconditions:
1. Teacher will have to log in into the system.
2. Teacher will have to click on Mark Attendance Icon.
3. Teacher has assigned to some course/s.
Postconditions:
1. The system will save attendance detail into the system.
2. The system will display error message, if someone’s attendance
is not being marked.
Priority: High
Frequency of Use: Maximum
Normal Course of
1. The teacher indicates that he/she wants to mark attendance of
Events:
the students.
2. First he/she will click on the button, then System send a request
to database to retrieve data of all courses of that teacher.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all his/her courses with section.
6. Teacher will select the class, section and timing.
7. After that the registered student in that class and section will be
displayed in tabular form.
8. The teacher will set the status of the student as Present or
Absent.
9. The system will display a save button at the end of the table.
10. Teacher save the attendance by clicking on Save Button.
11. System will ask user to enter pin again for authentication and
after it data will be save to database.
12. The use case ends.
Alternative Courses: 10A1: The Teacher did not enter some students’ attendance.
1. The system will display an error message that ask teacher to
mark all students’ attendance.
2. Teacher will find which student is not being marked.
3. The use case return to step 8.
11A1: If pin is invalid.
1. System will generate error message and ask to enter pin again.
2. The use case return to step 10.
Includes: None
Page 10
ofo1
sd 5
<Semester Management System>
Special Requirements:
Assumptions:
1. The system must show the record in tabular form.
1. All the record of registered students will be in the database.
2. All the data will be accurate and correct according to the class
and section.
5.3 Update Attendance
Use Case ID: UpdAttnd-02
Use Case Update Attendance
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to update attendance of their classes that has
marked already.
Triggers: The teacher indicates that he/she need to update attendance of the
students.
Preconditions:
1. Teacher will log in into the system.
2. Teacher will click on Update Attendance Icon.
3. Teacher has already marked attendance.
Postconditions:
1. The system will update attendance detail into the system.
2. The system will display error message, if someone’s attendance
is not being marked.
Priority: High
Frequency of Use: Minimum
Normal Course of
1. The teacher indicates that he/she wants to update attendance of
Events:
the students.
2. First he/she will click on the button, then System send a request
to database to retrieve data of all courses of that teacher.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all his/her courses with section.
6. Teacher will select the class, section and timing.
7. After that the registered student with their marked attendance in
that class and section will be displayed in tabular form.
8. The teacher will reset the status of the student as Present or
Absent.
9. The system will display an update button at the end of the table.
10. Teacher save the attendance by clicking on Update Button.
11. System will ask user to enter pin again for authentication and
after it data will be save to database.
12. The use case ends.
Alternative Courses: 11A1: If pin is invalid.
1. System will generate error message and ask to enter pin again.
Page 11
ofo1
sd 5
<Semester Management System>
2.
Includes: None
Special Requirements:
1.
Assumptions:
1.
2.
The use case return to step 10.
The system must show the record in tabular form.
All the record will be in the database.
All the data will be accurate and correct.
5.4 Mark Assessment
Use Case ID: MrkAssmnt-01
Use Case Mark Assessment
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to mark assessment of their classes.
Triggers: The teacher indicates that he/she wants to mark assessment of the
students.
Preconditions:
1. Teacher will have to log in into the system successfully.
2. Teacher will have to click on Mark Assessment Icon.
3. Teacher has assigned to some course/s.
Postconditions:
1. The system will save assessment detail into the system.
2. The system will display error message, if someone’s assessment
is not being marked.
Priority: High
Frequency of Use: Maximum
Normal Course of
1. The teacher indicates that he/she wants to mark assessment of
Events:
the students.
2. First he/she will click on the button, then System send a request
to database to retrieve data of all courses of that teacher.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all his/her courses with section.
6. Teacher will select the class and section.
7. After that the registered student in that class and section will be
displayed in tabular form.
8. Teacher will select the assessment type (Quiz, viva, mid, final,
etc.).
9. The teacher will set the total marks.
10. The teacher will enter obtained marks of each student.
11. The system will display a save button at the end of the table.
12. Teacher save the assessment by clicking on Save Button.
13. System will ask user to enter pin again for authentication and
after it data will be save to database.
14. The use case ends.
Page 12
ofo1
sd 5
<Semester Management System>
Alternative Courses: 12A1: The Teacher did not enter some students’ mark.
1. The system will display an error message that ask teacher to
enter all students’ marks.
2. Teacher will see which student is not being marked.
3. The user case return to step 10.
13A1: If pin is invalid.
1. System will generate error message and ask to enter pin again.
2. The use case return to step 12.
Includes: None
Special Requirements:
2. The system must show the record in tabular form.
Assumptions:
3. All the record of registered students will be in the database
available.
4. All the data will be accurate and correct according to class and
section.
5.5 Update Assessment
Use Case ID: UpdAssmnt-02
Use Case Update Assessment
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to update assessment.
Triggers: The teacher indicates that he/she wants to update assessment of the
students.
Preconditions:
1. Teacher will log in into the system.
2. Teacher will click on update Assessment Icon.
3. Teacher has already marked some assessments.
Postconditions:
1. The system will update assessment detail into the system.
2. The system will display error message, if someone’s assessment
is not being marked.
Priority: High
Frequency of Use: Minimum
Normal Course of
1. The teacher indicates that he/she wants to update assessment of
Events:
the students.
2. The System send a request to database to retrieve data of
registered students.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all his/her courses with section.
6. Teacher will select the class and section.
7. After that the registered student in that class and section will be
displayed in tabular form.
Page 13
ofo1
sd 5
<Semester Management System>
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
8. Teacher will select the assessment type (Quiz, viva, mid, final,
etc.).
9. The system will display the data in tabular form with marked
assessment.
10. The teacher will reset the total marks.
11. The teacher will re-enter obtained marks of required student.
12. The system will display an update button at the end of the table.
13. Teacher save the assessment by clicking on Update Button.
14. System will ask user to enter pin again for authentication and
after it data will be save to database.
15. The use case ends.
12A1: The Teacher did not enter some students’ mark.
1. The system will display an error message that ask teacher to
enter all students’ marks.
2. The user case return to step 7.
14A1: If pin is invalid.
1. System will generate error message and ask to enter pin again.
2. The use case return to step 13.
None
3. The system must show the record in tabular form.
4. All the record will be in the database.
5. All the data will be accurate and correct.
5.6 Teacher Time table
Use Case ID: TchTmTb-01
Use Case View Teacher Time Table
Name:
Created By: Areeb Arshad
Last Updated By: Null
th
Date Created: March 12 , 2021
Date Last Null
Updated:
Actor: Teacher
Description: It will allow teachers to have online access to their timetable of the
classes, so that he/she can manage his/her timing according to the
classes.
Triggers: The teacher indicates that he/she wants to view timetable.
Preconditions:
1. Teacher will have to log in into the system successfully.
2. Teacher will have to click on Mark Assessment Icon.
3. Teacher has assigned to some course/s.
Postconditions:
1. The system will display timetable, if the teacher has assigned
to a course.
Priority: High
Frequency of Use: Average
Normal Course of
1. The teacher indicates that he/she wants to view timetable.
Events:
2. First he/she will click on the button, then system send a
request to database to retrieve data.
Page 14
ofo1
sd 5
<Semester Management System>
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. The system will display the timetable.
6. The use case ends.
3A1: The timetable is not finalized.
1. The system will generate a popup message window that
there is no timetable yet.
2. The use case ends.
3A1: The teacher is not assigned to a course.
1. The system will generate a popup message window that
you are not assigned to any course yet.
2. The system will open the dashboard automatically.
3. The use case ends.
None
1. Time Table must display all the subject names, sections,
and timing of lecture.
2. The system must show the time table in tabular form.
1. The teacher has been assigned to a course.
2. The timetable has defined by admin module.
5.7 Upload Course Outline
Use Case ID: CrsOut-01
Use Case Upload Course Outline
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to upload course outline of his/her regarding
courses. It will also allow the teachers to upload the updated course
outline.
Triggers: The teacher indicates that he/she wants to upload course outline.
Preconditions:
1. Teacher will log in into the system.
2. Teacher will click on course outline Icon.
Postconditions:
1. The system will upload course outline successfully.
Priority: Medium
Frequency of Use: Minimum
Normal Course of Basic Flow 1:
Events:
1. The teacher indicates that he/she wants to upload course
outline.
2. The teacher will click on upload file button.
3. The teacher will upload the file by clicking on Upload Button.
4. The System will upload the file to the database.
5. The use case ends.
Page 15
ofo1
sd 5
<Semester Management System>
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
Basic Flow 2:
1. The teacher indicates that he/she wants to upload updated
course outline.
2. Teacher will deleted the previous uploaded course outline.
3. The teacher will click on upload file button.
4. The teacher will upload the file by clicking on Upload Button.
5. The System will upload the file to the database.
6. The use case ends.
BF1-2A1: The user click on upload file button.
1. The system will display a dialogue window that ask the location
from where he/she wants to upload the course outline.
2. The system will load that file to our system.
3. The user case return to step 3.
BF2-3A1: The user click on upload file button.
1. The system will display a dialogue window that ask the location
from where he/she wants to upload the course outline.
2. The system will load that file to our system.
3. The user case return to step 4.
None
None
1. The teacher has written the course outline.
5.8 Share Data into Share server
Use Case ID: ShareServer-01
Use Case Share Data into Share server
Name:
Created By: Areeb Arshad
Last Updated By: Null
Date Created: March 12th, 2021
Date Last Null
Updated:
Actor: Teachers
Description: It will allow teachers to upload/share course material. From this teacher
can share relevant data from anywhere, so that students can easily
access that data.
Triggers: The teacher indicates that he/she wants to upload/share course material.
Preconditions:
1. Teacher will log in into the system.
2. Teacher will click on Share Data Icon.
Postconditions:
1. The system will upload/share course material successfully.
Priority: High
Frequency of Use: Maximum
Normal Course of
1. The teacher indicates that he/she wants to share course material.
Events:
2. The teacher will click on upload file button.
3. The teacher will upload the files by clicking on Upload Button.
4. The System will upload the files to the database.
5. The use case ends.
Alternative Courses:
2A1: The user click on upload file button.
Page 16
ofo1
sd 5
<Semester Management System>
1. The system will display a dialogue window that ask the
location from where he/she wants to share course material.
2. The system will load that file to our system.
3. The user case return to step 3.
Includes: None
Special Requirements: None
Assumptions:
1. The teacher has required data to share.
5.9 View Pre-requisites Course Result
Use Case ID: PreReqCrsRes-01
Use Case View Pre-requisites Course Result
Name:
Created By: Areeb Arshad
Last Updated By: Null
th
Date Created: March 12 , 2021
Date Last Null
Updated:
Actor: Teacher
Description: It will allow teachers to view Pre-requisites Course Results of their
current student. In case teacher want to check some student
performance in his/her pre requisite course, teacher can see it.
Triggers: The teacher indicates that he/she wants to View Pre-requisites Course
Result.
Preconditions:
1. Teacher will log in into the system.
2. Teacher will click on Pre-requisites Course Icon.
Postconditions:
1. The system will shoe Pre-requisites Course Result.
Priority: Medium
Frequency of Use: Minimum
Normal Course of
1. The teacher indicates that he/she wants to View Pre-requisites
Events:
Course Result.
2. The System send a request to database to retrieve data.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. The system will display the data in tabular form of each student.
6. The teacher will the result of required students.
7. The use case ends.
Alternative Courses: None
Includes: None
Special Requirements: None
Assumptions:
1. All the record will be in the database.
2. All the data will be accurate and correct stored in the database.
5.10 View Academic Record
Use Case ID: AcRcd-01
Use Case View Academic Record
Page 17
ofo1
sd 5
<Semester Management System>
Name:
Created By: Areeb Arshad
Date Created: March 12th, 2021
Last Updated By: Null
Date Last Null
Updated:
Actor: HODs
Description: The system will allow HODs to have online access to view all students’
academic record. This will show the record of all students in his/her
department.
Triggers: The HOD indicates that he/she wants to view academic record of their
students in his/her department.
Preconditions:
1. HOD will log in into the system.
2. HOD will click on View Academic Record Icon.
Post conditions:
1. The system will display academic record, if the record is
available in database.
2. The system will display error message, if the record is not
available in database.
Priority: High
Frequency of Use: Minimum
Normal Course of
1. The HOD indicates that he/she wants to view academic record
Events:
of their students.
2. The System send a request to database to retrieve data.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all the registered students in his/her
department.
6. Teacher will select or search student and click on that.
7. The system will display the academic data in tabular form of
that student.
8. The use case ends.
Alternative Courses: None
Includes: None
Special Requirements:
1. HOD can search the student by his/her name and std id.
2. Data will be in form of list.
3. Record will be in tabular form.
Assumptions:
1. All the record will be in the database.
2. All the data will be accurate and correct stored in the database
by assessment module.
5.11 View Teachers’ Offered Course
Use Case ID: TchOffCrs-01
Use Case View Teachers’ Offered Course
Name:
Created By: Areeb Arshad
Last Updated By: Null
Date Created: March 12th, 2021
Date Last Null
Page 18
ofo1
sd 5
<Semester Management System>
Updated:
Actor: HODs
Description: The system will allow HODs to have online access to view all teachers
with their assigned courses. HODs will see their departments’ teachers’
offered courses.
Triggers: The HOD indicates that he/she wants to view all teachers’ assigned
courses.
Preconditions:
1. HOD will log in into the system.
2. HOD will click on View Teachers’ assigned courses Icon.
Post conditions:
1. The system will display teachers’ assigned courses.
Priority: High
Frequency of Use: Average
Normal Course of
1. The HOD indicates that he/she wants to view teachers’ assigned
Events:
courses.
2. The System send a request to database to retrieve data.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all teachers in his/her department.
6. HOD will search and select the teacher.
7. The system will display the assigned courses in tabular form of
that teacher.
8. The use case ends.
Alternative Courses: None
Includes: None
Special Requirements:
1. HOD can search the teachers by his/her name and id.
2. Data will be in form of list.
3. Record will be in tabular form.
Assumptions:
1. All the record will be in the database.
2. All the data will be accurate and correct stored in the database.
5.12 View Student’s Time Table
Use Case ID: StdTmTble-01
Use Case View Student’s Time Table
Name:
Created By: Areeb Arshad
Last Updated By: Null
Date Created: March 12th, 2021
Date Last Null
Updated:
Actor: HODs
Description: The system will allow HODs to have online access to view all students
time table with their assigned courses. HODs will see their
departments’ students’ offered courses.
Triggers: The HOD indicates that he/she wants to view students’ time table.
Preconditions:
1. HOD will log in into the system.
Page 19
ofo1
sd 5
<Semester Management System>
Post conditions:
Priority:
Frequency of Use:
Normal Course of
Events:
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
2. HOD will click on View Student time table Icon.
1. The system will display student time table.
Low
Minimum
1. The HOD indicates that he/she wants to view students time
table
2. The System send a request to database to retrieve data.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all teachers in his/her department.
6. HOD will search and select the teacher.
7. The system will display the assigned courses in tabular form of
that teacher.
8. The use case ends.
None
None
1. HOD can search the student by his/her name and id.
2. Data will be in form of list.
3. Record will be in tabular form.
4. Time table will display teacher name, course name, section
and timing.
1. All the record will be in the database.
2. All the data will be accurate and correct stored in the database.
5.13 Decide Courses and Pre-requisite Courses
Use Case ID: StdRegCrs-01
Use Case Decide Courses and Pre-requisite Courses
Name:
Created By: Areeb Arshad
Last Updated By: Null
th
Date Created: March 12 , 2021
Date Last Null
Updated:
Actor: HODs
Description: The system will allow HODs to assign courses to the student. They can
decide what kind of course they should offered and which courses are
the pre-requisite of which courses and add this detail to system.
Triggers: The HOD indicates that he/she wants to add course details to system.
Preconditions:
1. HOD will log in into the system.
2. HOD will click on add courses Icon.
Post conditions:
1. The data will be stored into the database.
Priority: High
Frequency of Use: Average
Normal Course of
1. The HOD indicates that he/she need to decide courses and preEvents:
requisite courses.
Page 20
ofo1
sd 5
<Semester Management System>
Alternative Courses:
Includes:
Special Requirements:
Assumptions:
2. HOD will type course name, credit hours, department, field,
and its pre requisite courses.
3. HOD will save the record by clicking on save button.
4. The use case ends.
None
None
None
None
5.14 View Student’s Registered Course
Use Case ID: StdRegCrs-01
Use Case View Student’s Registered Course
Name:
Created By: Areeb Arshad
Last Updated By: Null
th
Date Created: March 12 , 2021
Date Last Null
Updated:
Actor: HODs
Description: The system will allow HODs to have online access to view all students’
registered courses. This will show the record of all students in his/her
department.
Triggers: The HOD indicates that he/she wants to view registered courses of
their students in his/her department.
Preconditions:
1. HOD will log in into the system.
2. HOD will click on View registered courses Icon.
Post conditions:
1. The system will display registered courses record, if the record
is available in database.
2. The system will display error message, if the record is not
available in database.
Priority: Medium
Frequency of Use: Minimum
Normal Course of
1. The HOD indicates that he/she wants to view registered courses
Events:
of their students.
2. The System send a request to database to retrieve data.
3. The System will check whether the data is in the database or
not.
4. The system fetch the data to the system.
5. System will display all the registered students in his/her
department.
6. Teacher will select or search student and click on that.
7. The system will display the registered courses in tabular form
of that student.
8. The use case ends.
Alternative Courses: None
Includes: None
Special Requirements:
1. HOD can search the student by his/her name and student id.
Page 21
ofo1
sd 5
<Semester Management System>
Assumptions:
2. Data will be in form of list.
3. Record will be in tabular form with course code, name, and
credit hours.
1. All the record will be in the database.
2. All the data will be accurate and correct stored in the database
by registration module and according to the department.
6. Use Case Diagram:
The End
Page 22
ofo1
sd 5