Documente Academic
Documente Profesional
Documente Cultură
Version 1.0
17.01.2016
The students who submitted this team projects were Kshitij Minocha [UG201310043],
[UG201310037].
Table of Contents
Table of Contents ............................................................................................................................................ i
List of Figures ................................................................................................................................................ ii
1.0. Introduction ............................................................................................................................................. 1
1.1. Purpose ................................................................................................................................................ 1
1.2. Scope of Project................................................................................................................................... 1
1.3 Constraints ............................................................................................................................................ 3
1.4 Assumptions and Dependencies ........................................................................................................... 3
1.3. Glossary ............................................................................................................................................... 3
1.4. References ........................................................................................................................................... 3
1.5. Overview of Document ....................................................................................................................... 4
2.0. Overall Description ............................................................................................................................ 5
2.1 System Environment ....................................................................................................................... 5
2.2 Functional Requirements Specification .......................................................................................... 5
2.2.1 Use case 1 ............................................................................................................................... 5
Use case: ............................................................................................................................................. 5
2.3 User Characteristics ........................................................................................................................ 5
2.4 Non-Functional Requirements ........................................................................................................ 5
3.0. Requirements Specification ................................................................................................................ 6
3.1 Functional Requirements ................................................................................................................ 6
3.1.1 << Name of the first feature>> ............................................................................................... 6
3.1.2 << Name of the second feature>> ......................................... Error! Bookmark not defined.
3.3 Detailed Non-Functional Requirements ......................................................................................... 8
3.4 Logical Structure of the Data .................................................................................................... 9
4.0 Supporting information ............................................................................................................................ 9
4.1 Table of contents and index .................................................................................................................. 9
4.2 Appendixes ........................................................................................................................................... 9
i
List of Figures
No table of figures entries found.
ii
1.0. Introduction
1.1. Purpose
The purpose of this document is to describe the design and implement of a fee
management system for the students of an institution. The implementation of the system
will be based on .Net framework. The system will be based on a universal application
[Windows Desktop and Mobile App] that the students can use to pay their fee. The
system will have a simple UX and will be secured through encryption of important data,
will be fast enough to provide access to stored information and transaction history in
reasonable amount of time and have separate operation modes for the administrative staff
and students.
Role of Admin: The admin of the system will have master access to the
system. He will have full access to the database that will contain fee records
of all students of the institution. He can modify the information in the
database anytime. Only he will have the access to the encryption key that will
allow him the access to important information like transaction history, bank
details and private information of students.
Role of Administrative Staff: Their primary role will be to verify that the
transactions made by students are successful, by matching the transaction ID’s
in the generated fee receipts to the transaction history of the fee account of the
institution.
Role of Students: The students will log into the system using their unique
institute email ID’s as username and their password. The student will have
access to their own information only that includes transaction history along
with their personal information. The student will select the type of fee to be
paid for ex. Mess Fee, Mess Dues, etc. After that the entire fee payment
process will be automated and the student will just have to enter details into
the payment gateway to complete the fee payment.
1
(c) System Features:
User Login – This will be a one-step login procedure in which the user
will be required to enter his unique user id, his password and his role
[Admin, Staff or Student].
Automatic receipt generation – After the fee payment will be over, the
receipt of the fee payment will be generated automatically by the system.
In case any exception occurs then failsafe features like forwarding the
SMS that the user receives from the bank to a specified number of
uploading the receipt downloaded from the bank website as a proof of
payment, will be present to ensure the confirmation of fee payment.
Database that will store students’ personal information along with the
transaction history that will contain all the receipts generated till now for
record. There will be different levels of access to this database based on
the type of user.
Report Generation: After the process of fee payment is complete for all the
students the system can generate a summary report. The report will
2
contain details of all the transactions made during the process of academic
registration along with related details. Again different amount of
information will be made available in the report depending on the user
type.
1.3 Constraints
The database of registered students will be made available along with the
login details of administrative staff.
The list of dues of each department like mess, library etc. will be made
available.
The fee structure of the academic year will be made available beforehand.
We are assuming access to the payment gateway service of any bank.
The transaction history of the institution’s fee account will be made
available to the administrative staff for verification.
The Admin or Administrative staff should not be corrupt. :p
1.3. Glossary
Term Definition
1.4. References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
3
1.5. Overview of Document
4
2.0. Overall Description
2.1 System Environment
Use case:
Diagram:
Brief Description
The user of this software system requires the following skills to use this software
5
3.0. Requirements Specification
3.1 Functional Requirements
6
3.1.3 Automatic Receipt Generation
Use Case Name Receipt Generation
Trigger The user has completed the fee payment.
Precondition The user must have completed the fee payment process at the
payment gateway.
Basic Path 1. The user completes the fee payment at the payment gateway.
2. Then the receipt is generated by the system automatically and
is displayed to the user.
Alternative Paths None
Postcondition The confirmation of the fee payment follows the automatic
receipt generation. A confirmation email is sent to the user along
with a SMS. The generated receipt is added to the transaction
records [history] of the user.
Exception Paths 1. The user does not complete the fee payment process at the
gateway.
2. An exception occurs and the receipt does not get generated
automatically.
Other Even if due to some reason the receipt does not gets generated
automatically the user will have the option to confirm his
payment by either uploading the transaction record downloaded
from his bank account or forwarding the transaction message
that the user receives to a predefined mobile number.
7
3.1.5 Master Database Query
Use Case Name Database Query
Trigger The admin is logged into the system and decides to make the
query.
Precondition The user must be the admin of the system.
Basic Path 1. The user logs into the system as the admin.
2. After logging into the system the user clicks the view
database button.
3. The user makes the required query after entering the database.
Alternative Paths None
Postcondition The query is served and if any modification has been made then
the database is updated.
Exception Paths 1. The query is invalid.
2. The database is empty.
Other None.
8
Capacity: The system must have the capacity to handle large amount of
student data and should not slow down as the amount of data increases.
Maintainability: The system must be able to modify the stored records so
that any change in the student information that can occur can be
accommodated easily in the student database.
4.2 Appendixes