Software requirement specification

Version 1.0
21.1.2015

Sangamamkanini e-learning
Author: M.Shankar
Reg.No: 211612621026,
Guide: Mrs.R.S.Nisha
Rajalakshmi engineering college, Chennai.

Abstract:
The project is Sangamamkanini e-learning. The project is intended to improve
the teaching and learning capabilities of teachers and students in schools. The project goal is to
improve the teaching practices in schools by using technologies (Internet). The intention of the
project is to propose a new way education practices in schools not only in teaching and learning
but also in taking tests and exams.
The studying, learning, tests and exams all the academic activities can be done
using this product. All the academic activities can be controlled by the DPI at once like
distributing study materials, conducting tests and exams.
The study materials text books, study materials provided by khans academy,
wipro will also be provided to improve the teaching practices. The study materials can be
anything like PDFs, videos, audios and so on. Many teachers struggle to complete their portions
within the stipulated time, so a lesson plan will also be provided.
The students can be able to access the study materials related to not only their
standard level but also to all the standard level. Students can take up the online tests after the
completion of each lesson; students can also take up their exams also on online. Teachers
performance evaluation test will also be conducted to evaluate the teachers skills.
The activities of students and teachers in the web site will monitor and stored in
the database. Teachers and DPI staffs are given access to view the student activities. DPI staffs
are given access to view the teachers activities.

Table

of

SNO
1
1.1
1.2
1.3
1.4
1.5
2
2.1
2.2
2.3
2.4
2.5
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.1.1
3.2.1.2
3.2.2
3.2.2.1
3.2.3
3.2.3.1
3.3
3.3.1
3.3.2
3.3.3
3.3.4

Contents
Introduction
Purpose
Scope
Definitions, acronyms
and abbreviations
Reference
Overview
Overall description
Product perspective
Product functions
User characteristics
General constraints
Assumption
and
dependencies
Specific requirements
External
interface
requirement
Hardware interface
Communication
interface
Functional
requirements
User class : Admin
Functional
requirement 1.1
Functional
requirement 1.2
User class : Admin
Functional
requirement 2.1
User class : None
Functional
requirement 3.1
Non-Functional
requirement
User
interface
requirement
Performance
requirement
Availability
requirement
Security requirement

Pageno
5
5
5
5

contents:

6
6
6
6
7
8
8
8
8
8
8
9
9
9
9
10
11
11
12
12
13
13
13
13
13

SOFTWARE REQUIREMENT SPECIFICATION

1. Introduction
This section will describe the purpose and scope of this document. This section will also
specify the definition, acronyms; abbreviations used in this document and also mentioned the
references to prepare this document.

1.1. Purpose:The purpose of this document is to summarize the functional and non-functional
requirements of the Sangamamkanini e-learning. This document will be a reference for the
first version of the product. This document will also specify the constraints and external
interfaces with which our product will interact.

1.2.SCOPE:The Sangamamkanini e-learning is a web based application which intends to

improve the teaching and learning practices in the schools. The teaching capabilities will be
improved by providing a lesson plan to the teachers and also by providing appropriate study
materials in addition to usual text books. Each lesson will have study materials and a guide to
how to teach each lesson.
The students learning ability can be improved by providing various study
materials types like teaching material and worksheets which helps to improve the eagerness of
students towards the subjects. Students are facilitated to take up online test using the worksheets
provided. Each and every students assessment marks will be calculated and monitored.
The usage of study materials will be monitored and reported accordingly.

1.3.Definition,Acronyms,Abbreviations: Admin DPI staff.

Teacher One of the users who use this app to teach the students.
Student One of the users who uses this app for studying and to take up online
test.
Headmaster One of the user of this app for checking the students and teachers
marks and log details.

1.4. Reference: http://elf.cs.pub.ro/mps/wiki/_media/laboratoare/srs-sample.pdf

http://www.cse.chalmers.se/~feldt/courses/reqeng/examples/srs_exam
ple_2010_group2.pdf
1.5 Overview:
The rest of the document contains two major sections: overall description and specific
requirements. Overall description will describes about product perspectives, product functions,
user characteristics, general constraints, assumptions and dependencies.
The specific requirements will describe about the function and non-functional
requirements of the product.

2. OVERALL DESCRIPTION
2.1. Product perspectives:The project will be developed in several dimensions for the functionalities of DPI
staffs, teachers and students. Each user has their own functionalities. DPI staffs activities are
related to admin level activities. Teachers and student level activities are almost similar like
accessing study materials and taking tests.

