REQUIREMENTS GATHERING:

(Present working model)

USERS:

1) Students
2) Finance department
3) Hostel Wardens

DATABASES :

1) STUDENT DATABASE: This database includes personal details of students like name, parent’s name ,
mobile number, permanent address,batch details, department etc.
Primary key : enrollment ID

SCHEMA:

STUDENT

ENROLLMENT ID(PK)

NAME

D.O.B

EMAIL ADDRESS

FATHER’S NAME

MOBILE NUMBER

PERMANENT ADDRESS

DEPARTMENT

BATCH

2) STUDENT FEES DATABASE : This database includes fees status i.e. fees paid or not and the amount of
fees , fine etc. Of each student.
Primary key : enrollment ID
SCHEMA:

FEES

ENROLLMENT ID(PK)

CURRENT DUES

PAID

DURATION

FINES

REMARKS

3) HOSTEL RECORD DATABASE : This database includes hostel record of each hostel like hostel annual
expenditure, hostel wardens,hostel name.
Primary key : hostel name

SCHEMA:

HOSTEL RECORD

HOSTEL NAME(PK)

WARDEN NAME

MOBILE NO.(WARDEN)

EMAIL ADDRESS

ANNUAL EXPENDITURE

REMARKS
4) STUDENT HOSTEL RECORD : This contains hostel details of each student like hostel name, whether
student is hosteller/day scholar.
Primary key : enrollment ID of student
Foreign key : Hostel name

SCHEMA:

STUDENT-HOSTEL RECORD

ENROLLMENT ID(PK)

STUDENT NAME

HOSTEL NAME(FK)

HOSTEL NAME

HOSTELLER/DAY SCHOLAR

5) LOGIN CREDENTIALS DATABASE : This database is used to keep login credentials (username and
password) of each of the user of the software.

SCHEMA:

LOG IN

USERNAME

PASSWORD

EMAIL ADDRESS

MOBILE NO.

SRS DOCUMENTATION:

FUNCTIONAL REQUIREMENTS:

1.REGISTERING :
This requirement includes registering the student for the first time.
 1.1.
INPUT : ‘REGISTRATION ‘ option selected.
OUTPUT : user prompted to enter registration details.

1.2.VALIDATE REGISTRATION DETAILS :

This verifies registration details like mobile no. Email-id etc.
INPUT : Registration details entered by user in blank space.
PROCESSING : Verifies registration details e.g. sends verification mail to specified email address.
OUTPUT : Sends valid registration details to R 1.3 if registration details verified.

1.3. PROCESS REGISTRATION REQUEST:

INPUT : Registration details like name, department, enrollment ID , permanent address, batch,
mobile no, email-id,hostel name, category, scholarships,username and password(as set by the student)
and valid signal from R 1.2.
PROCESSING : Inserts the personal details of students into STUDENT database and login
credentials are entered into LOGIN CREDENTIALS DATABASE.
OUTPUT : A message showing ‘REGISTRATION IS SUCCESSFUL’.

1.4. REGISTRATION HELP :

This requirement is needed optionally giving the students guidelines for registration.
INPUT : Clicking ‘REGISTRATION HELP’ button.
OUTPUT : Displays the registration guidelines on screen.

2.LOGIN:
This requirement allows the users of software to login to avail services/functionalities of software using login
credentials(username and password).

2.1
INPUT : ‘LOGIN’ option selected.
OUTPUT : User prompted to enter login credentials.

2.2 VALIDATE LOGIN DETAILS :

This verifies the login credentials as entered by user.
INPUT : username and password entered by user.
PROCESSING : Checks if the login credentials are valid(from LOGIN CREDENTIALS DATABASE) .
OUTPUT : If user login credentials are valid the send tthe valid login credentials to R 2.3.

2.3 PROCESS LOGIN REQUEST:

This performs the actual login operation
INPUT : valid username and password of user .
PROCESSING : If VALID flag set then send a unique user key to USER TASK MANAGER which
redirects the user to his/her profile .
OUTPUT: Unique user key sent to USER TASK MANAGER.

3. USER TASK MANAGER :

This takes the user unique key and redirects the user to his/her profile so that the user can avail the
functionalities of software.
 INPUT : unique user key from LOGIN.
PROCESSING : For that particular user key bring his/her profile.
OUTPUT : User profile displayed on screen with the available functionalities.

Depending on the user there will be different functionalities available in his/her profile.

STUDENTS:
4. UPDATE/MODIFY PERSONAL DETAILS :

4.1
INPUT : ‘update ’ option selected.
OUTPUT : User prompted to enter enter details .

4.2
INPUT : User details which user wants to update like permanent address, mobile no.
PROCESSING : Make the corresponding modifications in student details in STUDENT database.
OUTPUT : A message showing ‘UPDATE DONE’,

5. CHECK DUE FEES AND FEES PAYMENT :

This requirement helps the student to check how much is the fees that they have to pay and allow them to pay
fees.

5.1 CHECK FEES:

INPUT : ‘check fees’ option selected.
PROCESSING : Searches the fees which is to be paid by the student from STUDENT FEES database.
OUTPUT : The fees to be paid by student is printed on the screen .

5.2 FEES PAYMENT :

INPUT : Student has to enter the means of fees payment be it credit card/debit card/net banking and
payment details.
PROCESSING : Sending payment request to bank
OUTPUT : Display ‘successful transaction’ if approval came from bank otherwise ‘unsuccessful
transaction’ is displayed on screen.

HOSTEL WARDEN:
6. ADD HOSTELLER:
6.1
INPUT : ‘ADD’ option selected.
OUTPUT : user prompted to enter student details .

