Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
asdasagAYJGSJYAGSJADSTUDENT PORTAL SOFTWARE REQUIREMENT SPECIFICATION
Typology: Exams
1 / 10
This page cannot be seen from the preview
Don't miss anything!
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for
Revision History
Admin can manage its profile, registered students and assign and add courses to the department for the students to enroll, manages Student information and reply to the student queries.
This program has the following functionalities:
1. Students Login Manage profile Enroll courses Access library View fee statement Submit queries View Grades Logout 2. Admin Login Manage profile Registered students Add, update, delete courses Manage student info Reply student queries Announcements
Following user classes are identified:
1. Student: Will be using this portal to manage their activities. 2. Admin Admin will be reviewing student activities. 3. Courses This will be assigned by Admin and enrolled by Students. 4. Library Admin will add books and students will issue them. 5. Department A department will be assigned to students. 6. Fee Statement Student can review fee statement and generate fee bill. 7. Queries Student will submit queries and admin will resolve them. 8. Marks Admin will be generating student grades.
Operating environment for the Student portal is listed below.
There is no such constraints except for some of the few listed. Windows 7 or later Ram: 512MB or more System: Core2duo (2.0ghz) or above Database: SQL Server 2008 or later A working internet connection
The software will be an easy to use application, there would be no manual required to operate.
The dependencies required are: Microsoft Visual Studio 2015 Microsoft SQL Server (Database)
3. External Interface Requirements
This is a desktop application. The GUI will be user friendly. The user will be able to add, update any info in a list or a textbox format for their ease. A back and Home button will be there at every form. The User interface will be needed at every information exchange with the Student and other entity classes.
The minimum hardware requirements are as follows: RAM: 512 MB Processor: Core2duo (2.0ghz) HDD: 10 GB Network: Ethernet or WIFI OS: Windows 7 or above .Net Framework 4.5 or above
This page will consist of several read only and some editable fields. Read only fields: ID, Name, Father Name, Gender, NIC, DOB, and Department. Editable fields: Mobile, Residence, Nationality, Religion, Email.
Student can update the editable fields only. Read only fields are just to be viewed by the student.
Courses panel for admin as well as students. Admin can add courses while students will enroll them.
Admin add courses within a department. Student can enroll the course. Admin can also edit and delete course.
Admin can only add a course by logging in and then going to the course panel. The fields required for adding a course: ID, Name, Cr Hours, Fee, Days, Time and Department.
Admin can delete a course from the panel. Selecting a course from dropdown and then removing the course. The course should also be removed from Student’s enrolled courses.
Student can enroll a course by going to the courses panel. The courses which are being offered by the admin for the department will only be viewed by students of the specific department. Student can then enroll the course by selecting it and clicking on enroll button.
After Selecting an enrolled course. Student can drop the course from the list by selecting it and clicking on drop.
Students can issue a book and then return later on. A library will be managed by the administrator.
Admin adds a book Student issues the book Student returns it later. Book is then again added to be issued.
Admin can add a book to the library. The required fields are: ID, Name, Author, Edition and Category.
Admin can remove a book from the library. The book must not be issued by anyone while it’s deleted.
Students can issue a book which is available. The student has to return a book within 7 days of time else they would be charged a fee.
Issued book by the student will have to be returned within 7 days. Student can return the book issued. If the book is not returned within the due time, a charge of 20 r.s per day will be fined.
Students will be reviewing the fee statement from the panel.
Student can generate fee bill of the courses. Student can view fee statement. Student can pay the fee. Admin can monitor the statement.
Student can generate the fee bill after selecting a course from the course panel. The fee of the course will be added to the bill. The result will be reflected in fee statement once the bill has been generated.
Student can pay the fee bill after generating it. He/she has to enter the amount equal to the fee bill in order to continue. Once the fees have been paid, Statement is updated under fee statement.
Student can review the transaction and the statement of the fees anytime he/she wants.
Every field will be containing data validation and verification along with data integrity to make sure the program is error and bug free.
Each user input will be validated on its data type. The error will be showed instantly if the user enters data in an incorrect format.
The system will make sure if the program is stuck at any time. There will be no loss of data.
5. Other Nonfunctional Requirements
The software (if met with the minimum requirements) should perform fast enough without any uncertainty. The response time of the software will be in milliseconds.
At any time, the software can be stuck. Therefore, data integrity will be added along with some data backups.
The required software will be as a desktop application along with SQL server therefore the queries and the inputs will be protected from SQL injection and other exploits.
The software will be easy to use so there would be no such manual or need of any help. The interfaces will be user friendly.
