Functional Requirements for a Student Portal: Features and Capabilities, Lecture notes of Computer science

The functional requirements for a student portal, including login, timetables, upcoming holidays, news bulletin and announcements, certificate requests, mess information, assignments, exam schedules, feedback/complaints, fee receipt generation, monthly menu and timings, results, mess rebate, course registration, and help. The portal aims to provide convenience, efficiency, and better adjustment for students.

Typology: Lecture notes

2019/2020

Uploaded on 12/19/2021

recon-wein
recon-wein 🇮🇳

1 document

1 / 28

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SOFTWARE REQUIREMENTS
SPECIFICATION
for
College Management System
Release 1.1
Prepared by Team 3
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c

Partial preview of the text

Download Functional Requirements for a Student Portal: Features and Capabilities and more Lecture notes Computer science in PDF only on Docsity!

SOFTWARE REQUIREMENTS

SPECIFICATION

for

College Management System

Release 1.

Prepared by Team 3

Contents

  • 1 Introduction
    • 1.1 Purpose
    • 1.2 Project Scope and Product Features
    • 1.3 Intended Audience and Document Overview
    • 1.4 Definations, Acronyms, and Abbreviations
      • 1.4.1 Definations
      • 1.4.2 Acronyms, and Abbreviations
    • 1.5 References
  • 2 Overall Description
    • 2.1 Product Perspective
    • 2.2 User Classes and Characteristics
    • 2.3 Constraints
    • 2.4 Assumptions and Dependencies
  • 3 Specific Requirements
    • 3.1 External Interfaces
    • 3.2 Functional Requirements
      • 3.2.1 User Class one - Student
      • 3.2.2 User Class two - Administrative head(Super user)
      • 3.2.3 User Class three - Faculty
      • 3.2.4 User Class four - HEC head
      • 3.2.5 User Class Mess committee head- Student
    • 3.3 Non Functional Requirements
      • 3.3.1 Performance Requirements
      • 3.3.2 Reliability
      • 3.3.3 Availability
      • 3.3.4 Security Requirements
  • 4 Supporting information
    • 4.1 upadate

1 Introduction

The title of the project is COLLEGE MANAGEMENT SYSTEM (CMS). CMS is an Internet based application that aims at providing information to all the levels of management within an organization. This system can be used as a information management system for the college.

For a given user, the administrator will create a loginid & password, using this user can access the system to either upload or download some information from the database.

The front-end will be HTML pages with Java Script for client side validation where as all business logics will be in PHP reside at middle layer. And these layers will interact with third layer of database, which will be MySql database. The web server will be Apache. To start working on this project environment required is a server having Apache as web server, MySql as database and XAMPP as development environment

1.1 Purpose

The purpose of this document is to present a detailed description of the College Management System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the client and the developers of the system and will be proposed to the Administrative head for its approval.

1.2 Project Scope and Product Features

This software system will be a College management system for a the members of an organization. This system will be designed to maximize the administrative, academic and overall productiv- ity by providing tools to assist in automating the technical procedures and proccesses, which would otherwise have to be performed manually. By maximizing the users work efficiency and production the system will meet the users needs while remaining easy to understand and use. It is a user-friendly portal to interact, manage, access the information.

1.3 Intended Audience and Document Overview

There are different types of intented audience for this document, such as developers, testers, documentation writers and most importantly the users.We have divided the rest of the docu- ment into different subsections. We suggest that you begin with understanding the definitions, acronyms and abbreviations, then sequentially go through contents, overview section and pro- ceeding through the detailed description sections that is most pertinent.

1.4 Definations, Acronyms, and Abbreviations

1.4.1 Definations

  • Browser : Software used to view hypertext documents. Internet Explorer and Netscape Navigator are examples of browsers.
  • HTML : Hypertext Markup Language is a specification for graphical layout of a document. The specification calls for the document to be stored as text containing a series of tags that contain formatting information
  • PHP : Server side scripting language.
  • JavaScript : is a high level, dynamic, untyped, and interpreted programming language.
  • MySQL : MySQL is an open-source relational database management system.
  • standalone application : A Software that is not a part of some bundled software. A program that is run as a separate computer process, not an add-on of an existing process. Standalone program, a program that does not require operating system’s services to run. A portable application, which can be run without the need for installation procedure.
  • Web Portal : A web portal is most often one specially designed web page that brings information together from diverse sources in a uniform way.
  • Data Integrity : Data integrity refers to maintaining and assuring the accuracy and consistency of data over its entire life-cycle, and is a critical aspect to the design, imple- mentation and usage of any system which stores, processes, or retrieves data.

