Use Case Descriptions of College Management System Project 

By: Prof. Fazal Rehman Shamil | Whatsapp:+923028700085

Use Case Descriptions of College Management System Project

College Management System Project SRS Download

Name: Student Management
Description: Register new students in college and maintain the record students in CMS. view the student information and “update” the record of students in case of any changes and “Delete” the record if any.

Precondition: The user type must be an admin to add a new student in the system. A student must be eligible for admission in college(students must fulfill the requirements of the college to get admission).

Flow:

  • Check whether the student is eligible to get admission in college.
  • Provide a form to the student to get the information about a student.
  • Check whether the student fills the form correctly.
  • Enter the data into CMS through an interface.
  • Save the information of student and student is registered.
  • Edit the existing information and “update” if any change is made.
  • Users can “Delete” the existing records.

Postcondition: student registered.

Alternative Flow: If the information provided by the student is not completed or not relevant to requirement then the student cannot get registered and asks for correct information.

 

Name: Attendance Management

Description: View the record of attendance of students and manage the attendance details.

Precondition: If the user type is admin then, have full access to view and make changes in the record if any.

Flow:

  • Enter the scholar number and other related information in the attendance

form.

  • “update” the attendance to save the record in the database.
  • View the attendance record of students and “Delete” if any.

Post Condition: Attendance record updated.

 

Name: Internal Marks

Description: view the marks of students in internal exams. And can add new marks in the system and manage the marks details.

Precondition:  If user type is an admin then, have full access to view and make changes in a record if any. A student must be registered for this module

Flow:

  • Enter the scholar number of student and other information related to student
    profile and exam details.
  • Enter the details of marks of exams.
  • Save the record if new entry.
  • If the record is already saved about the desired student then “update” the record of

Students related to marks. And can “Delete” if any.

Postcondition: Marks of students are entered into the system and saved in the database.

Name: User registration

Description: admin can create new users for the system which are employees of the college. Admin creates their profile for the user and provides the user name and password to login to the system.

Precondition: The user must be an employee of the college. One user can have only one user name about his profile.

Flow :

  • Check availability for a user if the user is new then it is able to create a new users for the system.
  • Enter the details of the user needed to create a new user.
  • Save the record if new entry.
  • When data is entered then save the information and register the user.
  • Admin can edit the information (user name/ password etc.).
  • “update” record if any change is made.
  • Users can “Delete” the existing records.

Postcondition:  User registered.

Alternative Flow: If the user is already registered with the same user name then it cannot be registered with the same user name, and have to change the user name and then again check availability and register.

 

Name: Employee Management

Description: Admin registers new employees in college and saves their information in a database for a different purpose. Admin can add new employees, can “Delete” and “update” the information of existing employees.

Precondition: the Desired person must fulfill the eligibility criteria that are defined by the college to get employment in college.

Flow :

  • Check whether the person is eligible to get employment in college.
  • Provide a form to the person to get the information about the employee.
  • Check whether the information is filled correctly in the form.
  • Enter the data into CMS through an interface.
  • Save the information about that person.
  • Registered as an employee.
  • Edit the existing information and “update” if any change is made.
  • Users can “Delete” the existing records.

Postcondition: employee registered.

Alternative Flow:

if the information given by the employee is incomplete or employee didn’t fulfill the criteria of college, the employee cannot be registered

 

Name: Salary Management

Description: Admin pays the employees in college and save their information about transactions of salary and “update” the salary record in the database.

Precondition: Employees must be registered in a database and only one time in a month he/she can get salary payment.

Flow :

  • Check whether the employee already got the salary or not.
  • If the employee didn’t get his/her salary in running month pay him/her.
  • Check salary details about employees and verify all deduction if any.
  • Enter salary detail into the database.
  • Give a receipt.

Postcondition: Salary paid.

 

Name: Department Management

Description: Admin can view the department details and can manage the information about any department.

Precondition: Admin is logged in to view the information about the department which is already stored in a database and can add a new department which didn’t already exist.

Flow :

  • To add a new department enter the information required for the department asked by the system.
  • Save the entered information into the database.
  • Edit the existing information and “update” in case of any change.
  • “Delete” if the user wants to remove any record.

Postcondition: The new department is saved in the database.

 

Name: Course management

Description: Admin can view the course which is offering by college and can manage the courses and can add new courses that college wishes to offer.

Precondition: User type must be an admin to add new courses and manage the existing courses.

Flow:

  • If a user wants to add a new course into the system, enter the information related

to course.

  • Save the entered information into the database.
  • Edit information and “update” it if any change is made.
  • Users can “Delete” the existing record.

Postcondition: Course entered

 

Name: Scholarship management

Description: Admin can add the scholarships and other description about scholarship and offers the scholarship to the students and add the details of students who got the scholarship and payment details of scholarship when the student got the get their scholarship

Precondition: User type must be an admin to add new scholarships and manage the details of existing scholarship.

Flow 1(add scholarship details):

  • Enter the name for the new scholarship college wishes to offer to the students.
  • Enter the amount of scholarship and the description about scholarship that what is the purpose of scholarship.
  • Save the information into the database for future use.
  • Edit the existing information and “update” if any change is made.
  • Users can “Delete” the existing records.

Postcondition: new scholarship is added to the system.

 

Flow 2(scholarship payment) :

  • Enter the scholarship payment ID against which student gets a scholarship.
  • Enter the scholarship ID and scholarship name against which scholarship student is getting a scholarship and scholarship amount.
  • Enter the required details of the student who is getting the scholarship.
  • Enter the payment details like date, amount of payment mode of payment (cash, check, etc.).
  • Save the information to ensure that the user is paid and in this duration, he/she cannot get the scholarship.

Postcondition: scholarship paid to the student.

 

Name: Student Management

Description: Employee only can view the student information.

Precondition: When user type is employee then it will get access only to limited features and only can view the students’ record.

Flow:

  • An employee enters the information need to view the information of a student.
  • Search record against entered information.

 

Postcondition: Record displayed to the user.

Alternative Flow: If the user enters the wrong/invalid scholar No then it cannot view the student information.

 

Name: Attendance Management

Description: view the attendance of students and manage the attendance details.

Precondition: If user type is employee then, have full access to view, add a new record and make changes in attendance record if any.

Flow:

  • Select the section and other related information in the attendance form.
  • “update” the attendance to save the record in the database.
  • View the attendance record of students.

Postcondition: Attendance of students updated.

 

Name: Marks Management

Description: Enter the marks of students they got in the exam. The employee can view the marks of students in internal exams. And can manage these marks details.

Precondition: If user type is employee then, have full access to view and make changes in the record if any.

Flow :

  • Enter the scholar number of students and other information related to student profile and exam details.
  • Enter the details of marks of exams.
  • Save the record if new entry.
  • If the record is already saved about desired student then “update”the record of student-related to marks. And can “Delete” if any.

 

Name : Course management

Description: Users can view the courses that are offering by the college.

Precondition:  When user type is employee it will have access only to limited features of the system and in this case only can view the courses.

Flow :

  • The employee selects the course.
  • All courses that are offered by the college would be displayed to the employee.

SRS of College Management System Project

Click here for the SRS of College Management System Project.