Software Engineering

2024/2025
Software Engineering project
Beni suef National university
Table of Contents
Team Information:............................................................................................2
Project proposal:..............................................................................................3
Project Idea:..................................................................................................3
Project scope:...............................................................................................3
Main functionalities:.....................................................................................3
Development platform:.................................................................................3
Stakeholders:................................................................................................3
Similar applications in the market:...............................................................3
SRS (Software requirement specification)........................................................4
Functional Requirements..............................................................................4
Non-Functional Requirements.......................................................................4
Team Information: (typed not handwritten, except for the attendance
signature):
ID Full Name Attendance Final
Grad
[Ordered by [In Arabic] [Handwritten e
ID] Signature]
1 220100132 ‫عبدالله بدري محمد عبدالظاهر‬
‫عبدالرحمن سمير عبدالعظيم‬
2 220100127
‫محمد‬
3 220100055 ‫ايه ناصر عويس خورشيد‬

4 22100045 ‫االء فيصل عبدالعال عبدالله‬

5 220100035 ‫اسراء حسن علي زهران‬

Project proposal:
Project Idea:
The project "College Admission Predictor" is a web-based system that
helps students predict their college admission chances based on their
academic scores. The system
allows students to register with their personal and academic details, and
based on the provided information, it suggests suitable colleges.
Administrators manage the system by adding college details, setting cut-
off marks, and managing student registrations.
Project scope:
 Assist students in selecting the right college based on their scores.
 Provide an automated system for seat allocation in colleges.
 Reduce the manual effort in admission prediction and seat allotment.
 Offer a user-friendly interface for students and administrators.

Main functionalities:
Admin Panel:
 Add College: Enter college details
 Set Cut-off Marks
 Manage Colleges.
 View Students.
View Feedback
Student Portal:
 Register
 View Colleges
 View Profile
Submit Feedback

Development platform:
 Frontend: Flutter
 Backend: Python ( Flask)
 Machine Learning: Scikit-learn
 Database: MySQL / PostgreSQL
 ……………(etc..)

Stakeholders:
 Students – End-users who register and check their admission chances.
  Administrators – Manage colleges, student data, and cut-off marks.
 Educational Institutions – Universities/colleges using the system for seat allocation.
 Government institutions- Determine the minimum level for admission to the college

Similar applications in the market:

 CollegeVine.
 Admit Predictor.
 Niche College Admissions Calculator.

SRS (Software requirement specification)

Functional Requirements
User requirements System requirements
Req1 1.1
The system shall allow The system shall store user credentials
students to register and securely.
log in using their
credentials. 1.2
The system shall provide authentication
using email and password.

1.3The system shall support password

recovery.

Req2 The system shall 2.1 The system shall allow admins to
enable administrators create, update, and delete college
 to add and manage records.
college details. 2.2 The system shall store college details
in the database.

Req3 The system shall 3.1

enable students to The system shall provide a feedback form.
submit feedback.
3.2
The system shall store feedback in the
database.

Non-Functional Requirements
User requirements System requirements
Req1 The system shall 1.1 The system shall encrypt stored
ensure data security passwords.
and privacy for all users

Req2 The system shall 2.1 The system shall have a responsive
provide a user-friendly design for various screen sizes.
interface for easy
navigation.

Req3 The system shall be 3.1

compatible with mobile The system shall work on modern web
and desktop devices. browsers and mobile platforms.

Software Design
Activity Diagram

Use case Diagram :

1- ACTORS
 a. Student (Registiers, login, view colleges, view profile, submit
feedback)

b. Admin (add college data, cut-off marks, mange colleges , manage

student data)

2- Use case
a. Register (student)
b. Login (student)
c. View colleges (student)
d. View profile (student)
e. Check admission (student)
f. Submit feedback (student)
g. Add , update college data (admin)
h. Cut-off marks (admin)
i. Mange colleges (admin)
j. Mange student data (admin)
k. Respond feedback ( admin)

Use case tables