1.4.2 Acronyms, and Abbreviations

Table: 1 lists the acronyms and abbreviations used in this document with respect to CMS.

Acronyms Meaning AJAX Asynchronous Java-Script and XML API Application Programming Interface XML Extensible Markup Language DBMS Database Management System IEEE Institute of Electrical and Electronics Engineers kbps Kilo-Byte Per Second HTML Hypertext Markup Language CSS Cascading Style Sheets GUI Graphical User Interface mbps Mega-Byte Per Second OS Operating System RAM Random Acess System SDLC Software Development Life Cycle URL Universal Resource Locator

2 Overall Description

2.1 Product Perspective

The product will be a standalone application and may be run on multiple systems within an Internet network. The product will require a keyboard, mouse and monitor to interface with the users. The minimum hardware requirements for the product are specified in this document

2.2 User Classes and Characteristics

The target audience for CMS product is the college Administrator/students/faculty/staff (Technical/Non- technical) .The users for this system are

  • Administrator The Super user of the system. Mainly focuses on administratiive and academic related issues.
  • Student A user with limited access rights.
  • Staff A user of the system who has more access rights than a normal user.
  • Users for specific task.
    • Warden/HEC head: For Hostel management
    • Mess Committee Head: For mess

2.3 Constraints

The current constraints on the project are related to the provision of hardware resources and software resources.

  • At present, we have a i3 gen4 intel core processor running on top of the Linux/windows operating system.
  • The documents will be present only in pdf format.
  • In the feedback forms, the replies will not be frequent and the petitioner will not be anonymous.
  • There will not be any moderater to filter out the fake complains with the genuine ones. The superuser have to do it himself manually.
  • The Internet connection is also a constraint for the application. Since the application fetches data from the database over the Internet, it is crucial that there is an Internet connection for the application to function.
  • The web portal will be constrained by the capacity of the database. Since the database may be forced to queue incoming requests and therefor increase the time it takes to fetch data.
  • Mess Rebate Will at least of 3days.
  • Registration will be open for short time.
  • All Document should be in .Zip file.
  • College will provide funds for SMS service if SMS service is not free.
  • After submitting the course evaluation form, the user cannot revert his or her actions.
  • The user cannot change his/her all personal or academic details. He/she first have to get permission from the super user to do so.

2.4 Assumptions and Dependencies

A number of factors that may affect the requirements specified in the SRS include:

  • It is assumed that only one person from the different department will have the access to a module.i.e. Only heads of administration, academics, HEC and Mess will have the access to their department except the faculty.
  • The complaints and the feedback given by the students and other members of the organi- zation are assumed to be reliable.
  • The schedule for the exam , the registration window will be open for only few days only after that these pages will be inactive until next exams or registration period.
  • Apportioning of requirements In the case that the project is delayed, there are some requirements that could be trans- ferred to the next version of the application. Those requirements are to be developed in the third release.

3.2 Functional Requirements

This section includes the requirements that specify all the fundamental actions of the software system

3.2.1 User Class one - Student

3.2.1.1 Functional Requirement

ID:FR TITLE:Login into the Portal. DESC: The user can login into the system by providing its loginid and password to the portal which are unique and provided by the college. RAT:To login into the portal and take advantage of the services provided by it. DEP:None

3.2.1.2 Functional Requirement

ID:FR TITLE:Change password DESC:Change the password after logging into the system.The user will be asked a security question if he/she forgets his/her password. In case, he/she is unable to do so, the user has to formally apply to the admin for the change of his/her password providing the necessary proof. RAT:For security purposes, the user can choose his/her password DEP:FR

3.2.1.3 Functional Requirement

ID:FR TITLE:View/change profile details. DESC:The user can view or change some of his/her personal details like email id, contact details and address details. The profile will contain name, age,permanent address, parent’s name, their address, their contact details, branch, year, semester, room alloted, hostel name and no. etc. RAT:To update his/her profile and know his or her status. DEP:FR

3.2.1.4 Functional Requirement

ID:FR TITLE:Help DESC: Can get help through the help option which gives information about the different fea- tures provided by the system. A copy of user manual will also be provided in this section. RAT:In case of any confusion, the user can solve the problem easily and better understand the functionality of the system. DEP:FR

3.2.1.5 Functional Requirement

ID:FR TITLE:Timetables DESC:The user can view timetable for classes, mess and buses on the front page of the portal after logging into the system. RAT:By geting this information, user can schedule his routine and better utilize his/her precious time. DEP:FR

