Software Requirements Specification for student teacher academic portal Page 1
Software Requirements
Specification for
STUDENT TEACHER
ACADEMIC PORTAL
Version 1.0 approved
Prepared by:
Daniyal Mujtaba (17k-3610)
Heeranand (17k-3614)
Sufiyan (17k-3944)
Date Created:
14/10/19
Instructor:
Syeda Rubab Manzar
Software Requirements Specification for student teacher academic portal Page 2
Table of Contents
Table of Contents ...........................................................................................................................2
1. Introduction ................................................................................ Error! Bookmark not defined.
1.1 Purpose............................................................................................Error! Bookmark not defined.
1.2 Document Conventions ...................................................................Error! Bookmark not defined.
1.3 Intended Audience and Reading Suggestions .................................Error! Bookmark not defined.
1.4 Product Scope .................................................................................Error! Bookmark not defined.
1.5 References .......................................................................................Error! Bookmark not defined.
2. Overall Description .................................................................... Error! Bookmark not defined.
2.1 Product Perspective.........................................................................Error! Bookmark not defined.
2.2 Product Functions ...........................................................................Error! Bookmark not defined.
2.3 User Classes and Characteristics ....................................................Error! Bookmark not defined.
2.4 Operating Environment ...................................................................Error! Bookmark not defined.
2.5 Design and Implementation Constraints .........................................Error! Bookmark not defined.
2.6 User Documentation .......................................................................Error! Bookmark not defined.
2.7 Assumptions and Dependencies .....................................................Error! Bookmark not defined.
3. External Interface Requirements ............................................. Error! Bookmark not defined.
3.1 User Interfaces ................................................................................Error! Bookmark not defined.
3.2 Hardware Interfaces ........................................................................Error! Bookmark not defined.
3.3 Software Interfaces .........................................................................Error! Bookmark not defined.
3.4 Communications Interfaces ............................................................Error! Bookmark not defined.
4. System Features ......................................................................... Error! Bookmark not defined.
4.1 System Feature 1 .............................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.
5.1 Performance Requirements .............................................................Error! Bookmark not defined.
5.2 Safety Requirements .......................................................................Error! Bookmark not defined.
5.3 Security Requirements ....................................................................Error! Bookmark not defined.
5.4 Software Quality Attributes ............................................................Error! Bookmark not defined.
5.5 Business Rules ................................................................................Error! Bookmark not defined.
6. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary...................................................................... Error! Bookmark not defined.
Appendix B: Analysis Models ......................................................... Error! Bookmark not defined.
Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.
Software Requirements Specification for student teacher academic portal Page 3
[Link]
1.1 Purpose:
The main objective of this software requirement specification design is to
illustrate all the requirements of the system. It provides detailed description
of all the functionalities and requirements proposed, user interfaces of
system after implementation. Therefore, the final system will meet all the
functional and non-functional requirements of system proposed.
1.2 Document Convention:
Main headings
Font: Calibri (Body)
Face: Bold, underline
Size: 24
Description
Font: Arial
Face: None
Size: 14
Text Sub headings
Font: Calibri (Body)
Face: Bold
Size: 22
Tables and images
Font: Calibri (Body)
Face: None
Software Requirements Specification for student teacher academic portal Page 4
Size: 22
1.3 Intended Audience and Reading Suggestions:
Lecturer
Since this is a student project, the lecturer will get clear idea how this SRS is
designed.
User
All the users in this system should have clear idea about hardware and
software requirements that engaged with system.
Team Members
All the team members will have advantage of easily understanding the
functionalities and techniques.
1.4 Project Scope:
The project will deliver the attendance management, resource
management, marks management and the Course registration features
along with small extra set of features like GPA calculator, fee information
and courses information.
This web application won’t cover the class management, assignment of
lectures in the particular class room. Time table will be available as
updated but it can’t be calculated through features of this web application.
Software Requirements Specification for student teacher academic portal Page 5
2. Overall Description
2.1 Product Perspective:
The web-based Student teacher portal is an independent stand-alone system.
2.2 Product Functions:
The following are the major functions.
User accounts with sign in on basis of the nu ID.
Separate interface depending on the role of the user (lecturer,
student administrator).
Creating the layout focus on the courses enrolled instead of the
features like attendance, marks section.
Building a space for the resources section.
Email based notifications for the assignments and recourses.
GPA embedded into the website with a separate GPA calculator
option to trace your expected GPA in current Semester.
Features like Registration, withdrawal of the course and
administrative authorities to drop/lock the course of student if the
attendance is lower than expected.
Software Requirements Specification for student teacher academic portal Page 6
The fee records can be maintained by administration.
2.3 User Classes and Characteristics:
Two types of users can use our product.
1. Administrator
2. Student
3. Teacher
Administrator:
Admin has all privileges to add, delete, modify or update any data of the
Students. Admin can access highly secure data. Admin can even change
timetable and Teacher assigned courses.
Student:
Student can view marks, attendance, GPA and Registered Courses.
Teacher:
Teacher can see his sections details i.e. Students enrolled, assignment
submissions, and updating scores.
2.4 Operating Environment
As the product is web-based so it’ll run on all the operating systems and
there will not be any specific hardware requirements. Any computer that
Software Requirements Specification for student teacher academic portal Page 7
has the computing power to run a web-browser and has a stable internet
connection will be able to use the web-app without any problem.
2.5 Assumptions and Dependencies:
There aren’t any design and implementation constraints (that we currently
know of) that’ll make it difficult to implement certain features of the project.
3. External Interface Requirements
3.1 User Interface:
In start there will be a log in page. When a user gets logged in a
Dashboard appears and the content of the dashboard depends on the
person’s log in type i.e. Admin and Student will have different overview.
3.2 Hardware Interface:
There will not be any hardware interfaces directly shown to the user as
most of the working will be behind the scenes to the server and database
on the cloud.
3.3 Software Interface:
Software Requirements Specification for student teacher academic portal Page 8
VS code
React
MongoDB
[Link]
ReactStrap
VsCode extensions
3.4 Communications Interfaces
The project will be using e-mail, web browser, and network server
communication. The communication standards like FTP and HTTP/HTTPS
will also be used.
Software Requirements Specification for student teacher academic portal Page 9
4. System Features
Following are the features of our system.
4.1 Student Data Management:
Student log in details are maintained in the database.
4.2 Teacher Schedule Management:
Administrator can update the sections and courses of the teacher.
4.3 Maintain Student Record:
This feature enables system to maintain record of Student. It will store
information of Student is enrolled in which section and course at what date.
4.4 Maintain Teacher Record:
Admin can update and add the teachers into the teachers list.
4.5 Student Academic Update:
Admin can change the course of the student, can delete the student record
from a section.
Teacher can update the score, attendance and grade of the student.
4.6 Notifications and Assignment:
Student gets the notification and assignment
Software Requirements Specification for student teacher academic portal Page 10
4.7 Resource Manager:
There is a manager model for the resources and contents. Where teacher
can update into it and student have the access to it.
5. Other Nonfunctional Requirements
5.1 Performance Requirements:
Speed: Depends on the bandwidth and service available to the user.
Precision: The data delivered is accurate with no variations.
Capacity: Record of various students and teachers can be maintained as there is
no overlapping of records.
Reliability: We are using MongoDB that is reliable and secure.
5.2 Safety Requirements:
Backup is maintained for safety purpose. The damage to the data and the server
is provided by regular surveillance of the system. This is to save the system from
any malicious activities that can be carried out.
5.3 Security Requirements:
Integrity is maintained by adding certain checks at the time when the user is
entering new data. This way the data remains uniform and no duplication is seen.
For security reasons not every user is allowed to access all the data. Each user is
provided with a login user id and password to protect the data. Sensitive data can
Software Requirements Specification for student teacher academic portal Page 11
only be edit by administrator. By providing login and password, unauthorized
access to data cannot be made.
5.4 Software Quality Attributes:
Adaptability: The product is open source, so it will be available for
everyone to see and can make modifications for further improvements.
Maintainability: A software maintainability measurement is a rating used
to assess the amount of effort or resources currently committed to an
application.
Reusability: A product can be reuse for other university purposes.
Reliability: Any failure reported will be correctly handled. System will reject
invalid user input without crashing.
5.5 Business Rules:
Keep backup of all data files.
Frequent auto-save information in case of system failure.
Data migration and retention can be easily performed.
Software Requirements Specification for student teacher academic portal Page 12
Appendix A: Glossary
Appendix B: Analysis Model