2.2 Product Functions: The product will let the admin to maintain user accounts, to map contents to the lessons
and it will publish the contents.
The product will the let teachers and students to access the study materials, lesson plans
and worksheets. Teachers and students can take up their test.
The product will monitor the study materials usage and stores the usage data in the
database.
The product will schedules the tests and exams for students and teachers, monitors their
activities, calculates marks and stored in the centralized database.
This product will help teachers to monitor the students academic activities.

2.3 Functional requirement specification:

This section outlines use cases of admin, teachers and students.

2.3.1 Admin use case:

Use case: Create user account
Diagram:

Admin

Creates user account

Stores the user details

Server
Notifies admin

Brief description:
This module will let admin to create user account.
Initial step-by-step:
Admin will visit the registration page.
Admin will provide the necessary details to create user accounts and submits.
For students first name, middle name, last name, class and medium should be provided.
For teachers first name, middle name, last name, classes and medium the respective
teacher is handling should be provided.
For students and teachers unique ID will be generated using which the students and
teachers will be identified.
User details will be stored in the database and user account will be created.
6

 Admin will be notified.

Use case: Document upload
Diagram:

Admin

Uploads documents

Stores the documents in database

Server

Notifies Admin

Brief description:
This module will let admin to store the study materials in the database.
Initial step-by-step:
Admin will navigate to the document storing web page.
Where admin will browse to the document and clicks store button.
The document will be stored in the database.
Use case: Question set preparation.
Diagram:

Admin

Submits questions

Stores the question

Server
Notifies admin

Brief description:
This module will let admin to store the study materials in the database.
Initial step-by-step:
Admin will visit the question submission web page.
Where in the text area admin will type the questions.
In the four texts area below admin will type the choices.
In the last text area admin will provide the right answers and clicks Submits.
The question with choices and right answer will be stored in the database.
The question set preparation will be done separately for students and teachers.
To prepare question sets a group of members should be given access to prepare questions
at the specified time.
The access will be revoked once the job is done.
Use case: Admin log & mark enquiry
Diagram:

Request log details of teachers

and students
Admin

Request marks of students and

teachers

Provides log details of teachers

and students

Server
Provides marks of teachers and
students

Brief description:
Admin requests to view the log details and marks of the students and teachers.
Initial step-by-step description:
The admin will visit the log details web page to view the log details.
The admin will enter the ID of the person whose log details and marks admin wants to
check.
While checking the log details by default user can see the last one month details of log
entries. User can change the dates range.
While checking the student marks recent result will be provided. Admin can select the
specific test or exam to the appropriate results.
Server will provide the log details and it will be provided in the tabular format.
Use case: Content mapping
Diagram:

Map contents

Admin

Mapped content details will be

stored

Server
Admin will be notified

Brief description:
Admin will map the contents to the lessons and classes.
Initial step-by-step description:
Before this use case can be initiated the author has established internet connection.
Admin will select a subject, medium, class, lesson, and then admin can browse to the url
of the contents.
The mapped content details will be stored in the database.

2.3.2 Teacher use case:

Use case: Class room app of teacher
Diagram:

10

Requests login

Access study materials

Access lesson plan

Takes up test

Checks marks
Teacher

Views marks of the students

Checks log details

Validates login

Grant access to study materials

and lesson plan

Monitors all the activities of

teachers while take up the test

Calculates & stores the marks

Server
Shows the marks

Provides marks of the students

Provides log details

11

Brief description:
Teachers can login into their account; they can able to access the study materials, lesson
plan and marks of the students.
Initial step-by-step:
Before this use case can be initiated the teacher has established internet connection.
Teachers will login into their account using their username and password.
Teacher can access the study materials by navigating the class, subject, medium and
lessons.
Teacher can access the lesson plan by navigating the class, subject, medium and lessons.
While taking the test the tab for test will be enabled for teachers.
Teachers will navigate to the test page and they will take their test.
While teachers take up the test their activities will be monitored, marks will be calculated
and stored.

2.3.3 Student Use case:

Use case: Class room app of student
Diagram:

12

Request login

Access study materials

Student

Takes up test

Checks marks

Validates login

Grants access to study materials

Distributes worksheets to take up

the test

Monitors student activites while

take up the test
Server
Calculates and stores the marks

Shows marks

Brief description:

13