3.2.1 6 Functional Requirement

ID:FR TITLE:List of upcoming holidays DESC:The user can view the list on upcoming holidays on the front page of the portal after logging into the system. RAT:He/she could plan for vacations and other co-curricular activites. DEP:FR

3.2.1.7 Functional Requirement

ID:FR TITLE:News bulletin and Announcements. DESC:On the front page , the user can view different news and announcements from various departments. RAT:The user gets updated about the college and knows whats going on in the college. DEP:FR

3.2.1.8 Functional Requirement

ID:FR TITLE:Academics DESC:This module on dashboard contains all the information about the academics and admin- istration. RAT:You can get all the information about academics after getting inside this module. DEP:FR

3.2.1.9 Functional Requirement

ID:FR TITLE:Request for certificates DESC:The user can request for different types of certificates like No Objection Certificate, Char- acter Certificate, Address Proof for Hostel etc. After filling the given format , the request will be send to the administrative department for verification of request. After the verification, the user can get his/her certificate.

3.2.1.14 Functional Requirement

ID:FR TITLE:Exam Schedule DESC:The user can view the exam schedule. RAT:By using this feature,the user can prepare and plan his efforts in a better way. DEP:FR1,FR

3.2.1.15 Functional Requirement

ID:FR TITLE:Feedback/Complains DESC: In this form, one can lodge a complaint or give a feedback by selecting the domain: Aca- demics, Administration, Hostel, Mess, Transportation.The head of each department will give response accordingly. RAT:The user can get relieve from his/her problems without much effort or conflicts. DEP:FR

3.2.1.16 Functional Requirement

ID:FR TITLE:Fee Receipt Generation DESC: Student can generate fee receipt by giving the bank details in the system authenticated by the administrative head for the current and the previous semesters. RAT:This feature makes the process move convinient,fast and less cumbersome. DEP:FR1,FR

3.2.1.17 Functional Requirement

ID:FR TITLE:Monthly menu and timings DESC:The user can view the monthly menu and timings of mess(breakfast,lunch,snacks and dinner). RAT:It helps the user to better adjust with the mess routine. DEP:FR1,FR

3.2.1.18 Functional Requirement

ID:FR TITLE:Result DESC: Student can access their results of past semester and generate a pdf file and print by logging into the portal. The user can not view results of other students. RAT:The user can easily keep track of his/her academic performance. DEP:FR1,FR

3.2.1.19 Functional Requirement

ID:FR TITLE:Mess Rebate DESC:The user can request for his/her mess rebate by formally applying providing a valid rea- son and the period of his abscence. After the verification of his request, the mess committee will either accept or deny the request and the user will be informed accordingly. The system will keep track of the days the rebate request was succesfully accepted. RAT:The user can easily get rebate from mess and can also keeps track of his rebate request. DEP:FR1,FR

3.2.1.20 Functional Requirement

ID:FR TITLE:Course Registration DESC:Here, the user can register for the courses at the start of the semester. This page will be open for a very short time interval. The user has to provide all the necessary details and select the electives for the semester. RAT:The user can easily register for the semester without cumbersome paperwork. DEP:FR1,FR

3.2.2 User Class two - Administrative head(Super user)

3.2.2.1 Functional Requirement

ID:FR TITLE:Login into the Portal. DESC: The user can login into the system by providing its loginid and password to the portal which are unique and provided by the college. RAT:To login into the portal and take advantage of the services provided by it. DEP:None

3.2.2.2 Functional Requirement

ID:FR TITLE:Change password DESC:Change the password after logging into the system.The user can also change the password for other users if requested. If he/she forgets his/her password. RAT:For security purposes, the user can choose his/her password. DEP:FR

3.2.2.3 Functional Requirement

ID:FR TITLE:View/change profile details. DESC:The user can view or change some of his/her personal details like email id, contact details

DEP:FR

3.2.2.8 Functional Requirement

ID:FR TITLE:Academics DESC:This module on dashboard contains all the information about the academics and admin- istration. RAT:You can get all the information about academics after getting inside this module. DEP:FR

3.2.2.9 Functional Requirement

ID:FR TITLE:Course Registration DESC:Here, the user can register for the courses at the start of the semester. This page will be open for a very short time interval. The user has to provide all the necessary details and select the electives for the semester. RAT:The user can easily register for the semester without cumbersome paperwork. DEP:FR21,FR

3.2.2.10 Functional Requirement

