Specification
for
Prepared by
Group Member
Date:
Contents
Software Requirements Specification for mentor and mentee management system
Table of Contents
Table of Contents ...........................................................................................................................2
Revision History .............................................................................................................................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 ........................................................................................................................................ 2
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 Use case for Mentor and Mentees ...................................................Error! Bookmark not defined.
4.2 Entity Relationship Diagram...........................................................Error! Bookmark not defined.
4.3 Activity Diagram………………………………………………………………………….4
5. Functional Requirements
5.1 Functional Requirements for Mentor
5.2 Functional Requirements for Mentees
6. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.
6.1 Performance Requirements .............................................................Error! Bookmark not defined.
6.2 Safety Requirements .......................................................................Error! Bookmark not defined.
6.3 Security Requirements ....................................................................Error! Bookmark not defined.
6.4 Software Quality Attributes ............................................................Error! Bookmark not defined.
6.5 Business Rules ................................................................................Error! Bookmark not defined.
7. 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.
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for mentor and mentee management system
1 Introduction
Mentor and Mentee management system has become important factors in modern education field.
This system helps the institutional to streamline the administrator task and provides real-time access to
the data. Building this system in web based interface will further help the ease of accessibility through
any web browser. The study finding enable the definition of the project problem statement ,its objectives
,scope and advantages of the mentor and mentee management system .
1.1 Purpose
The purpose this document is to present a detailed description of the Mentor and Mentee Management
System. It will explain the purpose and features of the software. The document not only define the system
functions, user characteristics, constraints, and specific requirement of the system,, but also serve as a
basic for the software Design Document that is prepared according to IEEE std. This document is
intended for both the end user and the developers of the system.
To maintain/process complete details of students and mentors about their personal, academic,
internship and placements domain.
To enable students and mentors to view their details any time from anywhere. No need to meet
professors personally.
To enable mentors to verify theirs mentees details and send approval of entered data.
To maintain information of the passed out students.
1.5 References
nvlpubs.nist.gov/nistpubs/sp958-lide/250-253.pdf
http://www.aaronmiller.in/thesis/
http://www.tutorialspoint.com/software_engineering/software_design_basics.htm
http://www.geeksforgeeks.org/greedy-algorithms-set-3-huffman-coding/
Minqing Hu and Bing Liu 2004, American Association for Artificial Intelligence
(www.aaai.org). “Mining Opinion Features in Customer Reviews.”
Software Requirements Specification for mentor and mentee management system
2 Overall Description
2.1 Product Perspective
The Mentor and Mentee Management System, is an independent product and does not depend on any
other product or system. The system will automate various tasks associated with handling student details
and better organizing the stored information and optimum performance, thus helping the college to unsure
smooth working of these processes.
1. Administrator
2. User
2.1 Mentor
2.2 Mentee
i. Administrator
This system is managed by Administrator has to update and monitor the registered Mentor and
Mentees details , add new Mentor and Mentees, provide register number for all students, etc.
Administrator can update databases as per requirements and also can give help to the mentors
and mentees. Facilitate the maintenance of the important records of the students and mentors.
ii. User :
There are two users:
a. Mentor :
Mentor can see the mentees detail related to mentees academic, Exams, Internships
,attendance and placement related data. Once the mentees upload their data on portal mentor
will check entered data and approve or disapprove the data. Mentor will also handle the
previously passed out mentees data. To keep track of improvement. Decline in the
performance of the mentees.
b. Mentee :
Mentees can add the their all required data related to Exams, Personal, Internship, placements
and attendance data and send for approval to the respective mentor .
The data is editable, mentees can change is whenever required. Mentees can access this data
anytime anywhere.
Software Requirements Specification for mentor and mentee management system
1. Administrator: the personnel and system administrator will have administrator access to add,
delete and modify information stored in the database.
2. Authorized User: Mentors will have access to only view the data stored in the database and
can update the mentees attendance in the form of formatted report. Mentees will have access to
the system to fill required details.
1. OS – Windows 7,8,10,XP
2. Visual Studio Code
3. HTML, CSS ,JavaScript, Bootstrap
4. MySQL for RDBMS on Xampp/Wampserver
5. For documentation : Microsoft Word
When invalid input are given to the module then the error message will be popped up in order to inform
the user that the input provided is not taken by the database. When incomplete information is provided by
the user and the user tries to submit the form in order to store the details in the database the system will
pop up a message box asking the user to enter all the details required.
4 System Features
4.1 Use Case for Mentor and Mentee
A use case diagram is a dynamic or behaviour diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases. Use cases are a set of actions, services, and
functions that the system needs to perform. In this context, a "system" is something being
developed or operated, such as a web site. The "actors" are people or entities operating under
defined roles within the system.
5 Functional Requirements
5.1 Functional Requirements for Mentor
Maintaining The Mentees Records: Mentor consist of number of students assign to each mentor .
Mentor has authority to see the mentees record filled by individual mentee. Mentor will keep
maintain this record and can generate report as per requirement. due to this mentor can track the
his/her mentees progress during whole year .
Verification of the Records: Mentor will have to verify all academic, placements,exams,
internship,etc .records filled by mentees and once after finishing of verification mentor can send
confirm verification to mentee or can suggest some changes also in the records.
Maintaining Attendance Sheet : This module meant to keep detail record of mentees throughout
the sessions . It include the attendance of mentees in regular classes ,lectures , seminars , practices
,etc.
Recording communications with students: It will help in providing student with updates on latest
notices. It will reduce the burden on management as well as of students in manually providing
notices of information.
Mentees Profile: The full information of each and every mentee must be maintained in System
along with the facility to regularly update it from time to time at regular intervals which will be
easily possible through each students unique registration number.
Creation of new Records : This module creates a new records for new student’s
Filling new All Related Academic Information : This phase will maintain information of mentees
performance track record. All the result of mentees including internal class test, unit test, mid
semester marks, session marks ,practical exams and final examination record will be kept. And
also other records like placement, internship,etc.
Software Requirements Specification for mentor and mentee management system
6 Non-functional Requirements
6.1 Performance Requirements
Easy tracking of records and updating can be done. All the requirements relating to performance
characteristics of the system are specified in the section below. There are two types of
requirements.
A. Static Requirements :
These requirements do not impose any constraints on the execution characteristics of the
system
1) Number of Terminals :
The system makes use of an underlying database that will reside at the server, while the
front end will be available online to the administrative and departmental computers as well
as students.
2) Number of Users :
The number of users may vary, as this system finds applications in almost all department
of the organization.
B. Dynamic Requirements :
These specify constraints on the execution characteristics of the system. They typically include
response time and throughout of the system, Since these factor are not applicable to the
proposed system. It will suffice if the response time is high and the transaction are carried out
precisely and quickly.
NIL
<Data dictionary is used to track all the different variables, states and functional requirements that you
described in your document. Make sure to include the complete list of all constants, state variables (and
their possible states), inputs and outputs in a table. In the table, include the description of these items as
well as all related operations and requirements.>
Software Requirements Specification for mentor and mentee management system