Teachers can login into their account; they can able to access the study materials, they
can able to take up the tests using worksheets and they can able to check their assessment marks.
Initial step-by-step:
Before this use case can be initiated the teacher has established internet connection.
Students will login into their account using their username and password.
Students can access the study materials by navigating the class, subject, medium and
lessons.
While taking the test the tab for test will be enabled for students.
Students will navigate to the test and exam page and they will take their test.
While student takes up the test their activities will be monitored, marks will be calculated
and stored.

2.3.3 Head master Use case:

Use case: Headmaster log & mark enquiry
Diagram:

14

Request log details of teachers

and students
Headmaster

Request marks of students and

teachers

Provides log details of teachers

and students

Server
Provides marks of teachers and
students

Brief description:
Headmaster requests to view the log details and marks of the students and teachers.
Initial step-by-step description:
The headmaster will visit the log details web page to view the log details.
The headmaster will enter the ID of the person whose log details and marks admin wants
to check.
While checking the log details by default user can see the last one month details of log
entries. User can change the dates range.
While checking the student marks recent result will be provided. Admin can select the
specific test or exam to the appropriate results.
Server will provide the log details and it will be provided in the tabular format.

2.4. User Characteristics:15

There are four types of users of this system, admin, teachers and students.
1. Admin is responsible to map the content and publish it to be used in the schools.
He/she is responsible to maintain account for schools, teachers and class rooms.
Admin can also able to view the statistics graphs about the content usage.
2. Head masters will check the marks of the students and teachers and their log
details.
3. Teacher will teach the students by accessing the study materials and lesson plan.
Teacher will also check the marks the students and their log details.
4. Students will study by accessing the study materials and also they will take their
test and exam.

2.5. General Constraints: Students and teachers will be authenticated by their username and password.
The contents will be mapped only by the admin.
Newly published contents should be reflected at the client side.

Teacher and student activities must be monitored and stored in the database. The
details must be provided whenever needed.

Students can only be able to view their marks only.

Admin, head masters and teachers can only be able to view the marks of all the
students.
Log details of students can be viewed by the corresponding subject teachers, class
teachers, head masters and admin.
Log details of teachers can be viewed by the head masters and admin.

Only admin and teacher can able to view the activities of students in the web site.
Class teachers only can able to view the marks and activities of students related to all
the subjects. Others teachers can only be able to view the marks of their subjects and
the activities related to their subjects.

Admin only can able to view the all the teachers marks and their activities on site.
16

2.6. Assumption and Dependencies: All the schools will have internet access with facilities like webcam, projectors, and
speakers and so on.

3. SPECIFIC REQUIREMENTS
This section describes all the functional requirements and features of the system.

3.1. External Interface Requirements:3.1.1. Hardware Interface: OS Linux, windows

Hard disk 80 GB
RAM 1 GB
Keyboard Standard QWERTY keyboard for interface
Mouse Standard mouse with 2 buttons

3.1.2. Communication Interface: Internet.

3.2. Functional Requirements:This section will list out the functional requirements of the product.

3.2.1 User class : Admin

3.2.1.1 Functional requirement 1.1
Title:Document uploads
Use case:Document uploads
Description:
This module will let admin to upload the documents in the server.
Precondition:
The study materials must be collected and organized.
17

Basic path:
Admin will navigate to the document storing web page.
Where admin will browse to the document and clicks store button.
The document will be stored in the database.

Post condition:
Document will be stored in the database.
Admin will be notified.

3.2.1.2 Functional requirement 1.2

Title: Content mapping
Use case: Content mapping
Description:
The content map app will provide both the mapped and unmapped contents.
The content map app will let admin to map the contents to the appropriate lessons
corresponding to a particular class.
The content map app will provide unmapped contents so that admin will map that content
to a lesson.
The mapped contents can be unmapped later if it is considered to be invalid.
The content mapped details will be stored in a database.
Precondition:
The contents must be available.
Basic path:
Admin will select the appropriate content to map to the lessons of the particular subject.
Admin can unmap the already mapped contents.
Exception path:

18

 Trying to map or unmap the already mapped or unmapped contents of same lesson
corresponding to a class, subject and medium.
Post condition:
The mapped details will be stored in a database.
If a mapped content is unmapped it will be reflected in the database accordingly.
The mapped content will be provided along with the existing study materials accordingly.

3.2.1.3 Functional requirement 1.3

Title: Create user account
Use case: Create user account
Description:
This module will let admin to create user account.
Precondition:
Usage data must be collected and stored in the database.
Basic path:
Admin will visit the registration page.
Admin will provide the necessary details to create user accounts and submits.
For teachers following details will be collected first name, middle name, last name, DOB,
school, classes and medium. Each teacher may take more than one class for several
subjects. Those details will also be collected.
For students following details will be collected first name, middle name, last name, DOB,
school, class and medium.
Whenever account for a class has been created details about the teachers, class teachers
and head masters will also be collected.
An unique ID will be generated for students, teachers and head masters.
Exception path:
Admin missed out any fields as blank.