ID:FR TITLE:Request for certificates DESC:The user attends the request for certificates like No Objection Certificate, Character Certificate, Address Proof for Hostel etc.The administrative department verifies request and accordingly accepts or denies the request and procedes subsequently. RAT:This feature makes the process move convinient,fast and less cumbersome. DEP:FR21,FR

3.2.2.11 Functional Requirement

ID:FR TITLE:Faculty DESC:This module provides the information about the faculties. This includes name, education details, areas of interest and expertise, email id and contact details(optional). RAT:You can get all the information about faculties in one place after getting inside this mod- ule. DEP:FR21,FR

3.2.2.12 Functional Requirement

ID:FR TITLE:Assignments and reading references DESC:The user can download the reading and writing assignments uploaded by the faculty for their course. RAT:The user will have a remote access to the assignments. DEP:FR21,FR

3.2.2.13 Functional Requirement

ID:FR TITLE:Course Evaluation DESC:: At the end of the semester, a new page will be available for evaluation of a particular course for the students. The user prepares the format for the course evaluation and decides the window when the users can give their feedback. He also evaluates all the evaluations. RAT:This helps faculties to get a feedback for their course and improve their performance by introspecting and also it helps the administration in better allocation of the faculty. DEP:FR21,FR

3.2.2.14 Functional Requirement

ID:FR TITLE:Exam Schedule DESC:The user can view the exam schedule. The user have the right to update/ modify the exam schedule by either automatically generating the timetable by providing the required details or manually filling the blanks. RAT:By using this feature,the user can prepares a perfect timetable without any conflicts.It is very time efficient. DEP:FR21,FR

3.2.2.15 Functional Requirement

ID:FR TITLE:Feedback/Complains DESC: In this form, one can lodge a complaint or give a feedback by selecting the domain: Academics, Administration, Hostel, Mess, Transportation.The user deals with the complains and feedback in the field of academics and administration. RAT:The user can get relieve from his/her problems without much effort or conflicts. DEP:FR

3.2.2.16 Functional Requirement

ID:FR TITLE:Fee Receipt Generation

3.2.3 User Class three - Faculty

3.2.3.1 Functional Requirement

ID:FR TITLE:Login into the Portal. DESC: The user can login into the system by providing its loginid and password to the portal which are unique and provided by the college. RAT:To login into the portal and take advantage of the services provided by it. DEP:None

3.2.3.2 Functional Requirement

ID:FR TITLE:Change password DESC:Change the password after logging into the system.The user will be asked a security question if he/she forgets his/her password. In case, he/she is unable to do so, the user has to formally apply to the admin for the change of his/her password providing the necessary proof. RAT:For security purposes, the user can choose his/her password DEP:FR

3.2.3.3 Functional Requirement

ID:FR TITLE:View/change profile details. DESC:The user can view or change some of his/her personal details like email id, contact details and address details. The profile will contain name, age,permanent address, parent’s name, their address, their contact details, branch, year, semester, room alloted, hostel name and no. etc. RAT:To update his/her profile and know his or her status. DEP:FR

3.2.3.4 Functional Requirement

ID:FR TITLE:Help DESC: Can get help through the help option which gives information about the different fea- tures provided by the system. A copy of user manual will also be provided in this section. RAT:In case of any confusion, the user can solve the problem easily and better understand the functionality of the system. DEP:FR

3.2.3.5 Functional Requirement

ID:FR TITLE:Timetables DESC:The user can view timetable for classes, mess and buses on the front page of the portal

after logging into the system. RAT:By geting this information, user can schedule his routine and better utilize his/her precious time. DEP:FR

3.2.3.6 Functional Requirement

ID:FR TITLE:List of upcoming holidays DESC:The user can view the list on upcoming holidays on the front page of the portal after logging into the system. RAT:He/she could plan for vacations and other co-curricular activites. DEP:FR

3.2.3.7 Functional Requirement

ID:FR TITLE:News bulletin and Announcements. DESC:On the front page , the user can view different news and announcements from various departments. RAT:The user gets updated about the college and knows whats going on in the college. DEP:FR

3.2.3.8 Functional Requirement

ID:FR TITLE:Academics DESC:This module on dashboard contains all the information about the academics and admin- istration. RAT:You can get all the information about academics after getting inside this module. DEP:FR

3.2.3.9 Functional Requirement

ID:FR TITLE:Faculty DESC:This module provides the information about the faculties. This includes name, education details, areas of interest and expertise, email id and contact details(optional). RAT:You can get all the information about faculties in one place after getting inside this mod- ule. DEP:FR42,FR