1 – use case : student registration
Use case id Uc_ UC-001
use case name Student Registration
Actor Student
Goal To allow students to register in the system successfully.
Precondition 1. The student has a valid email address and required personal details.
2. The system is online and accessible.
Postcondition The student is successfully registered in the system and can log in.
Main Success The student accesses the registration page.
Scenario
The student enters their personal details (name, email, date of birth)

The student sets up a username and password.

The student submits the registration form.

The system validates the input data.

The system sends a confirmation email to the student.

The student verifies their email.

Alternative invalid Email Format: The system displays an error

Scenarios message if the student enters an invalid email.

Username Already Taken: The system prompts the

student to choose a different username.

Weak Password: The system suggests a stronger

password if the entered password is weak.

Email Not Verified: If the student does not verify their

email, they cannot log in.

2-use case : login

Use case id : UC-002

use case name : Student Login
Actor: Student
Goal: to allow students to log in successfully and access their accounts.
Precondition : 1. The student is already registered in the system.
 2. The system is online and accessible.
Postcondition: The student is authenticated and redirected to their dashboard.
Main Success Scenario: 1. The student accesses the login page.

2. The student enters their username/email and the student

clicks the "Login" but

The system verifies the credentials.

Alternative Scenarios: 1. Incorrect Username/Password: The system displays an

error message if the credentials are incorrect.

2.Account Not Verified: If the student hasn’t verified their email, the system
prompts them to verify before logging in.

3- Use case : View colleges

Use case id : UC-003

use case name :View Colleges
Actor : Student
Goal : To allow students to browse and view available colleges.
Precondition : 1.The student must be logged into the system.

2.The system must have a list of available colleges.

Postcondition: The student successfully views the list of colleges and can
access details about each college.
Main Success Scenario1: The student logs into the system.

The student navigates to the "Colleges" section.

The system displays a list of available colleges.

The student selects a college to view its details.

Alternative Scenarios : No Colleges Available: If no colleges are listed in the

system, an appropriate message is displayed.

Student Not Logged In: If the student tries to access the page without logging in, the system
redirects them to the login page.

Use case : Add , update college data

Use case id : UC-004

use case name : Add & Update College Data
Actor : Admin
Goal : To allow the admin to add new colleges and update existing college
details.
Precondition : The admin must be logged into the system.
The system must provide an interface for managing college data
Postcondition: The system successfully saves the new or updated college
information.
Main Success Scenario :The admin logs into the system
The system displays a form to enter college details (name,
location, courses offered(
The admin fills in the details and submits the form
Alternative Scenarios : Missing Required Fields: If the admin leaves required
fields empty, the system prompts them to fill in the missing data.

Invalid Data Format: If any field contains invalid data (e.g., incorrect email
format), the system displays an error message.

5 – use case : Cut-off marks

Use case id: UC-005

use case name : Manage Cut-off Marks
Actor: Admin
Goal :To allow the admin to set and update cut-off marks for colleges and
courses
Precondition : The admin must be logged into the system.

The system must have a list of colleges and courses available.

Postcondition : The system successfully saves the new or updated cut-off
marks.
Main Success Scenario : The admin logs into the system

The system displays a list of colleges and their courses.

The system saves the cut-off mark and confirms the update.

Alternative Scenarios: Missing Required Fields: If the admin does not enter a
cut-off mark, the system prompts them to fill in the required field.

Invalid Data Format: If the admin enters a non-numeric value for the cut-off
mark, the system displays an error message.

a. -6 Use case : Mange colleges (admin)

Use case id : UC-006

use case name : Manage Colleges
Actor : Admin
Goal : To allow the admin to add, update, and delete college records in the
system
Precondition : The admin must be logged into the system.

The system must provide an interface for managing college data

Postcondition : The system successfully saves, updates, or deletes college
records as required.
Main Success Scenario: The admin logs into the system.
The admin clicks on "Add New College
The admin fills in the required details and submits the form.
Alternative Scenarios: The system displays a list of existing colleges.

The admin selects a college to edit.

The system displays the existing details.