19

Post condition:
User details will be stored in the database and user account will be created.
Admin will be notified.

3.2.1.4 Functional requirement 1.4

Title: Question submission
Use case: Question set preparation
Description:
This module will let DPI staffs to prepare the questions and uploads it to the server.
Precondition:
Separate user account must be created for teachers to prepare and submit questions.
Basic path:
DPI must grant access to the teachers who are all preparing questions.
User will be logged into their account.
They will type the question; provide choice and the right answers.
Exception path:
Invalid user tries to login.

3.2.1.5 Functional requirement 1.5

Title: View log details
Use case: Log enquiry_admin
Description:
This module will let admin to view the log details of each student and teachers
Precondition:
Usage data must be collected and stored in the database.
Basic path:

20

 Student or teacher id will be given as input.

Last one month student activities will be displayed in a table date wise.
Alternate path:
Dates range can be altered to view the student activities.
Exception path:
Entering invalid student id.

3.2.2 User class : Teachers and students

3.2.2.1 Functional requirement 2.1
Title: Class room app
Use case:Class room app of teachers and class room app of students.
Description:
This application will be used by the teachers and students in the class rooms for teaching
and studying.
This app will validate user login.
If the user is student, it will grant access to study materials, worksheets and their test and
examination marks.
If the user is teacher, it will grant access to study materials, lesson plans test and
examination marks of students and their activities on the site.
When the student or teacher opens a study material the following details: student or
teacher id, study material id, date, open time and closing time will be sending to the
usage data manager.
It will distribute worksheets among students and teachers to take up online test and stores
the test and examination marks.
Precondition:
User accounts must be created.
Questions must be prepared and available in the database.
21

 Internet connection must be established.

The updated contents must be reflected and available to be used by the schools.
Basic path:
Teacher or student will login into their account using their username and password.
Teacher or student can navigate to access the study materials, lesson plans, worksheets
and marks of students.
While take up the test activities of the students and teachers will be monitored, marks will
be calculated and stored.
Exception path:
Unregistered user may try to login.
Post condition:
After successful login appropriate access should be granted to the users.
The online test for the students must be monitored, evaluated and their marks must be
stored.
Usage data will be uploaded to the usage data manager.

3.2.2.2 Functional requirement 2.2

Title: View log details
Use case: Class room app of teacher and class room app of student.
Description:
This module will let teachers to view the activities of each student.
This module will let the admin and head master to view the activities of each student and
teacher.
Precondition:
Usage data must be collected and stored in the database.
Basic path:
Student or teacher id will be given as input.
22

 Last one month student activities will be displayed in a table date wise.
Alternate path:
Dates range can be altered to view the student activities.
Exception path:
Entering invalid student id.

3.2.3 User class : Head master

3.2.3.1 Functional requirement 3.1
Title: View log details
Use case: Class room app of teacher and class room app of student.
Description:
This module will let head master to view the activities of each students and teachers
Precondition:
Usage data must be collected and stored in the database.
Basic path:
Student or teacher id will be given as input.
Last one month student activities will be displayed in a table date wise.
Alternate path:
Dates range can be altered to view the student activities.
Exception path:
Entering invalid student id.

3.2.4 User class : None

23

3.2.4.1 Functional requirement 4.1

Title: Usage data manager
Description:
This module will store the usage data in the database.
Whenever a teacher or student clicks opens a study material, the details user id, study
material id, date, open time and closing time will be stored in the database..
Precondition:
Data must be received from the class room app by passing the data as URL parameters.
Database connection must be established.
Basic path:
Class room app will be redirected to the usage data manager whenever a student or
teacher closing an opened study material.
While redirecting the data will be received as the URL parameter.
Post condition:
Data will be stored in the database.
Database connection must be closed.

3.3 Non-Functional requirements:

This section will describe about the non-functional requirements of the system.

3.3.1User interface requirements:

The user interface must be designed in a manner easy to be used by the users.

3.3.2 Performance requirements:

The performance of the system will differ based on the network speed and connection.

3.3.3 Security requirements:

To access the study materials user must be logged into their account.
24

 The data in the database will be accessed only by the authorized persons.

3.3.4. Software attributes:

3.3.4.1 Availability:
The system will provide 24X7 services.

25