6.2
INPUT : Student details entered by hostel warden like enrollment ID of the student, student name, hostel
name to add him/her to particular hostel.
PROCESSING : The hostel name in ‘hostel’ attribute in STUDENT HOSTEL RECORD database is
added which is initially NULL.Hostel name is inserted in ‘hostel’ attribute for that student.
OUTPUT : A message showing ‘STUDENT HOSTEL DETAILS ADDED’.
7.DELETE HOSTELLER:

7.1
INPUT : ‘DELETE ’ option selected.
OUTPUT : user prompted to enter student details .

7.2
INPUT : Hostel warden enters the enrollment ID of the student whose record has to be deleted from the
particular hostel.
PROCESSING : ‘hostel’ attribute of STUDENT HOSTEL RECORD database is made NULL.
OUTPUT: A message showing ‘STUDENT HOSTEL DETAILS DELETED’.

8. SUBMIT ANNUAL EXPENDITURE OF HOSTEL:

8.1
INPUT : ‘SUBMIT HOSTEL EXPENDITURE ’ link clicked.
OUTPUT : user prompted to enter hostel expenditure details .

8.2 SUBMIT EXPENDITURE:

INPUT : Hostel warden enters in a space provided , the annual expenditure of his/her hostel and also
scanned copies of bills.
PROCESSING : Inserts annual expenditure in HOSTEL RECORD .
OUTPUT : Message showing ‘hostel anuual expenditure submitted’ or ‘submission failed’.

FINANCE DEPARTMENT:
9.DELETE STUDENT RECORD:
This requirement deletes student records from STUDENT database.

9.1 DELETE BATCH:

This requirement deletes all student records from STUDENT DATABASE when the student passes out
from the institute.
9.1.1 CHECK IF THE BATCH IS PASS OUT BATCH :
INPUT: Batch details(starting-ending year) of students in STUDENT database.
PROCESSING: Verifies batch is pass out batch.
OUTPUT: Valid batch passed to DELETE BATCH RECORDS.

9.1.2 DELETE BATCH RECORDS :

INPUT : Valid batch .
PROCESSING : Deletes all student records having batch as valid batch from STUDENT
database.
OUTPUT : Message showing ‘BATCH SUCCESSFULLY DELETED’ or ‘BATCH DELETION
FAILED’.

9.2 DELETE STUDENT:

This requirement deletes student records of a particular student.
INPUT: Admin enters enrollment ID of student whose details have to be deleted from STUDENT as well
as STUDENT database.
PROCESSING : Deletes student details of that particular student from STUDENT database.
OUTPUT: A message showing ‘STUDENT RECORD DELETED SUCCESSFULLY’.

10. MODIFY BATCH

This requirement modifies the batch details of a student in case the student receives a year lag.
10.1
INPUT : ‘MODIFY BATCH’ button clicked.
OUTPUT : User prompted to enter batch details of student.

10.2
INPUT: Batch details, enrollment ID of student.
PROCESSING : Modifies batch details of the particular student.
OUTPUT: A message showing ‘BATCH DETAILS MODIFIED’.

11. FEES CALCULATION:

This requirement calculates the fees of each student depending on various factors:
1) Fine
2) Hostel
3) Batch
4) Caste certificates/scholarships
5) Semester(Odd semster/even semester)
11.1 CHECK IF EVEN/ODD SEMESTER :
INPUT : Currecnt month.
PROCESSING : Based on current month decision is taken about even or odd semester.
OUTPUT : Semester type sent to R 11.6 .

11.2 CHECK FINE :

INPUT : STUDENT FEES RECORD
PROCESSING : Checks whether student has pending dues(fine) from previous semesters.
OUTPUT : Fine status sent to R 11.6.

11.3 CHECK CASTE CERTIFICATES/SCHOLARSHIPS:

INPUT : user input (valid caste /scholarship certificates or not) by finance department
OUTPUT : some status indicating that certificates are valid are sent to R 11.6.

11.4. CHECK STUDENT’S BATCH :

INPUT : STUDENT database.
PROCESSING : Check which student belongs to which batch as fees can change from one batch to
another.
OUTPUT : Fees of that particular batch is provided to R 11.6.

11.5 CHECK HOSTELIER/DAY SCHOLAR:

INPUT : STUDENT HOSTEL RECORD.
PROCESSING : Checks if the student is hostelier or day scholar.
OUTPUT : If hostelier passe then sends the hostel expenditure to R 11.6 else sends 0.

11.6 CALCULATE FEES :

 This requirement actually calculates the fees of each student based on above mentioned inputs.
INPUT: OUTPUT of requirement 11.2, 11.3, 11.4 , 11.5 and 11.1.
PROCESSING : Calculates the fees of each students based on input parameters.
OUTPUT : Calculated fees of each student is entered into STUDENT FEES database for each student.

NON FUNCTIONAL REQUIREMENTS :

SECURITY :

1) All the login credentials must be in encrypted form and secure.

2) Personal information of a student should be modified by only that student.
3) STUDENT HOSTEL RECORD and HOSTEL RECORD should be modified by only hostel warden.
4) STUDENT FEES RECORD should be modified by only finance department.
5) Fees payment should be secure.

PERFORMANCE REQUIREMENTS:

HIGH STORAGE REQUIREMENTS:

For the five databases high storage requirements are there is a need of Database Management system for
retrieval and modification of data in databases to tackle concurrency issues.
GOALS OF IMPLEMENTATION:

1)In the existing software implementation verification of caste/scholarship certificates and hostel annual
expenditure bills have to be done manually.
Later for validating and verifying caste/scholarship certificates and hostel annual expenditure bills artificial
intelligence techniques and other machine learning approaches can be applied.

2) PORTABILITY :
This software should work for both desktop as well as mobile phone environments.For mobile usage software
can be provided as an android application compatible with android OS.