Professional Documents
Culture Documents
Final Srs SGP
Final Srs SGP
Final Srs SGP
Prepared by
Muhammad Mehtab
Afsheen Bibi
Department of Computing
12-12-2019
Table of Contents
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................1
1.4 Product Scope.............................................................................................................................1
1.5 References..................................................................................................................................1
2. Overall Description..................................................................................................................1
2.1 Product Perspective....................................................................................................................1
2.2 Product Functions.......................................................................................................................2
2.3 User Classes and Characteristics................................................................................................2
2.4 Operating Environment..............................................................................................................2
2.5 Design and Implementation Constraints.....................................................................................2
2.6 User Documentation...................................................................................................................2
2.7 Assumptions and Dependencies.................................................................................................2
4. Functional Requirements........................................................................................................3
4.1 Functional Requirements (and so on).........................................................................................3
Student Grade Prediction is a way of predicting a student grade based on his/her previous marks.
This also makes the student know whether he/she is in a position to reach his/her expected marks or
not. If this model shows that he/she needs to improve then that student can prepare more for that
semester so that he/she can reach their expected score.
1.1 Purpose
This document describes a system capable of predicting the Student grade. The student success
statistics such as progression and retention are commonly regarded as the main indicators of
institutional performance. Prediction of student’s performance became an urgent desire in most of
educational entities and institutes. Student Grade Prediction is a way of predicting a student grade
based on his/her previous marks. This also makes the student know whether he/she is in a position
to reach his/her expected marks or not. If this system shows that he/she needs to improve then that
student can prepare more for that semester so that he/she can reach their expected score. This
system aimed to inform about previous lessons information including who passes, fails, lesson
grades or students’ information’s. Especially department head, faculty head, rector and professors
can use our system.
DB Database
MVC Model views controller
API Application programmable interfaces
UI User interface
UX User experience
1.3 Intended Audience and Reading Suggestions
This document is useful for the teachers and the students, because this project is related to the
educational institute. The student will get to know about their performance using this system as well
as a teacher can check his students performance.
The developer, students, and teachers are the most people which can get knowledge after reading
this document.
Students often want to have future knowledge of the notes. In addition, teachers may want to be
informed about GPA or previous lessons’ letter grades and also in universities, there are worries
caused by student grades and uncertainty. In the system, students can have knowledge about GPA
estimation so that way teachers can also. A system for GPA prediction or other predictions were
developed to remove the problems for teachers and students. It also helps the professor to determine
weak students in the class and to provide necessary interventions to improve their performance. In
this way rate of the students’ retention can be increased.
The goal of the Student Grade Prediction is to create a guide that can be answered by the questions,
which may be information for students. Faculty head, department head, professors can use this
system by entering student’s registration number.
1.5 References
Student Grade Prediction System: It is a desktop application that allows students to learn future
GPAs and also allows teachers or other workers learn previous lessons. The project divided into two
parts: student mode and other user’s mode such as faculty head, department head and professors.
Student mode allows student to view future predictions. For example, they can view their future
GPAs. Students enter previous grades then the system calculates new GPA.
The following are the main features that are included in Student Grade Prediction are
1. Profile builds:
In the first phase of our system we have to parse students and courses data into the form of
(Student, Course, and GPA) triplet to built students’ profile.
Now we have a profile, for which we are interested to find the unknown GPAs for the courses,
which the student has not taken yet. To find the predicted
GPA we will use data mining and machine learning techniques.
In our feedback model, student knowledge in different course domains is calculated by taking an
average of GPAs for the courses the student has taken which fall into the same domain by using the
course domain table.4. Knowledge Inference:
Hidden Markov Model (HMM) is a model used to predict students performance based on their
historical performance. According to the model, the probability of knowledge P(Lj) increases with
every step j and can be calculated using the equation.
5. Feedback:
After computing the student knowledge in particular course domain and knowledge
Inference, the feedback is made. If the student knowledge inference results are less than 2.00 GPA
in a course, then the system generates a warning that the student needs effort in that course. In this
way, feedback results can inform the instructors that the student is weak in a particular course.
2.2.1 Participants
2.2.1.1
Participant must be a student, professor, faculty head, and department head of the Abasyn
University.
2.2.1.2
Participant must read and understand English language due to simulation language is English.
2.2.1.3
If participant is a professor, he or she must enter at least the first term grades.
Operating Environment
1. Visual Studio
2. Internet Connection
3. Operating System Windows, Mac, Linux (Ubuntu)
Frontend:
The system shall be Desktop application.
The language used will be C Sharp.
Backend:
The Desktop application should be developed by using Framework.
The backend language is python.
The system adopts most frequent used User experience and interface so each and every user can
easily use it.
2.5 Assumptions and Dependencies
Let us assume that this is a desktop application system and it is served on server there may
be traffic sometimes if it may take time to load it may be issue with server.
.
Homepage Module
Login Module
Student Module
professor or teacher Module
Course Prediction Module
GPA Prediction Module
Create Model Module
Data Base Module
Windows.
A system which supports visual studio.
Functional Requirements
Modifiability
Interoperability
Maintainability
Usability
Efficiency